buster53 Posted May 20, 2013 Report post Posted May 20, 2013 I'm upgrading to SCCM2012, and most of my clients have upgraded correctly. However I have some clients failing to install the new Config manager client. I cannot find a fix. Please help CCMSETUP.log Item 'x64/client.msi' is not applicable. ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)Default CSP Type is 24 ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)Discovering whether item 'i386/vcredist_x86.exe' exists. ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)CheckProductInstalled - MSI product code {1F1C2DFC-2D24-3E06-BCB8-725134ADF989} received unexpected return value: 1608 ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)Failed to discover MSI item. Error 0x80070648 ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)Error processing node: <Discovery Type="MSI" Identifier="{1F1C2DFC-2D24-3E06-BCB8-725134ADF989}"/>. Error 0x80070648 ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)GetInstallList failed error 0x80070648 ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)A Fallback Status Point has not been specified. Message with STATEID='301' will not be sent. ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)Deleted file C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408)CcmSetup failed with error code 0x80070648 ccmsetup 5/20/2013 9:31:23 AM 1032 (0x0408) Quote Share this post Link to post Share on other sites More sharing options...
Eswar Koneti Posted May 21, 2013 Report post Posted May 21, 2013 this is not complete log.there is more about error that would help the guys to help you better. Quote Share this post Link to post Share on other sites More sharing options...
buster53 Posted May 21, 2013 Report post Posted May 21, 2013 I think I figured this out today. I did a Google search for the MSI" Identifier={1F1C2DFC-2D24-3E06-BCB8-725134ADF989} and it turns out it is a MS visual C++ 2008 Redistributable key. I searched for the Identifier in the registry on the problem machines and found it, but it was incomplete or corrupt. I deleted the key and reinstall the client, the client installed correctly. I checked the same key after the install completed successfully and the key was there and looked like MS visual C++ 2008 Redistributable reinstalled without any problems. This might be something unique to my environment but I thought I would share my solution steps incase someone has a similar issue. Here is the registry path I found on the problem machines: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{1F1C2DFC-2D24-3E06-BCB8-725134ADF989} I wanted to also mention that this forum is an absolute life saver for SCCM admins. I have found so many solutions and answers here. I wanted to thank each and everyone of you for contributing. I appreciate all of your knowledge and hard work. Thank you 1 Quote Share this post Link to post Share on other sites More sharing options...
oblique Posted August 27, 2014 Report post Posted August 27, 2014 Just replying to let people know that this helped me resolve an issue I was having on a handful of clients that were reporting the same (different ID) error as the OP. Mine seemed to have a corrupt install of MS Visual C++ 2010 Redistributable (both x86 and x64). They were showing okay in the registry (see below URL for registry locations), but not even showing at all in Programs and Features. http://blogs.msdn.com/b/astebner/archive/2010/05/05/10008146.aspx To resolve it I manually ran the install for these from the source files within the SCCM 2012 Client package. Once they showed as successfully installed I then manually removed both versions (x86 and x64). I then ran the install of the SCCM 2012 client on this machine from the console and it went through perfectly fine. Hope this helps anyone else having this (or similar) problem Quote Share this post Link to post Share on other sites More sharing options...