Everyone should know that the previous recommendations from Quest were to increase the CPU Reservations to 1500 on ESX servers for the best performance from vRanger.
I just recently ran across an article (here) from Sept 2011 detailing that this is NOT the case for ESXi. There is no performance gain on ESXi by increasing the CPU reservations from the default 293.
------
Dustin Shaw
VCP
Thursday, July 19, 2012
vRanger error "There is an error in XML document"
I ran into an issue with one of our repositories - every job in the particular repository was failing with the error:
An internal error occurred during execution, please contact Quest support if the error persists. Error Message: There is an error in XML document (823, 223).
This error is commonly caused by a corruption or issue with the manifest file as detailed here.
To fix it, go into the manifest file for the repository (GlobalManifest.metadata), make sure that all trailing brackets are closed, and add </vRangerGlobalManifestFile> at the end of the document.
Save and test.
------
Dustin Shaw
VCP
An internal error occurred during execution, please contact Quest support if the error persists. Error Message: There is an error in XML document (823, 223).
This error is commonly caused by a corruption or issue with the manifest file as detailed here.
To fix it, go into the manifest file for the repository (GlobalManifest.metadata), make sure that all trailing brackets are closed, and add </vRangerGlobalManifestFile> at the end of the document.
Save and test.
------
Dustin Shaw
VCP
Subscribe to:
Posts (Atom)