June 21, 2006 at 10:48 pm
Hi,
We are running SQL 2000 with SP4 on Windows 2003 (we have just recently migrated to Windows 2003) and our databases reside on IBM SAN drives.
We have noticed this Error 17883 in the Event Viewer as well as the SQL logs and today this caused our system to hang for a few minutes. According to the Microsoft knowledge base SP4 is suppose to fix this problem and we have had SP4 now for more than a year.
Does anyone have any idea or knowledge about this problem and how we can ovecome it.
Many Thanks,
Sebastian
June 23, 2006 at 10:25 am
Upgrading to build 2175 took care of our UMS Scheduler issues. Build 2187 is also out now but we have not installed it as of yet.
June 23, 2006 at 10:46 am
Take a look at the following whitepaper for help trying to troubleshoot why this is happening:
How To Diagnose and Correct Errors 17883, 17884, 17887, and 17888
K. Brian Kelley
@kbriankelley
June 28, 2006 at 1:55 am
We had a very similar problem a while back, and after intensive debugging and assistance from MS support, tracked it down to occational IO problems with the SAN and a poor storage architecture.
I would suggest you run perfmon on the server for a day or so, look at especially the physical disk counters, memory paging and the SQL server buffer-management, lazy writes and checkpoint pages
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply