At 08:16 AM 29/06/2010, sboydlns wrote:

>Using FB 1.5.5 SS on Windows 2003 Enterprise Edition.
>
>Firebird won't start when the system boots even though the Guardian is set to start automatically. The Guardian can be started manually without difficulty.
>
>We are seeing the following error in the Windows event log:
>
>The description for Event ID ( 212 ) in Source ( FirebirdGuardianDefaultInstance ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The registry information is missing.

This much is just the standard Windows message when the server can't start.

>Please run the Firebird Configuration Utilitto launch the server thread. errno : 1055.

Weird - looks like some custom component involved there.

>Any ideas what this means?

Apart from the quasi-Italian at the end, it normally means that the Guardian can't start the Superserver because the network service isn't available yet. Since Windows makes its own decisions about which services to start first, AFAIR, there isn't an obvious solution, as long as you are running both network and Firebird services on the same box.

However, I do recall someone suggesting that it's possible to enumerate the dependencies in the service definition, so that Windows won't even try to start Firebird until the network is running.

./heLen