When I try to install the SCCM client on some machines I get an installation error 1603. Setup starts ok, but after a while ends in a 1603 error. ccmsetup.log ...... MSI: Action 13:45:12: AllocateRegistrySpace. Allocating registry spaceccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: ProcessComponents. Updating component registrationccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: UnpublishComponents. Unpublishing Qualified Componentsccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: UnpublishFeatures. Unpublishing Product Featuresccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: SmsTSManagerStopServiceInit. ccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: CcmStopService. ccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: StopServices. Stopping servicesccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: SmsStopUIComponents. Stopping UI Componentsccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)MSI: Action 13:45:12: StopDeleteWUSER32. Stopping and deleting WUSER32 serviceccmsetup14/07/2008 13:45:12 PM2532 (0x09E4)Installation failed with error code 1603ccmsetup14/07/2008 13:45:12 PM2532 (0x09E4) There were no previous SMS/SCCM clients installed. Tried a new install after the rebuild of WMI but without any luck.

That part of the logfile does not contain the reason why it was failing. The error happened earlier. 1603 translates to "Fatal error during installation."

1603 is a generic error. I have never seen it for client installs but for other msi files you can look at the msi log for details. that's normally in %temp% during other install but not sure in client installs if it's there or not

In the same folder as the ccmsetup.log, there should be a client.msi.log. Search in this log for "value 3" that is the value an msi returns when it fails which eventually shows up in ccmsetup.log as 1603. The first "value 3" entry (if there is more than 1) in the client.msi.log is where your error occured - the lines above this entry should tell you what failed.

Just had a look in client.msi.log and it fails on: StopDeleteWUSER32. Return value 3. Hope this makes sense.

Please include the ten lines above "StopDeleteWUSER32. Return value 3" from the client.msi.log. Thanks.

Thanks, here it is: ===================================================== Action start 12:25:44: StopServices.MSI (s) (0C:BC) [12:25:44:170]: Skipping action: SmsUninstallPrepDrvr (condition is false)MSI (s) (0C:BC) [12:25:44:170]: Skipping action: SmsUninstallPrepDrvrX64 (condition is false)MSI (s) (0C:BC) [12:25:44:170]: Skipping action: SmsUninstallPrepDrvrAMD64 (condition is false)MSI (s) (0C:BC) [12:25:44:170]: Skipping action: SmsSwDistCacheDirDelete (condition is false)MSI (s) (0C:BC) [12:25:44:170]: Doing action: SmsStopUIComponentsAction ended 12:25:44: StopServices. Return value 1.Action start 12:25:44: SmsStopUIComponents.MSI (s) (0C:BC) [12:25:44:186]: Doing action: StopDeleteWUSER32Action ended 12:25:44: SmsStopUIComponents. Return value 1.MSI (s) (0C:4C) [12:25:44:201]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSI265.tmp, Entrypoint: StopDeleteWUSER32Action start 12:25:44: StopDeleteWUSER32.MSI (s) (0C:BC) [12:25:44:201]: Machine policy value 'DisableRollback' is 0MSI (s) (0C:BC) [12:25:44:201]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 12:25:44: StopDeleteWUSER32. Return value 3. =====================================================

From what I could gather, the "StopDeleteWUSER32 action" stops and deletes the Wuser32 service(surprise!) which isthe older remote control solution. For some reason this is failing, possibly the service is running or somehow locked. I would look at the services on these machines and see if wuser32 is listed, if so stop and delete it manually. Sorry I am not more help here, but without seeing a machine where this is failing, it is very difficult to guess why. Good luck, and maybe someone else has an idea. If you findthe cause of this issueplease let this post know.

I'm having this same problem with several PCs. I have the same error messages in ccmsetup and client.msi and it is failing at the same spot as discussed above. The SCCM client is not installed at all (no older version installed, no old client files hanging around or anything) on these machines. I see no WUSER32 service on these machines (nor any other SMS-related services). Additionally, earlier in the CCMSETUP.LOG it appears that the installation process is aware that no client is currently installed:No client is currently installed.7/30/2009 10:41:47 PMInstalling version 4.00.6221.1700 of the client with product code {0CB63ED9-8B6C-4312-B214-8AE8896DCC25}7/30/2009 10:41:59 PMSo... there's no way for me to stop/delete the WUSER32 service automatically, since it doesn't exist... any other ideas anyone?Thanks! --Jo

1603 is a generic msi error, check the ccmsetup.log but you will likely not find anything helpful there, also check the windows installer log located at %temp%. If you can't figure it out post errors from those logs or email them to me offlineJohn Marcum, Systems Management Consultant - www.TrueSec.com

Hi John,The client.msi.log shows this error (same as above):---------------------------------------------------------------Action start 23:52:25: StopDeleteWUSER32.MSI (s) (08:1C) [23:52:26:037]: Machine policy value 'DisableRollback' is 0MSI (s) (08:1C) [23:52:26:037]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 23:52:26: StopDeleteWUSER32. Return value 3.---------------------------------------------------------------At the bottom of the ccmsetup.log it ends with this error:---------------------------------------------------------------MSI: Action 23:52:25: StopDeleteWUSER32. Stopping and deleting WUSER32 service8/20/2009 11:52:25 PMInstallation failed with error code 16038/20/2009 11:52:26 PMNext retry in 120 minute(s)...8/20/2009 11:52:38 PM---------------------------------------------------------------I'm having trouble locating a windows installer log. The %temp% folder would be in docs&settings\userid\local settings\temp, I would assume and I've looked through the folders for the acct that is doing the client install as well as all the other acct folders and can't seem to locate any logs with a current date/time stamp. Any idea where I would look?Also, BTW, I reinstalled MSI 4.5 before I did this last client installation, but I did it remotely/silently, so no prompts or data returned... I just found the errors below in the\windows\KB942288-v3.log file... might be related?--------------------------------------------------------------4.140: 2009/08/20 23:44:40.146 (local)4.140: e:\6c0499dd2b70eebd34aa8b8c33\UPDATE\update.exe (version 6.3.13.0)4.172: Hotfix started with following command line: /quiet /norestart 4.187: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with error 0x28.578: In Function TestVolatileFlag, line 11825, RegOpenKeyEx failed with error 0x28.578: In Function TestVolatileFlag, line 11857, RegOpenKeyEx failed with error 0x28.578: DoInstallation: CleanPFR failed: 0x2 8.593: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with error 0x28.593: SetProductTypes: InfProductBuildType=BuildType.IP8.593: SetAltOsLoaderPath: No section uses DirId 65701; done.8.718: DoInstallation: FetchSourceURL for e:\6c0499dd2b70eebd34aa8b8c33\update\update_SP3QFE.inf failed8.718: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallKB942288-v3$ 8.718: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe00001028.734: BuildCabinetManifest: update.url absent8.750: Starting AnalyzeComponents8.750: AnalyzePhaseZero used 0 ticks8.750: No c:\windows\INF\updtblk.inf file.8.750: OEM file scan used 0 ticks10.812: AnalyzePhaseOne: used 2062 ticks10.812: AnalyzeComponents: Hotpatch analysis disabled; skipping.10.812: AnalyzeComponents: Hotpatching is disabled.10.812: FindFirstFile c:\windows\$hf_mig$\*.*16.500: AnalyzeForBranching used 0 ticks.16.500: AnalyzePhaseTwo used 0 ticks16.500: AnalyzePhaseThree used 0 ticks16.500: AnalyzePhaseFive used 0 ticks16.515: AnalyzePhaseSix used 15 ticks16.515: AnalyzeComponents used 7765 ticks16.515: Downloading 0 files16.515: bPatchMode = FALSE16.515: Inventory complete: ReturnStatus=0, 7797 ticks16.515: Num Ticks for invent : 779716.547: VerifyTargetFileSize: Unable to verify size as Source = NULL for file c:\windows\inf\HFX269.tmp16.578: Copied file: c:\windows\inf\branches.inf38.625: Allocation size of drive C: is 4096 bytes, free space = 4751011840 bytes38.625: Drive C: free 4530MB req: 5MB w/uninstall 0MB38.625: CabinetBuild complete38.625: Num Ticks for Cabinet build : 2211038.625: DynamicStrings section not defined or empty.38.656: FileInUse:: Detection disabled.38.656: FileInUse:: Add to list - Service Name: msiserver39.656: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe000010240.015: Copied file: C:\WINDOWS\system32\spmsg.dll40.125: PFE2: Not avoiding Per File Exceptions.41.734: DoInstallation: Installing assemblies with source root path: e:\6c0499dd2b70eebd34aa8b8c33\41.734: Num Ticks for Copying files : 310941.812: Num Ticks for Reg update and deleting 0 size files : 7841.828: DoInstallation: ApplyAdminSystemAclsRecursive for c:\windows\$hf_mig$\KB942288-v3 failed; error=0x0000000341.843: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.43.187: RebootNecessary = 0,WizardInput = 1 , DontReboot = 1, ForceRestart = 0---------------------------------------------------------------Thanks again!! --Jo

After much searching of multiple forums for the 1603 error, I found an entry where someone suggested the following: 1) Uninstall the SCCM client from the target computer 2) Open a command line on the target and type REGSVR32 ALT.DLL <enter> 3) Reinstall the client using CCMSETUP I have used this to fix dozens of failed client installs having the 1603 error. I also wish I could give credit to the one who originally posted the fix. I'll dig around and see if I can find their handle.... Regards, Jon

Thanks so much for the tip, Jon. I tried it on one of my failing machines and it worked for me too. --Jo

Hi jon, Thankyou for you answer. But it is not working for me it is saying Loadlibrary(alt.dll)failed the specified module could not be found. Please help me in this issue. Regards, P.Narasimha swamy

Any chance that it does not spell "alt.dll", but "atl.dll"? Try registering that .dll manually (using regsvr32) and retry the installation again.

I'm having the same issue.. The ccmsetup.log stops on the following part: --- MSI: Action 13:05:13: CcmStopService. MSI: Action 13:05:13: StopServices. Stopping services MSI: Action 13:05:13: SmsStopUIComponents. Stopping UI Components MSI: Action 13:05:13: StopDeleteWUSER32. Stopping and deleting WUSER32 service Installation failed with error code 1603 ccmsetup --- And the client.log stops on the following part: --- MSI (s) (74:6C) [13:05:13:609]: Doing action: StopDeleteWUSER32 Action ended 13:05:13: SmsStopUIComponents. Return value 1. MSI (s) (74:28) [13:05:13:640]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIB2.tmp, Entrypoint: StopDeleteWUSER32 Action start 13:05:13: StopDeleteWUSER32. MSI (s) (74:6C) [13:05:13:656]: Machine policy value 'DisableRollback' is 0 MSI (s) (74:6C) [13:05:13:656]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 13:05:13: StopDeleteWUSER32. Return value 3. MSI (s) (74:6C) [13:05:13:656]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (74:6C) [13:05:13:656]: No System Restore sequence number for this installation. MSI (s) (74:6C) [13:05:13:656]: Unlocking Server Action ended 13:05:13: INSTALL. Return value 3. I followed the steps above, but didn't solve. I know that if I uninstall the Scua Security, it works. I already set the exceptions on the Scua, but just some workstation can install the client. Any help regarding this error, or the processes taht involve the thread 'StopDeleteWUSER32' will help. Thanks.

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

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

Hi there, I have a similar problem with client: MsiInstaller was ended with error: 1603 Client.msi.log: [10:24:32] The service 'smstsmgr' is not installed MSI (s) (F0:D8) [10:24:32:994]: Doing action: CcmStopService Action ended 10:24:32: SmsTSManagerStopServiceInit. Return value 1. MSI (s) (F0:D8) [10:24:32:994]: Transforming table CustomAction. MSI (s) (F0:D8) [10:24:32:994]: Transforming table CustomAction. MSI (s) (F0:D8) [10:24:32:994]: Transforming table Binary. MSI (s) (F0:D8) [10:24:32:994]: Transforming table Binary. Action start 10:24:32: CcmStopService. MSI (s) (F0:D8) [10:24:33:010]: Doing action: StopServices Action ended 10:24:32: CcmStopService. Return value 1. Action start 10:24:33: StopServices. MSI (s) (F0:D8) [10:24:33:010]: Skipping action: SmsUninstallPrepDrvr (condition is false) MSI (s) (F0:D8) [10:24:33:010]: Skipping action: SmsUninstallPrepDrvrX64 (condition is false) MSI (s) (F0:D8) [10:24:33:010]: Skipping action: SmsUninstallPrepDrvrAMD64 (condition is false) MSI (s) (F0:D8) [10:24:33:010]: Skipping action: SmsSwDistCacheDirDelete (condition is false) MSI (s) (F0:D8) [10:24:33:010]: Doing action: SmsStopUIComponents Action ended 10:24:33: StopServices. Return value 1. MSI (s) (F0:D8) [10:24:33:010]: Transforming table CustomAction. MSI (s) (F0:D8) [10:24:33:010]: Transforming table CustomAction. MSI (s) (F0:D8) [10:24:33:010]: Transforming table Binary. MSI (s) (F0:D8) [10:24:33:010]: Transforming table Binary. Action start 10:24:33: SmsStopUIComponents. MSI (s) (F0:D8) [10:24:33:010]: Doing action: StopDeleteWUSER32 Could you help me with this please ? Thx Michal

This part of the logfile does not contain the cause for the failure. Search for "return value 3". The error should be listed a few lines above it.Torsten Meringer | http://www.mssccmfaq.de

Here.... MSI (s) (F0:D8) [10:25:16:260]: Executing op: ComponentUnregister(ComponentId={1CA051B6-1B70-11D2-9ADD-006097C4E452},ProductKey={2609EDF1-34C4-4B03-B634-55F3B3BC4931},BinaryType=0,) MSI (s) (F0:D8) [10:25:16:260]: Executing op: ActionStart(Name=SmsPublishPatch,,) MSI (s) (F0:D8) [10:25:16:260]: Executing op: ActionStart(Name=SmsGenerateSuccessMIF,,) MSI (s) (F0:D8) [10:25:16:260]: Executing op: ActionStart(Name=SmsGenerateFailureMIF,,) MSI (s) (F0:D8) [10:25:16:260]: Executing op: CustomActionRollback(Action=SmsGenerateFailureMIF,ActionType=3329,Source=BinaryData,Target=SmsGenerateFailureMIF,CustomActionData={D478B8EE-EE0A-4004-980B-4D55533EE3C2} sccm2007ac-sp2-kb2509007-x86-enu ) MSI (s) (F0:D8) [10:25:16:260]: Creating MSIHANDLE (8878) of type 790536 for thread 5848 MSI (s) (F0:DC) [10:25:16:260]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSICFA.tmp, Entrypoint: SmsGenerateFailureMIF MSI (s) (F0!04) [10:25:16:276]: Creating MSIHANDLE (8879) of type 790531 for thread 4868 MSI (s) (F0!04) [10:25:16:276]: Closing MSIHANDLE (8879) of type 790531 for thread 4868 MSI (s) (F0:DC) [10:25:16:276]: Closing MSIHANDLE (8878) of type 790536 for thread 5848 [10:25:16] ERROR: Failed to load ISMIF32.DLL (126) MSI (s) (F0:D8) [10:25:16:276]: Executing op: ActionStart(Name=CcmStopServiceRollback,,) MSI (s) (F0:D8) [10:25:16:276]: Executing op: CustomActionRollback(Action=CcmStopServiceRollback,ActionType=3329,Source=BinaryData,Target=CcmStartService,) MSI (s) (F0:D8) [10:25:16:276]: Creating MSIHANDLE (8880) of type 790536 for thread 5848 MSI (s) (F0:5C) [10:25:16:276]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSICFB.tmp, Entrypoint: CcmStartService MSI (s) (F0!24) [10:25:16:291]: Creating MSIHANDLE (8881) of type 790531 for thread 5156 MSI (s) (F0!24) [10:25:16:291]: Closing MSIHANDLE (8881) of type 790531 for thread 5156 MSI (s) (F0:5C) [10:25:16:291]: Closing MSIHANDLE (8880) of type 790536 for thread 5848 MSI (s) (F0:D8) [10:25:16:291]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0) MSI (s) (F0:D8) [10:25:16:291]: Error in rollback skipped. Return: 5 [10:25:16] The service 'ccmexec' is not installed MSI (s) (F0:D8) [10:25:16:307]: No System Restore sequence number for this installation. MSI (s) (F0:D8) [10:25:16:307]: Unlocking Server MSI (s) (F0:D8) [10:25:16:307]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'. MSI (s) (F0:D8) [10:25:16:307]: Transforming table InstallExecuteSequence. MSI (s) (F0:D8) [10:25:16:307]: Transforming table InstallExecuteSequence. Action ended 10:25:16: INSTALL. Return value 3. thx for your help.. Michal