FIX: The synchronous database mirroring session status may remain disconnected when you set up synchronous database mirroring but do not configure a witness database and you run a DBCC STACKDUMP command in SQL Server 2005

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Information about whether you must restart the computer after you install the hotfix package
• Information about whether the hotfix package is replaced by any other hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

In Microsoft SQL Server 2005, the synchronous database mirroring session status may remain disconnected. You experience this problem when the following conditions are true:

• You set up synchronous database mirroring but do not configure a witness database. For example, you do not enable automatic failover.
• You run a DBCC STACKDUMP command on the principal database server.

The following error messages are logged in the primary SQL Server error log:The following error message is logged in the witness SQL Server error log:

This problem may occur when any one of the following conditions is true:

• A 17883 error occurs.
• You stop the execution of the SQL Server process when an external debugger is attached to the SQL Server process and is debugging the process.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix. However, the hotfix installation stops and then restarts the MSSQLSERVER service.

Registry information

You do not have change the registry after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2005 32-bit versions

SQL Server 2005 64-bit version

SQL Server 2005 Itanium architecture version

To work around this problem, use one of the following methods:

• Disable trace flag 2544 when the trace flag is enabled.
• Disable minidumps from being created by using the Sqldumper.exe utility.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1.

The Sqldumper.exe utility is one example of a debugger that is typically used when SQL Server threads receive Scheduler errors or other exceptions.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: