KB977384 Not valid?
I am currently running SCCM 2007 Sp2 R2 and I am trying to upgrade to R3. It has worked fine on 6 DP servers but I am having trouble with two of them. I get the Hotfix is not valid for this version of Cong Manager 2007 message even though it
is the same set up as the rest.
Where so I begin troubleshooting this?
May 18th, 2011 2:41pm
Do you have UAC enabled on the servers? If so, make sure you elevate first.
You can also check the log file which should be getting created in the temp directory of the user performing the installation.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 3:56pm
No UAC. Here is the log output. I have verified the agent version is 4.0.6487.2000.
MSI (c) (88:CC) [04:11:24:944]: Note: 1: 1708
MSI (c) (88:CC) [04:11:24:944]: Product: Software Update for ConfigMgr 2007 SP2 (KB977384) -- Installation operation failed.
MSI (c) (88:CC) [04:11:24:944]: Windows Installer installed the product. Product Name: Software Update for ConfigMgr 2007 SP2 (KB977384). Product Version: 4.0.6487.2157. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or
error status: 1603.
MSI (c) (88:CC) [04:11:24:944]: Grabbed execution mutex.
MSI (c) (88:CC) [04:11:24:944]: Cleaning up uninstalled install packages, if any exist
MSI (c) (88:CC) [04:11:24:944]: MainEngineThread is returning 1603
=== Verbose logging stopped: 5/19/2011 4:11:24 ===
May 18th, 2011 3:58pm
Hi,
Are you using the ICP language packs? If so have you applied them to all the DP's otherwise this error will show as the update is not for that ICP level.
/Jörgen-- visit my System center blog at http://ccmexec.com --
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 4:56pm
MSI Error code 1603 is a generic MSI error code that means you need to dig into the log more to find out what went wrong:
http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
May 18th, 2011 5:56pm
Hi,
This issue can be caused by the version of the console in the registry is different.
You may check the version on the following registry key to see if the server which failed has the invalid console version:
HKLM\SOFTWARE\Microsoft\ConfigMgr\Setup\Full UI Version
Regards,
Sabrina
This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question.
This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2011 6:30am
Please ensure you have SCCM 2007 SP2 and not SP1. The R3 can only be pushed to SP2. :)
May 25th, 2011 6:28pm
I ended up rebuilding the entire site from scratch. Thanks everyone for your help.
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2011 10:18pm