Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2000 Forums  SQL Server Administration (2000)  disable Error 17883 in event log.

Author  Topic  Why_gh Starting Member 3 Posts Posted - 2006-12-13 : 11:09:24 Hi all, Clusted , two nodes. SQL Server 2000 EE Sp4. build 2187 . Windows 2003 EE, 8G memory, 4CPU. Last Friday, SQL Server failover to another node automatically because of error 17883. Errorlog: 2006-12-08 02:43:00.98 backup Database backed up: Database: 2006-12-08 03:00:19.45 server Using 'dbghelp.dll' version '4.0.5' 2006-12-08 03:00:19.45 server process_commands: Process 1580 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.2006-12-08 03:00:21.92 server Stack Signature for the dump is 0x4DF99E0C 2006-12-08 07:12:02.18 logon Login failed for user 'xxx'. 2006-12-08 07:33:20.25 logon Login failed for user 'xxx'. 2006-12-08 07:55:18.32 logon Login failed for user 'xxx'. 2006-12-08 08:14:51.67 server Stack Signature for the dump is 0x00000000 2006-12-08 08:14:51.67 server Error: 17883, Severity: 1, State: 0 2006-12-08 08:14:51.67 server Process 0:0 (105c) UMS Context 0x00CCE188 appears to be non-yielding on Scheduler 0. 2006-12-08 08:14:51.67 server Error: 17883, Severity: 1, State: 0 2006-12-08 08:14:51.67 server Process 0:0 (498) UMS Context 0x088D9610 appears to be non-yielding on Scheduler 1. 2006-12-08 08:14:51.67 server Error: 17883, Severity: 1, State: 0 2006-12-08 08:14:51.67 server Process 0:0 (1044) UMS Context 0x088E7110 appears to be non-yielding on Scheduler 2. 2006-12-08 08:14:51.67 server Error: 17883, Severity: 1, State: 0 2006-12-08 08:14:51.67 server Process 0:0 (111c) UMS Context 0x088F2798 appears to be non-yielding on Scheduler 3. 2006-12-08 08:15:51.67 server Error: 17883, Severity: 1, State: 0 2006-12-08 08:15:51.67 server Process 0:0 (105c) UMS Context 0x00CCE188 appears to be non-yielding on Scheduler 0. 2006-12-08 08:15:51.67 server Error: 17883, Severity: 1, State: 0 2006-12-08 08:15:51.67 server Process 0:0 (498) UMS Context 0x088D9610 appears to be non-yielding on Scheduler 1. 2006-12-08 08:15:51.67 server Error: 17883, Severity: 1, State: 0 After SQL Server failover to another node, I didn't see any Error 17883. But in System Event viewer-->Application log, every 1 minutes , got 4 Error 17883, until now. My question is: Why SQL Server didn't capture the Error 17883? Does it mean that SQL Server still have this problem because system capture it? How can I stop system capturing this error? Thanks