Re: sql client connectivity errors
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Mon, 10 Oct 2005 18:36:48 -0600
It can actually be several different things and isn't always
easy to track down when it's intermittent.
Sometimes you can see the error with timeout issues so you'd
want to be monitoring the activity on SQL Server itself and
make sure you don't have locking or blocking issues.
To check any potential TCP/IP issues, the following is a
pretty good article:
http://support.microsoft.com/?id=169790
As long as it's intermittent, it may not help to try
changing protocols on a client but if you do have one client
who has the issue more often, you could try changing that
client over to using named pipes and see if that makes a
difference.
-Sue
On Fri, 7 Oct 2005 11:03:08 -0700, "GaryC"
<GaryC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>It's a new HP DL740 server with the latest drivers and the NIC diagnostics
>show no errors. I see zero "Packet Outbound Errors" and "Packets Recieved
>Errors" in Performance monitor on the server. I'm not sure on the other
>questions you asked, but have posed them to the software vendor and am
>awaiting a response.
>Thanks.
>
>"MeanOldDBA" wrote:
>
>> Have you looked at using performance monitor to track for packet errors?
>> There should be a diagnostic card for the NICs on the server also. Have you
>> checked it to see if there have been any errors?
>>
>> Why type of connection components are being used by the application? Is a
>> constant connection required? It's not old RDO stuff is it?
>>
>> --
>> MeanOldDBA
>> derrickleggett@xxxxxxxxxxx
>> http://weblogs.sqlteam.com/derrickl
>>
>> When life gives you a lemon, fire the DBA.
>>
>>
>> "GaryC" wrote:
>>
>> > We're getting error messages on XP Pro clients connecting to an SQL 2000+SP3a
>> > server running Windows Ent. Ed.+SP1. The clients have SP2 installed which
>> > includes MDAC 2.81. The error messages come up in the following sequence:
>> > SQL Error: 01000 (10054):[Microsoft][ODBC SQL Server Driver][TCP/IP
>> > Sockets]ConnectionRead (recv()).
>> >
>> > SQL Error: 08501 (11): [Microsoft][ODBC SQL Server Driver][TCP/IP
>> > Sockets]General Network Error. Check your network documentation.
>> >
>> > SQL Error: 08501 (0): [Microsoft][ODBC SQL Server Driver]Communication link
>> > failure.
>> >
>> > These errors occur at random with no common thread of time or location.
>> > There are no errors in the event logs of either the server or the clients
>> > that correspond with the SQL errors. After the errors come up the
>> > application needs to be closed then it will run fine. There are no other
>> > application errors for other apps running on the clients at the same time.
>> > The clients are connected via 100mb switched network and the switches don't
>> > show any errors. The server is connected via gigabit to a core switch with
>> > no more than 3 switch hops between it and the clients. There aren't any
>> > errors on the core switch either.
>> >
>> > If you have any suggestions or ideas on how to troubleshoot this please
>> > help. The application vendor is refusing to help, saying it's a network
>> > issue.
>> > Thank you.
>> > Gary
.
- Follow-Ups:
- Re: sql client connectivity errors
- From: GaryC
- Re: sql client connectivity errors
- Prev by Date: Re: Client Connection Problem.
- Next by Date: Re: Accessing shares over internet
- Previous by thread: Re: security proplem
- Next by thread: Re: sql client connectivity errors
- Index(es):
Relevant Pages
|
