Have you guys tried executing the same kind of thing in a power shell script instead of a batch file in an attempt to "eat" error code 63?
I would think this would work fine, but I am running into some issues where the compare works, but any output I request does not.
I am passing parameters for the script file output, html report as well as trying to limit the scope of the compare using a filter file. When passing this directly to the command line, it works fine.
However, when trying to pass all of this through a power shell script, I receive no errors, the compare works, but it ignores my filter file, does not output the script file and it does not save the html report.
I am going to submit a support ticket and provide you the power shell script I am trying to run.