Net-Library errors every 48 hours -- sql server connect

Dan Kimble
10/17/2006 7:28:02 AM

At 2:00 AM every other morning we are getting errors that are causing us to
have to restart SQL Server 2000.

The event log registers the following:
Source: MSSQLSERVER
Event ID: 17052
Error: 17825, Severity: 18, State: 4
Could not close Net-Library ''.

We will also see the following error:
Source: MSSQLSERVER
Event ID: 17052
Error: 17059, Severity: 18, State: 0
Operating system error 10093: Either the application has not called
WSAStartup, or WSAStartup failed..

We would appreciate some help as we would like to sleep through the night

Sue Hoegemeier
10/18/2006 11:22:53 PM

What application runs against the server at 2:00 am? Why do
you have to restart SQL Server? I'd create a server trace
to run and schedule it to capture the activity during that
time.

-Sue

On Tue, 17 Oct 2006 07:28:02 -0700, Dan Kimble
[quoted text, click to view]

Dan Kimble
10/19/2006 5:23:01 PM

We have no other jobs that are running at 2:00 AM. The Retrospect backup has
finished by then and we have eliminated/rescheduled all other tasks in the
process of trying to figure out what is going wrong.

We have to restart the SQL service as it will no longer accept connections
which causes our web site to stop responding (at least the pages that rely on

Sue Hoegemeier
10/19/2006 10:01:13 PM

Are both SQL Server and the OS on the latest service packs?
You have some issue with a program or app that is doing some
winsock calls. I'd still run some traces. One problem with
rescheduling and changing tasks is that you are only
changing the ones you know about. There can be others you
don't know about.

-Sue

On Thu, 19 Oct 2006 17:23:01 -0700, Dan Kimble
[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server connect

sql server connect : Net-Library errors every 48 hours