A Windows Patch-generated deploy job fails against a Windows target. The bldeploy log on the target states:
 

Error Jun 13, 2015 9:17:35 PM BlPatchCheck2.exe failed. Return Code: 1
Error Jun 13, 2015 9:17:35 PM Unable to run the Shavlik packager for generating deployment batch files
Error Jun 13, 2015 9:17:35 PM Parsing of file 'C:\Program Files\BMC Software\BladeLogic\RSCD\Transactions\e9d3033e63a13d46ae67326456b4b253\bldeploy.xml' failed at line 2: no element found
Error Jun 13, 2015 9:17:35 PM Parsing of file 'C:\Program Files\BMC Software\BladeLogic\RSCD\Transactions\e9d3033e63a13d46ae67326456b4b253\bldeploy.xml' failed at line 2: no element found
Error Jun 13, 2015 9:17:35 PM Caught exception during bldeploy.
Error Jun 13, 2015 9:17:35 PM Failed to parse C:\Program Files\BMC Software\BladeLogic\RSCD\Transactions\e9d3033e63a13d46ae67326456b4b253\bldeploy.xml
Error Jun 13, 2015 9:17:35 PM Apply failed, auto rollback failed.

BLPatchCheck2.exe is BSA’s wrapper on top of Shavlik engine files which are used for analysis and well as packaging( which is step prior to deploy).

BSA calls BLPatchCheck2.exe with one of two flags - 0 or 1.
 
BLPatchCheck2.exe 0 – is used for Patch Analysis which uses the Ivanti/Shavlik analysis engine file (stPachAssessment.dll) and generates a Shavlik_results.xml showing analysis results.
BLPatchCheck2.exe 1 - is used for packaging (leverages Shavlik packager stPackager.dll) which does packaging for BSA that essentially provides more information on how to deploy the patches in question, their interdependency, sequence etc.(and generates shavlik config files, batch files for deploy etc).


The error above is seen during deploy and the following things must be checked in these scenarios :

1) The version of MSXML (the version should be MSXML6.0 SP2 and above)

 The BSA documentation details the minimum version of MSXML as required by the RSCD Agent version.  Some detail from the BSA 8.9 documentation:

https://docs.bmc.com/docs/display/public/bsa89/Minimum+hardware+requirements
https://docs.bmc.com/docs/pages/releaseview.action?pageId=489033548
https://docs.bmc.com/docs/display/public/bsa86/Troubleshooting+jobs+issues


Please install an updated version of MSXML 6.0 SP2 on the target server.
Latest KB for MSXML 6.0 SP2 is KB973686
Link : https://www.microsoft.com/en-in/download/details.aspx?id=9774

2) Check whether multiple version of RSCD is installed or not? If they are installed then install RSCD again by removing the older versions.

3) Re-register the Shavlik dlls  (For 8.9.03 add STDeployment.dll and  stPatchAssessment.dll will not be present )
b) run regsvr32 stPackager.dll    and    regsvr32 stPatchAssessment.dll (The regsvr32 should be executed from SYSWOW64 and System32. One each time)

• Re-run the job after following these steps with the option "Preserve Staging Area on Failure" checked in Deploy.
• If the job fails, please raise a support case with the following logs
• bltargetjobmanager*.log and bldeploy*.log from <RSCD_Install>/RSCD/Transaction/logs
• RSCD logs from target server
• Job run logs
• Application server logs
• The zip of the staging folder from the target server.