September 11, 2007 at 5:31 am
Hi All,
Running SQL 2005 SP1 on Windows Server 2003, Dual core 4 cpu, 16gb memory, 4 San partitions, data, log & tempddb all partitioned on separate san devices.
No jobs were running that I know of at the time only a development server at this stage, although a data load from an application server had been running earlier in the day.
Could not connect to SQL Server default instance at all, found hundreds of the following msg's in the error log
All schedulers on Node 0 appear deadlocked due to a large number of worker threads waiting on ASYNC_NETWORK_IO. Process Utilization 0%.
Had to cycle SQL and restart
September 11, 2007 at 8:14 am
had a similar issue but different error message. check the KB for a hotfix and call MS. this is most likely a Windows issue and not SQL related
September 11, 2007 at 8:31 am
Unfortunately this Application vendor only wants SP1 for this project - all our other SQL 2005 servers are sp2 + hot fixes.
Thanks for the info - will open a case tomorrow (its midnight in Oz)
Thanks for your reply
Mao.
September 25, 2010 at 1:57 pm
I am really curious to hear what you had to do for this problem. I am suffering from the same issue myself and am starting to pull my hair out.
Thanks.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply