System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

More meaningful TS error messages in UI (no more 0x80004005!)

When a task sequence fails, the most common error message that you see is 0x80004005 which is useless. Normally, you get much better information from SMSTS.log file, but there are scenarios when you cannot access SMSTS.log.

There must be a way to provide more meaningful error messages in UI when a task sequence fails.

15 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Panu Saukko shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
Noted  ·  sangeev responded  · 

Thanks for the feedback. We have made some improvements to the task sequence monitoring – adding columns for Exit Code and Action Output to the status view.

We’ve more work to do replacing use of Generic E_FAIL with more meaningful error codes.

Updated by bobmn for sangeev/OSD


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
An error occurred while saving the comment
  • Tom Stack commented  ·   ·  Flag as inappropriate

    How about when the issue with with a package you use the friendly name like Adobe Reader DC instead of D05ooooDA2 I don't know the backend name of all my packages.

  • yannara commented  ·   ·  Flag as inappropriate

    How about transform the real error message from smsts.log directly to the TS progress window?

  • Nicke commented  ·   ·  Flag as inappropriate

    Spit out the packageid or even better - the friendly name when a content chevk fails...

  • M. Wolvetang commented  ·   ·  Flag as inappropriate

    Working with Task Sequences you'll do a lot of troubleshooting. The amount of time required to do this can be minimized when a meaningful error is displayed in the "Task Sequence Error" dialog box. Add a details button that reveals the same line as in the SMSTS log file and include the step in which the error occurred.

Feedback and Knowledge Base