Share via

Software Centre Status Failed Error code meanings

  • Article

Question

Wednesday, August 5, 2015 8:55 AM

Hi,

I found a list which described all the error codes which Software Centre throws back when application installs/unistalls fail. Stupidly I did not save this and now I cannot find it. Does anyone have the list describing what each error code means?

Thanks.

All replies (5)

Wednesday, August 5, 2015 9:26 AM ✅Answered

This?
http://anoopcnair.com/2012/04/20/sccm-configmgr-2012-how-to-read-log-files-cmtrace-exe-vs-trace32-exe/

Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Thursday, August 6, 2015 2:09 AM ✅Answered

Thanks guys, all a great help.

That's what I was after Don! I just re-found the page I saw before as well which includes information on how to extract the error codes yourself:

https://social.technet.microsoft.com/Forums/en-US/0aa25d02-3163-4628-84f7-87b77a1de85b/sccm-2012-view-or-table-that-has-error-code-details?forum=configmanagerapps

I was having an issue with an application not uninstalling. You can search for the 0x87D01280 code in AppEnforce.log using CTRL+L but no logs seem to have the -2016406912 (which was the only error code I had written down so that's why i was trying to find that one).

Cheers.

Wednesday, August 5, 2015 11:22 AM

You could also simply use cmtrace.exe.

Start cmtrace and press CTL+L enter the error code and do lookup.

Wednesday, August 5, 2015 1:13 PM | 1 vote

There's no magic list:

http://blog.configmgrftw.com/error-codes/

Jason | http://blog.configmgrftw.com | @jasonsandys

Thursday, August 6, 2015 2:58 AM | 1 vote

-2016406912 = 0x87D01280

They are one in the same. The first is a decimal representation in two's complement (I believe) of the hex code and is thus shown as a negative number. CMTrace knows this and adjust appropriately. That's why simply having a table is useless aside from the fact that it will never be complete. CMTrace is great but it's not necessarily complete either and there are many other ways to define and interpret error codes which was the purpose of my blog post.

Jason | http://blog.configmgrftw.com | @jasonsandys