Known issue #QM001738441 should be fixed in 8.2 SP1 build#39. It seems like you are on 8.3 which contains the fix already.
Which version you upgraded from?
The Server was upgraded from 8.2 SP2. The Agent on the affected server that i just upgraded from was 8.2.
There are two most probable causes for this to happen:
- Shavlik dll files need to be reregistered on the target server:
- If reregistering the dll files does not resolve the issue, then the problem could be with the use of the CAB files rather than XML.
Review the following article for more information about this issue: https://kb.bmc.com/infocenter/index?page=content&id=KA322916
Per KA322916, perform the CAB -> XML switch, then rerun Patch Analysis Job and generate the new Deploy Job (NOTE: do not run the old Job, as it will still fail)
Should the same issue persist, review the //target/[RSCD_DIR]/Transactions/log/bldeploy-xxx.log. If you see that the BLPatchCheck2 command still references the cab files ...
cmd=BlPatchCheck2.exe 0 -s -pt 13 "C:\temp\stage\xxx\\shavlik\hfnetchk6b.cab" ...
cmd=BlPatchCheck2.exe 1 "C:\temp\stage\xxx\\shavlik\pd5.cab" ...
... then the steps were not followed correctly; revisit them.
From BBSA Console, Right click on the Server in question and select "Browse" and select "Hotfixes" node from Live Browse view and see if it shows any error or displays all the hotfixes...
We have been using the XML Link for a long time since we upgraded to 8.2.2. and i have tried re-registering the DLL's.
The annoying thing is that this server patched successfully last month.
Check the MSXML version on the target. If this is less than 6.0 SP2 then upgrade it and see if it resolve the issue.