I have the following errors on one of 12 databases in our enviroment: After a trojan Horse was detected and quarentined, the replication to the passive database was broken. Also backup is failed and will not complete successfully, that results in not purging the logfiles for this database.
When trying to fix the replication with a full reseed, I get the following error:
MDB12
Failed
Error:
A source-side operation failed. Error An error occurred while performing the seed operation. Error: Communication was terminated by server 'SRV02': Data could not be read because the communication channel was closed.. [Database: MDB12, Server: SRV01.domain.local]
Communication was terminated by server 'SRV02': Data could not be read because the communication channel was closed.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.318.4&t=exchgf1&e=ms.exch.err.Ex4543D9
Exchange Management Shell command attempted:
update-MailboxDatabaseCopy -Identity 'MDB12\SRV01' -DeleteExistingFiles
When performing this operation from EMS the following error occurs:
[PS] C:\Windows\system32>Update-MailboxDatabaseCopy -identity MDB12\SRV01
The attempt to access the registry on machine 'SRV01.domain.local' did not succeed after 10 seconds.
+ CategoryInfo : NotSpecified: (0:Int32) [Update-MailboxDatabaseCopy], RemoteRegistryTimedOutException
+ FullyQualifiedErrorId : A7934919,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopy
Output from Test-ReplicationHealth:
[PS] C:\Windows\system32>Test-ReplicationHealth
Server Check Result Error
------ ----- ------ -----
SRV02 ClusterService Passed
SRV02 ReplayService Passed
SRV02 ActiveManager Passed
SRV02 TasksRpcListener Passed
SRV02 TcpListener Passed
SRV02 DagMembersUp Passed
SRV02 ClusterNetwork Passed
SRV02 QuorumGroup Passed
SRV02 FileShareQuorum Passed
SRV02 DBCopySuspended Passed
SRV02 DBCopyFailed Passed
SRV02 DBInitializing Passed
SRV02 DBDisconnected Passed
SRV02 DBLogCopyKeepingUp Passed
SRV02 DBLogReplayKeepingUp Passed
All other databases are replicating als they should be.
I fear that when I dismount the database and remount it again, it will fail, and not be mounted again. without a passive copy or a recent backup, this will be a big issue.
Anyone a hint or solution for this?