oasysadmin

Systems Administration tech notes

  • Home
  • About
Posts Comments
  • Windows
    • Deployment
    • Active Directory
    • IIS
  • Cisco
  • Exchange
  • General
  • Citrix
  • Uncategorized
  • VMware

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

Advertisement

Filed under VMware Tagged with corrupt repository, GlobalManifest.metadata, Quest, recreate repository, repair repository, reposyn02.ps1, There is an error in XML document, vRanger

8.3 8.4 9 877 877W 2007 2010 Active Directory activesync Allow ASA ASDM backup Cisco Citrix Clean-MailboxDatabase Create Domain Controller dsget ESX Exchange Exchange Management Console Exchange Management Shell export GPMC GPO group policy Group Policy Object HTTPS IIS Install Installation kcc KMS linux Management MDT NTP Office 2010 Patch PDC Emulator PIX Powershell PXE repadmin replication restart Robocopy Router Samsung DCS Compact II SDM Search Service Pack 1 Site to Site SP1 SSH SSL Certificate telnet Time-Service Tunnel update Upgrade Verify VMware VPN vSphere WAS WDS Windows 7 Windows Server 2008 Windows Server 2012 Windows Update winlogon WSUS zone based firewall

Latest Posts

  • Force Manual Synchronisation When Using Azure AD Connect
  • Determine Which Version of Powershell is installed
  • Find Out if an Update, Hotfix or KB is installed on a Windows Server Using Powershell
  • Windows Backup encountered an error. There is not enough space on the disk
  • Delete Temporary Internet Files in All User Profiles

Archive

  • February 2016 (4)
  • October 2013 (1)
  • September 2013 (1)
  • July 2013 (4)
  • June 2013 (1)
  • May 2013 (1)
  • April 2013 (2)
  • March 2013 (4)
  • February 2013 (1)
  • January 2013 (1)
  • December 2012 (1)
  • November 2012 (3)
  • September 2012 (2)
  • August 2012 (3)
  • July 2012 (2)
  • June 2012 (3)
  • May 2012 (1)
  • April 2012 (2)
  • March 2012 (5)
  • February 2012 (6)
  • January 2012 (8)
  • December 2011 (1)
  • November 2011 (4)
  • October 2011 (4)
  • September 2011 (2)
  • August 2011 (2)

Disclaimer

Any information posted in this blog is for use at your own risk. Always make sure that you have adequate backups before making changes to your systems.

Create a free website or blog at WordPress.com.

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy
  • Follow Following
    • oasysadmin
    • Already have a WordPress.com account? Log in now.
    • oasysadmin
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar