Answered by:
Server 2008 Server Manager Roles and Features Error 0x800F0900

Question
-
I am running server 2008 and I am unable to open Roles or Features. Error 0x800F0900. Below are the following reports after running the :System update readiness tool".
Server Manager Log.
5596: 2012-11-08 14:34:20.217 [LoadExtensionAssemblies] No extension assemblies registered.
5596: 2012-11-08 14:34:20.255 [OobOptionalComponentInfo] Loading OCs from registry.
5596: 2012-11-08 14:34:20.256 [OobOptionalComponentInfo] Name: '%windir%\system32\wsmsvc.dll,103', description: '%windir%\system32\wsmsvc.dll,104', discovery hint: 'Microsoft-Windows-Web-Services-for-Management-IIS-Extension', install command: 'ocsetup.exe WAS-WindowsActivationService;WAS-ProcessModel;WAS-ConfigurationAPI;IIS-WebServerRole;IIS-WebServerManagementTools;Microsoft-Windows-Web-Services-for-Management-IIS-Extension /quiet', uninstall command: 'ocsetup.exe Microsoft-Windows-Web-Services-for-Management-IIS-Extension /uninstall /quiet /norestart'
5596: 2012-11-08 14:34:20.258 [OobOptionalComponentInfo] Localized name: 'WinRM IIS Extension', localized description: 'WinRM IIS Extension'
5596: 2012-11-08 14:34:20.772 [CBS] LastModified CBS Time (UTC): 10/10/2012 23:05:27
5596: 2012-11-08 14:34:20.772 [Provider] C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
5596: 2012-11-08 14:34:20.773 [CBS] IsCacheStillGood: False.
5596: 2012-11-08 14:34:20.773 [CBS] CreateSessionAndPackage: begin
5596: 2012-11-08 14:34:25.042 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800f0900 (-2146498304)
5596: 2012-11-08 14:34:25.070 [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)
2952: 2012-11-08 14:48:00.539 [LoadExtensionAssemblies] No extension assemblies registered.
2952: 2012-11-08 14:48:00.576 [OobOptionalComponentInfo] Loading OCs from registry.
2952: 2012-11-08 14:48:00.577 [OobOptionalComponentInfo] Name: '%windir%\system32\wsmsvc.dll,103', description: '%windir%\system32\wsmsvc.dll,104', discovery hint: 'Microsoft-Windows-Web-Services-for-Management-IIS-Extension', install command: 'ocsetup.exe WAS-WindowsActivationService;WAS-ProcessModel;WAS-ConfigurationAPI;IIS-WebServerRole;IIS-WebServerManagementTools;Microsoft-Windows-Web-Services-for-Management-IIS-Extension /quiet', uninstall command: 'ocsetup.exe Microsoft-Windows-Web-Services-for-Management-IIS-Extension /uninstall /quiet /norestart'
2952: 2012-11-08 14:48:00.579 [OobOptionalComponentInfo] Localized name: 'WinRM IIS Extension', localized description: 'WinRM IIS Extension'
2952: 2012-11-08 14:48:01.054 [CBS] LastModified CBS Time (UTC): 10/10/2012 23:05:27
2952: 2012-11-08 14:48:01.118 [CBS] Cache Last Write Time (UTC): 10/02/2012 16:33:33
2952: 2012-11-08 14:48:01.118 [CBS] IsCacheStillGood: False.
2952: 2012-11-08 14:48:01.118 [CBS] CreateSessionAndPackage: begin
2952: 2012-11-08 14:48:05.463 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800f0900 (-2146498304)
2952: 2012-11-08 14:48:05.468 [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)
CheckSur.persist.log
=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22574
Package Version 16.0
2012-11-08 14:38
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum Line 1:
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c.manifest amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c
Summary:
Seconds executed: 300
Found 2 errors
CSI Manifest Failed Catalog Check Total count: 1
CBS MUM Corrupt Total count: 1
Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c.manifest
servicing\packages\Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum
servicing\packages\Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.cat
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
checkSUR.log
=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22574
Package Version 16.0
2012-11-08 14:38
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum Line 1:
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c.manifest amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c
Summary:
Seconds executed: 300
Found 2 errors
CSI Manifest Failed Catalog Check Total count: 1
CBS MUM Corrupt Total count: 1
Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c.manifest
servicing\packages\Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum
servicing\packages\Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.cat
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
----------------------
Any help would be appreciated as i have been working on this for over 2 days now.
Thursday, November 8, 2012 11:04 PM
Answers
-
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx
Note: Refer to the “Options for obtaining files” section to get the files required.
For detailed steps, refer to the following steps:
1. Download the KB from Microsoft Download Center. Go to https://www.microsoft.com/en-us/download/details.aspx?id=26593 This link is for Update forWindows Server 2008 x64 Edition (KB2545698)
2. Expand the package.
Assuming you downloaded the msu package to the %temp% directory and you want to expand the package to c:\targetDir, for example, run the followingcommand:
expand %Windir%\Temp\Windows6.0-KB2545698-x64.msu /f:* c:\targetDir
3. Expand the cab files to the same location.
expand C:\targetDir\Windows6.0-KB2545698-x64.cab /f:* c:\targetDir
All the files will be located in the above directory as only payload files are located in specific subdirectories.
Occasionally, the required file may be a root package. Check the above link for detailed instructions.
Then, move to the following steps to fix the error:
4. Copy the files to %Windir%\Temp\CheckSUR directory of the corrupted computer following the subdirectory format as follows:
All files of type *.mum and *.cat should be placed in the %windir%\Temp\CheckSUR\servicing\packages directoryAll files of type *.manifest should be placed in the %windir%\Temp\CheckSUR\manifests\ directory
For Example:
copy C:\targetDir\package_for_kb2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.cat to %Windir%\Temp\CheckSUR\servicing\packages\
copy C:\targetDir\package_for_kb2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum to %Windir%\Temp\CheckSUR\servicing\packages\Repeat for rest of files
5. Rerun the System Update Readiness tool.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Saturday, November 10, 2012 12:57 AM
All replies
-
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx
Note: Refer to the “Options for obtaining files” section to get the files required.
For detailed steps, refer to the following steps:
1. Download the KB from Microsoft Download Center. Go to https://www.microsoft.com/en-us/download/details.aspx?id=26593 This link is for Update forWindows Server 2008 x64 Edition (KB2545698)
2. Expand the package.
Assuming you downloaded the msu package to the %temp% directory and you want to expand the package to c:\targetDir, for example, run the followingcommand:
expand %Windir%\Temp\Windows6.0-KB2545698-x64.msu /f:* c:\targetDir
3. Expand the cab files to the same location.
expand C:\targetDir\Windows6.0-KB2545698-x64.cab /f:* c:\targetDir
All the files will be located in the above directory as only payload files are located in specific subdirectories.
Occasionally, the required file may be a root package. Check the above link for detailed instructions.
Then, move to the following steps to fix the error:
4. Copy the files to %Windir%\Temp\CheckSUR directory of the corrupted computer following the subdirectory format as follows:
All files of type *.mum and *.cat should be placed in the %windir%\Temp\CheckSUR\servicing\packages directoryAll files of type *.manifest should be placed in the %windir%\Temp\CheckSUR\manifests\ directory
For Example:
copy C:\targetDir\package_for_kb2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.cat to %Windir%\Temp\CheckSUR\servicing\packages\
copy C:\targetDir\package_for_kb2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum to %Windir%\Temp\CheckSUR\servicing\packages\Repeat for rest of files
5. Rerun the System Update Readiness tool.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Saturday, November 10, 2012 12:57 AM -
Great thanks, sorry for the late reply but that worked great. Now i have a problem with the manifest files. the ones i need are not listed in the download.
Here is a new report.
=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22574
Package Version 16.0
2012-12-14 00:19Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum Line 1:
(fix) CBS MUM Corrupt CBS File Replaced Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB2545698_server~31bf3856ad364e35~amd64~~6.0.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.1.8112.20551_none_c2455b74f8ed4b95.manifest x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.1.8112.20551_none_c2455b74f8ed4b95
(f) CSI Manifest Zero Length 0x00000000 winsxs\Manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20553_none_811f70aebd94e6dc.manifest amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20553_none_811f70aebd94e6dc
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c.manifest amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1cSummary:
Seconds executed: 749
Found 4 errors
Fixed 1 errors
CSI Manifest Zero Length Total count: 2
CSI Manifest Failed Catalog Check Total count: 1
CBS MUM Corrupt Total count: 1
Fixed: CBS MUM Corrupt. Total count: 1
Fixed: CBS Paired File. Total count: 1Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.1.8112.20551_none_c2455b74f8ed4b95.manifest
winsxs\manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.20553_none_811f70aebd94e6dc.manifest
winsxs\manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.1.8112.16440_none_809da2f1a471df1c.manifestCustomer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
Friday, December 14, 2012 9:00 AM -
Ok so I put the files up here.
https://docs.google.com/folder/d/0B304XeoKstFqUlNTLVl1QUxhdkE/edit
Dowload them and place in %windir%\Temp\CheckSUR\manifests\ directory. Then rerun SUR tool.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Saturday, December 15, 2012 7:39 PM