I agree it's not elegant. However, this stunningly simple suggestion solves
*our* intermittent, similar problem. I feel like a doofus for not thinking of
it right off.

Thanks Olivier,
Kevin Herrmann

> Message: 16
> Date: Wed, 7 Jan 2004 16:16:13 +0200
> From: "Andre du Plessis" <andre@...>
> Subject: RE: Firebird Server (Service Startup)
>
> This is rather a less than elegant solution.
>
> -----Original Message-----
> From: Olivier Mascia [mailto:om@...]
> Sent: Wednesday, January 07, 2004 12:11
> To: firebird-support@yahoogroups.com
> Subject: Re: [firebird-support] Firebird Server (Service Startup)
>
> Dear,
>
> On Wed, 7 Jan 2004 10:01:52 +0200,
> Andre du Plessis wrote :
>
> > The problem is that I have other services which are dependent on the
> > firebird service
> > ...
> > but it appears that the firebird
> > Service is not completely initialized/started after the Start service
> > control request was sent to it and processed, because my service
> > Tries to query the database too soon, and I keep on getting funny errors
> and
> > have to restart my service.
> > ...
> > ...how can I from my
> > service wait for the firebird service to completely initialize,
>
> If your own service correctly depends on Firebird engine service, then
> the most important thing is done. I would suggest to just add a Wait
> (30 sec) in the startup of your own service application. That should
> leave plently of time for the firebird engine to be ready. Honestly,
> seeing the time to boot Windows, a 30 sec pause before your
> application service actually starts is probably nothing important.
>
> --
> Best Regards,
> Olivier Mascia

=====
Kevin Herrmann