locked
Yet another Roles & Service corruption thread. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello there

    I have the same problem mentioned in quite a few threads already (namely the Roles/Windows Modules installer/Service corruption), however they have been little help to me.

    My system is a Windows Server 2008 R2 x64.

    I can tell from the even log, that something broke sometime in October, after an automatic windows update.

     

    The Windows Modules installer is completely broken, so installing stuff is often tricky, and the windows update service hangs when attempting to stop it.

    However, thanks to Mike Burr in another thread, I managed to run the System Update Readiness Tool by extracting it and then the following parameters:

     

    CheckSURPackage.EXE /Quiet /WindowsUpdate /DeleteBadCab /pkgversion=9.0 /fixcab=%windir%\CheckSur\v1.0\*.CAB /fixcab=%windir%\CheckSur\*.CAB /pkgdownload

     

    It did its thing and I got a log file out of it:

     

    =================================
Checking System Update Readiness.
Binary Version 6.0.6002.22511
Package Version 9.0
2010-12-02 13:12

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum.mum		Expected file name Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum does not match the actual file name
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum		Line 10:    <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10:    <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10:    <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-Xps-Foundation-Server-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10:    <customInformation SoftBlockLink="http://go.microsoft.com/
(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 name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 287
 Found 6 errors
 CBS MUM Corrupt Total count: 6

Unavailable repair files:
	servicing\packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum.mum
	servicing\packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum
	servicing\packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
	servicing\packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
	servicing\packages\Microsoft-Windows-Xps-Foundation-Server-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
	servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum 
	servicing\packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum.cat
	servicing\packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.cat
	servicing\packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.cat
	servicing\packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.cat
	servicing\packages\Microsoft-Windows-Xps-Foundation-Server-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.cat
	servicing\packages\Package_for_KB2360131_RTM~31bf3856ad364e35~amd64~~6.1.1.3.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.

     

    This is my newest log file, after attempting to repair using the two files I already tracked down by their KB number:

    package_for_kb2360131_rtm~31bf3856ad364e35~amd64~~6.1.1.3.mum

    package_for_kb2360131_rtm~31bf3856ad364e35~amd64~~6.1.1.3.cat

     

    However, these repair files now show up in the list as "unavailable repair files" (as you can see in the log file), even though they are placed in the right place (%windir%\servicing\packages)

    So I now have a 6th "error" because of them.

    Btw. I also tried placing the files in \Windows\Temp\CheckSUR\servicing\Packages directory, which the MS article on service corruption & repair mentioned; this didn't work either.

     

    So I'm running out of materials to try.

    Hope some of you fine folk have some good ideas.

    If you need more info on f.ex. the event log errors, let me know.

    Thursday, December 2, 2010 12:45 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
     
    The remaining packages should be obtained from another server with the
    same OS/architecture or obtained from the install media using imagex,
    see my procedure at
     
     
    -- Mike Burr
    MS Technologies - Development - *nix
    Thursday, December 2, 2010 9:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mike, thanks for the reply. I'll see if I can locate an iso of it from within our organization.

     

    I have a question about the behavior I described in my first post.

    Initially I had 5 errors, but after downloading and extracting  KB2360131 and placing package_for_kb2360131_rtm~31bf3856ad364e35~amd64~~6.1.1.3.cat & mum in the windows\servicing\packages folder I now get an additional error:

    Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum.cat & mum

    Is that normal?

    Friday, December 3, 2010 12:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm not completely sure, I usually restore all of the files at once, rather than incrementally, but on occasion I have seen it need more repair files after finishing a restore.
    -- Mike Burr
    MS Technologies - Development - *nix
    Saturday, December 4, 2010 12:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've managed to fix the Roles system by using the above approach.

    However there are still problems with:

    • Windows Update - doesn't work.
    • TrustedInstaller - doesn't work.
    • Windows Modules Installer keeps crashing (might be the same as TrustedInstaller, I don't know).

    The Application log gives me this error on the 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: 0x00000000000536ba
Faulting process id: 0x1b98
Faulting application start time: 0x01cb96c7800461e2
Faulting application path: C:\Windows\servicing\TrustedInstaller.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c0cd1523-02ba-11e0-b9c7-002564df2fa7

    I have quite a lot of 10010 DistributedCOM errors in the System log:
    The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
    The server {9B1F122C-2982-4E91-AA8B-E071D54F2A4D} did not register with DCOM within the required timeout.
    The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout.
A lot with this GUID.

    Another (apparently) DCOM error in the Application log:
    The COM+ Event System could not marshal the subscriber for subscription {F3E76D79-1C1F-495E-8B7F-F275F7CAAB07}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The HRESULT was 80070005.

    The System Readiness Tool still claim there are 4 corrupt mum files (even though I have found and placed those files already):
    (f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-Xps-Foundation-Server-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/
    I don't get why line 10 apparently is corrupt in those files, it seems fine upon inspection.


    Here is the entire log for your leisure:
    =================================
Checking System Update Readiness.
Binary Version 6.0.6002.22511
Package Version 9.0
2010-12-08 14:48

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/
(f)	CBS MUM Corrupt	0x800F080D	servicing\Packages\Microsoft-Windows-Xps-Foundation-Server-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum		Line 10: <customInformation SoftBlockLink="http://go.microsoft.com/

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 258
 Found 4 errors
 CBS MUM Corrupt Total count: 4

Unavailable repair files:
	servicing\packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum
	servicing\packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
	servicing\packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
	servicing\packages\Microsoft-Windows-Xps-Foundation-Server-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum
	servicing\packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.cat
	servicing\packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.cat
	servicing\packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.cat
	servicing\packages\Microsoft-Windows-Xps-Foundation-Server-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.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.
    Wednesday, December 8, 2010 2:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm a little confused by your post, did you restore all of the files listed under "Unavailable repair files" above?
    -- Mike Burr
    MS Technologies - Development - *nix
    Thursday, December 9, 2010 1:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mike

    Yes I did, all the files have been located from another Windows Server 2008 R2 just installed for that purpose (and fully updated), and placed in %windir%\servicing\packages.

    I, myself, don't understand why it continues to complain about them.

    Maybe they are corrupt everywhere? It does complain about line 10 in the mum-file, which I inspected: Couldn't find anything wrong with line 10.

    I'll check the "just-installed" version with the Readiness Tool.

    Thursday, December 9, 2010 12:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Going back to your original CheckSUR.log, it appears that you are using
    2008 (not R2), or you ran the 2008 version of the SUR tool,
     
    Binary Version 6.0.6002.22511
     
     
    -- Mike Burr
    MS Technologies - Development - *nix
    Thursday, December 9, 2010 9:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ahh Thanks Mike. Didn't know there were 2 versions of the SUR tool.

    I apparently downloaded the SUR tool for 2008.

    I'm downloading this one as we speak:

    http://go.microsoft.com/fwlink/?LinkID=180979

     

    Thanks, cant wait to try it out.

    Friday, December 10, 2010 4:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Use this one:

     

    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=32978546-8108-408f-b78e-0e95eff14c92

     

    Tim Quan

     

    Monday, December 13, 2010 2:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Use this one:

     

    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=32978546-8108-408f-b78e-0e95eff14c92

     

    Tim Quan

     

    Hi Tim

    I don't think thats for the R2 version.

    It says so on the page: Supported Operating Systems:Windows Server 2008

     

    I believe that one is what I started with.

    Anyway, the SUR tool for R2 says I only need two files. So I just need to locate those I guess.

     

    Thanks for the help.

    [EDIT]

    I've located the last two files needed.
    After a reboot, everything works as intended again.

    Thanks for the help Mike and Tim.

    Monday, December 13, 2010 9:01 AM