Thursday, March 24, 2011

SCCM - MSI Error 1603 error when deploying an application to a standard user.

I recently came across and issue whereby I created a deployable package and it worked fine under admin but kept failing on a users machine.

In the MSI log it would error out with

ISMsiServerStartup Failure, Failed to Initialize script support, Error = 0x80070006
Exit code 1603

The application was deployed using and MSI and it was trying to start up the installscript engine but failed. It seems this application was meant to use a setup.exe to invoke the MSI.

the root cause of this turns out to be the InstallScript DCOM Permissions for any version of IISscript installed. We need to change the Installsheild permissions from executing as the 'interactive user' to executing as the 'Launching User'. this way when he MSI executes and calls the installscript service to start it will start up as the user who kicked off the installer, not as the logged on user (standard user) who doesn't have rights to install software.

AppDeploy have a good write up on this issue.

More info here:
Appdeploy forum
A good video here
Appdeploy Video - Dealing with InstallScript


  1. Hi,

    I think this issue is due to missing dll file of NEWDEV.DLL and not registering the ATL.DLL file check this out, for me it got solved for more than 100 machines which has this 1603 error/MSI installer error/Certificate error/windows embedded or wrong os error (Fatal error during installation).

    Solution 1 :

    Goto command prompt and run SFC /SCANNOW. Make sure that u have i386 dump in the system or copy it from installation media. Check the CBS logs for the error fixed during this process, Make sure u uninstall the sccm using the command CCMSETUP.EXE /UNINSTALL

    Solution 2 :

    Goto command prompt type : REGSVR32 ATL.DLL in windows xp machines and copy the NEWDEV.DLL file in syswow64 in windows 7 64bit and system32 in windows 7 32 bit machines

  2. Error 1603 is "Fatal error during installation" which is really just a term for "Something somewhere went wrong, we don't exactly know what went wrong".

    I've seen other error 1603's when packaging applications since posting this. Often it comes down to different issue and solution each time after extensive testing and log diving.

    I really should of made mention of the specific application I was having issues with as I can't remember it now.

    Thank you for your comment and input. It's always helpful to revise my old posts.

  3. A user can use the Windows search facility from the start menu to locate the missing installation files. It is also required that the user logs on to the computer as administrator to initiate the installation program.

    error 1603

    1. It may not just be the installation files are missing. 1603 could also be a failed custom action or unknown fault in the MSI logic or something missing in the OS. as before 1603 really is a error that requires you to investigate what went wrong.

      You also don't necessarily need to logon to a PC as an administrator to install software. The software need to be executed in a context that has enough rights to install software. This admin context can be achieved through elevation of permissions or logging on as admin. Generally software installations do require admin rights to install software. This is why SCCM is able to deploy software without having to logon to the PC as a local admin, SCCM is running the install in the 'SYSTEM' context which has rights to install.