Subject | Re: [firebird-support] Firebird log |
---|---|
Author | Helen Borrie |
Post date | 2006-05-24T06:27:07Z |
At 01:20 PM 24/05/2006, you wrote:
pleasing itself about when and in what order it's going to start up services.
So, for example, if you have a Firebird service starting up at some
point and a database replicator service starting up at some point,
and Win tries to start up the replicator service before it starts the
Firebird service you'll get this error.
Next bet is an unplugged network card somewhere; or even just that
Windows hasn't gotten around to starting the network services yet.
The symbolic constants just represent OS error conditions in the Windows API.
./heLen
>Hi RichardStick with Rick's theory. This error is almost always due to Windows
>
>No idea what all that means. However searching for
>ERROR_SERVICE_CANNOT_ACCEPT_CTRL and firebird brought up a spanish site
>that mentioned a similar (but different) issue, being caused by
>incorrect network card drivers.
>
>It is all Greek to me :)
pleasing itself about when and in what order it's going to start up services.
So, for example, if you have a Firebird service starting up at some
point and a database replicator service starting up at some point,
and Win tries to start up the replicator service before it starts the
Firebird service you'll get this error.
Next bet is an unplugged network card somewhere; or even just that
Windows hasn't gotten around to starting the network services yet.
The symbolic constants just represent OS error conditions in the Windows API.
./heLen