Error 17883 with build 2195

Question

We are running a third party SQL Server 2000 system that currently has SP4 build 2195. We received the 17883 error last weekend which ultimately put the database in suspect mode and so on. After a restart it came up fine and has not caused an issue since. I read some things about the hotfix for this error and the build for SP4 that addresses the issue is 2187 I believe. Since our build is newer than the hotfix build what would be my next step in resolving this issue?

Answer 1

Hello,

Microsoft have released many hot fixes for error 17883 and SQL Server 2000 SP4. Maybe you still need to apply some of them:

http://support.microsoft.com/kb/909379

http://support.microsoft.com/kb/909380

http://support.microsoft.com/kb/891268

http://support.microsoft.com/kb/892205

http://support.microsoft.com/kb/892840

http://support.microsoft.com/kb/892940

http://support.microsoft.com/kb/891268

http://support.microsoft.com/kb/892205

http://support.microsoft.com/kb/892840

http://support.microsoft.com/kb/892940

http://support.microsoft.com/kb/892985

http://support.microsoft.com/kb/900416

http://support.microsoft.com/kb/917565

http://support.microsoft.com/kb/929410

Try to apply them from bottom to top.

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

Answer 2

Thanks for the reply.None of the fixes that you listed seem to match the symptoms that we experienced. I will post the portion of the log where the error occured and maybe you can tell me your thoughts. I don't have  a lot of experience with SQL Server itself, so I may be missing something but to me it looks as though nothing was running at the time. The backups that run, do so every half hour:

2012-05-05 22:00:04.81 backup    Log backed up: Database: dc00ewh, creation date(time): 2008/02/19(08:16:41), first LSN: 259412:4438:1, last LSN: 259414:2558:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\MSSQL2000\BACKUP\dc00ewh\dc00ewh_tlog_201205052200.TRN'}).
2012-05-05 22:00:05.75 backup    Log backed up: Database: dc01ewh, creation date(time): 2003/12/20(07:35:56), first LSN: 148161:111611:1, last LSN: 148161:111671:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\MSSQL2000\BACKUP\dc01ewh\dc01ewh_tlog_201205052200.TRN'}).
2012-05-05 22:00:06.48 backup    Log backed up: Database: dc02ewh, creation date(time): 2003/12/20(08:35:34), first LSN: 26862:5493:1, last LSN: 26862:5553:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\MSSQL2000\BACKUP\dc02ewh\dc02ewh_tlog_201205052200.TRN'}).
2012-05-05 22:00:07.14 backup    Log backed up: Database: dc03ewh, creation date(time): 2007/08/09(13:32:06), first LSN: 122830:48026:1, last LSN: 122830:48086:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\MSSQL2000\BACKUP\dc03ewh\dc03ewh_tlog_201205052200.TRN'}).
2012-05-05 22:00:07.79 backup    Log backed up: Database: TMS32, creation date(time): 2006/06/18(21:24:57), first LSN: 42079:12870:1, last LSN: 42079:12870:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\MSSQL2000\BACKUP\TMS32\TMS32_tlog_201205052200.TRN'}).
2012-05-05 22:01:59.30 server    Error: 17883, Severity: 1, State: 0
2012-05-05 22:01:59.30 server    The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x03D0F1F0.
2012-05-05 22:15:09.17 server    Error: 17883, Severity: 1, State: 0
2012-05-05 22:15:09.17 server    The Scheduler 3 appears to be hung. SPID 0, ECID 0, UMS Context 0x03D04AB0.
2012-05-05 22:15:09.82 spid2     LogWriter: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered.
2012-05-05 22:15:09.82 spid2     Write error during log flush. Shutting down server
2012-05-05 22:15:09.86 spid15    Error: 9001, Severity: 21, State: 4
2012-05-05 22:15:09.86 spid15    The log for database 'msdb' is not available..
2012-05-05 22:15:10.89 spid18    Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2012-05-05 22:15:10.90 spid18    Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2012-05-05 22:15:10.90 spid18    Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2012-05-05 22:15:10.90 spid18    Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2012-05-05 22:15:10.93 spid18    Starting up database 'msdb'.
2012-05-05 22:15:11.68 spid18    702 transactions rolled forward in database 'msdb' (4).
2012-05-05 22:15:11.72 spid18    0 transactions rolled back in database 'msdb' (4).
2012-05-05 22:15:11.73 spid18    Recovery is checkpointing database 'msdb' (4)
2012-05-05 22:30:09.43 spid2     LogWriter: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered.
2012-05-05 22:30:09.43 spid2     Write error during log flush. Shutting down server
2012-05-05 22:30:09.43 spid2     LogWriter: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered.
2012-05-05 22:30:09.43 spid2     Write error during log flush. Shutting down server
2012-05-05 22:30:09.43 spid52    Error: 9001, Severity: 21, State: 1
2012-05-05 22:30:09.43 spid52    The log for database 'tempdb' is not available..
2012-05-05 22:30:09.43 spid17    Error: 9001, Severity: 21, State: 4
2012-05-05 22:30:09.43 spid17    The log for database 'dc00ewh' is not available..
2012-05-05 22:30:09.43 spid52    Error: 9001, Severity: 21, State: 1
2012-05-05 22:30:09.43 spid52    The log for database 'tempdb' is not available..
2012-05-05 22:30:09.51 spid236   Error: 9001, Severity: 21, State: 4
2012-05-05 22:30:09.51 spid236   The log for database 'dc00ewh' is not available..
2012-05-05 22:30:09.51 spid52    Error: 3314, Severity: 21, State: 5
2012-05-05 22:30:09.51 spid52    Error while undoing logged operation in database 'tempdb'. Error at log record ID (82361:160:633)..
2012-05-05 22:30:09.51 spid236   Error: 9001, Severity: 21, State: 1
2012-05-05 22:30:09.51 spid236   The log for database 'dc00ewh' is not available..
2012-05-05 22:30:09.54 spid236   Error: 9001, Severity: 21, State: 1
2012-05-05 22:30:09.54 spid236   The log for database 'dc00ewh' is not available..
2012-05-05 22:30:09.54 spid52    Error: 3449, Severity: 21, State: 1
2012-05-05 22:30:09.54 spid52    An error has occurred that requires SQL Server to shut down so that recovery can be performed on database ID 2..
2012-05-05 22:30:09.56 spid236   Error: 3314, Severity: 21, State: 4
2012-05-05 22:30:09.56 spid236   Error while undoing logged operation in database 'dc00ewh'. Error at log record ID (259414:2701:239)..
2012-05-05 22:30:09.57 spid236   Error: 9001, Severity: 21, State: 1
2012-05-05 22:30:09.57 spid236   The log for database 'dc00ewh' is not available..
2012-05-05 22:30:09.57 spid236   Error: 3314, Severity: 21, State: 5
2012-05-05 22:30:09.57 spid236   Error while undoing logged operation in database 'dc00ewh'. Error at log record ID (259414:2616:17)..
2012-05-05 22:30:09.57 spid274   Error: 9001, Severity: 21, State: 1
2012-05-05 22:30:09.57 spid274   The log for database 'dc00ewh' is not available..
2012-05-05 22:30:09.59 spid274   Error: 3314, Severity: 21, State: 4
2012-05-05 22:30:09.59 spid274   Error while undoing logged operation in database 'dc00ewh'. Error at log record ID (259414:2616:10)..
2012-05-05 22:30:09.59 spid274   Error: 9001, Severity: 21, State: 1
2012-05-05 22:30:09.59 spid274   The log for database 'dc00ewh' is not available..
2012-05-05 22:30:09.59 spid274   Error: 3314, Severity: 21, State: 5
2012-05-05 22:30:09.59 spid274   Error while undoing logged operation in database 'dc00ewh'. Error at log record ID (259414:2616:1)..
2012-05-05 22:30:10.92 spid18    Starting up database 'dc00ewh'.

Answer 3

Hello,

As you can see error 17883 is very common on SQL Server 2000, the fixes I posted were the fixes for SP4 only.   You can see also that Microsoft have released fixes for this error and almost no workarounds. If you consider that SQL Server 2000 is not supported anymore, and no more fixes will be released, I would recommend to consider installing all those fixes and see if the issue disappear as first step.

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

Answer 4

Check this link this may help

http://www.sqlservercentral.com/Forums/Topic515321-5-1.aspx