FileSync SyncManifest.xml Corruption

Follow

SecureAuth FileSync Version Affected:  4.0.9 and higher

 

Description:

FileSync is no longer syncing and Application event logs are showing Event ID 7117 “Error executing job. System.Exception: Error syncing realms.  System.Exception: Unable to deserialize manifest from “D:\SecureAuth\SecureAuth0\SyncManifest.xml”. Upon investigation of the SyncManifest.xml part or all of the file contents are missing.

 

Cause:  

SyncManifest.xml has become corrupt or blank.

 

Resolution: 

Follow these steps to recreate SyncManifest.xml:

  1. Stop the FileSync Service on all IdP’s
  2. On the Filesync master, rename D:\SecureAuth\SecureAuth0\SyncManifest.xml to SyncManifest_old.xml
  3. Start the FileSync Service on the Master, then the remaining IdP’s
  4. Upon next sync a new SyncManifest.xml will be created on each IdP
  5. Verify in the Application Event log that Sync is starting and completing successfully

 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

3 out of 3 found this helpful

Comments

0 comments

Article is closed for comments.