I've been looking at this problem for a few days now trying to figure out why this error appears or how I can solve it but failed..
Server manager gives the following error :
Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
At first I thought it was the same failure as with server 2008 a while ago so started by using the SUR tool but that gave me the following result:
=================================
Checking System Update Readiness.
Binary Version 6.1.7600.20532
Package Version 6.0
2010-01-27 21:06
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 417
No errors detected
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
So No errors, no missing NUM files nothing.. ok.. looking at the servermanager.log reveals the following:
2288: 2010-01-27 21:05:52.446 [Provider] C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
2288: 2010-01-27 21:05:52.759 [CBS] IsCacheStillGood: False.
2288: 2010-01-27 21:06:08.665 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800706be (-2147023170)
2288: 2010-01-27 21:06:09.353 [ExceptionHandler] Error (Id=0) 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)
Looked here in the forum for solutions but most of the people had NUM files missing or other errors. I've tried copying the missing cache files from another server to the cache diretory but these files are deleted by server manager on the next refresh:
1684: 2010-01-27 21:00:48.325 [CBS] LastModified CBS Time (UTC): 01/26/2010 20:57:31
1684: 2010-01-27 21:00:48.325 [CBS] Cache Last Write Time (UTC): 01/26/2010 19:25:41
1684: 2010-01-27 21:00:48.325 [CBS] IsCacheStillGood: False.
1684: 2010-01-27 21:00:58.013 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800706be (-2147023170)
also the CBS.log gives there errors
2010-01-27 19:10:05, Info CBS Failed to get session package state for package: Package_2_for_KB974431~31bf3856ad364e35~amd64~~6.1.1.5 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2010-01-27 19:10:05, Info CBS Failed to get session package state for package: Package_2_for_KB975467~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2010-01-27 19:10:05, Info CBS Failed to get session package state for package: Package_2_for_KB972270~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
So i've downloaded those packages, renamed them to cab, extracted the cab file to another directory and extracted the new cab file again to a temporary directory, then copied the extracted files to the windows\servicing\packages directory. I've copied the manifest to the winsxs\manifests directory and the other files to the services\packages directory.
Rebooted server, waited for server manager to come up again but still same error:
Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
Checked the registry for corrupted settings :
- HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\@CorruptPendingXml (REG_SZ)
- HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\@CorruptPendingXmlIdentifiers (REG_SZ)
But both keys had no @corrupted entries or what so ever..
Anyone has other suggestions?
