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 (912422)
The information in this article applies to:
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition
Bug #: 409556 (SQL BU Defect Tracking)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. SUMMARYThis 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
SYMPTOMSIn 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: DateTime Server
Microsoft SQL Server 2005 - 9.00.1355.11 (X64) Sep 25 2005 01:44:38 Copyright
(c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT
5.2 (Build 3790: Service Pack 1)
DateTime Logon Error: 18456,
Severity: 14, State: 16.
DateTime Logon Login failed for
user 'Domain\UserID'. [CLIENT:
LocalComputer]
DateTime
spid21s Error: 1474, Severity: 16, State: 1.
DateTime spid21s Database
mirroring connection error 2 'Connection attempt failed with error: '10060(A
connection attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because connected host
has failed to respond.)'.' for
'tcp://sapsb2r3db2.redmond.corp.microsoft.com:5022'.
DateTime spid53 WARNING:
Mirroring not active for database DatabaseName The following error message is logged in the witness SQL Server error log: DateTime Server
Microsoft SQL Server 2005 - 9.00.1355.11 (X64) Sep 25 2005 01:44:38 Copyright
(c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT
5.2 (Build 3790: Service Pack 1)
DateTime Server (c) 2005
Microsoft Corporation.
DateTime
spid16s The Database Mirroring protocol transport is now listening for
connections.
DateTime spid16s
Service Broker manager has started.
DateTime spid17s Bypassing
recovery for database 'DatabaseName'
because it is marked as a mirror database, which cannot be recovered. This is
an informational message only. No user action is required. Note You experience the above problem on SQL Server 2005 x64 Edition
which has 16 GB of memory. CAUSEThis 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.
RESOLUTIONService 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:
913089 How to obtain the latest service pack for SQL Server 2005
Hotfix informationPrerequisitesThere 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 informationThis 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 |
| Msvcp80.dll | 8.0.50727.42 | 548,864 | 14-Oct-2005 | 07:26 | x86 | | Msvcr80.dll | 8.0.50727.42 | 626,688 | 14-Oct-2005 | 07:26 | x86 | | Osql.exe | 2005.90.1518.0 | 51,416 | 21-Jan-2006 | 01:11 | x86 | | Sqldiscoveryapi.dll | 2005.90.1518.0 | 527,064 | 21-Jan-2006 | 01:11 | x86 |
SQL Server 2005 64-bit version |
| Msvcp80.dll | 8.0.50727.42 | 1,097,728 | 14-Oct-2005 | 19:46 | x64 | | Msvcr80.dll | 8.0.50727.42 | 822,784 | 14-Oct-2005 | 19:46 | x64 | | Osql.exe | 2005.90.1518.0 | 83,672 | 21-Jan-2006 | 05:14 | x64 | | Sqldiscoveryapi.dll | 2005.90.1518.0 | 745,688 | 21-Jan-2006 | 05:14 | x64 |
SQL Server 2005 Itanium architecture version |
| Msvcp80.dll | 8.0.50727.42 | 1,385,472 | 14-Oct-2005 | 19:35 | IA-64 | | Msvcr80.dll | 8.0.50727.42 | 1,484,800 | 14-Oct-2005 | 19:35 | IA-64 | | Osql.exe | 2005.90.1518.0 | 123,096 | 21-Jan-2006 | 04:30 | IA-64 | | Sqldiscoveryapi.dll | 2005.90.1518.0 | 1,924,312 | 21-Jan-2006 | 04:30 | IA-64 |
WORKAROUNDTo 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.
STATUSMicrosoft 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.
| Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
|---|
| Keywords: | kbsql2005sp1fix KBsql2005connect kbsql2005engine kbHotfixServer kbsql2005presp1fix kbQFE kbpubtypekc KB912422 kbAudITPRO kbAudDeveloper |
|---|
|