myITforum.com : Non-Zero EXIT Codes

The program for advertisement "WHQ2010A" failed ("Security - Authorized Workstation Updates" - "Security - Authorized Workstation Updates"). A non-zero exit code of 1073807364 was returned.

Or maybe you see the equally informative exit code of "3221225478" or maybe the other little gem "128".

Well I've ignored these long enough and decided to find out just what they were really telling me. In my case I get these every time I advertise new security patches via SMSFP. They occur on a small percentage of the client base, and eventually the patches do get installed, so I generally ignore them for awhile... but here's the "why".

First off, I have a lot of SMS clients across a wan link to both their CAP and DP(s), so they are all trying to execute the scan and patch install jobs remotely. That in itself makes things ugly... On many of the clients where I see the errors I also see Event ID 1000 returned by USERENV nearly instantly after the SMS job kicks off:

For the USER: <machine_name>\SMSCliToknAcct&

Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.

DETAIL - Access is denied. , Build number ((2195)).

This is then followed by the SMS Advert Error status message with one of these three bogus number included.

Here's what I found from a chat with PSS:

128 - "No child processes"
1073807364 - "Cannot open file"
3221225478 - (haven't got a definitive answer back as I write this, but I'm betting it's similar to the two above!)

Here's the bottom line as I see it. The advert kicks off, using the <machine_name>\SMSCliToknAcct& credentials to run the job. The client then uncovers the problem documented in Q816967, rendering the local SMS account unusable for the moment, which then causes the SMS program execution to fail, essentially because <machine_name>\SMSCliToknAcct& cannot access the necessary files in the package, returning the oddball non-zero exit codes. You will also typically see that neither SecurityPatch.log or PatchInstall.log is even touched.

Add to the equation (in my case) clients WAN remote from the DP and you now introduce yet another boatload of variables that can all result in file access issues when the advert tries to run. I believe this will also cause similar errors even without the Event ID 1000 issue... generating the same non-zero exit codes.

By the way! Do a GOOGLE search on these exit code numbers. GOOD LUCK finding a translation!


		myITforum.com ©2010 \| Legal \| Privacy