April 8, 2002 at 10:18 pm
I manage a few SQL 6.5 server which is running 24x7 mission critical. Normally, All the server given this message onces a while (may be one or two time a day and the durations is less then 2 min) and this didn't effect the user.
But, currently, one of the server given a block of this error and it cause a lot of clients have difficulty to connect to the server or hang. But this situation last for 20min to 30min and it come back to normal by itself. This happen intermitently and It make me very difficult to trouble shoot. Below is some descriptions, I hope somebody can help me or give me some idea on how to slove it. Thanks
btw : I ask network guy to check the network but it seem like no problem on the network.The utilization of the network is less then 10% and the clients is able to ping to server.
Server OS : win NT4 with latest service pack
Database : SQL 6.5 with post service pack 6a
Conneciton : TCP/IP port 1433
Clients : Win 95 or Win 98
No Of user : About 200
The block of error as below:
2002/04/01 14:00:22.58 ods Error : 17824, Severity: 10, State: 0
2002/04/01 14:00:22.58 ods Unable to write to ListenOn connection '1433', loginname 'sa', hostname 'FONGYIUN'.
2002/04/01 14:00:22.58 ods OS Error : 64, The specified network name is no longer available.
2002/04/01 14:00:22.58 spid10 Error : 1608, Severity: 21, State: 2
2002/04/01 14:00:22.58 spid10 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information.
April 9, 2002 at 5:16 am
Have you recently changed anything about the server (name, ip address, segment, nic, etc.), Also have you checked the nic to make sure it isn't going bad on you. Also check drivers to make sure current on the server.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 9, 2002 at 8:05 pm
Hi thanks for your reply. I didn't change anything on server side. But on clients side, the changes are quite frequence as there always got new installations and relocation of some clients machines.
May be i should update my nic driver on that server or change the nic card. Ohh, i need to schedule another downtime again..
Just ask your openion.. Any possiblity of ODBC or OS layer that cause the problem?
Thanks again for your help, really appreciated.
April 10, 2002 at 4:42 am
Possibly even a bad NIC. Cheap enough to just replace it if it continues.
Andy
April 10, 2002 at 4:55 am
At this point I would ahve to say NIC as the errors are clearly networking related.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply