Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot move a mailbox database to an Exchange Server 2010 cluster node that is part of a database availability group when you try to install a hotfix or an update rollup for Exchange Server 2010


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You try to install a hotfix or an update rollup for Microsoft Exchange Server 2010 on Exchange Server cluster nodes that are part of a database availability group.
  • You upgrade the passive node, and then you restart the server.
  • You move the active mailbox database to the passive node that was upgraded.
In this scenario, you cannot move the active mailbox database to the passive node. Additionally, you receive the following error message:
PS] C:\Windows\system32>Update-MailboxDatabaseCopy db1\mbx1 -CatalogOnlyserver-side seed operation has failed. Error: An error occurred while performing the seed operation, which may indicate a problem with the source disk. Error: An error occurred while updating the search catalog files from server 'MBX2' to 'MBX1'. Error: Can't pause the search catalog. Error: Microsoft.Exchange.Search.Common.FteCatalogN
tFoundException: SearchCatalog.PauseIndexing failed, error 0x80043629 ---> System.ComponentModel.Win32Exception: Unknown error (0x80043629)
  --- End of inner exception stack trace ---
  at Microsoft.Exchange.Cluster.Replay.SearchCatalogProxy.PauseIndexing()
  at Microsoft.Exchange.Cluster.Replay.CiFilesSeederInstance.<SeedThreadProcInternal>b__3(Object , EventArgs )
  at Microsoft.Exchange.Cluster.Replay.CiFilesSeederInstance.RetryCiOperation(EventHandler evt) [Database: db1, Server: MBX1.tails.com]
   + CategoryInfo          : InvalidOperation: (:) [Update-MailboxDatabaseCopy], CiSeederGenericException
   + FullyQualifiedErrorId : F03D6D,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopy

↑ Back to the top


Workaround

To work around this issue, use the following command to move the active mailbox database to the passive node:
Move-ActiveMailboxDatabase <Database Name> -ActivateOnServer <Server Name> -skipclientexperiencechecks

Note You can check whether the search catalog is up to date by using the -skipclientexperiencechecks parameter. If you skip the search catalog check by using the parameter in the Move-ActiveMailboxDatabase command, you must either recrawl or reseed the search catalog.

↑ Back to the top


Resolution

This hotfix is scheduled to be included in Exchange Server 2010.

↑ Back to the top


More information

For more information about the Move-ActiveMailboxDatabase command, visit the following Microsoft Web site:

↑ Back to the top


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


Keywords: KB977952, kbsurveynew, kbtshoot, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 977952
Revision : 2
Created on : 12/18/2009
Published on : 12/18/2009
Exists online : False
Views : 378