Repair or recreate a corrupt repository GlobalManifest.metadata file in Quest vRanger – There is an error in XML document (x, x).
August 16, 2012 Leave a comment
I recently got the following error message from some of my backup jobs in Quest vRanger after one of my CIFs data repositories became out of sync with vRanger. The error I was getting was:
An internal error occurred during execution, please contact Vizioncore support if the error persists. Error Message: There is an error in XML document (1, 1).
I had a stack of backups in this repository and didn’t really want to try and edit the file manually. Renaming the corrupt GlobalManifest.metadata and running one of the backup jobs again created a new GlobalManifest.metadata file but this didn’t include any of the existing savepoints so I looked for another solution.
In the end I found this KB Article, that referenced this post explaining how to use the reposync02.ps1 powershell script to scan and recreate the GlobalManifest.metadata file for the repository. Its a great script. You may need to install Powershell 2 if you are running vranger on an older OS. The Windows 2003 version of Powershell 2 can be found here