>>>Sharing—general CheckSur.log troubleshooting<<<:
http://social.microsoft.com/Forums/en-US/partnerwinserver/thread/3d82d527-14d8-4db3-b440-ba1f73d84512

We usually haveServer Manager issue, Service Pack installation failure which is caused by servicing corruption detected by CheckSUR tool(http://support.microsoft.com/kb/947821). It would generate a log at %windir%\logs\cbs\checksur.log as below:

Summary:

Seconds executed:

Found XX errors

Fixed XX errors

Generally, it would have two kinds of result as below:

1. The System Update Readiness Tool has fixed all found errors, as in the example below:

Summary:

Seconds executed: 100

Found 10 errors

Fixed 10 errors

2. If you get the Unavailable repair files message, this indicates that some of the inconsistent files found by the tool cannot be fixed as the correct versions of the replacement files are not carried by the tool. After this message appears, a list of the missing files follows.

Summary:

Seconds executed: 264

Found 3 errors

CBS MUM Missing Total Count: 3

Unavailable repair files:

servicing\packages\Package_for_KB958690_sc_0~31bf3856ad364e35~amd64~~6.0.1.6.mum

servicing\packages\Package_for_KB958690_sc~31bf3856ad364e35~amd64~~6.0.1.6.mum

servicing\packages\Package_for_KB958690~31bf3856ad364e35~amd64~~6.0.1.6.mum

servicing\packages\Package_for_KB958690_sc_0~31bf3856ad364e35~amd64~~6.0.1.6.cat

servicing\packages\Package_for_KB958690_sc~31bf3856ad364e35~amd64~~6.0.1.6.cat

servicing\packages\Package_for_KB958690~31bf3856ad364e35~amd64~~6.0.1.6.cat

winsxs\manifests\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0.manifest

winsxs\manifests\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6.manifest

To resolve the mum, cat files missing issue, most of us know that copying from a working source computer with same version to the problematic computer could fix the issue. However, I would like to share the solutions to fix the error message except mum, cat files missing as below:

1. If you get a Payload File Missing message, then the binary required is not available. This means that the issue is not fixed.

Summary:

Seconds executed: 100

Found 5 errors

Fix 2 errors

CSI Payload File Missing Total count: 5

Fix CSI Payload File Missing Total Count: 2

(f) CSI Payload File Missing 0x00000000 admparse.dll x86_microsoft-windows-ie-adminkitmostfiles_31bf3856ad364e35_6.0.6000.16386_none_abfb5fd109dad8b8 servicing_31bf3856ad364e35_6.0.6000.16386_none_23ddbf36a8a961bc

(f) CSI Payload File Missing 0x00000000 bootmgr x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_6.0.6000.16386_none_c0f2f087b6457236

(fix) CSI Payload File Missing 0x00000000 bootmgr x86_microsoft-windows-b..re-bootmanager-pcat_31bf3856ad364e35_6.0.6000.16386_none_c0f2f087b6457236

(f) CSI Payload File Missing 0x00000000 winload.exe x86_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.0.6000.16386_none_6701d52e8fdf8d45

(f) CSI Payload File Missing 0x00000000 setbcdlocale.dll x86_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.0.6000.16386_none_6701d52e8fdf8d45

(f) CSI Payload File Missing 0x00000000 winresume.exe x86_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.0.6000.16386_none_6701d52e8fdf8d45

(fix) CSI Payload File Missing 0x00000000 winresume.exe x86_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.0.6000.16386_none_6701d52e8fdf8d45

Solution:

========

a. Find out which payload files are missing by looking at checkSUR.log. Identify any line that have (f) that is not followed by (fix). From the previous example the three payload files that are not fixed are:

(f) CSI Payload File Missing 0x00000000 winload.exe x86_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.0.6000.16386_none_6701d52e8fdf8d45

(f) CSI Payload File Missing 0x00000000 setbcdlocale.dll x86_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.0.6000.16386_none_6701d52e8fdf8d45

(f) CSI Payload File Missing 0x00000000 admparse.dll x86_microsoft-windows-ie-adminkitmostfiles_31bf3856ad364e35_6.0.6000.16386_none_abfb5fd109dad8b8 servicing_31bf3856ad364e35_6.0.6000.16386_none_23ddbf36a8a961bc

b. Get the files required from other sources. The options available can be found in the “Options for obtaining files” section below.

Note: Ensure the binary you get from matches the directory name mentioned on checkSUR.log. For the above example, the directory name is x86_microsoft-windows-ie-adminkitmostfiles_31bf3856ad364e35_6.0.6000.16386_none_abfb5fd109dad8b8

c. Paste the files onto the proper subdirectory under c:\windows\winsxs.

Important: Please only paste the files that are needed. Replacing additional files may lead the system into an unserviceable state.

Before placing the files in the appropriate locations, you may need to grant yourself permissions to edit the folder’s contents; below is a quick guide on how to achieve this.

· At an elevated command prompt: takeown /f Path_And_File_Name

· Next, to grant administrators full access to the file: icacls Path_And_File_Name /GRANT ADMINISTRATOR:F

· To replace the file with a known good copy: Copy Path_And_File_Name_Of_Source_File Path_And_File_Name_Of_Destination

2. Bad Pending.xml

The file used to record operations required during system reboot is bad or corruptedCheckSUR.log does not record this information, however this can be easily identified by checking if one of the registry values below exist:

· HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\@CorruptPendingXml (REG_SZ)

· HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\@CorruptPendingXmlIdentifiers (REG_SZ)

Important In Windows 7 and Windows Server 2008 R2, a restart may help resolve the problem by removing the corrupted file. While users may see that some updates fail after a reboot, reinstalling the updates should now succeed.

In Windows Vista and Windows Server 2008, no solution to recover this file exists. For more information followed method three in article 949358in the Microsoft® Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=165004).

3. Bad Winner Keys

The registry used by the system to keep records of installed components is corrupt. CheckSUR.log does not record this information. However in Windows 7, this can be easily identified by checking if the registry value below exists:

· HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\@CorruptWinners (REG_SZ)

Note: For Windows Vista SP1 and higher, check this phrase on %windir%\logs\CBS\CBS.log or CBS.persist.log to identify winners key corruption “Install-map entry missing component key in populate”.

CheckSUR does not currently repair this type of corruption. Attempting a System Restore or reinstalling the operating system is recommended.

Regarding the source for obtaining files, we could gain the files as below:

1. Obtaining a file from another computer

2. Obtain files from the update package

3. Obtaining the files from a Windows DVD

For more details, please refer to the website below:

Advanced guidelines for diagnosing and fixing servicing corruption

http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx

 

Comments are closed.