Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Error 17824 follow by 1608. on SQL6.5
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Ask SQLTeam Question

0 Posts

Posted - 04/09/2002 :  13:03:52  Show Profile  Visit AskSQLTeam's Homepage  Reply with Quote
khoo writes "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."

Most Valuable Yak

15732 Posts

Posted - 04/09/2002 :  13:29:25  Show Profile  Visit robvolk's Homepage  Reply with Quote
Two things to try. First is to have the network admin perform diagnostics on the SQL Server's network card, just to rule out the possibility of any trouble.

The other thing is to see if some kind of packet sniffer or some other kind of network crawler is being run...even if your local network guy says there isn't. Some of these tools don't cause a lot of network traffic, but can cause the server to ping everything and eat up a lot of resources.

The company I worked for had national and local level IT divisions, and the national people would do things that would totally FUBAR the network, without telling the local guys that they were doing it. We finally had to get the local market president to complain to the CIO of the company to get them to stop!

Go to Top of Page

The Chadinator

1974 Posts

Posted - 04/09/2002 :  16:00:15  Show Profile  Visit chadmat's Homepage  Reply with Quote
The third thing is to get mission critical DBs on 7.0 or better yet 2000.


Go to Top of Page

BC Khoo
Starting Member

1 Posts

Posted - 04/09/2002 :  22:49:04  Show Profile  Reply with Quote
Thanks for your advices.
We change the server nic card already and the problem still happen. May be I will ask the network guy monitor the network traffic for a few days.
I have a tot to upgrade to SQL2000 but I don't think we can just upgrade like that right? The applicaton have 800++ store procedure. Do we need to rewrite all of them? (sorry, i does not know how compatiable the application in SQL2000). What is the concern if we go for upgrading?

thanks again for your valuable suggestion..

Go to Top of Page

SQL Slashing Gunting Master

3246 Posts

Posted - 04/10/2002 :  00:20:00  Show Profile  Visit AjarnMark's Homepage  Reply with Quote
I would definitely do this in a test mode. I've done upgrades from 7.0 to 2000 without trouble, but I can't say that we're doing anything too fancy in our databases. I would expect that you'd be in really good shape, and not have to rewrite everything, but there will probably be a couple of issues. Do a Forum Search here on upgrading to 2000 because there are a couple of good threads with people's experiences.

I have it on pretty good authority there will be an article coming out about one man's experiences, but you probably won't want to wait that long...

GENERAL-ly speaking...
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.04 seconds. Powered By: Snitz Forums 2000