locked
Server Manager fails, as does install of Service Pack 2. RRS feed

  • Question

  • In trying to add a role, I found that my Server Manager was failing. I then found that IE  and SP2 were also failing from Windows Update. I ran the readiness tool, and found files that were problems. I received those files, and IE 8 successfully installed. Now, the Readiness Tool has noissues, but SP2 will not install, and I still have Server Manager not allowing me to add roles or features.

    I've tried installing SP2 from the stand alone, and it claims I need Service Pack 1. I am running Windows Server 2008 x64 Standard. I have Exchange 2007 installed on this machine, as well.

    I checked the Server Manager log, and it says:

    3172: 2009-10-20 18:20:37.965 [LoadExtensionAssemblies]   No extension assemblies registered.
    3172: 2009-10-20 18:20:38.293 [OobOptionalComponentInfo]  Loading OCs from registry.
    3172: 2009-10-20 18:20:39.400 [CBS]                       LastModified CBS Time (UTC): 10/20/2009 23:05:45
    3172: 2009-10-20 18:20:39.400 [Provider]                  C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
    3172: 2009-10-20 18:20:39.400 [CBS]                       IsCacheStillGood: False.
    3172: 2009-10-20 18:20:39.400 [CBS]                       CreateSessionAndPackage: begin
    3172: 2009-10-20 18:23:44.906 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800f0818 (-2146498536)
    3172: 2009-10-20 18:23:45.436 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x800F0818): Exception from HRESULT: 0x800F0818
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
       at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

    I'm not sure where to go from here, and would prefer to stay away from FFR.

    Thursday, October 22, 2009 4:48 PM

All replies

  • Hi,

     

    Let’s try below:

     

    Note: Before doing this, please backup your important files on the system drive.

     

    1.  Close all applications, and then restart the computer. 

    2.  Insert the Windows Server 2008 DVD in the computer's DVD drive. 

    3.  In the Setup window, click Install Now .

     

    Note If Windows does not automatically detect the DVD, follow these steps:

     

    a.  Click Start , and then type Drive :\setup.exe in the Start Search box.

     

    Note The Drive placeholder is the drive letter of the computer's DVD drive. 

     

    b.  In the Programs list, click Setup.exe . 

    c.  In the Setup window, click Install Now . 

     

    4.  Click Go online to obtain the latest updates for installation (recommended) . 

    5.  Type the CD key if you are prompted to do this. 

    6.  Click Yes to accept the Microsoft Software License Terms. 

    7.  On the Which kind of installation do you want? screen, click Upgrade . 

    8.  When the installation is complete, restart your computer, and then try to install the updates.

     

    Hope it helps.

     

    Tim Quan - MSFT

     

    Friday, October 23, 2009 3:27 AM
  • Won't this make a mess of the system, particularly Exchange?

    Friday, October 23, 2009 7:31 PM
  • I'm almost in the same spot as vanakenk above. I'm running Windows Server Enterprise x64.

     

    I can't install WS2008 SP2 x64, can't "Add Role" or "Add feature" in Server Manager. The Roles and Features part of Server Manger shows "Unexpected error refreshing Server Manager: Exception from HRESULT: 0x800F0818". Windows update shows Error code 800F0818 when viewing details on the failed update.

     

    After manually added some missing packages (KB973874) in "C:\Windows\servicing\Packages" with some help from another thread on the forum there is no error in "C:\Windows\Logs\CBSCheckSUR.log". I have also run the readiness tool.

     

    I have also tired your suggestion to do an upgrade with the installation dvd. That resulted in a rollback with an error saying something like I can't upgrade to that version. As a last attempt tonight I tried to upgrade to WS2008 R2 Enterprise with the same result. Rollback.

     

     

    Last entries from servermanager.log

     

    716: 2009-11-29 23:07:08.135 [LoadExtensionAssemblies]   No extension assemblies registered.

    716: 2009-11-29 23:07:08.294 [OobOptionalComponentInfo]  Loading OCs from registry.

    716: 2009-11-29 23:07:08.873 [CBS]                       LastModified CBS Time (UTC): 11/28/2009 09:07:45

    716: 2009-11-29 23:07:08.873 [Provider]                  C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.

    716: 2009-11-29 23:07:08.874 [CBS]                       IsCacheStillGood: False.

    716: 2009-11-29 23:07:08.874 [CBS]                       CreateSessionAndPackage: begin

    716: 2009-11-29 23:07:11.239 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800f0818 (-2146498536)

    716: 2009-11-29 23:07:11.245 [ExceptionHandler] Error (Id=0) An unexpected exception was found:

    System.Runtime.InteropServices.COMException (0x800F0818): Exception from HRESULT: 0x800F0818

       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

       at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)

       at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()

       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()

       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)

       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

     

    How should I proceed? I don't want to reinstall because this is the and this is the Domain Controller, DHCP, DNS, Hyper-V server, SQL server etc.

     

     

    Sunday, November 29, 2009 10:23 PM
  • Hi vanakenk,

    Did you ever get this resolved? I am currently in the same situation.

    I have not yet tried the upgrade. But I have run the SUR and that has come back ok with no problems.

    TIA
    Thursday, January 7, 2010 3:09 AM
  • Same issue as Wamprat and vanakenk, also running Hyper-V and WDS from this server. (Windows server 2008 R2 standard)

    Copy of event log error:

    "Could not discover the state of the system. An unexpected exception was found:

    System.Runtime.InteropServices.COMException (0x800F0818): Exception from HRESULT: 0x800F0818

    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

    at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)

    at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()

    at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()

    at Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery()

    at Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery()

    at Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult(RefreshType refreshType)

    at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)"


    If you're not living on the edge you're taking up too much room
    Tuesday, January 18, 2011 12:23 PM
  • Hi Dave,
     
    Does the SUR tool come back clean for you?
     

    -- Mike Burr
    MS Technologies - Development - *nix
    Tuesday, January 18, 2011 7:33 PM
  • I'm having the same problem.

    Dave: The tool comes back clean for me.

    Thursday, March 3, 2011 2:38 PM
  • If you have another w2k8 R2 (good) server:
    1.
    takeown /F c:\Windows\Servicing\Packages /D y /R
    2.
    c:\Windows\Servicing\Packages /E /T /C /G "UserName":F
    3.
    From good copy and overwrite all C:\Windows\servicing\Packages files to problematic server
    4.
    Secure back 1. and 2.
    Worked for me.
    Monday, June 27, 2011 5:36 AM
  • This worked for me 
    Wednesday, May 23, 2012 8:48 AM