Microsoft KB Archive/288562

= XADM: Isinteg Does Not Patch an Information Store That Is Running on a Cluster =

Article ID: 288562

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition

-



This article was previously published under Q288562





SYMPTOMS
After you restore an online backup of the Exchange Server information store to a computer that is running Microsoft Windows NT Server and Microsoft Cluster Server, you may receive a message that states that you need to run the isinteg -patch command when you start the service from Cluster Administrator.



CAUSE
This problem can occur if some of the registry keys are not updated correctly when you run the isinteg -patch command.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server 5.5 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: Isinteg

NOTE: Due to file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4.



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

Keywords: kbhotfixserver kbqfe kbbug kbexchange550presp5fix kbfix kbqfe KB288562

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.