Re: Unable to Connect to Database

[Justin Willey]

Hi

You might get a better response from a new topic, but anyway here goes:

Your log file suggests that the client is connecting OK, but is then losing
the connection:

19:35:48 Connected to ASA Engine version 9.0.2.3302
19:35:48 Connected to the server, attempting to connect to a running
database...
19:35:48 [ 3] Connected to database successfully
19:35:48 [ 3] The number of prefetch rows has been reduced to 62 due to
the prefetch buffer
19:35:48 [ 3] limit. Consider using the PrefetchBuffer connection
parameter.
19:35:54 [ 3] The number of prefetch rows has been reduced to 0 due to
the prefetch buffer
19:35:54 [ 3] limit. Consider using the PrefetchBuffer connection
parameter.
19:36:09 [ 3] The number of prefetch rows has been reduced to 76 due to
the prefetch buffer
19:36:09 [ 3] limit. Consider using the PrefetchBuffer connection
parameter.
19:36:53 [ 3] Connection terminated abnormally; server socket shut down

19:36:53 [ 3] Communication function i_cs_HandleSQLPresError code 6
19:36:53 [ 3] Communication function StrmGetInd code 3
19:36:53 [ 3] Client disconnected

This suggest that it was connected for a whole minute, before the connection
is lost. The

19:36:53 [ 3] Connection terminated abnormally; server socket shut down

message implies that it was not a planned disconnection, but that the client
simply lost contact with the server.

Is there a corresponding message on the server window? Is it always the same
length of time before the disconnection?

In the absence of any further information it looks like a network issue.

Justin Willey

"Scott Young" <sco...@centaursoftware.com> wrote in message
news:49c99380$1@forums-1-dub...
> When I am trying to connect the client computer to the DB engine it is
> giving me a message stating connection to DB has been lost.
>
> The server is running McAffe and the client is running Norton. I have
> disabled both of these in services.msc and this still does not connect.
>
> I have attached a copy of the log file from the client trying to connect.
> What would be causing this issue?
>
>

[Chris Keating [Sybase iAnywhere]]

It is best to get a pairing of the server and client communications log
to determine the cause. To do so, add -z -o <filespec> to your engine
startline (only add the -o if not already in that start line).

If both the client and server report "... socket shut down" as the cause
of the disconnect and neither report timeouts, this may indicate a
problem at the network/OS layer.