CA Client Automation

When deploying a UPM Cumulative patch that includes multiple patches, the Job Output shows errors for individual patches that failed to install. 

They are signed decimal numbers. i.e. -2147221164 is common.

Is there a list of what these codes mean?

I found a few articles that say to convert them to HEX, but when I do this the HEX conversion does not match any of the published error codes. 

List of Error Codes:

https://support.microsoft.com/en-us/help/938205/windows-update-error-code-list 

Conversion Instructions:

Run CALC.exe, place CALC into "Programmer" mode (View, Programmer)
Set CALC.exe into "Dec" mode (Decimal)
Paste the decimal value: -2145124329 
Click "Hex" (the conveted result is shown: FFFFFFFF80240017)
Open cmtrace tool
Press CTRL+L (open error lookup utility)
Paste converted Hex value (remove the leading FFFFFFFF)
Click "Lookup" button (error lookup result is displayed)

(Also used some online Decimal to HEX converters all with the same results).

Thank you,

Jeff

Hi Jeff,

If you can grab the TRC_USD_SDAGENT_x.log from one of the systems reporting this error, we can see if the return code recorded in the SD Agent log is any different-- possibly something got changed in translation of the actual return code here.

We'll be looking for a line like this in the SD Agent log:

Line 4302: 310517-09:40:51.7019342L|012952|00003d70|SDAgent   |                |sdjecontainerif.cpp |001402|NOTIFY | SDjob 1 returns: 0 ExitCode: 0

Regards,

Brian

Hi Brian,

I found the record, but it only returns the final exit code of the install script that we see in the DSM Explorer's Status Message for in the Job Container. (Exit Code 1).

          |sdjecontainerif.cpp |001384|NOTIFY |SDjob 1 returns : 1 ExitCode:1

I need an explanation of the code for these codes highlighted below:

10 out of 188 patches require installation

The Number of patches to install: 10

Rollup batch script error code: 1

Not all patches installed successfully

Windows6.1-KB3185911-x64.msu error code: 126

Windows6.1-KB3192391-x64.msu error code: -2145116147

Windows6.1-KB3188730-x64.msu error code: -2145116147

Windows6.1-KB3197867-x64.msu error code: -2145116147

Windows6.1-KB3205394-x64.msu error code: -2145116147

Windows6.1-KB3212642-x64.msu error code: 126

Windows6.1-KB4012212-x64.msu error code: -2145116147

ie11-windows6.1-kb4014661-x64.msu error code: -2145116147

windows6.1-kb4014573-x64.msu error code: 126

windows6.1-kb4015546-x64.msu error code: -2145116147

Number of patches installed successfully : 0

All required patches failed to install. No Reboot required.

Thank you Brian

Hi Jeff,

The ONLY time I have seen this is during the implementation at your current employer. At that time, it occurred only during initial build after the OSIM image was applied, and the job was successful on rerun. We were unable to identify the cause, We surmised it may be something do to with policies which were being applied after the re-image and during the initial package push. We tried moving the rollup earlier and later in the job sequence but it didn't seem to help. Your windows admins were supposed to contact MS for help since it is their jobs which are failing, not ours, but they never did.

As far as I can recall, we did find that the code being reported IS the actual error code coming from wusa.exe, but we could not find it documented anywhere, hence MS support would need to be involved to find the cause. After all our research (which was quite exhaustive), we concluded this was something environmental and transient, and required Microsoft support.

I don't know if it would make any difference, but have you tried switching to intellirollups? The exact same patches would be installed, but the payload transferred is smaller and each patch runs in a separate shell (as opposed to all of them running from a single batch file built by and called from our rollup script) since each is delivered as a separate package. Might be worth a shot.

Regards

Steve

On Google there were some links that talked about gpo settings

Sent from my Verizon, Samsung Galaxy smartphone

Hi Jeff,

Exit Code -2145116147 is Hex value 8024200D which is a Microsoft Update handler error meaning:

"0x802400D WU_E_UH_NEEDANOTHERDOWNLOAD The Update handler did not install the update because it needs to be downloaded again."

Exit Code 126 is a Windows System exit code meaning:

"126 The specified module could not be found."

OK, very interesting. Perhaps something is getting corrupted during transmission or unpacking then, or perhaps the source is being removed somehow during the job?

I really think switching to intellirollups then might help since each package is downloaded and run independently. Definitely worth a shot I would think!

Steve

Richard sent me a link that had another link in the thread. 

This link has a list of the HEX and DEC Error Codes.

Windows Update Codes