none
Error Installing SP1 on Server 2008 R2

    Question

  • Hi, 

     

    I recently did an in place upgrade of my Server 2008 R2 Standard VM's to Server 2008 R2 Enterprise via

     

    Dism /online /Set-Edition:ServerEnterprise /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

     

    After doing this I am not able to install SP1 via either the standalone package OR the windows update:

    the CBS.log indicates the following errors:

    2011-02-23 11:58:30, Info                  CBS    SPI: Starting SPInstall version 6.1.7601.17514

    2011-02-23 11:58:31, Error                 CBS    SPI: (CheckForPendingFlag:90)Failed to open component hive at C:\Windows\System32\config\components er=0x0

    2011-02-23 11:58:31, Error                 CBS    SPI: (CSystem::Initialize:317)Failed to GetProductInfo GLE=0x0

    2011-02-23 11:58:31, Error                 CBS    SPI: (wmain:939)Failed to initialize system hr=0x80004005

    2011-02-23 11:58:32, Info                  CBS    SPI: SPInstall terminating, return code 0x80004005

    2011-02-23 11:58:32, Error                 CBS    SPI: (SPIRegQueryStringValue:700)Failed to query registry value: MiscString2 er=0x2

    2011-02-23 11:58:32, Error                 CBS    SPI: (CSystem::GetMachineName:395)Failed to query machine name from RAC hr=0x80070002

    2011-02-23 11:58:32, Error                 CBS    SPI: (CCrimsonLogger::Unregister:50)Crimson logger not registered hr=0x8000ffff


    Any suggestions on how to fix this?

     

    Wednesday, February 23, 2011 5:06 PM

Answers

  • What is the kind of product key you used? Was the machine activated by KMS host? If so, you may need to install the KMS Client setup key to switch the product back to KMS client. The KMS Client setup key for Windows Server 2008 R2 Enterprise is: 489J6-VHDMP-X63PK-3K798-CPX3Y

     

    KMS Client setup key

    http://technet.microsoft.com/en-us/library/ff793421.aspx

     

    Best Regards

    Dale


    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. ”
    Friday, February 25, 2011 2:27 AM
    Moderator
  • Hi George and Dale,

    I figured out a workaround last night.  I discovered it had something to do with my original MAK key and its reuse.

    The original VM was a Server 2008 R2 VM with an MSDN MAK Key (which is valid for standard and enterprise edition)

    I did the DISM upgrade using the "489J6-VHDMP-X63PK-3K798-CPX3Y" KMS key for enterprise (from this post) http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/0c68ffd9-ed83-4437-aa79-2f7decc75c0f.

    After the DISM upgrade I switched back to my original MAK key (and activated successfully).  A secondary behavior of this was that Remote Desktop was no longer functional on any machine that used the MAK Key.  I then did some additional research and found that other people had experienced the same problem using the DISM upgrade (http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/6debc586-0977-4731-b418-ca1edb34fe8b).  On a hunch I switched back to the KMS key and was then able to install SP1 (and remote desktop was reenabled).  I then tried a Std/Enterprise license from a different MSDN account and it activated successfully, as well as kept Remote Desktop enabled.  I also tested switching back to my original MAK key and this worked as well.  I then just switched the rest of my VM's to the new MSDN key and this was successful as well, without re-introducing the KMS key.

    Best I can tell, there must be something unique to using the same key at each end of the standard -> enterprise DISM upgrade path path.  I've got my environment back up and running and all at SP1 but I can fire up a test VM to test a different scenario.

    -Tod

    • Marked as answer by TodK Friday, February 25, 2011 6:55 PM
    Friday, February 25, 2011 1:40 PM

All replies

  • Hi,

     

    Is the VM a DC? As I know, the server can’t be a DC at the time of upgrade.

     

    It seems that the In-place upgrade doesn’t work completely. There might be some corrupt files or settings. Please run System Update Readiness Tool to scan the whole computer and share us the error in CheckUSR.log:

     

    Description of the System Update Readiness Tool for Windows Vista and for Windows Server 2008

    http://support.microsoft.com/kb/947821/en-us

     

    Meanwhile, you could perform an In-place Upgrade to repair corrupted files. In-place Upgrade is a special upgrade process to repair the system. In-place Upgrade will not affect settings like photos, movies, documents, etc. that are saved on the computer. It won’t require activation again. Please refer to the following site:

     

    How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2

    http://support.microsoft.com/kb/2255099

     

    Best Regards

    Dale


    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. ”
    Thursday, February 24, 2011 7:43 AM
    Moderator
  • Hi Dale,

    Ran the SURT:  Below are the results.  next step will be the in-place upgrade, I'll share those results.  the VM is not a DC, just a plain jane server running ASP.NET 4 and SQL Server.

     

    =================================

    Checking System Update Readiness.

    Binary Version 6.1.7601.21645

    Package Version 11.0

    2011-02-24 09:50

     

    Checking Windows Servicing Packages

     

    Checking Package Manifests and Catalogs

     

    Checking Package Watchlist

     

    Checking Component Watchlist

     

    Checking Packages

     

    Checking Component Store

     

    Summary:

    Seconds executed: 347

     No errors detected

     

    Thursday, February 24, 2011 3:14 PM
  • Running the Server 2008 R2 upgrade caused this error:

     

    The following issues are preventing Windows from upgrading. Cancel the upgrade, complete each task, and then restart the upgrade to continue.

     

    <li><ComplianceIssuePri1 xmlns="">

    An error prevented a required compliance check from completing. Cancel the installation and try upgrading again.

    </ComplianceIssuePri1></li>

    Thursday, February 24, 2011 3:25 PM
  • What is the kind of product key you used? Was the machine activated by KMS host? If so, you may need to install the KMS Client setup key to switch the product back to KMS client. The KMS Client setup key for Windows Server 2008 R2 Enterprise is: 489J6-VHDMP-X63PK-3K798-CPX3Y

     

    KMS Client setup key

    http://technet.microsoft.com/en-us/library/ff793421.aspx

     

    Best Regards

    Dale


    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. ”
    Friday, February 25, 2011 2:27 AM
    Moderator
  • Thank you for reporting this. My team developed this installer - I just checked the code and the symptoms you're describing are truly baffling.  We take the output of GetVersionEx (http://msdn.microsoft.com/en-us/library/ms724451(VS.85).aspx) and feed it into GetProductInfo (http://msdn.microsoft.com/en-us/library/ms724358(VS.85).aspx). I whipped up a quick executable to show the output of these calls. Would you mind running it and providing the output?

    Exe (I hosted it on my personal site): http://www.pac-blog.com/GetVersionExOutput.exe

    Code:

    int _tmain(int argc, _TCHAR* argv[])
    {
    	OSVERSIONINFOEXW osVersionInfo = {0};
    	osVersionInfo.dwOSVersionInfoSize = sizeof(osVersionInfo);
    	BOOL bGetVersionEx = ::GetVersionExW((LPOSVERSIONINFOW)&osVersionInfo);
    	if(!bGetVersionEx)
    	{
    		wprintf(L"Failed to call GetVersionExW. status=0x%x", ::GetLastError());
    		return 0;
    	}
    	wprintf(L"GetVersionExW returned:\n");
    	wprintf(L"\t OSMajor: %d\n", osVersionInfo.dwMajorVersion);
    	wprintf(L"\t OSMinor: %d\n", osVersionInfo.dwMinorVersion);
    	wprintf(L"\t ServicePackMajor: %d\n", osVersionInfo.wServicePackMajor);
    	wprintf(L"\t ServicePackMinor: %d\n", osVersionInfo.wServicePackMinor);
    	wprintf(L"\t CSDVersion: %s\n\n", osVersionInfo.szCSDVersion);
    
    	DWORD dwProductType = 0;
    	BOOL bGetProductInfo = ::GetProductInfo(osVersionInfo.dwMajorVersion, osVersionInfo.dwMinorVersion, osVersionInfo.wServicePackMajor, osVersionInfo.wServicePackMinor, &dwProductType);
    	if(!bGetProductInfo)
    	{
    		wprintf(L"Failed to call GetProductInfo. status=0x%x", ::GetLastError());
    		return 0;
    	}
    	wprintf(L"\t GetProductInfo: %d\n", dwProductType);
    	return 0;
    }
    
    Friday, February 25, 2011 3:32 AM
  • You can also try getting the exe in zipped form: http://www.pac-blog.com/GetVersionExOutput.zip

    Depending on your browser or firewall settings the .exe download might not work

    Friday, February 25, 2011 5:13 AM
  • Hi George and Dale,

    I figured out a workaround last night.  I discovered it had something to do with my original MAK key and its reuse.

    The original VM was a Server 2008 R2 VM with an MSDN MAK Key (which is valid for standard and enterprise edition)

    I did the DISM upgrade using the "489J6-VHDMP-X63PK-3K798-CPX3Y" KMS key for enterprise (from this post) http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/0c68ffd9-ed83-4437-aa79-2f7decc75c0f.

    After the DISM upgrade I switched back to my original MAK key (and activated successfully).  A secondary behavior of this was that Remote Desktop was no longer functional on any machine that used the MAK Key.  I then did some additional research and found that other people had experienced the same problem using the DISM upgrade (http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/6debc586-0977-4731-b418-ca1edb34fe8b).  On a hunch I switched back to the KMS key and was then able to install SP1 (and remote desktop was reenabled).  I then tried a Std/Enterprise license from a different MSDN account and it activated successfully, as well as kept Remote Desktop enabled.  I also tested switching back to my original MAK key and this worked as well.  I then just switched the rest of my VM's to the new MSDN key and this was successful as well, without re-introducing the KMS key.

    Best I can tell, there must be something unique to using the same key at each end of the standard -> enterprise DISM upgrade path path.  I've got my environment back up and running and all at SP1 but I can fire up a test VM to test a different scenario.

    -Tod

    • Marked as answer by TodK Friday, February 25, 2011 6:55 PM
    Friday, February 25, 2011 1:40 PM
  • Dale,

    I started with an MSDN MAK Key, upgraded using the Server 2008 R2 Enterprise KMS key (which did not activate), then re-used my existing MSDN MAK Key, which is valid for both standard and enterprise.  This is when the problems started occurring.  I then switched to a MSDN MAK Key from a different MSDN account, which resolved all of the problems.  Additionally, i can re-activate the machine with the original MAK key and remote desktop continues to work.

    Monday, February 28, 2011 2:46 PM
  • I had a similar issue 32 GB installed (16 GB usable).  For me the fix was in BIOS, Memory Operating Mode, Mirror option was selected.  I set to Optimized and now I have almost the full 32.

    Dell PowerEdge R710

     

    Adam

    Wednesday, May 25, 2011 11:02 PM