CO_E_SERVER_EXEC_FAILURE (Server Manager) Server 2008 R2 Std

[madlan]

Hi All,

I was wondering if someone could help me with an issue that I've been struggling with for some time.
The core issue\symptom is being unable to open roles or features in server manager (This is a VPS So cannot boot from CD to repair):



CO_E_SERVER_EXEC_FAILURE 0x80080005

If I try to start the trusted installer I get this error:

I've been trying to follow two guides: Windows Modules Installer Error 126 - Fix
and http://www.sevenforums.com/tutorial...eadiness-tool-checksur-log-file-analyzis.html

I've checked that the registry path is correct (HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version):

Which matches the Trusted Installer ID (C:\Windows\WinSxS directory\
)

(Not sure why theres two folders...?)


Something odd I noticed, the missing components listed in the CheckSUR.txt file have no version numbers, just 0.0.0.0 : ...31bf3856ad364e35_0.0.0.0_none...


CheckSUR.txt:
----------------------------

Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 22.0
2014-01-06 15:39

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27 Package_6_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27 Package_7_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27 Package_7_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27 Package_7_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27 Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27 Package_3_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27 Package_3_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-browserservice-netapi_31bf3856ad364e35_0.0.0.0_none_ad85f50a98427e27
.....................................
.....................................
.....................................


Summary:
Seconds executed: 3583
Found 440 errors
CSI Create Hard Link Failed Total count: 4
CSI Missing Identity Total count: 255
CSI Repairing: CreateFile Failed Total count: 1
CSI Payload File Missing Total count: 103
CBS Watchlist Component Missing Total count: 77

 

[NoelDP]

The Watchlist components are the things that tie together the Package files with the content - the registry entries are present, but the files aren't.
This creates a problem - as you've found out!
Please upload the full CheckSUR.Persist.log file, and I'll see what I can do about creating a fix - it may take a while!

 

[madlan]

Very very kind! thank you

File attached.

 

[NoelDP]

Hmmm - here's the summary from the first run of the tool...

Summary:
Seconds executed: 4157
 Found 652 errors
 Fixed 212 errors
  CSI Create Hard Link Failed Total count: 4
  CSI Catalog Missing Total count: 2
  Fixed: CSI Catalog Missing.  Total count: 2
  CSI Missing Component Key Total count: 21
  Fixed: CSI Missing Component Key.  Total count: 21
  CSI Missing Pinned Component Key Total count: 44
  Fixed: CSI Missing Pinned Component Key.  Total count: 44
  CSI Missing Identity Total count: 309
  Fixed: CSI Missing Identity.  Total count: 54
  CSI Missing C Mark Total count: 65
  Fixed: CSI Missing C Mark.  Total count: 65
  CSI Repairing: CreateFile Failed Total count: 1
  CSI Payload File Missing Total count: 103
  CSI F Mark Missing Total count: 68
  Fixed: CSI F Mark Missing.  Total count: 68
  CBS Watchlist Component Missing Total count: 77
  CSI Catalog Thumbprint Invalid Total count: 2
  Fixed: CSI Catalog Thumbprint Invalid.  Total count: 2

There are indications in the remaining errors that there may be problems with permissions - or at least access - to certain files...
(snippets concatenated)

(f) CSI Payload File Missing 0x00000000 GlobalInstallOrder.xml amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f 
(f) CSI Repairing: CreateFile Failed 0x00000003 winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\GlobalInstallOrder.xml amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f 
(f) CSI Payload File Missing 0x00000000 CbsMsg.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f 
(f) CSI Create Hard Link Failed 0x00000003 CbsMsg.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f Could not delete existing file
(f) CSI Create Hard Link Failed 0x000000B7 CbsMsg.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f Linking to C:\Windows\winsxs\amd64_microsoft-windows-servicingstack-msg_31bf3856ad364e35_6.1.7600.16385_none_9a945b9a44b86e2d\CbsMsg.dll

In view of the second error, I suspect that an SFC /SCANNOW may fail - but please try it anyhow, and post the resulting CBS.log file whatever the result.

I'm beginning to think that the problems found here may simply be the tip of a large iceberg - any you may be better off attempting a repair install, than attempting to manually fix the known errors.

 

[madlan]

Hi,

I get the following error from SFC /SCANNOW:
Windows Resource Protection could not start the repair service.

Is it possible to change the permissions on the problem folder\files?

Thanks.

 

[NoelDP]

Let's have a look at what they are now... (there are a lot of other files missing from that folder as well)

Open an Elevated COmmand Prompt, and run the following commands

ICACLS C:\Windows\Winsxs >>%userprofile%\desktop\npfile.txt
ICACLS C:\Windows\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f /T >>%userprofile%\desktop\npfile.txt

They should create a new file on your desktop 'npfile.txt' - please upload that

 

[madlan]

C:\Windows\winsxs>ICACLS C:\Windows\Winsxs\amd64_microsoft-windows-servicingstac
k_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f /T >>%userprofile%\deskt
op\npfile.txt
C:\Windows\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.76
01.17592_none_672ce6c3de2cb17f\amd64_installed: The system cannot find the path
specified.

I've also attached the contents of the folder "C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f"

 

[NoelDP]

Ooooh - this could be fun

CHKDSK to the rescue? - this type of error could be due to MFT corruption, or to disk problems (or something else entirely!)

Depending on the partition size, please either do a CHKDSK /R (ordinary partition) or a CKDSK /F (large partition >200GB)
then try the commands again - post the new txt file

 

[madlan]

Hmm, I've ran chkdsk /R which asked if I wanted to schedule a check for the next reboot. I hit Y and rebooted but running chkdsk again it lists the same issues so not sure if it actually ran on reboot?

It's a VPS so I cannot see the startup process or initiate a repair install

 

[NoelDP]

This probably means that the CHKDSK didn't run - a CHKDSK /R can take a couple of hours even for a 200GB drive, as it checks every sector on the drive for readability (A /F doesn't do the readability checks)

Try again using /F and see if that works. - there should also be a record of the attempted /R run in the Event Viewer logs
Event Viewer > Windows Logs > Application > Filter on Wininit as Event Source.

 

[madlan]

Hi Noel,

Apparently the VPS provider disable chkdsk on boot - I've decided to wipe it and start again!

Thanks for your help and guidance

 

[NoelDP]

You're welcome!

Good luck with it.