Subject RE: [firebird-support] Connection issues
Author seanspcpower IT Services

Please see text of the error message and Firebird log file below.

 

Database Error heading: A Database or connection error has occurred!

dmSecurity.LicenseDB:

Unsuccessful execution caused by a system error that precludes successful execution of subsequent statements.

Unable to complete network request to host “servername”

Failed to establish a connection.

Unknown Win32 error 10060.

 

Specified In: StartupID passed in command line (LIVE)

Specified Value: SERVER2:C:\Program Files (x86)\Ostendo\Database\LWH\Ostendo.fdb

 

Additional information from Development-X Web Site

 

Firebird service not started on server or the server you are pointing to does not have Firebird installed, The Firebird TCP port used (3050 default) maybe incorrect or blocked, check the server name when pinged comes back with the ip address you expect, if not your DNS maybe incorrect and maybe going to your isp.

Incorrect computer name or firebird tcp port (3050 default) specified, if computer name is correct make sure is resolves to correct ip address.

 

1.     I have preformed troubleshooting steps to resolve any port or network connection issue for Winsock error 10060 and I cannot see anything blocking the client workstation

2.     Firebird server – DefaultInstance service and Fibrebird guardian – DefaultInstance service are both running on the server

3.     I have stopped and restarted the services

4.     Ping tests both ways successful

5.     All other network access is working between the client and shared resources on the server

6.     Server is listening on port 3050 (netstat –a)

7.     Port 3050 is forwarded in the firewall

8.     Only change is the server received security updates for windows and .NET Framework 4.5.2 over the weekend and I have since removed these updates

9.     The Ostendo folder is shared and there are no restriction or permission issues

 

Firebird log:

 

WORKSHOP1 (Client)    Mon May 25 07:31:54 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 07:32:17 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 07:32:39 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 07:33:02 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 07:34:43 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 07:35:06 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 08:08:55 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 08:09:18 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 08:16:05 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 08:16:28 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 08:52:42 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 08:53:05 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 11:05:28 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 11:05:51 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 11:31:42 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 11:32:05 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 12:12:36 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 12:22:03 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Mon May 25 12:24:28 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Mon May 25 12:24:38 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Mon May 25 12:25:38 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Mon May 25 12:25:41 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Mon May 25 13:12:52 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 13:13:15 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 14:38:09 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 14:38:32 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 17:46:11 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 17:46:34 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 17:50:46 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 17:51:09 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 21:28:58 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 21:29:21 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 21:30:53 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 21:31:16 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 21:32:09 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 21:32:32 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 22:12:08 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Mon May 25 22:12:31 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 12:30:47 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 12:31:10 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 12:32:50 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 12:33:13 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:25:01 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:25:24 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:29:17 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:29:40 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:41:08 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:41:31 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:44:23 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:44:46 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:45:40 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 13:46:03 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 14:08:45 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 14:09:08 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 14:11:35 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 14:12:17 2015

            INET/inet_error: read errno = 10054

 

WORKSHOP1 (Client)    Tue May 26 14:12:17 2015

            INET/inet_error: send errno = 10054

 

WORKSHOP1 (Client)    Tue May 26 14:12:17 2015

            INET/inet_error: send errno = 10054

 

WORKSHOP1 (Client)    Tue May 26 14:12:17 2015

            INET/inet_error: send errno = 10054

 

WORKSHOP1 (Client)    Tue May 26 14:28:22 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 14:28:45 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 14:54:26 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 14:54:30 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 15:02:05 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 15:02:08 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 15:02:46 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 15:02:49 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 15:17:14 2015

            INET/inet_error: connect errno = 10060

 

WORKSHOP1 (Client)    Tue May 26 16:05:12 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Tue May 26 16:05:15 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Wed May 27 12:23:33 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Wed May 27 12:23:36 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Thu May 28 13:05:46 2015

            INET/inet_error: connect errno = 10061

 

WORKSHOP1 (Client)    Thu May 28 13:05:49 2015

            INET/inet_error: connect errno = 10061  

 

Sorry about the “signature guff” but I cannot see any way of replying to these posts on the web forum.

Perhaps they shouldn’t encourage people to create posts from an email client which may include signatures and guff.

 

Regards,

 

Sean Wright

 

From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Sent: Thursday, 28 May 2015 2:46 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Connection issues

 

 

At 01:25 p.m. 28/05/2015, 'seanspcpower IT Services' tech@... [firebird-supp wrote:

>The issue is lately the 1 client can no longer connect to the database using
>the client application.
>
>
>The application Ostendo and we have the Firebird database runs on an sbs2008
>box.
>
>It is a domain controller.
>Exchange server.
>DHCP
>DNS
>File and printer sharing.
>Vipre Business Premium console dashboard
>Vipre client runs on the server and the firewall policy is disabled.
>Windows firewall is running but I have ports 3050 and 9050 open.
>
>
>It was working fine until a few days ago.
>
>The user says he was using Friday ok and came in Monday morning and when he
>launches the ostendo client gets the following error (see attached).

You can't post attachments in this list. Report the error message and also check the latest entries in firebird.log.

>We spoke to Ostendo support and they said to just reinstall the client but
>that made no difference.

What "client" did you try to reinstall? My suspicion (and possibly theirs) is that someone installed something that overwrote the Firebird 1.5 client. Check again with Ostendo support. Ask them (1) where the application expects to find the Firebird client when running with a local user and (2) whether it expects to load fbclient.dll or gds32.dll.

>I am just understanding the error message not sure how to troubleshoot as I
>know nothing about Ostendo and Firebird databases.

Post the text of the error message and also paste the entries from firebird.log that correspond to the times of the failed connection attempts.

And please remove all that signature guff from your future postings to these lists.

Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net
__________________________________________________________