| Subject | Re: [IBO] Windows 2003 Server, ISC ERROR CODE:335544726 |
|---|---|
| Author | Helen Borrie |
| Post date | 2007-08-20T01:10:57Z |
At 10:00 AM 20/08/2007, you wrote:
that both of these facts are true:
1. the client is not connected.
2. if the client was connected previously, it detached cleanly, or
its connection timed out and the server cleaned up the
connection. In the latter case, with normal TCP/IP settings, cleanup
would occur at least two hours after the connection went idle.
dataset operation when there is no connection to the database.
If the "no connection" condition were caused by a crash, you would
see a network error in the log. No network error in the log only
means that the network system didn't report that an abnormal socket
loss had occurred. It seems you might need to investigate the network
settings and find out what the server is doing to idle connections....
One possibility (amongst the haystack) is that your network is using
DHCP to allocate IP addresses and that quiet sockets are getting
silently disconnected and their IP addresses are being released for
reallocation to another socket. I have this vague recollection of a
Server2003 "feature" called Media Sense that does that by
default. The setting to disable it is something like
DisableDHCPMediaSense...look it up on Google. (I don't have Server2003.)
Helen
>hello, i have a big problem and no idea, where it comes:If there is no network error appearing in the log then it's a sign
>
>..............................
>Windows 2003 Server SP1,
>Firebird 1.5.4 Superserver
>(standard config)
>IBO 4.7.16
>database is on local server
>hardware:
>Xeon cpu 3.60 GHz, 6 giga RAM
>..............................
>
>from time to time i get:
>
>2007-08-19 14:37:47; ERROR: ISC ERROR CODE:335544726
>
>ISC ERROR MESSAGE:
>Error reading data from the connection.
>
>STATEMENT:
>TIBOInternalDataset: "<TIBOQuery>.<TIBOInternalDataset>."
>
>5-10 times the day, but no entry in the firebird.log that
>there was an connect error or anything.
that both of these facts are true:
1. the client is not connected.
2. if the client was connected previously, it detached cleanly, or
its connection timed out and the server cleaned up the
connection. In the latter case, with normal TCP/IP settings, cleanup
would occur at least two hours after the connection went idle.
>I checked all selects and so on, found no error.You will get this exception in an application that tries to perform a
dataset operation when there is no connection to the database.
If the "no connection" condition were caused by a crash, you would
see a network error in the log. No network error in the log only
means that the network system didn't report that an abnormal socket
loss had occurred. It seems you might need to investigate the network
settings and find out what the server is doing to idle connections....
One possibility (amongst the haystack) is that your network is using
DHCP to allocate IP addresses and that quiet sockets are getting
silently disconnected and their IP addresses are being released for
reallocation to another socket. I have this vague recollection of a
Server2003 "feature" called Media Sense that does that by
default. The setting to disable it is something like
DisableDHCPMediaSense...look it up on Google. (I don't have Server2003.)
Helen