locked
SCCM Client installation error 1603 RRS feed

  • Question

  • Dear Team,

    I am facing the below issue in more than 20 computers , I have done all the Troubleshooting and all the service are up and running and I found in one blog that it is WMI issue and repaired the same. but still we are unable to install sccm client.

    and found it is related to Windows installer hence checked windows installer was stopped hence I started the same but same issue is persist on the machine,

    kindly help us to solve the same

    Wednesday, August 5, 2015 1:15 PM

Answers

  • In the same folder as the ccmsetup.log, there should be a client.msi.log What does that log show? Anything helpful? Have your tried to manually uninstall the client (ccmsetup.exe /uninstall) and then reinstall it?

    Another option is to try using CCMClean, but it is not supported with current ConfigMan releases.

    Also, how are you installing the client? Which method?

    This thread could be helpful, too.

    -Tony



    • Edited by Tony Chirillo Wednesday, August 5, 2015 1:34 PM
    • Proposed as answer by Joyce L Tuesday, August 11, 2015 9:00 AM
    • Marked as answer by Joyce L Monday, August 17, 2015 10:28 AM
    Wednesday, August 5, 2015 1:29 PM
  • 1603 is a Windows Installer error code that means "Fatal error during installation." Basically, its a generic message that means you need to do some more digging which generally starts with looking at the verbose log file for the installation. In this case, as Tony pointed out, that file in client.msi.log on the system in question. For MSI verbose log files, you need to search for the phrase "return value 3" and search up from there (reference: http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx). Note that the problem could be different on each system. You may get lucky and it may be the same on all though or somewhere in between.


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

    • Proposed as answer by Joyce L Tuesday, August 11, 2015 9:00 AM
    • Marked as answer by Joyce L Monday, August 17, 2015 10:28 AM
    Wednesday, August 5, 2015 1:59 PM

All replies

  • In the same folder as the ccmsetup.log, there should be a client.msi.log What does that log show? Anything helpful? Have your tried to manually uninstall the client (ccmsetup.exe /uninstall) and then reinstall it?

    Another option is to try using CCMClean, but it is not supported with current ConfigMan releases.

    Also, how are you installing the client? Which method?

    This thread could be helpful, too.

    -Tony



    • Edited by Tony Chirillo Wednesday, August 5, 2015 1:34 PM
    • Proposed as answer by Joyce L Tuesday, August 11, 2015 9:00 AM
    • Marked as answer by Joyce L Monday, August 17, 2015 10:28 AM
    Wednesday, August 5, 2015 1:29 PM
  • 1603 is a Windows Installer error code that means "Fatal error during installation." Basically, its a generic message that means you need to do some more digging which generally starts with looking at the verbose log file for the installation. In this case, as Tony pointed out, that file in client.msi.log on the system in question. For MSI verbose log files, you need to search for the phrase "return value 3" and search up from there (reference: http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx). Note that the problem could be different on each system. You may get lucky and it may be the same on all though or somewhere in between.


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

    • Proposed as answer by Joyce L Tuesday, August 11, 2015 9:00 AM
    • Marked as answer by Joyce L Monday, August 17, 2015 10:28 AM
    Wednesday, August 5, 2015 1:59 PM
  • In my case, client install error 1603 was caused by workstation low disk space.
    Friday, January 3, 2020 11:31 AM