Re: SQLSTATE 08S03, SQLCODE -30060. -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: SQLSTATE 08S03, SQLCODE -30060.
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Tue, 14 Nov 2017 16:45:15 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 11/14/2017 4:10 PM, Alan Shore wrote:

and I have it working on our development box
I have just promoted everything to our production box - and when I attempt to connect to an external database, I receive

SQLSTATE 08S03, SQLCODE -30060.

08xxx are comms errors. The external database is listening on a
specific port. Make sure that port is open through the firewall /
network infrastructure.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: SQLSTATE 08S03, SQLCODE -30060. , Alan Shore

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.