You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this applies to FBGuradian and FBServer both.
I recommend adding Windows service dependencies for the
windows implementation. The issue is that in certain
circumstances (like a Windows update/patch) the boot
order of various Windows services can change. This
means that the service called "lanmanserver" (which is
displayed as "Server") which initializes the networking
stack in Windows may be changed to start AFTER Firebird
starts. This means Firebird cannot bind to the socket
because it hasn't been initialized yet.
This happens to some of our clients occassionally and
would not happen if a service dependency existed.
My applications run as services also and *must* access
Firebird through TCP connection. To make my
applications usable with Firebird or Interbase I've let
the service dependencies be defined from a config file
so it can be changed if needed. Something similar might
be helpful with Firebird. It believe it would fix the
issues that I've encountered.
-Mark E.
PS> Excellent work with Firebird. It is now my DB of
choice for embedded applications. Great job!
The text was updated successfully, but these errors were encountered:
Submitted by: mericksen (mericksen)
SFID: 914240#
Submitted By: mericksen
I think this applies to FBGuradian and FBServer both.
I recommend adding Windows service dependencies for the
windows implementation. The issue is that in certain
circumstances (like a Windows update/patch) the boot
order of various Windows services can change. This
means that the service called "lanmanserver" (which is
displayed as "Server") which initializes the networking
stack in Windows may be changed to start AFTER Firebird
starts. This means Firebird cannot bind to the socket
because it hasn't been initialized yet.
This happens to some of our clients occassionally and
would not happen if a service dependency existed.
My applications run as services also and *must* access
Firebird through TCP connection. To make my
applications usable with Firebird or Interbase I've let
the service dependencies be defined from a config file
so it can be changed if needed. Something similar might
be helpful with Firebird. It believe it would fix the
issues that I've encountered.
-Mark E.
PS> Excellent work with Firebird. It is now my DB of
choice for embedded applications. Great job!
The text was updated successfully, but these errors were encountered: