How to handle Windows 0x800706be errors

Case scene

This example is a phenomenon that occurs after a collective reboot after a multiple overlay update

Figure 1 at the time of the failure of the scene, from the Servermanager of an abnormal error

Unable to discover the state of the system. An unexpected exception was found:

System.Runtime.InteropServices.COMException (0X800706BE): Remote Procedure call failed. (Exception from HRESULT:0X800706BE)

In System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal (Int32 errorcode, IntPtr errorinfo)

In Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage (intptr& session, intptr& Package

In Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo ()

In Microsoft.Windows.ServerManager.ComponentInstaller.Initialize ()

In Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery ()

In Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery ()

In Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult (Refreshtype refreshtype)

In Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult (Object state)

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/OS/home/

The error shown in the illustration above results in the corresponding Service manager not being able to add/remove roles and functions, recalling that the previous operation was to update the system, install new system updates, antivirus software updates, IE10, and some other drivers.

Plus the system has its own error code hint, by retrieving Microsoft's Knowledge Base (http://Support.microsoft.com) found that may be the result of complex intertwined update, resulting in some files and essential content lost or not, I used the corresponding KB947821 Update Error Repair tool.

Detailed content please contact the problem friend click on the link to check carefully: http://support.microsoft.com/kb/947821 the error code in the connection does not contain my this, but ultimately solves the problem, the following is the KB diagnostics log.

=================================

Checking System Update Readiness.

Binary Version 6.1.7601.21645

Package Version 18.0

2013-05-13 21:42

Checking Windows Servicing Packages

Checking Package manifests and catalogs

(f) CBS MUM corrupt 0x00000000 servicing\packages\package_for_kb2691442_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

(fix) CBS MUM corrupt CBS File replaced Package_for_kb2691442_rtm~31bf3856ad364e35~amd64~~6.1.1.3.mum from Cabinet:c:\windo Ws\checksur\v1.0\windows6.1-servicing-x64-2jan13.cab.

(fix) CBS paired file CBS file also replacedpackage_for_kb2691442_rtm~31bf3856ad364e35~amd64~~6.1.1.3.cat from Cabinet:c:\wi Ndows\checksur\v1.0\windows6.1-servicing-x64-2jan13.cab.

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:

Seconds executed:424

Found 1 Errors

Fixed 1 Errors

CBS MUM Corrupt Total count:1

Fixed:cbs MUM corrupt. Total Count:1

Fixed:cbs paired File. Total Count:1

(W) Unable to get system disk properties0x0000045d Ioctl_storage_query_property disk Cache

It should be very detailed, showing that the entire resolution process has been recorded (extracted KB file replacement/added to the system) so that it is complete, so that the confusion files caused by staggered updates are smoothed.

Summary:

This KB is interesting, almost all of the failures and problems caused by the update can be resolved, or even some of the documentation does not exist in the error code repair, if a friend encountered update related problems in many of the invalid when the visionary can implement this KB.

At the same time to deal with the multiplex update when it is still very recommended that you follow, it is best not to add together updates, and for accidental power outages and other dangerous operations must have a sense of risk.

For this KB to see Microsoft's update date should be a monthly, for the Windows 8 version is very useful, and for Windows 8来 said that no need to separate this KB can complete self-healing, using the DISM command, and for Windows Server 2012 Since the system's health has exceeded all previous windows, this KB does not apply to this system.