January 24, 2007 at 9:33 am
Greetings,
Last night our database server (Windows 2000 SP4) running SQL 2000 (SP4) produced the following errors:
1) Error: 0, Severity: 19, State: 0
2) SqlDumpExceptionHandler: Process 69 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 01/24/07 01:27:18 spid 69
*
* Exception Address = 77F8910E (RtlAllocateAndInitializeSid + 0000004C Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 0DBDFF90
* Input Buffer 1146 bytes -
* DECLARE @msg varchar(255) SELECT @msg = 'The attached report is a summ
* ary of the automated maintenance carried out for plan ' + datename(dw
* , getdate()) + ' ' + convert(varchar, datepart(dd, getdate())) + ' '
* + datename(mm, getdate()) + ' ' + convert(varchar, datepart(yy, ge
* tdate())) + ':' + CHAR(13) EXEC xp_sendmail @recipients = '
* (Address removed in post)', @subject = 'SQL Server DB Maintenance Rep
* ort - CPHSQLBO41\DB Cleanup_No Backup (Success)', @message = @msg,
* @attachments = 'g:\MSSQL\LOG\DB Cleanup_No Backup2_200701232255.txt'
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBAFFF 008bb000
* ntdll 77F80000 77FFAFFF 0007b000
* ADVAPI32 7C2D0000 7C331FFF 00062000
.
.
.
.
.
The entire dump is rather lengthy so I thought I would hold off posting it unless asked to do so. Essentially the errors occurred at the end of a nightly database maintenance plan configured as follows:
Optimizations Tab
Reorganize data & index pages (Checked or Yes)
Change free space per page percentage to: 10%
Integrity Tab
Check database integrity (Checked or Yes)
Include indexes (Checked or Yes)
Reporting Tab
Write report a text file in directory: (Checked or Yes and a path specified)
Delete text files older than: 4 Weeks
E-mail report to operator: (Checked or Yes and my email address provided)
Write history to the table msdb.dbo.sysdbmaintplan_history (Checked or Yes)
Limit rows in the table to: 1000 rows for this plan
That is the extent of the maintenance plan which runs nightly. The plan has run without issue for months and has been in place for roughly 2-3 years. Last night however, once the plan had completed successfully, its last step was to email me the results. This appears to be when the error occurred as seen below (taken from DB Cleanup_No Backup2_200701232255.txt in the Log directory).
.
.
.
.
[9] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 2 secs **
[10] Database eCPH_dev: Check Data and Index Linkage...
** Execution Time: 0 hrs, 25 mins, 24 secs **
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Cleanup_No Backup' on 1/24/2007 1:27:18 AM
SQLMAINT.EXE Process Exit Code: 0 (Success)
Emailing report to operator 'Botkin, Michael'
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 0: [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler: Process 69 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
When compared to a previous night's success execution the log should end like this:
.
.
.
.
[9] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
[10] Database eCPH_dev: Check Data and Index Linkage...
** Execution Time: 0 hrs, 25 mins, 14 secs **
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Cleanup_No Backup' on 1/20/2007 1:20:52 AM
SQLMAINT.EXE Process Exit Code: 0 (Success)
Emailing report to operator 'Botkin, Michael'
Apologies for the long read but thus far I've not been able to locate any information online that sounds applicable to this scenario. The access violation error is most likely related to SQL mail attempting to send me the success notice but I would certainly like to find more concrete evidence and possibly leads towards a fix or resolution (if need be). I would like to think that this is a one-time isolated fluke and will have to monitor tonight's execution to determine whether or not this is the case but should it occur again, I would like to have some information with which to work.
Any input or direction that could be provided would be most appreciated. If I find any additional information while searching, I will post the update(s) here.
Thanks in advance,
Michael
January 24, 2007 at 3:39 pm
Thus far SQL Mail appears to be working correctly and no other obvious problems have manifested themselves as a result of the indicent. I'll post any updates.
Thanks,
Michael
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply