locked
Server manager refresh failure error 0x800F0900 RRS feed

  • General discussion

  • Running Windows Server 2008 Enterprise, x64

    Server Manager complains "Last Refresh: Failed".

    Error details displays: "Unexpected error refreshing Server manager: Exception from HRESULT: 0x800F0900"

    Contents of %windir%\logs\servermanager.log

    ...

    5460: 2010-05-20 16:44:26.002 [CBS]                       IsCacheStillGood: False.
    5460: 2010-05-20 16:44:26.007 [CBS]                       CreateSessionAndPackage: begin
    5460: 2010-05-20 16:44:27.979 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800f0900 (-2146498304)
    5460: 2010-05-20 16:44:27.986 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x800F0900): Exception from HRESULT: 0x800F0900
       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)

    5460: 2010-05-20 16:44:28.037 [PendingRebootDetection]    No reboot pending from CBS...

    ...

    Followed dcomcnfg.exe instructions from this thread http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/ae1a7f09-2f50-4521-9bae-283631963283/. That did not help.

    Any other ideas?

    Thanks

    Abhi

     

    • Changed type Tim Quan Thursday, May 27, 2010 1:27 AM
    Thursday, May 20, 2010 9:01 PM

All replies

  • Hi,

     

    Please run the System Update Readiness Tool from the following site and then paste the result in %SYSTEMROOT%\Logs\CBS\CheckSUR.log here.

     

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

     

    Tim Quan - MSFT

     

    Friday, May 21, 2010 6:39 AM
  • Any update?
    Monday, May 24, 2010 3:10 AM
  • I'm having the same problem. CheckSUR.log:

    Checking System Update Readiness.
    Binary Version 6.0.6002.22359
    Package Version 8.0
    2010-06-03 16:59

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB981332_ie8_0~31bf3856ad364e35~amd64~~8.0.1.0.mum  Line 1: «÷€GÙŠ{”
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB981332_ie8_0~31bf3856ad364e35~amd64~~8.0.1.0.cat  
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB981332_ie8~31bf3856ad364e35~amd64~~8.0.1.0.cat  

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-f..ype-microsoftuighur_31bf3856ad364e35_6.0.6002.18208_none_152add74c1239cac.manifest amd64_microsoft-windows-f..ype-microsoftuighur_31bf3856ad364e35_6.0.6002.18208_none_152add74c1239cac 
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-f..ype-microsoftuighur_31bf3856ad364e35_6.0.6001.22635_none_13aa97b5dd35ef20.manifest amd64_microsoft-windows-f..ype-microsoftuighur_31bf3856ad364e35_6.0.6001.22635_none_13aa97b5dd35ef20 
    (f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\x86_microsoft-windows-ie-behaviors_31bf3856ad364e35_8.0.6001.22995_none_1fd9f74c213d2f14.manifest x86_microsoft-windows-ie-behaviors_31bf3856ad364e35_8.0.6001.22995_none_1fd9f74c213d2f14 
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\wow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.0.6001.22636_none_78c590e982491c41.manifest wow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.0.6001.22636_none_78c590e982491c41 
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\x86_microsoft-windows-ie-behaviors_31bf3856ad364e35_8.0.6001.18904_none_1fb0ab6907d777a1.manifest x86_microsoft-windows-ie-behaviors_31bf3856ad364e35_8.0.6001.18904_none_1fb0ab6907d777a1 
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6002.22346_none_e9446b5c588240ab.manifest amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6002.22346_none_e9446b5c588240ab 
    (f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\amd64_microsoft-windows-f..type-franklingothic_31bf3856ad364e35_6.0.6002.22340_none_e8be4967871c5789.manifest amd64_microsoft-windows-f..type-franklingothic_31bf3856ad364e35_6.0.6002.22340_none_e8be4967871c5789 
    (f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\amd64_microsoft-windows-f..type-leelawadeebold_31bf3856ad364e35_6.0.6001.22635_none_4c1edaba5b056972.manifest amd64_microsoft-windows-f..type-leelawadeebold_31bf3856ad364e35_6.0.6001.22635_none_4c1edaba5b056972 
    (f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\amd64_microsoft-windows-f..type-leelawadeebold_31bf3856ad364e35_6.0.6001.18426_none_4ba10c3f41dec9e7.manifest amd64_microsoft-windows-f..type-leelawadeebold_31bf3856ad364e35_6.0.6001.18426_none_4ba10c3f41dec9e7 

    Summary:
    Seconds executed: 813
     Found 12 errors
      CSI Manifest Zero Length Total count: 3
      CSI Manifest and S256H Do Not Match Total count: 1
      CSI Manifest Failed Catalog Check Total count: 5
      CBS MUM Corrupt Total count: 1
      CBS Catalog Corrupt Total count: 2

    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-f..ype-microsoftuighur_31bf3856ad364e35_6.0.6002.18208_none_152add74c1239cac.manifest
     winsxs\manifests\amd64_microsoft-windows-f..ype-microsoftuighur_31bf3856ad364e35_6.0.6001.22635_none_13aa97b5dd35ef20.manifest
     winsxs\manifests\x86_microsoft-windows-ie-behaviors_31bf3856ad364e35_8.0.6001.22995_none_1fd9f74c213d2f14.manifest
     winsxs\manifests\wow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.0.6001.22636_none_78c590e982491c41.manifest
     winsxs\manifests\x86_microsoft-windows-ie-behaviors_31bf3856ad364e35_8.0.6001.18904_none_1fb0ab6907d777a1.manifest
     winsxs\manifests\amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.0.6002.22346_none_e9446b5c588240ab.manifest
     winsxs\manifests\amd64_microsoft-windows-f..type-franklingothic_31bf3856ad364e35_6.0.6002.22340_none_e8be4967871c5789.manifest
     winsxs\manifests\amd64_microsoft-windows-f..type-leelawadeebold_31bf3856ad364e35_6.0.6001.22635_none_4c1edaba5b056972.manifest
     winsxs\manifests\amd64_microsoft-windows-f..type-leelawadeebold_31bf3856ad364e35_6.0.6001.18426_none_4ba10c3f41dec9e7.manifest
     servicing\packages\Package_for_KB981332_ie8_0~31bf3856ad364e35~amd64~~8.0.1.0.mum
     servicing\packages\Package_for_KB981332_ie8_0~31bf3856ad364e35~amd64~~8.0.1.0.mum
     servicing\packages\Package_for_KB981332_ie8~31bf3856ad364e35~amd64~~8.0.1.0.mum
     servicing\packages\Package_for_KB981332_ie8_0~31bf3856ad364e35~amd64~~8.0.1.0.cat
     servicing\packages\Package_for_KB981332_ie8_0~31bf3856ad364e35~amd64~~8.0.1.0.cat
     servicing\packages\Package_for_KB981332_ie8~31bf3856ad364e35~amd64~~8.0.1.0.cat

    Any ideas how to resolve this issue?

    Friday, June 4, 2010 3:53 PM