Error 17883
-
Hello all,
I have been problem with the Error 17883 that hang the SQL Scheduler all the time. I made some research on this error, Mircosoft suggests to install two security patches. I did it all last night but the error pops up more than before...
any idea? I would really appreciate your feed backs.
-
What about running Profiler and Perfmon to monitor whats happening on the server when the problem occurs. This will hopefully enable you to establish some sort of pattern as to why the error is occurring.
We had the same error message occurring and it was actually causing the Server to stop responding. Turns out it was because the backup guys were copying files at the same time that other backups were occurring. After streamlining the backup operations and put the file copying after the backups, the message hasn't come back.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
-
quote:
I have been problem with the Error 17883 that hang the SQL Scheduler all the time. I made some research on this error, Mircosoft suggests to install two security patches. I did it all last night but the error pops up more than before...Wow. Synchronicity...
I've just received a white paper from one of our other software suppliers addressing causes of their software hanging. Item 11 on their "Top Ten"
is "SQL Server Error 17883".Here's what it says:
quote:
Microsoft has acknowledged a bug in SQL Server 2000 that can cause what appears to be a RouteEngine hang condition. The hang is actually occurring in SQL Server, and can occur under high volume database processing (such as the daily System Reset, which purges and exports the LOG table). When this condition occurs, the computer UI becomes unresponsive (it takes five minutes to click Start...Programs). However, Task Manager shows 99% idle. SQL Server's error log will show error 17883 with the message "The Scheduler 0 appears to be hung".Fixes for some of the causes for error 17883 are addressed in SQL Server 2000 Service Pack 4, or in a SQL Server 2000 hotfix detailed in security bulletin MS03-031. However, error 17883 can still occur for other scenarios.
If you continue to receive error 17883 in the SQL Error Log after applying the patch, search the Microsoft Knowledge Base for 17883.
The problem can also occur in SQL Server 7.0
Not hugely helpful, but it may reassure you that you're not the only one out there that suffers this problem!
Thomas Rushton
blog: https://thelonedba.wordpress.com -
quote:
In fact that's what I did. As I mentioned, I already installed the security patches located on the links you specified. I am still having the same problem. -
quote:
What about running Profiler and Perfmon to monitor whats happening on the server when the problem occurs. This will hopefully enable you to establish some sort of pattern as to why the error is occurring.We had the same error message occurring and it was actually causing the Server to stop responding. Turns out it was because the backup guys were copying files at the same time that other backups were occurring. After streamlining the backup operations and put the file copying after the backups, the message hasn't come back.
Hope this helps
Phill Carter
I will try the profiler then ...
thank you Phill
--------------------
Colt 45 - the original point and click interface
-
quote:
Tryhttp://support.microsoft.com/?id=810885
http://support.microsoft.com/default.aspx?scid=kb;en-us;319892
I already installed the security patches ...
is "SQL Server Error 17883".Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply