January 16, 2004 at 3:18 am
Error: 17883, Severity: 1, State: 0
Process 57:0 (928) UMS Context 0x020E81B0 appears to be non-yielding on Scheduler 3
I know this message crops up all over the net after the release of SP3 but I continue to get it with no other messages on the log to point to why. I have spoken to Microsoft who say it is not the 'bug' which required a new patch, so now I am stuck, unless I pay for continued help from Microsoft.
Has anyone had and dealt with this error? Does anyone actually know what it means (I have read all the KB articles but still don't really know). We use COM+ components (written in VB) a lot, does anyone know how these could be causing this error?
I'm really struggling with this one. It appears to be load related, in that it will occur at times of heavy usage.
Sometimes the errors will be logged two or three times, then go away without affecting perormance.
Sometimes the SQL Server will hang after a number of them and one of the COM+ components will seem to be 'stuck' also. Shutting down the package seems to clear the blockage and everything continues as normal.
Sometimes the SQL Server will hang, and no amount of shutting down of components helps, SQL Server does not respond to request to stop the service and I end up either re-booting or killing the sqlserver.exe process!
Can anyone give me any pointers as to what could be going on?
Many thanks for your help!
Adge
January 16, 2004 at 7:12 am
" I'm really struggling with this one. It appears to be load related, in that it will occur at times of heavy usage. "
I agree with you. It is realted the workloads. I have seen such messages in one of my server during the data loading from a text file into database.
if the warning keeps coming back every 60 seconds for a large period of time and it is not resolved then SQL Server may have a hung processor. We seen slow I/O performance during same period time and I/O seems the bottleneck.
Suggest to review machine application/system logs and check your hardware especilly in I/O subsystem performance.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply