I have a windows 2003 64bit were the client won't install. The setup loggs say that the ccmcore.dll fails to register. I saw another forum, but didn't see a definitive answer. Just wondering if anyone has some experience dealing with this issue before.Louis Paxton

Have you tried cleaning up and reinstallig? Do you get the same result? I am assuming that the DLL exists. What if you manually register it? Does that work? Since it is a 64 bit machine, you'll have to use the 32 bit version of regsvr32.dll in the sysWOW64 folder, if I recall correctly. If it doesn't work, what error do you get?John DeVito

Can you please post the relevant portion of the ccmsetup.log log file?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Here is a part of the log: ==========[ ccmsetup started in process 5940 ]========== ccmsetup 5944 (0x1738) Version: 4.0.6487.2000 ccmsetup 5944 (0x1738) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 5944 (0x1738) Command line: CCMSetup.exe /mp:SCCM.XXXXX.COM SMSSITECODE=COU FSP=SCCM.XXXXX.COM SMSSLP=SCCM.XXXXX.COM SMSMP=SCCM.XXXXX.COM CCMLOGLEVEL=0 CCMDEBUGLOGGING=1 CCMENABLELOGGING=true ccmsetup 5944 (0x1738) User credentials are not required to access installation files. ccmsetup will be executed in service-only mode. ccmsetup 5944 (0x1738) Updated security on object C:\WINDOWS\ccmsetup\. ccmsetup 5944 (0x1738) A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 5944 (0x1738) Ccmsetup is not registered in the Run key ccmsetup 5944 (0x1738) Downloading file C:\Manual SCCM Client install\Client\ccmsetup.exe ccmsetup 5944 (0x1738) Downloading C:\Manual SCCM Client install\Client\ccmsetup.exe to C:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 5944 (0x1738) File download 10% complete (65536 of 611168 bytes). ccmsetup 5944 (0x1738) File download 21% complete (131072 of 611168 bytes). ccmsetup 5944 (0x1738) File download 32% complete (196608 of 611168 bytes). ccmsetup 5944 (0x1738) File download 42% complete (262144 of 611168 bytes). ccmsetup 5944 (0x1738) File download 53% complete (327680 of 611168 bytes). ccmsetup 5944 (0x1738) File download 64% complete (393216 of 611168 bytes). ccmsetup 5944 (0x1738) File download 75% complete (458752 of 611168 bytes). ccmsetup 5944 (0x1738) File download 85% complete (524288 of 611168 bytes). ccmsetup 5944 (0x1738) File download 96% complete (589824 of 611168 bytes). ccmsetup 5944 (0x1738) File download 100% complete (611168 of 611168 bytes). ccmsetup 5944 (0x1738) Download complete. ccmsetup 5944 (0x1738) Successfully created the ccmsetup service ccmsetup 5944 (0x1738) ==========[ ccmsetup started in process 5996 ]========== ccmsetup 6000 (0x1770) Version: 4.0.6487.2000 ccmsetup 6000 (0x1770) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 6000 (0x1770) Command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /mp:SCCM.XXXXX.COM SMSSITECODE=COU FSP=SCCM.XXXXX.COM SMSSLP=SCCM.XXXXX.COM SMSMP=SCCM.XXXXX.COM CCMLOGLEVEL=0 CCMDEBUGLOGGING=1 CCMENABLELOGGING=true ccmsetup 6000 (0x1770) CCMHTTPPORT: 80 ccmsetup 6000 (0x1770) CCMHTTPSPORT: 443 ccmsetup 6000 (0x1770) CCMHTTPSSTATE: 2147483648 ccmsetup 6000 (0x1770) CCMHTTPSCERTNAME: ccmsetup 6000 (0x1770) FSP: SCCM1.COURT.GOV ccmsetup 6000 (0x1770) Config file: ccmsetup 6000 (0x1770) Retry time: 10 minute(s) ccmsetup 6000 (0x1770) MSI log file: ccmsetup 6000 (0x1770) MSI properties: SMSSITECODE="XXX" FSP="SCCM.XXXXX.COM" SMSSLP="SCCM.XXXXX.COM" SMSMP="SCCM.XXXXX.COM" CCMLOGLEVEL="0" CCMDEBUGLOGGING="1" CCMENABLELOGGING="true" CCMHTTPPORT="80" CCMHTTPSPORT="443" ccmsetup 6000 (0x1770) Source List: ccmsetup 6000 (0x1770) MPs: ccmsetup 6000 (0x1770) SCCM1.XXXXX.COM ccmsetup 6000 (0x1770) Updated security on object C:\WINDOWS\ccmsetup\. ccmsetup 6000 (0x1770) Sending Fallback Status Point message, STATEID='100'. ccmsetup 6000 (0x1770) State message with TopicType 800 and TopicId {DAC3B355-82FE-4F77-A8EE-0921EF016323} has been sent to the FSP FSPStateMessage 6000 (0x1770) Successfully started the ccmsetup service ccmsetup 5944 (0x1738) Running as user "SYSTEM" ccmsetup 6024 (0x1788) Detected 11242 MB free disk space on system drive. ccmsetup 6024 (0x1788) DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 6024 (0x1788) Client OS Version is 5.2, Service Pack Version 2 ccmsetup 6024 (0x1788) Client OS is not a supported Windows Embedded Platform ccmsetup 6024 (0x1788) Waiting for existing instances of ccmsetup to exit. ccmsetup 6024 (0x1788) Deleted file C:\WINDOWS\ccmsetup\ccmsetup.exe.download ccmsetup 5944 (0x1738) All other instances of ccmsetup have completed. ccmsetup 6024 (0x1788) Successfully ran BITS check. ccmsetup 6024 (0x1788) IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\ccmsetup\ccmsetup.cab' is MS signed. ccmsetup 6024 (0x1788) Successfully extracted manifest file C:\WINDOWS\ccmsetup\ccmsetup.xml from file C:\WINDOWS\ccmsetup\ccmsetup.cab. ccmsetup 6024 (0x1788) Loading manifest file: C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 6024 (0x1788) Successfully loaded ccmsetup manifest file. ccmsetup 6024 (0x1788) Couldn't get directory list for directory 'http://SCCM.XXXXX.COM/CCM_Client/ClientPatch'. This directory may not exist. ccmsetup 6024 (0x1788) Adding file 'http://SCCM.XXXXX.COM:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\ccmsetup\client.msi'. ccmsetup 6024 (0x1788) Couldn't get directory list for directory 'http://SCCM.XXXXX.COM/CCM_Client/i386/00000409'. This directory may not exist. ccmsetup 6024 (0x1788) Starting BITS download for client deployment files. ccmsetup 6024 (0x1788) Download Update: Connecting to the server. ccmsetup 6024 (0x1788) Successfully completed BITS download for client deployment files. ccmsetup 6024 (0x1788) Successfully downloaded client files via BITS. ccmsetup 6024 (0x1788) Updated security on object C:\WINDOWS\ccmsetup\. ccmsetup 6024 (0x1788) An MP does not exist on this machine. ccmsetup 6024 (0x1788) No client is currently installed. ccmsetup 6024 (0x1788) Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931} ccmsetup 6024 (0x1788) MSI PROPERTIES are SMSSITECODE="XXX" FSP="SCCM.XXXXX.COM" SMSSLP="SCCM.XXXXX.COM" SMSMP="SCCM.XXXXX.COM" CCMLOGLEVEL="0" CCMDEBUGLOGGING="1" CCMENABLELOGGING="true" CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 6024 (0x1788) IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' is MS signed. ccmsetup 6024 (0x1788) Running installation package Package: C:\WINDOWS\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi Log: C:\WINDOWS\ccmsetup\client.msi.log Properties: SMSSITECODE="COU" FSP="SCCM.XXXXX.COM" SMSSLP="SCCM.XXXXX.COM" SMSMP="SCCM.XXXXX.COM" CCMLOGLEVEL="0" CCMDEBUGLOGGING="1" CCMENABLELOGGING="true" CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 6024 (0x1788... ... MSI: Module C:\WINDOWS\SysWOW64\CCM\x64\ccmcore.dll failed to register. HRESULT -2147024703. Contact your support personnel. ccmsetup 6024 (0x1788) MSI: Action 14:47:23: Rollback. Rolling back action: ccmsetup 6024 (0x1788) Installation failed with error code 1603 ccmsetup 6024 (0x1788) Next retry in 120 minute(s)... ccmsetup 6024 (0x1788) Sorry I could paste better, but this part of it. Let me know if you need to see any more. Thanks Louis Paxton

Error code 1603 is the generic Windows Installer error code that means you need to check the verbose log file. Thus you need need to check client.msi.log (use http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx for a quick reference on how to dig through Windows Installer verbose log files).Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Thanks Jason, I comb through the client.msi.log: MSI (s) (D8:FC) [14:47:23:059]: Product: Configuration Manager Client -- Error 1904. Module C:\WINDOWS\SysWOW64\CCM\x64\ccmcore.dll failed to register. HRESULT -2147024703. Contact your support personnel. Error 1904. Module C:\WINDOWS\SysWOW64\CCM\x64\ccmcore.dll failed to register. HRESULT -2147024703. Contact your support personnel. MSI (s) (D8:FC) [14:47:23:106]: User policy value 'DisableRollback' is 0 MSI (s) (D8:FC) [14:47:23:106]: Machine policy value 'DisableRollback' is 0 Action ended 14:47:23: InstallFinalize. Return value 3. Louis Paxton

Had you tried manually registering the DLL yet? If not, try and let us know what result you get.John DeVito

Any help from the following thread?.. I think they had same problem ... http://social.technet.microsoft.com/Forums/en-HK/configmgrsetup/thread/52e565dc-3700-4f7b-a82e-9713976d18dd Anoop C Nair - @anoopmannur :: MY Site: www.AnoopCNair.com :: FaceBook: ConfigMgr(SCCM) Page :: This posting is provided AS-IS with no warranties/guarantees and confers no rights.