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

Article ID: 946038 - View products that this article applies to.
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.
Expand all | Collapse all

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.
Back to the top | Give Feedback

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
(http://support.microsoft.com/kb/943656/LN/ )
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
(http://support.microsoft.com/kb/937137/LN/ )
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.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

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
(http://support.microsoft.com/kb/943656/LN/ )
Cumulative update package 5 for SQL Server 2005 Service Pack 2
Back to the top | Give Feedback

REFERENCES

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137
(http://support.microsoft.com/kb/937137/LN/ )
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/LN/ )
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089
(http://support.microsoft.com/kb/913089/LN/ )
How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=71711
(http://go.microsoft.com/fwlink/?LinkId=71711)
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/LN/ )
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/LN/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 946038 - Last Review: December 26, 2007 - Revision: 1.2
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
Keywords: 
kbsql2005engine kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced KB946038
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top