locked
Deployment status shows deployment of package to client failed even though it was successful. RRS feed

  • Question

  • Deployment status shows deployment of package to client failed even though it was successful. Why? It's been like this for days. Message ID 10053, Description: Program failed (download failed). That is not a valid error.

    James A+, Network+, MCP

    Monday, March 16, 2015 3:13 PM

Answers

  • Ultimately, that error code is from the command-line that you are running and is outside of ConfigMgr's control; ConfigMgr is simply reporting it. Thus you need to troubleshoot your command-line. 1603 is the Windows Installer generic error code -- troubleshooting the root cause of this error code almost always involves creating a verbose log file and examining it per Jeff's suggestion. To create a Windows Installer verbose error log, add the /l*v option to your command-line with the name of the output file to create (of course this assume that your msi isn't wrapped in an exe in which case you'll need to do some research).

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

    • Proposed as answer by Daniel JiSun Tuesday, March 31, 2015 1:37 AM
    • Marked as answer by Daniel JiSun Wednesday, April 1, 2015 1:08 AM
    Monday, March 16, 2015 6:45 PM

All replies

  • Examine execmgr.log on the client. 

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, March 16, 2015 3:15 PM
  • I did it is error 1603. Which is least helpful.

    James A+, Network+, MCP

    Monday, March 16, 2015 3:18 PM
  • Are you creating an MSI log? If so, search the log for Return Value 3.  Just above that will be the actual error.

    Jeff

    Monday, March 16, 2015 4:09 PM
  • Ultimately, that error code is from the command-line that you are running and is outside of ConfigMgr's control; ConfigMgr is simply reporting it. Thus you need to troubleshoot your command-line. 1603 is the Windows Installer generic error code -- troubleshooting the root cause of this error code almost always involves creating a verbose log file and examining it per Jeff's suggestion. To create a Windows Installer verbose error log, add the /l*v option to your command-line with the name of the output file to create (of course this assume that your msi isn't wrapped in an exe in which case you'll need to do some research).

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

    • Proposed as answer by Daniel JiSun Tuesday, March 31, 2015 1:37 AM
    • Marked as answer by Daniel JiSun Wednesday, April 1, 2015 1:08 AM
    Monday, March 16, 2015 6:45 PM