Test-replication throwing exception Windows Failover Clustering encountered a transient error

כל התגובות

• 

  

  0

  היכנס כדי להצביע

  we have 3 mailbox servers with DAG.

  When we run below  command across one,it got failed with below error and other two servers working fine.

  Test-ReplicationHealth -Server ,it throwing below error

  indows Failover Clustering encountered a transient error. Trying the operation again may be successful. Error:
  IsNodeClustered'.
     + CategoryInfo          : NotSpecified: (:) [Test-ReplicationHealth], ExClusTransientException
     + FullyQualifiedErrorId : [Server=,RequestId=f15d7126-089e-42ab-98a3-552d69c419fe,TimeStamp=11/18/2019
    11:47:32 AM] [FailureCategory=Cmdlet-ExClusTransientException] AC2ED50B,Microsoft.Exchange.Monitoring.TestReplicat
   ionHealth
     + PSComputerName        : 

  Also we found multiple warnings as below

  
  

  RPC request to the Microsoft Exchange Information Store service for log truncation failed for database Mailbox Database 0039068123\S. Error: Failed to notify source server about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.

  If anyone is able help me please advice

  ---

  Ashraf

  Reboot the server and try again
  

  • נערך על-ידי Andy DavidMVP, Moderator יום שני 18 נובמבר 2019 13:31 remove server

  יום שני 18 נובמבר 2019 12:37

  תגובה

  |

  ציטוט

  מנחה דיון
• 

  

  0

  היכנס כדי להצביע

  Done.But same result.

  Could you please remove from your post.

  ---

  Ashraf

  
  

  • נערך על-ידי P T Ashraf יום שני 18 נובמבר 2019 12:41

  יום שני 18 נובמבר 2019 12:40

  תגובה

  |

  ציטוט
• 

  

  0

  היכנס כדי להצביע

  Done.But same result.

  Could you please remove from your post.

  ---

  Ashraf

  
  

  Ok, but thats not abuse and shouldnt have been marked as such

  יום שני 18 נובמבר 2019 13:32

  תגובה

  |

  ציטוט

  מנחה דיון
• 

  

  0

  היכנס כדי להצביע

  Thanks Mr. David,

  It was by mistake and tried to undo it.

  
  

  ---

  Ashraf

  יום שלישי 19 נובמבר 2019 04:56

  תגובה

  |

  ציטוט
• 

  

  0

  היכנס כדי להצביע

  Hi Ashraf,

  We helped you remove the domain name in your question, please pay attention next time.

  Please use the following command to check database copies status:

  Get-MailboxDatabaseCopyStatus -Server <MailboxServerIdParameter> | Format-List
  

  Check and make sure Microsoft Exchange Information Store service and Microsoft Exchange Replication service are running on MBX02 and MBX03. You can try to restart the services on two servers.

  Please check the Event Viewer for further analysis. Some related event logs may be generated.

  Regards,
  

  Lydia Zhou

  ---

  Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

  יום שלישי 19 נובמבר 2019 08:24

  תגובה

  |

  ציטוט

  מנחה דיון
• 

  

  0

  היכנס כדי להצביע

  Thanks all for your valuable support.

  It was due to "Remote Registry" service was disabled in the mbx03 server.

  Once it enabled, it started working.

  Regards

  Ashraf

  ---

  Ashraf

  • סומן כתשובה על-ידי P T Ashraf יום שלישי 19 נובמבר 2019 10:24

  יום שלישי 19 נובמבר 2019 10:24

  תגובה

  |

  ציטוט
• 

  

  0

  היכנס כדי להצביע

  It's great that your issue is solved and thanks for your sharing. Here is a brief summary about this issue.

  Issue Symptom

  ==========================================

  Have 3 mailbox servers with DAG.

  When run below command across one,it got failed with below error and other two servers working fine: Test-ReplicationHealth -Server mbx03. It throwing below error "Windows Failover Clustering encountered a transient error. Trying the operation again may be successful."
  

  Also we found multiple warnings as below:

  RPC request to the Microsoft Exchange Information Store service for log truncation failed for database Mailbox Database 0039068123\MBX03. Error: Failed to notify source server 'MBX02' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file

  Cause

  ==========================================

  "Remote Registry" service was disabled in the mbx03 server.

  Solution

  ==========================================

  Enable the "Remote Registry" service and everything works.

  Regards,
  

  Lydia Zhou

  ---

  Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

  יום שלישי 19 נובמבר 2019 13:58

  תגובה

  |

  ציטוט

  מנחה דיון