There is an error in XML Document (1, 1851) when initially referencing recent jobs (4034828)

The following situation reoccurs even though it seemingly does not affect Ranger functionality.

Ranger GUI opens, view switched to My Jobs, Successful/Failed/Canceled/Aborted Tasks are selected.

System Error: An internal error occurred during execution, please contact Quest support if the error persists. Error message: There is an error in XML document (1, xxxx).

xxx number is usually greater than 1000. In particular case it was 1851. Since error refers to 1st line in xml document, assumption is that it is related to VmConfig.metadata because this file is relatively big and does not contain CR/LF. It is a long single line.

Customer confirmed that he had rolled back from Ranger version 6.0.1 to 6.0.0.

In 6.0.1 Developers introduced few new VM configuration objects that can be serialized. One of them is "tools.lastInstallInfo.fault". Below is an example of this setting from the VmConfig.metadata file:

tools
  lastInstallInfo
      counter
      fault
         fault xsi:type="ConcurrentAccess"
         localizedMessage = Cannot complete operation due to concurrent
                modification by another operation.

Ranger 6.0.0 would not be able to backup VM with the setting above. Error would be: "Database trasaction was rolled back."

Customer successfully backed up VM with this setting using Ranger 6.0.1. Then he created and ran a restore job from this savepoint. At some point in time there was a need to rollback to a previous (6.0.0) version. When Successful/Failed/Canceled/Aborted Tasks are selected, Ranger perfroms some kind of check up against restore job configuration. Part of this checkup is a validation of the savepoints. Ranger 6.0.0 finds tag that it has no instructions how to handle and throws an original error message.

There are few possible ways:

1. Definitely Ranger 6.0.1 and greater won't display this error because they are familiar with this tag/setting.
2. This error can be ignored. Unless restore job from one of these savepoints should be executed. This has not been tested. Chances are job will fail.
3. Culprit block can be deleted from the SavePointXml table. Below is SQL command for <fault> tag.
   

   UPDATE SavePointXml
   SET VMConfigurationXml.modify('delete /*/VMConfig/*:tools/*:lastInstallInfo/*:fault[1]')
   WHERE VmConfigurationXml.value('/*[1]/VMConfig[1]/*:tools[1]/*:lastInstallInfo[1]/*:fault[1]', 'varchar(80)') IS NOT NULL