FIX: The monitor server does not monitor all primary servers and secondary servers when you configure log shipping 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 you must make any registry changes
• The files that are contained in the hotfix package

When you configure log shipping in SQL Server 2005, you may notice that the monitor server does not monitor all primary servers and secondary servers in the following two scenarios:

• When you configure log shipping and database mirroring, you use one server both as the principal server and as the primary server. You use another server as both the witness server and the monitor server. The witness/monitor server does not monitor the principal/primary server.
• You configure log shipping and then add two or more secondary servers to log shipping. The monitor server only monitors the secondary server that you added last. The monitor server does not monitor the other secondary servers.

Cumulative hotfix information

To resolve this problem, install the cumulative hotfix package (build 2153) for 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.

Registry information

You do not have to change the registry.

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 item in Control Panel.

SQL Server 2005, 32-bit hotfix

SQL Server 2005, 64-bit hotfix

SQL Server 2005, 64-bit hotfix for Itanium processors

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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