SQL Server Q&A

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘divide by zero’

FIX: A minidump file is generated, and an error message is logged in the SQL Server error log when you run the DBCC MEMORYSTATUS statement in SQL Server 2005

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you run the DBCC MEMORYSTATUS statement in Microsoft SQL Server 2005, a minidump file is generated. Additionally, the following error message is logged in the SQL Server 2005 error log:

Date Time SPID ***Stack Dump being sent to T:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
Date Time SPID SqlDumpExceptionHandler: Process 128 generated fatal exception c0000094 EXCEPTION_INT_DIVIDE_BY_ZERO. SQL Server is terminating this process.
Date Time SPID *
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 07/27/07 09:55:00 spid 128
Date Time SPID *
Date Time SPID *
Date Time SPID * Exception Address = 0000000001911CC8
Module(sqlservr+0000000000911CC8)
Date Time SPID * Exception Code = c0000094
EXCEPTION_INT_DIVIDE_BY_ZERO

FIX: A minidump file is generated, and an error message is logged in the SQL Server error log when you run the DBCC MEMORYSTATUS statement in SQL Server 2005

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you run the DBCC MEMORYSTATUS statement in Microsoft SQL Server 2005, a minidump file is generated. Additionally, the following error message is logged in the SQL Server 2005 error log:

Date Time SPID ***Stack Dump being sent to T:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
Date Time SPID SqlDumpExceptionHandler: Process 128 generated fatal exception c0000094 EXCEPTION_INT_DIVIDE_BY_ZERO. SQL Server is terminating this process.
Date Time SPID *
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 07/27/07 09:55:00 spid 128
Date Time SPID *
Date Time SPID *
Date Time SPID * Exception Address = 0000000001911CC8
Module(sqlservr+0000000000911CC8)
Date Time SPID * Exception Code = c0000094
EXCEPTION_INT_DIVIDE_BY_ZERO

BUG: Perfmon Terminates While Monitoring SQL Procedure Cache

Symptoms
If you shut down SQL Server while you are monitoring any SQL Server -Procedure Cache counter in Performance Monitor (Perfmon.exe), Perfmon.exeand Winlogon.exe close with a Divide By Zero Exception error. If you runPerfmon.exe on the Windows NT console, an Unhandled Exception error inSQLCTR60.DLL appears in Perfmon.exe.
If you monitor the counter in Perfmon.exe from a client computer, theException error occurs in Winlogon.exe and a STOP: 0xc000021a (Fatal SystemError) screen appears.
In addition, the following Application event appears in Event Viewer:

Event ID: 8Source:SQLCTR60.DLLDescription: DB-LIBRARY error: Attempt to bind to a non-existent column.
Resolution
To work around this problem:Do not monitor SQL Server – Procedure Cache counters when you shut down SQL Server.
-or-Use “On Demand Mode” for SQL Server Perfmon Integration. For moreinformation, see the “Integration with Windows NT Performance Monitor”section in the SQL Server Administrator’s Companion guide.