it looks like the patch failed to install. have you looked for that exit code on the bmc kb or google to see what it indicates ?
you can see more detailed log entries in the 'bldeploy' log which is in the <install>\Transactions\log directory on the target.
Looks like this sometimes happens, and is potentially related to permissions on the agent. Found this when looking in the KB for your error message:
I'd start with who the agent is mapping to.
Bill there are no other details on the target.
Sean what do you mean agent is mapping to?
I have a similar environment where I use this smb url and it work just fine. The only difference is there I use a local account: smb://server_name;local_user:password@server/share/folder while here I use
In both situations this accounts are part of the Administrators Group on that server.
As well I have no problem browsing that share with Windows Explorer using same domain credentials.
Anything else I could look into?
so there is no bldeploy log for this job run in the <install>/RSCD/Transactions/log folder on the target?
there is nothing in the <install>/RSCD/rscd.log file from when this job runs on the target ?
is the server w/ the share in the domain you are using ? are there any authentication errors in the event logs on the share server or domain ?
i find it hard to believe there is only the job run log entry here. what about running the deploy job w/ the DEBUG_MODE_ENABLED property set to true ? then go look in <install>/NSH/tmp/debug on the appserver(s) that ran the job.
The exit code -2146959355 (0x80080005) is coming from the patch installation itself.
Error code 0x80080005 (CO_E_SERVER_EXEC_FAILURE)
Google for 0x80080005 MS13-082 or 0x80080005 KB2861191 produces no hits.
Google for 0x80080005 or CO_E_SERVER_EXEC_FAILURE produces some hits, and it does look like it could be permissions related.
Depending upon the version of .NET Framework installed, there may be patch install log with further details