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