THANK YOU!

This happened to a client today: after a reboot of a Win2000 server, Fb
service (SS) would not start (and Guardian could not be stopped). Faintly
remembering these posts, we managed to kill the APC services (with
ProcessExplorer). And - Fb just started.


--
Aage J.
(Sorry for top-posting)


Peter McLeod wrote:

> Hello Tim,
>
> Please find attached details of a previous post that I made which I
> think describes your circumstances with Firebird not starting.
>
> Regards
> Peter
>
>
> _____
>
> From: Peter McLeod
> Sent: Wednesday, 3 August 2005 8:59 AM
> To: firebird-support@yahoogroups.com
> Subject: RE: [firebird-support] Re: Server Services failures. Is this
> Firebird related?
>
>
> Hello Roger,
>
>
> Do you use APC server and agent software on this machine? If so if it
> is at version 6.x then this is possibly the probeem. Use Process
> explorer from sysinternals to kill this service and set it to manual.
> This will cause it to release the msvcrt.dll that it is attempting to
> load which allows Firebird to start. Then upgrade to version 7.x of the
> product.
>
> _____
>
> From: rogervellacott [mailto:rvellacott@...]
> Sent: Wednesday, 3 August 2005 8:54 AM
> To: firebird-support@yahoogroups.com
> Subject: [firebird-support] Re: Server Services failures. Is this
> Firebird related?
>
>
> Thanks for the replies to this. The problem extends beyond FB to all
> the other services. Most of them start on rebooting the server, but
> once booted, you can't stop or start any of them. You can't even
> change the properties on any of them (eg from Manual to Automatic)
> without getting a time-out failure.
>
> As it has happened on two separate servers running FB, I am worried
> that FB may have caused the problem. But I have uninstalled FB on
> one of the servers, and this has not solved the problem. You still
> can't stop or start services. I have run RegistryMechanic to fix any
> registry errors, and the only thing left is to re-install Windows.
>
> I suppose it is reassuring if nobody in this newsgroup has seen
> anything similar, as that probably means fB is not guilty. It would
> be nice to know what is going on though.
>
> Roger Vellacott
>
>
> --- In firebird-support@yahoogroups.com, "rogervellacott"
> <rvellacott@p...> wrote:
>
>>Last week a client's Win2000 server running FB1.50 Classic ground to a
>>halt. On inspection, FBGuard was running, but FBServer was not.
>> Trying to stop FBServer timed out, leaving FBServer in a "Stopping"
>> state.
>>None of the other services could be stopped or started, including
>>simple ones, like Telnet. So I assumed it was a nasty Windows
>> problem.
>>Firebird is now happily running on a temporary server (one of the
>>workstations) and we are waiting for a Windows re-install on the
>> server.
>
>>However, last night another client with FB1.50 Superserver had a power
>>cut, and the UPS battery ran out. Firebird stopped working, and has
>>the same symptoms as the first client. Services cannot be started
>> or stopped. Firebird 1.5.2 installs, but fails when it times out at
>> the end when it tries to install the service.
>>
>>If this is not a Firebird issue, then it is a strange coincidence.
>>Does anyone know what is going on?
>>
>>Roger Vellacott
>>Passfield Data Systems
>