Microsoft KB Archive/946038

= FIX: Error message when you run the sp_dbmmonitorresults stored procedure in SQL Server 2005: &quot;An internal error has occurred in the database mirroring monitor&quot; =

Article ID: 946038

Article Last Modified on 12/26/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



Bug #: 50002182 (SQL Hotfix)



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.



SYMPTOMS
Consider the following scenario:
 * In Microsoft SQL Server 2005, you configure Database Mirroring in high-safety mode with automatic failover on a database.
 * You run the sp_dbmmonitorresults stored procedure on the principal server to make sure that the state of the principal server is set to SYNCHRONIZED.
 * You stop the SQL Server service on the principal server. The mirror database on the mirror server becomes the principal database.

For example, the principal server is named ServerA, and the mirror server is named ServerB.
 * You pause mirroring on the database on ServerA. The database on ServerB is now the principle database. The state of the principal database becomes SUSPENDED.
 * You start the SQL Server service on ServerA.

In this scenario, if you run the sp_dbmmonitorresults stored procedure on the database on ServerB, you receive the following error message:

Msg 32038, Level 16, State 3, Procedure sp_dbmmonitorupdate, Line 180

An internal error has occurred in the database mirroring monitor.

Additionally, if you run the sp_dbmmonitorresults stored procedure on the database on ServerA, you see that the state of ServerA is set to SYNCHRONIZED. However, you expect the state of ServerA to be set to SUSPENDED.



RESOLUTION
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

