Subject | Re: [firebird-support] Incredible problem with Win2K Server -- is this a bug? |
---|---|
Author | Olivier Mascia |
Post date | 2004-02-17T07:54:41Z |
On 16/02/2004 22:38 GMT+1, Franz J Fortuny wrote:
Did you read the Release Notes before doing so ?
Is it Win2K Server SP4 ?
How did you proceed with the install ?
Using the ZIP kit or an installer ?
Was there previous BETA or RC versions of FB 1.5 before on this machine ?
A shutdown / restart of the machine is rarely required when installing
Firebird, unless some previous versions are present on the machine. Was
there a shutdown / restart requested by the installer or by the
command-line tools (using the zip kit) ?
Was there any shutdown (no matter who decided it) after install of RC9
and tests ?
service starts the engine service, is that what we talk about (which is
correct) or are you talking of the GUI control panel applet that let's
you click on buttons to do the same and to switch between service or not
service mode ?
Service applet (from Microsoft) ? Or those from the Firebird Control Panel ?
for the last 5 days without a single issue... There is undoubtly
something ongoing on your machine when you install FB 1.5 RC9. Maybe a
wrong client DLL left somewhere ?
Or one of those issues related to TCP/IP and Win2K SP4.
--
Best Regards,
Olivier Mascia
> Proceed to make a CLEAN install of Fireber 1.5 RC9 in a Win2K server.Some questions.
> Server.
Did you read the Release Notes before doing so ?
Is it Win2K Server SP4 ?
How did you proceed with the install ?
Using the ZIP kit or an installer ?
Was there previous BETA or RC versions of FB 1.5 before on this machine ?
A shutdown / restart of the machine is rarely required when installing
Firebird, unless some previous versions are present on the machine. Was
there a shutdown / restart requested by the installer or by the
command-line tools (using the zip kit) ?
Was there any shutdown (no matter who decided it) after install of RC9
and tests ?
> Install it as a SERVICE. Let The Guardian start and stop it (controlSo both guardian and engine are installed as services and that guardian
> it).
service starts the engine service, is that what we talk about (which is
correct) or are you talking of the GUI control panel applet that let's
you click on buttons to do the same and to switch between service or not
service mode ?
> Then, through Localhost, try to connect any client application:Never seen such a thing, but there is a first in everything in life :)
> IT FREEZES! Along with the client application.
> And freezes to the point where The Guardian can NOT stop the serviceWhich buttons are we talking about ? Those of the Administrative Tools -
> (or restart it). Windows can not stop the service or restart it.
> It stays there, forever. And if any application intends to connect to
> this gone to "limbo" server, the client application will also remain,
> FOREVER stuck, unusable.
>
> Hint: the Guardian STARTS the server, but the button, instead of
> going to STOP form, DOES informe that the server is running, but
> instead of showing "STOP" (the server) it continues to show START.
Service applet (from Microsoft) ? Or those from the Firebird Control Panel ?
> Also, if you try to STOP the server right after you start it (with TheThen I wonder how my three company servers (Win2K Server SP3) run FB RC9
> Guardian it is "impossible", since the button says "start" even
> though it's already started) through the services page you can stop
> and restart. As a matter of fact, you can stop it and restart it if
> IT HASN'T BEEN INTENDED BY ANY client to connect to it.
for the last 5 days without a single issue... There is undoubtly
something ongoing on your machine when you install FB 1.5 RC9. Maybe a
wrong client DLL left somewhere ?
Or one of those issues related to TCP/IP and Win2K SP4.
--
Best Regards,
Olivier Mascia