Networking Forums

Networking Forums > Computer Networking > Windows Networking > Connection errors

Reply
Thread Tools Display Modes

Connection errors

 
 
Griff
Guest
Posts: n/a

 
      06-21-2006, 12:12 PM
Hi

I have database application that stops working and the event log shows two
errors - I suspect that they are related but I don't know for certain and
I'm not sure whether they refer to connections to SQL Server or to the
Windows server.

The first error is number 17883:

Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung.

And the second is number 17809
Could not connect. The maximum number of '32767' configured ...
Error: 17809, Severity: 20, State: 1

Unfortunately, I don't have the FULL text.

Now, I've investigated this as best I can and Microsoft say that the 17883
error occurs when the underlying disk system is too quick (e.g. when using a
SAN), but that this was fixed in SQL Server 2000 sp4. Yes, my server is
fibre-attached to a SAN **but I'm already running sp4** ... Here are some
URLs that I found:

http://www.developersdex.com/sql/mes...crosoft.com%3E
http://support.microsoft.com/default.aspx?kbid=810885
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/816840

Regarding error 17809, I've put in some monitoring software and the number
of SQL Server connections never goes above 200, so I'm thinking that the
32767 connections is not a SQL Server connection but in fact a "lower" level
connection to the server [I say "lower" because I don't really understand
this side of networking (I'm just a VB developer)]. It sounds to me as if
the Windows 2003 sp1 server hosting the SQL Server has all its connections
open and can't cope with anything new. If this is the case it's either that
Windows 2003 can't cope with being on a SAN (which I simply can't believe)
or - if I'm being ultra paranoid - the server is suffering some sort of
denial of service (DOS) attack.

Any help or suggestions would be most appreciated,

Thanks!

Griff


 
Reply With Quote
 
 
 
 
Griff
Guest
Posts: n/a

 
      06-21-2006, 12:26 PM
Also...when the database application connection dies, it returns one of the
following error messages (trapped from the ADO object error stack):

Number = -2147467259, Description = [DBNETLIB][ConnectionRead
(recv()).]General network error. Check your network documentation., Source =
Microsoft OLE DB Provider for SQL Server, SQLState = 08S01, Native Error =
11.
Number = -2147467259, Description = [DBNETLIB][ConnectionWrite
(send()).]General network error. Check your network documentation., Source =
Microsoft OLE DB Provider for SQL Server, SQLState = 08S01, Native Error =
11.


 
Reply With Quote
 
Griff
Guest
Posts: n/a

 
      06-28-2006, 10:12 AM
As I didn't get any responses to this thread, I've re-started it in the
sqlserver.connect ng.


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
connection reset errors dave64 Linux Networking 1 11-10-2008 04:37 PM
Network Connection Window empty / netsh errors out Spicy Mikey Windows Networking 2 06-21-2007 02:45 PM
ssh dynamic port forwarding: works but getting connection errors Anthropic Aorta Linux Networking 0 10-30-2005 02:33 PM
No VPN connection get errors:721 and 800 Joe Windows Networking 2 04-25-2005 01:52 PM
MN-740 Errors W. Nunn Broadband Hardware 1 08-28-2004 04:30 AM



1 2 3 4 5 6 7 8 9 10 11