|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
17883 errorcan. Any directions to other resources would be appreciated. This is on SQL server 2000, with SP4 running on windows server 2003. Sunday, the 25th, at 3:00am, the server installed the timezone patch (kb931836). at 4:00am, ntbackup.exe started a system state backup. at 4:01am, SQL server started filling it's errorlog file with the following: 2007-02-25 04:01:15.87 server Error: 17883, Severity: 1, State: 0 2007-02-25 04:01:15.87 server Process 97:0 (8c0) UMS Context 0x05A9C478 appears to be non-yielding on Scheduler 0. 2007-02-25 04:01:15.89 server Error: 17883, Severity: 1, State: 0 2007-02-25 04:01:15.89 server Process 82:0 (e78) UMS Context 0x05A977F8 appears to be non-yielding on Scheduler 1. These continued several times a second. During that time, I could not connect to SQL server. Profiler or enterprise manager would just hang. Some applications would get responses to queries, but it appeared to be random. We rebooted the server and the errors continued. SQL server was usable for about 10 minutes after the reboot and then went back to hanging. The errors continued to fill the errorlogs. The problem was finally "corrected" by uninstalling the patch for kb931836. I'm puzzled by that because it doesn't seem to have anything to do with SQL. Thanks. Error 17883 was supposed to be a bug in sql server 2000 (sp3) and corrected
in sp4. Did you know the cause now? I am asking this as we have this error last week on sql server 2000 (sp3) -- Show quoteHide quoteontario, canada "bb" wrote: > > I have a bit of a strange problem, I'll attempt to describe it as best I > can. Any directions to other resources would be appreciated. > > This is on SQL server 2000, with SP4 running on windows server 2003. > > Sunday, the 25th, at 3:00am, the server installed the timezone patch > (kb931836). > at 4:00am, ntbackup.exe started a system state backup. > at 4:01am, SQL server started filling it's errorlog file with the following: > 2007-02-25 04:01:15.87 server Error: 17883, Severity: 1, State: 0 > 2007-02-25 04:01:15.87 server Process 97:0 (8c0) UMS Context 0x05A9C478 > appears to be non-yielding on Scheduler 0. > 2007-02-25 04:01:15.89 server Error: 17883, Severity: 1, State: 0 > 2007-02-25 04:01:15.89 server Process 82:0 (e78) UMS Context 0x05A977F8 > appears to be non-yielding on Scheduler 1. > > These continued several times a second. During that time, I could not > connect to SQL server. Profiler or enterprise manager would just hang. Some > applications would get responses to queries, but it appeared to be random. > > We rebooted the server and the errors continued. SQL server was usable for > about 10 minutes after the reboot and then went back to hanging. The errors > continued to fill the errorlogs. > > The problem was finally "corrected" by uninstalling the patch for kb931836. > I'm puzzled by that because it doesn't seem to have anything to do with SQL. > > Thanks.
View Primary Keys Clustered?
Fastest way to insert? faster? Foreign key Constraint DBCC DBREINDEX failure find the date a sp was installed Why won't the log truncate internally? (I'm NOT trying to shrink the file itself!) Installing SQL Express from command prompt SQL Mobile Merge Replication Questions? archiving data |
|||||||||||||||||||||||