What is the logging type in the job. Can you change it to all information and see if adds more details to log.
Can you search for that exit code on the BMC KB ? there should be some KB articles about that.
We set logging to All Information, and still have the same results with no additional logs in the results displayed in the console or the rscd.log on the target.
Tell me if you by any chance have the following file in c:\windows or c:\windows\system32 folder: xerces-c_2_8.dll or xerces-c_2_7.dll
Also tell us if bltargetjobmanager-xxx.log was generated, and if you see any errors there.
Also see if there are any errors in the Event Viewer during this failure
Neither file exists in c:\windows or c:\windows\system32.
no bltargetjobmanager-xxx.log file was generated.
no errors in Event Viewer.
Email us the PATH variable from the target system.
Upgrading the agent on the target to 18.104.22.1681 solved the issue. Patch deployment was successful.
hmm, I don't see a connection. What is the appserver version, and what was the agent version before the upgrade (just so we know which combination to watch out for)?
App server version is 8.2.01.290. Agent version prior to upgrade was 22.214.171.1240.
Michael C. Cook, CTR
Dell Services Federal Group
US Coast Guard Operations Systems Center