Answered by:
Unable to view Roles & Features in Server Manager

Question
-
Help! Server Manager has suddenly stopped displaying Roles and Features but I can't work out why. I have followed all the instructions in other threads but none have fixed my problem.
When I download the System Update Readiness Tool (http://support.microsoft.com/kb/947821) the application launches ok but does not complete and does not write any logs to the C:\Windows\Logs\CBS folder so I can't even find out which update has caused the issue.
Happy to share any logs or error messages if it helps. I haven't posted any here because I'm still not sure what's causing the issue. The Event log has a number of TrustedInstaller service failures which i can post if they will help?
Windows Update is constantly trying to run but is stuck at 0%.
My Server is Windows 2008 R2 running on a x64 AMD server.
Any help much appreciated.
Tuesday, November 9, 2010 9:01 PM
Answers
-
Here's what I ended up doing in the VM to extract and manually kick it off (note that I got the switches from procmon when I looked at what it appeared to be doing). Note that these commands were run from and elevated command prompt and the SUR tool update was downloaded to a temporary working directory, c:\servicing.
Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>cd c:\servicing c:\servicing>wusa Windows6.1-KB947821-v7-x64.msu /extract:c:\servicing\kb947821 c:\servicing>cd kb947821 c:\servicing\kb947821>CheckSURPackage.EXE /Quiet /WindowsUpdate /DeleteBadCab /pkgversion=9.0 /fixcab=%windir%\CheckSur\v1.0\*.CAB /fixcab=%windir%\CheckSur\*.CAB /pkgdownload c:\servicing\kb947821>
The last command is somewhat deceiving as the command prompt immediately returns and is ready for additional commands. You'll see three processes kick off, checksur.exe, checksurlauncher.exe, CheckSURPackage.exe. The checksur.exe process seems to do most of the work and uses most of the memory (between 28 and 35 MB) and CPU time (between 4 and 10%) for the package. When these three exit, then the log file should be generated at c:\Windows\Logs\CBS\CheckSUR.log.
-- Mike Burr- Marked as answer by DivingMonkey Monday, November 15, 2010 2:24 PM
Monday, November 15, 2010 11:00 AM -
Hi Ben,
Glad to hear that you got it worked out. My apologies for not getting back to you sooner, but I usually am unable to respond to posts during business hours here and I usually post in the evening or in the early morning. I'll post the steps here for getting the files directly from the update package in case anyone else runs across this thread with a similar issue. I downloaded the Server 2008 R2 update to the same temporary folder as before, c:\servicing, and ran the following commands from an elevated command prompt,
Update for Windows Server 2008 R2 x64 Edition (KB2345886)
http://www.microsoft.com/downloads/en/results.aspx?freetext=kb2345886&displaylang=en&stype=s_basic
Note the link above is a generic search link in case someone needs the update for a different OS.
Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>cd c:\servicing c:\servicing>wusa Windows6.1-KB2345886-x64.msu /extract:c:\servicing\kb2345886 c:\servicing>cd kb2345886 c:\servicing\kb2345886>mkdir files c:\servicing\kb2345886>expand Windows6.1-KB2345886-x64.cab -F:* files Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_5fcc2897520742ce.manifest to Extraction Queue Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_5f532a3238ddec6f.manifest to Extraction Queue Adding files\update.mum to Extraction Queue Adding files\update.cat to Extraction Queue Adding files\update-bf.mum to Extraction Queue Adding files\update-bf.cat to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16664_none_5fdfc51b29c8c39a\srvnet.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20789_none_6058c38042f219f9\srvnet.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20789_none_366f2ebb2946b708\srv2.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16664_none_35f63056101d60a9\srv2.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16664_none_36010042101544b8\srv.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20789_none_3679fea7293e9b17\srv.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\srvsvc.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\srvsvc.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\sscore.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\sscore.dll to Extraction Queue Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_5fcc2897520742ce\sscore.dll to Extraction Queue Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_5f532a3238ddec6f\sscore.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16664_none_5fdfc51b29c8c39a.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\smbserver-ppdlic.xrm-ms to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\smbserver-ppdlic.xrm-ms to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20789_none_6058c38042f219f9.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20789_none_366f2ebb2946b708.manifest to Extraction Queue Adding files\amd64_f60a62f57ba5e8075a6740f539ab1358_31bf3856ad364e35_6.1.7600.16664_none_c5bf4ee046d93c5f.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16664_none_35f63056101d60a9.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_bf6c60b476fc0e5881d08f30295ad8dc_31bf3856ad364e35_6.1.7600.16664_none_45e206e5acd674fb.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20789_none_3679fea7293e9b17.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_9d953bea998ee670e0091b63d284a09a_31bf3856ad364e35_6.1.7600.20789_none_719cf72566c8025d.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16664_none_36010042101544b8.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_98be01555fcbc6fccfc61f3db00cecc4_31bf3856ad364e35_6.1.7600.16664_none_7dcad3eead131963.manifest to Extraction Queue Adding files\package_2_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_8119d5f2965f172c790e6cd36f13db2e_31bf3856ad364e35_6.1.7600.16664_none_cf5679c5bb29d787.manifest to Extraction Queue Adding files\package_2_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_6b77eede10ed5dcbb31545b9d72f638f_31bf3856ad364e35_6.1.7600.20789_none_2767e4b8c3a66ec1.manifest to Extraction Queue Adding files\package_2_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_39998a16599b59247895baba3129f207_31bf3856ad364e35_6.1.7600.20789_none_d2eeedd1cd8a2f65.manifest to Extraction Queue Adding files\package_2_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_0faf1deebe383942f8f381afc132aa88_31bf3856ad364e35_6.1.7600.20789_none_52b82e586461d09b.manifest to Extraction Queue Adding files\package_1_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\package_1_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\package_1_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\package_1_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\netserv.inf to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\netserv.inf to Extraction Queue Expanding Files .... Expanding Files Complete ... 50 files total. c:\servicing\kb2345886>
Following these steps exactly, the files to restore should be in c:\servicing\kb2345886\files. I have bolded the ones that were needed based on your CheckSUR.log. These files would need to be restored to %systemroot%\servicing\Packages (usually c:\Windows\servicing\Packages). Note that you may need to take ownership of the c:\Windows\servicing\Packages directory and assign yourself permissions to create files to perform the restore. Note the original ownership and perms so that you can reset them after the restore is done.
-- Mike Burr- Marked as answer by DivingMonkey Tuesday, November 16, 2010 8:35 AM
Tuesday, November 16, 2010 4:36 AM
All replies
-
Hi Mike
Thanks for your reply. Your advice has partially helped. I had to do the aggressive Windows Update fix however some of the dlls did not register cleanly or successfully:
Loaded but with entry-point error:
regsvr32.exe shdocvw.dll
regsvr32.exe qmgr.dll
regsvr32.exe gpkcsp.dll
regsvr32.exe browseui.dll
Failed to load:
regsvr32.exe sccbase.dll
regsvr32.exe wuaueng1.dll
regsvr32.exe msxml.dll
regsvr32.exe initpki.dll
regsvr32.exe mshtml.dll
regsvr32.exe slbcsp.dll
regsvr32.exe wuweb.dll
regsvr32.exe wucltui.dll
regsvr32.exe muweb.dllWhen I rebooted my server after reinstalling the Update Client Windows Update kicked into life but promptly got stuck again at 69% where it's been for the last 24 hours. I tried to run SUR again but I have the same result - it's been stuck at searching for updates for the last 12 hours.
Everything else on the server that I have checked is working okay.
Do you have any more advice?
Thanks
Ben
Thursday, November 11, 2010 8:00 AM -
I ran through a sample from your list and I received the same errors onmy 2008 R2 system ( and could not find the spcific files I sampled fromthe second list), so it is possibly a difference between the Vista/2008family and the 7/2008 R2 family.Can you upload your c:\Windows\WindowsUpdate.log andC:\Windows\Logs\ServerManager.log and c:\Windows\Logs\CBS\CBS.log filesto skydrive and post a link to the thread,
-- Mike BurrThursday, November 11, 2010 4:18 PM -
Hi Mike
I've uploaded the files to my skydrive as requested - http://cid-7f81f12572b103a9.skydrive.live.com/redir.aspx?resid=7F81F12572B103A9!119
Regards
Ben
Thursday, November 11, 2010 6:08 PM -
Hi Ben,
Could you please also upload them to the following site?
https://sftus.one.microsoft.com/choosetransfer.aspx?key=ca76c7a7-1c38-4fa9-a827-67f5ca235d76
Password: KK4H-tOKos
Tim Quan
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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, November 12, 2010 4:58 AM -
Hi Tim
Files uploaded as requested.
Ben
Friday, November 12, 2010 11:23 AM -
Here's what I'm seeing,2010-11-11 18:00:01, Info CBS TrustedInstaller terminated unexpectedly with pending operations the last time around; will skip core startup processing.2010-11-11 18:00:01, Info CBS Starting TrustedInstaller initialization.Do you have an xml file at c:\windows\winsxs\pending.xml orc:\windows\winsxs\pending.xml.bad that you can upload? Also, let's lookat c:\windows\winsxs\poqexec.log and c:\windows\logs\DPX\setupact.log.
-- Mike BurrFriday, November 12, 2010 11:26 AM -
Hi Mike
There's no pending.xml or .bad file in the winsxs folder, just reboot.xml and poqexec.log plus a load of folders. I've uploaded the two log files to my skydrive as requested.
Thanks again for your help with this.
Ben
Friday, November 12, 2010 2:35 PM -
If it helps here's the error message in the event log for TrustedInstaller:
Faulting application name: TrustedInstaller.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc4b0
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
Exception code: 0xc00000fd
Fault offset: 0x00000000000550b7
Faulting process id: 0x1574
Faulting application start time: 0x01cb813b5d0bb032
Faulting application path: C:\Windows\servicing\TrustedInstaller.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: bbec0f25-ed2e-11df-bdcf-005056c00008Do you think TrustedInstaller could be goosed and need reinstalling?
Cheers
Ben
Friday, November 12, 2010 2:54 PM -
In the DPX setupact.log file,
2010-11-10 20:42:21, Info DPX CreateFileW failed, FileName:\\?\C:\Windows\SoftwareDistribution\Download\e1dd1fcc8af5f1a7d33fea0da934e9b8\$dpx$.tmp\job.xml, Error:0x80070002 2010-11-10 20:43:30, Info DPX CreateFileW failed, FileName:\\?\C:\Windows\SoftwareDistribution\Download\993c1fd900b4c14870044531e532e59a\$dpx$.tmp\job.xml, Error:0x80070002 2010-11-10 20:43:57, Info DPX CreateFileW failed, FileName:\\?\C:\Windows\SoftwareDistribution\Download\c80fe8727d10de349c75a7f5f0ddc146\$dpx$.tmp\job.xml, Error:0x80070002 2010-11-10 20:44:06, Info DPX CreateFileW failed, FileName:\\?\C:\Windows\SoftwareDistribution\Download\f5798630ac67933ea7520f793bf00115\$dpx$.tmp\job.xml, Error:0x80070002 2010-11-10 21:05:10, Info DPX CreateFileW failed, FileName:\\?\C:\Windows\SoftwareDistribution\Download\993c1fd900b4c14870044531e532e59a\$dpx$.tmp\job.xml, Error:0x80070002 2010-11-10 21:05:20, Info DPX Started DPX phase: Inventory 2010-11-10 21:06:00, Info DPX Ended DPX phase: Inventory 2010-11-10 21:06:01, Info DPX CreateFileW failed, FileName:\\?\C:\Windows\SoftwareDistribution\Download\e1dd1fcc8af5f1a7d33fea0da934e9b8\$dpx$.tmp\job.xml, Error:0x80070002 2010-11-10 21:18:46, Info DPX CreateFileW failed, FileName:\\?\C:\Windows\SoftwareDistribution\Download\e1dd1fcc8af5f1a7d33fea0da934e9b8\$dpx$.tmp\job.xml, Error:0x80070002 2010-11-10 22:18:12, Info DPX Started DPX phase: Resume and Download Job 2010-11-10 22:18:12, Info DPX Started DPX phase: Apply Deltas Provided In File 2010-11-10 22:18:12, Info DPX Ended DPX phase: Apply Deltas Provided In File 2010-11-10 22:18:12, Info DPX Started DPX phase: Apply Deltas Provided In File 2010-11-10 22:18:36, Info DPX Ended DPX phase: Apply Deltas Provided In File 2010-11-10 22:18:36, Info DPX Ended DPX phase: Resume and Download Job
These appear to be somewhat normal as they exist on my systems that are patching and showing server manager properly. Can you try running
sfc /scannow
to verify the protected OS files and retry the SUR tool? When you retry it, can you give some insight into approximately where it hangs? If it hangs at a stage where it is searching for updates, I have an experimental procedure that I have been testing in a VM to kick it off manually by extracting the SUR tool update package.
-- Mike BurrSaturday, November 13, 2010 4:31 PM -
Any update?Monday, November 15, 2010 2:28 AM
-
Hi Mike/Tim
Sorry for the delay responding I have been away for the weekend. Running sfc returns no issues:
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.When I run the Windows Update Standalone Installer tool (Windows6.1-KB947821-v7-x64.msu) it displays the message 'Preparing the installation' for about 30 seconds then displays 'Searching for updates on this computer'. So far it's been 'stuck' on searching for an hour. I can't find any logs or event log messages to suggest where it's actually stuck. Does the SUR tool have any verbose logging?
Ben
Monday, November 15, 2010 10:04 AM -
Here's what I ended up doing in the VM to extract and manually kick it off (note that I got the switches from procmon when I looked at what it appeared to be doing). Note that these commands were run from and elevated command prompt and the SUR tool update was downloaded to a temporary working directory, c:\servicing.
Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>cd c:\servicing c:\servicing>wusa Windows6.1-KB947821-v7-x64.msu /extract:c:\servicing\kb947821 c:\servicing>cd kb947821 c:\servicing\kb947821>CheckSURPackage.EXE /Quiet /WindowsUpdate /DeleteBadCab /pkgversion=9.0 /fixcab=%windir%\CheckSur\v1.0\*.CAB /fixcab=%windir%\CheckSur\*.CAB /pkgdownload c:\servicing\kb947821>
The last command is somewhat deceiving as the command prompt immediately returns and is ready for additional commands. You'll see three processes kick off, checksur.exe, checksurlauncher.exe, CheckSURPackage.exe. The checksur.exe process seems to do most of the work and uses most of the memory (between 28 and 35 MB) and CPU time (between 4 and 10%) for the package. When these three exit, then the log file should be generated at c:\Windows\Logs\CBS\CheckSUR.log.
-- Mike Burr- Marked as answer by DivingMonkey Monday, November 15, 2010 2:24 PM
Monday, November 15, 2010 11:00 AM -
Mike
I've finally managed to get a log file based on your instructions:
=================================
Checking System Update Readiness.
Binary Version 6.1.7600.20751
Package Version 9.0
2010-11-15 11:30
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 507
Found 1 errors
CBS MUM Corrupt Total count: 1
Unavailable repair files:
servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.catI've downloaded the update that was corrupt but it fails to install. I think the Windows Update service has got it's nickers in a twist because it won't allow me to restart the service. I'm going to do a reboot and try the install again.
Ben
Monday, November 15, 2010 11:48 AM -
Ok... I think I must be doing something wrong. When I execute the msu it starts the SUR and gets stuck again 'Searching for updates'. Do I have to manually unpack the files?
I'm going to check back through the previous articles I read but if you can offer some assistance that would be great?
Ben
Monday, November 15, 2010 12:43 PM -
I've managed to unpack KB2345886 (64bit version) but the two files referenced in my CheckSUR.log are not present. In the end I created a new VM and installed 2008 R2 downloaded the updates from the MS website and copied across the two files that were corrupt on my main server after granting modify permissions on the servicing foler. Server Manager looks to be back in action now.
Mike - Thanks for all your help.
Monday, November 15, 2010 2:26 PM -
Hi Ben,
Glad to hear that you got it worked out. My apologies for not getting back to you sooner, but I usually am unable to respond to posts during business hours here and I usually post in the evening or in the early morning. I'll post the steps here for getting the files directly from the update package in case anyone else runs across this thread with a similar issue. I downloaded the Server 2008 R2 update to the same temporary folder as before, c:\servicing, and ran the following commands from an elevated command prompt,
Update for Windows Server 2008 R2 x64 Edition (KB2345886)
http://www.microsoft.com/downloads/en/results.aspx?freetext=kb2345886&displaylang=en&stype=s_basic
Note the link above is a generic search link in case someone needs the update for a different OS.
Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>cd c:\servicing c:\servicing>wusa Windows6.1-KB2345886-x64.msu /extract:c:\servicing\kb2345886 c:\servicing>cd kb2345886 c:\servicing\kb2345886>mkdir files c:\servicing\kb2345886>expand Windows6.1-KB2345886-x64.cab -F:* files Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_5fcc2897520742ce.manifest to Extraction Queue Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_5f532a3238ddec6f.manifest to Extraction Queue Adding files\update.mum to Extraction Queue Adding files\update.cat to Extraction Queue Adding files\update-bf.mum to Extraction Queue Adding files\update-bf.cat to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16664_none_5fdfc51b29c8c39a\srvnet.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20789_none_6058c38042f219f9\srvnet.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20789_none_366f2ebb2946b708\srv2.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16664_none_35f63056101d60a9\srv2.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16664_none_36010042101544b8\srv.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20789_none_3679fea7293e9b17\srv.sys to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\srvsvc.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\srvsvc.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\sscore.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\sscore.dll to Extraction Queue Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_5fcc2897520742ce\sscore.dll to Extraction Queue Adding files\wow64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_5f532a3238ddec6f\sscore.dll to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16664_none_5fdfc51b29c8c39a.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\smbserver-ppdlic.xrm-ms to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\smbserver-ppdlic.xrm-ms to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20789_none_6058c38042f219f9.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20789_none_366f2ebb2946b708.manifest to Extraction Queue Adding files\amd64_f60a62f57ba5e8075a6740f539ab1358_31bf3856ad364e35_6.1.7600.16664_none_c5bf4ee046d93c5f.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16664_none_35f63056101d60a9.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_bf6c60b476fc0e5881d08f30295ad8dc_31bf3856ad364e35_6.1.7600.16664_none_45e206e5acd674fb.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20789_none_3679fea7293e9b17.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_9d953bea998ee670e0091b63d284a09a_31bf3856ad364e35_6.1.7600.20789_none_719cf72566c8025d.manifest to Extraction Queue Adding files\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16664_none_36010042101544b8.manifest to Extraction Queue Adding files\package_for_kb2345886_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_98be01555fcbc6fccfc61f3db00cecc4_31bf3856ad364e35_6.1.7600.16664_none_7dcad3eead131963.manifest to Extraction Queue Adding files\package_2_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_8119d5f2965f172c790e6cd36f13db2e_31bf3856ad364e35_6.1.7600.16664_none_cf5679c5bb29d787.manifest to Extraction Queue Adding files\package_2_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_6b77eede10ed5dcbb31545b9d72f638f_31bf3856ad364e35_6.1.7600.20789_none_2767e4b8c3a66ec1.manifest to Extraction Queue Adding files\package_2_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\amd64_39998a16599b59247895baba3129f207_31bf3856ad364e35_6.1.7600.20789_none_d2eeedd1cd8a2f65.manifest to Extraction Queue Adding files\package_2_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_0faf1deebe383942f8f381afc132aa88_31bf3856ad364e35_6.1.7600.20789_none_52b82e586461d09b.manifest to Extraction Queue Adding files\package_1_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\package_1_for_kb2345886~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\package_1_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\package_1_for_kb2345886_bf~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.16664_none_54fe7fe0047d2a74\netserv.inf to Extraction Queue Adding files\amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.1.7600.20789_none_55777e451da680d3\netserv.inf to Extraction Queue Expanding Files .... Expanding Files Complete ... 50 files total. c:\servicing\kb2345886>
Following these steps exactly, the files to restore should be in c:\servicing\kb2345886\files. I have bolded the ones that were needed based on your CheckSUR.log. These files would need to be restored to %systemroot%\servicing\Packages (usually c:\Windows\servicing\Packages). Note that you may need to take ownership of the c:\Windows\servicing\Packages directory and assign yourself permissions to create files to perform the restore. Note the original ownership and perms so that you can reset them after the restore is done.
-- Mike Burr- Marked as answer by DivingMonkey Tuesday, November 16, 2010 8:35 AM
Tuesday, November 16, 2010 4:36 AM -
Mike -
Thank you SO MUCH for your post!
I have been having the same issue with one of our Server 2008 R2 machines. I followed your recommended steps exactly and the problem was solved!
Friday, December 31, 2010 1:39 PM -
Hello,
I am having a similar type of problem with a VM running Windows Server 2008 R2 Web Edition.
I set the vm up in the middle of last year and all appeared to be running ok. I was able to add roles and features and got IIS running with a number of website all running successfully. No problems were being reported in the event log and everything was ok. Unfortunately I was not able to momitor the box for a few months due to a suddden unexpected illness but have now begun to work on the server again. Windows Update has been running at all times and the only updates that failed were two Silverlight (KB978464 and KB 2416427) on 1st Nov 2010.
The error codes associated with these two updates are
KB978464 : error code 800706BE
KB 2416427 : error code 800706BA
Clicking the "Get help with this error" on both these errors shows a general window that does not specifically refer to these errors.
Coincidentally with this I an receiving between 15 and 25 errors in the Event Viewer as follows
Faulting application name: TrustedInstaller.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc4b0
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b
Exception code: 0xc00000fd
Fault offset: 0x0000000000055237
Faulting process id: 0x92c
Faulting application start time: 0x01cbaebc0686dc32
Faulting application path: C:\Windows\servicing\TrustedInstaller.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 515d9a21-1aaf-11e0-a4b1-00155d2104e9
Over the last week I have been trying to install CGI/PHP onto the server and the first step from an article in http://learn.iis.net says that I have to enable the CGI role. Going to the server manager role (and, I subsequently discovered the featues) facility I get an error message. The following is what is recorded in the app and service log for the ServerManager
Could not discover the state of the system. An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
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)
I have tried following the solutions outlined above , in particular the SUR tool and the following is contained in the CheckSUR.log. The CBS.log is 16kb large. If you want that file please advise where to upload it to.
=================
Checking System Update Readiness.
Binary Version 6.1.7600.20822
Package Version 9.0
2011-01-07 22:24Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file nameChecking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 650
Found 1 errors
CBS MUM Corrupt Total count: 1Unavailable repair files:
servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.catKB2360131 installed successfully on 16th October - this is the first date of errors appearing in the ServerManager Operational logs in the Application & Services Log.
Sorry this is so long but can you please advise what I should do to fix this?
Many thanks
Ciaran
- Edited by ITSparkles Friday, January 7, 2011 11:25 PM Sorry forgot details of the CBS.log file
Friday, January 7, 2011 11:21 PM -
Please see this thread for my discussion of KB2360131:
http://social.technet.microsoft.com/Forums/en/winservermanager/thread/e133179d-412c-4e20-8208-cec0ae401505
The files below need to be restored.
Unavailable repair files:
servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat
-- Mike Burr
MS Technologies - Development - *nix- Proposed as answer by ITSparkles Tuesday, January 11, 2011 12:13 AM
Monday, January 10, 2011 9:09 PM -
Thank you Mike,
That looks like it is working now.
Regards
Ciaran
Tuesday, January 11, 2011 12:14 AM -
Hi Mike,
The above solution worked for me.
Had the same problem on a Server 2008 R2 box.
Thanks.
Jolomi F Amuka
Wednesday, March 9, 2011 11:11 AM -
Thank you very much.
works like a charm!
Markus
Thursday, September 29, 2011 3:57 PM -
Hi Mike,
I just started to experience the same problem on one of our servers. It's a Windows Server 2008 R2 as Terminal Server and Terminal Services Broker.
I am not able to install Windows Updates on the server anymore.I already downloaded and extracted the SUR tool and created the log file.
Is there a chance you could help me to solve this problem?
Thank you very much.
Manuel
Tuesday, October 4, 2011 3:48 PM -
Sure,Can you post the CheckSUR.log file that is generated inc:\windows\logs\cbs\checksur.log? Thanks.Mike Burr
-- Mike Burr
TechnologyWednesday, October 5, 2011 1:38 PM -
Hi Mike,
please find the CheckSUR.log below:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 9.0
2011-10-04 17:21Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2559049_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file nameChecking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 679
Found 1 errors
CBS MUM Corrupt Total count: 1Unavailable repair files:
servicing\packages\Package_for_KB2559049_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB2559049_RTM~31bf3856ad364e35~amd64~~6.1.1.2.catHow would I repair/replace those two files?
Thank you for your help.
Manuel
Friday, October 7, 2011 6:41 AM -
Manuel,
Sorry for the delay. Based on the CheckSUR.log...
Looks like this is related to KB2559049 on Windows 2008 R2, Internet Explorer 8...
Cumulative Security Update for Internet Explorer 8 in Windows Server 2008 R2 x64 Edition (KB2559049)
http://www.microsoft.com/download/en/search.aspx?q=kb2559049&p=1&r=50&t=35
I downloaded the update to a temporary working directory, c:\servicing and ran the following commands from an elevated command prompt:
c:\servicing>mkdir kb2559049 c:\servicing>expand Windows6.1-KB2559049-x64.msu -F:* kb2559049 Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. Adding kb2559049\WSUSSCAN.cab to Extraction Queue Adding kb2559049\Windows6.1-KB2559049-x64.cab to Extraction Queue Adding kb2559049\Windows6.1-KB2559049-x64-pkgProperties.txt to Extraction Queue Adding kb2559049\Windows6.1-KB2559049-x64.xml to Extraction Queue Expanding Files .... Progress: 1 out of 4 files Expanding Files Complete ... 4 files total. c:\servicing>cd kb2559049 c:\servicing\kb2559049>mkdir files c:\servicing\kb2559049>expand Windows6.1-KB2559049-x64.cab -F:* files Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. ...lots of files... Adding files\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7600.20992_none_beceb8b7365f90e0.manifest to Extraction Queue Adding files\package_for_kb2559049_rtm~31bf3856ad364e35~amd64~~6.1.1.2.mum to Extraction Queue Adding files\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_8.0.7600.20992_none_1a3615098c01ea6c.manifest to Extraction Queue Adding files\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7600.16839_none_be8cfd7a1d0afad1.manifest to Extraction Queue Adding files\package_for_kb2559049_rtm~31bf3856ad364e35~amd64~~6.1.1.2.cat to Extraction Queue Adding files\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_8.0.7600.16839_none_19f459cc72ad545d.manifest to Extraction Queue ...lots of files... Expanding Files .... Expanding Files Complete ... 460 files total. c:\servicing\kb2559049>
After completing the extract, if you followed my instructions exactly, the files that you need will be in C:\servicing\kb2559049\files.
Based on your log file, you will need to restore the following files:
Package_for_KB2559049_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
Package_for_KB2559049_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
These files will need to go into c:\windows\servicing\packages. Note that you may need to take ownership to grant permissions to modify this directory. Remember to assign the original ownership and permissions after you complete the repair.
-- Mike Burr
TechnologyThursday, October 13, 2011 2:39 AM -
Thank YOU wery much! All it's work! :) Windows 2008 R2 Standart.
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 9.0
2011-10-17 14:14Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2552343_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file nameChecking Package Watchlist
I was changed that packege Package_for_KB2552343_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum in c:\windows\servicing\packages and after that my Roles and Feautures go to work :))))
PS. Sorry for my English ;)
IBS, L'OrealMonday, October 17, 2011 11:21 AM -
Mike ,Thank you!
I have been having the same issue with one of our Server 2008 R2 machines. I followed your recommended steps exactly and the problem was solved!
Wednesday, May 9, 2012 8:56 AM -
Signed in to vote this up. Thanks so much!!!Wednesday, November 28, 2012 11:38 PM
-
Hello All,
Hello All, Am unable to Add or Remove Any roles from the system Manager. Any Ideas? My CheckSUR log below
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-05-27 10:39
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
(f) CSI Unable to Query Store Version 0x00000002
Summary:
Seconds executed: 11
Found 1 errors
CSI Unable to Query Store Version Total count: 1
Monday, May 27, 2013 3:32 PM