Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing,
however when i checked the event logs on all servers,
there is no error message there. all different messages
include a "General network error" for example one of them
is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobHi Rob,
10054 is usually seen when the underlying tcp session is dropped. The
only way to tshoot this is to make network traces from the client capturing
the problem. Then work with your network staff to resolve them. More than
likely, the cause is a dropped tcp session.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Can you explain a bit more, How can I make the Network
trace? Basically, I can not see any problem with the
network, what kind of network problems should I looking
for?
Thanks a lot-Rob
>--Original Message--
>Hi Rob,
> 10054 is usually seen when the underlying tcp session
is dropped. The
>only way to tshoot this is to make network traces from
the client capturing
>the problem. Then work with your network staff to
resolve them. More than
>likely, the cause is a dropped tcp session.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||Hi Rob,
So all SQL connections from clients are supported by underlying tcp or
smb sessions. ODBC and OLEdb applications rely on the integrity of the
underlying network session. If the session is torn down, then the
application will fail. In our case we tend to report "general network
Error".
So, if this is the error you're seeing, you need to make network traces
from the client and see if the underlying tcp or smb session was dropped.
Then work with your network team to resolve it.
Otherwise, you can make the traces and open a case with us to help do the
review.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sqlsql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment