At 03:09 PM 2/09/2005 +0000, you wrote:

>Hello:
>
>We have a client that is reporting that our application is locking up
>on start up. They told us that they have to restart the server that
>firebird is on to get our application to run again. I had them send
>me their firebird.log file to see if I could see anything since this
>is the first time we have heard of something like this.
>
>Some of the messages I am seeing in the log, please note I have cut
>out some of the messages that I do not see important.
>
>ICAP1 (Client) Tue Aug 30 10:43:02 2005
> Control services error 1061
>
>ICAP1 (Server) Wed Aug 31 09:42:09 2005
> SERVER/process_packet: broken port, server exiting
>
>ICAP1 (Server) Thu Sep 01 08:48:55 2005
> INET/inet_error: accept errno = 10093
>
>ICAP1 (Server) Thu Sep 01 08:48:55 2005
> INET/select_wait: select failed, errno = 0
>
>ICAP1 (Server) Thu Sep 01 08:48:55 2005
> SRVR_multi_thread/RECEIVE: error on main_port, shutting down
>
>ICAP1 (Client) Thu Sep 01 08:53:38 2005
> Guardian starting: C:\Program Files\Firebird\Firebird_1_5
>\bin\fbserver.exe
>
>
>
>ok, the messages from Sep 1 happened again this morning (Sept 2).
>
>Does anyone know what could be causing these errors?

10093 is a windows socket initialisation error (could not initialize socket).

The two most likely causes are:

1) the client is trying to connect to the database server before the
database server has properly started. It is likely to happen when a client
tries to connect before the server has finished booting up and starting
services.

2) a Firebird client is trying to connect to a Firebird server while
another Firebird server, an InterBase server (or something else that uses
port 3050) is running connections through the same service port. Try to
find out what your customer has installed on the server recently. Like it
or not, there are freebie downloads out there that blindly install
themselves without checking what's already installed.

./heLen