Subject | Re: [firebird-support] Firebird + Windows Server 2008 |
---|---|
Author | Mark Rotteveel |
Post date | 2011-09-16T10:01:44Z |
On 16-9-2011 10:07, donovanboddy@... wrote:
AFAIK Windows Server 2008 was released *after* Firebird 2.0.4. You might
want to try upgrading to either 2.0.6, or 2.1.4.
symptom of problems like program crashes, network problems or maybe a
virusscanner/IDS closing the socket (or of sloppy programming where
connections aren't closed before exiting your program); and not actually
a cause of problems.
I would advice to also consult the Windows Event log on both server and
client, check if a virus scanner or IDS is installed (server, client or
network appliance!) which closes sockets if there is 'too much' traffic
(I believe NOD32 does this).
--
Mark Rotteveel
> Hi AllI am not sure if Windows Server 2008 and Firebird 2.0.4 are compatible;
>
> Really hoping someone here will be able to help me.
>
> We have a client running windows server 2008 and Firebird 2.0.4.
AFAIK Windows Server 2008 was released *after* Firebird 2.0.4. You might
want to try upgrading to either 2.0.6, or 2.1.4.
> For some reason we are having endless problems with this client, all kinds of strange errors that seem totally inexplicable.I think a more detailed description of the problems would be helpful.
> Eventually we turned to the log file generated by Firebird and found numerous reports of this error INET/inet_error: read errno = 10054In my opinion, this error (connection reset by peer) is usually a
symptom of problems like program crashes, network problems or maybe a
virusscanner/IDS closing the socket (or of sloppy programming where
connections aren't closed before exiting your program); and not actually
a cause of problems.
I would advice to also consult the Windows Event log on both server and
client, check if a virus scanner or IDS is installed (server, client or
network appliance!) which closes sockets if there is 'too much' traffic
(I believe NOD32 does this).
--
Mark Rotteveel