Subject | Re: Classic Server stops working overnight (socket errors?) |
---|---|
Author | jarnon42 |
Post date | 2008-03-28T00:35:27Z |
Hi Helen,
Thanks for your reply. :)
We restarted the host machine twice and stopped/started the Firebird
service several times as well.
Thanks for pointing out the consequences on the cache size. I wasn't
aware of that.
Just for clarity, we uninstalled FB 2.0.1 and re-installed FB 2.0.3
(so we didn't just copy some files, etc).
While SS ran the Guardian was enabled and during CS it wasn't
running (no option).
Our ODBC connection strings looks like:
DELPHI3:C:\PC4\PrimeCut4.fdb
I assume that runs on TCP/IP in the background. We could actually
telnet to the FB 3050 port (CS and SS), but we had problems when we
tried "Test Connection" in ODBC or even with isql. We also had a
*lot* of inet errors in the FB log, etc.
It always worked like that, so something subtle must have changed in
the environment in which FB was running (update of socket DLL by a
anti-virus scanner maybe).
We haven't tried re-installing 2.0.1 again yet, because our customer
needed to get back to work again - fair enough. I'm not sure if it
will make any difference though. Any particular reason you suggested
that?
Once again thanks for your help! :)
Kind regards,
Jarno
Thanks for your reply. :)
We restarted the host machine twice and stopped/started the Firebird
service several times as well.
Thanks for pointing out the consequences on the cache size. I wasn't
aware of that.
Just for clarity, we uninstalled FB 2.0.1 and re-installed FB 2.0.3
(so we didn't just copy some files, etc).
While SS ran the Guardian was enabled and during CS it wasn't
running (no option).
Our ODBC connection strings looks like:
DELPHI3:C:\PC4\PrimeCut4.fdb
I assume that runs on TCP/IP in the background. We could actually
telnet to the FB 3050 port (CS and SS), but we had problems when we
tried "Test Connection" in ODBC or even with isql. We also had a
*lot* of inet errors in the FB log, etc.
It always worked like that, so something subtle must have changed in
the environment in which FB was running (update of socket DLL by a
anti-virus scanner maybe).
We haven't tried re-installing 2.0.1 again yet, because our customer
needed to get back to work again - fair enough. I'm not sure if it
will make any difference though. Any particular reason you suggested
that?
Once again thanks for your help! :)
Kind regards,
Jarno