Sysprep Server 2008 R2 Vmware' title='Sysprep Server 2008 R2 Vmware' />Unexpected error refreshing Server Manager errors 0x. BE and 1. 60. 1 on Window Server 2. R2. Home  Articles  Unexpected error refreshing Server Manager errors 0x. BE and 1. 60. 1 on Window Server 2. R2. Unexpected error refreshing Server Manager errors 0x. BE and 1. 60. 1 on Window Server 2. R2. On certain Windows Server 2. R2 machines you may experience the Server Manager being unable to open Roles andor Features in the MMC. The error it usually comes back with is Unexpected error refreshing Server Manager The remote procedure call failed. Exception from HRESULT 0x. BE. You may also find that there is also Error 1. Event Log. Introduction. On certain Windows Server 2. R2 machines you may experience the Server Manager being unable to open Roles andor Features in the MMC. The error it usually comes back with is Unexpected error refreshing Server Manager The remote procedure call failed. Exception from HRESULT 0x. BE.  Certain people have also reported finding that there is also an error being logged in the event log Error 1. Various reasons lead us to believe that this is an issue related to file corruption. More specifically, file corruption caused by failed Windows Updates. If your Server Manager is crashing and youre unable to add Roles or Features this article will talk you through a number of steps which may help you resolve the issue. Step 1 Download Install System Update Readiness Tool KB9. Sysprep Server 2008 R2 Vmware' title='Sysprep Server 2008 R2 Vmware' />I was going sysprep a base image of Windows Server 2008 this morning and followed my own instructions on sysprepping Windows. I went to the installation DVD and. Tutorial on doing a complete Sysprep on a Windows 7 Machine from start to finish copyprofiletrue, automatically activating windows, etc. The first step in trying to diagnose this is to download and install KB9. System Manager and generating the 0x. BE refresh error. You can download it from http support. The System Update Readiness Tool, runs a onetime scan for inconsistencies that might prevent future servicing operations. This scan typically takes less than 1. However, the tool might take significantly longer on some computers. The Windows Update progress bar is not updated during the scan, and progress seems to stop at 6. This behavior is expected. The scan is still running and you should not cancel the update. If you are prompted to restart your computer, do so. Step 2 Analyze KB9. After you install KB9. History. A beta version of HyperV was shipped with certain x8664 editions of Windows Server 2008. The finalized version was released on June 26, 2008 and was. In last post I described how to check SID on Windows 7 and Windows Server 2008 R2, today Ill describe you how to change SID on Windows Server 2008 R2 and. Use IE for best view http http page missing microsoft. Sysprep Server 2008 R2 Vmware' title='Sysprep Server 2008 R2 Vmware' />You can find the file in C WindowsLogsCBSCheck. SUR. log. The log should show what files have been detected as corrupt or missing fromin the C windowsservicingpackages folder. For instance, on our test machine they were shown as 2. Info                  CBS    Failed to get session package state for package Package3forKB9. HRESULT 0x. 80. ERRORNOTFOUND. Info                  CBS    Failed to get session package state for package Package2forKB9. HRESULT 0x. 80. ERRORNOTFOUNDYou might also want to have a look at the Check. SUR. persist. log. In our case it looked like this. Checking System Update Readiness. Binary Version 6. Package Version 7. Checking Windows Servicing Packages. Checking Package Manifests and Catalogs. CBS MUM Corrupt 0x. PackagesPackageforKB9. RTM3. 1bf. 38. 56ad. Expected file name Microsoft Windows Foundation Package3. Checking Package Watchlist. Checking Component Watchlist. Checking Packages. Checking Component Store. Seconds executed 7. Found 1 errors. CBS MUM Corrupt Total count 1. Unavailable repair files. PackageforKB9. 76. RTM3. 1bf. 38. 56ad. PackageforKB9. 76. RTM3. 1bf. 38. 56ad. Unable to get system disk properties 0x. D IOCTLSTORAGEQUERYPROPERTY Disk Cache. We also checked the servermanager. Cbs. Update. State. C Windowssystem. Server. ManagerCache folder is missing. Provider                  C Windowssystem. Server. ManagerCacheCbs. Update. State. bin does not exist. CBS                       Is. Cache. Still. Good False. CBS Error Id0 Function Create. Session. And. Package SessionOpen. Package failed 8. Exception. Handler Error Id0 An unexpected exception was found. System. Runtime. Interop. Services. COMException 0x. BE The remote procedure call failed. Exception from HRESULT 0x. BE. at System. Runtime. Interop. Services. Marshal. Throw. Exception. For. HRInternalInt. Code, Int. Ptr error. Info. at Microsoft. Windows. Server. Manager. Component. Installer. Create. Session. And. PackageInt. Ptr session, Int. Ptr package. Microsoft. Windows. Server. Manager. Component. Installer. Initialize. Update. Info. at Microsoft. Windows. Server. Manager. Component. Installer. Initialize. at Microsoft. Windows. Server. Manager. Common. Provider. Refresh. Discovery. Microsoft. Windows. Server. Manager. Local. Result. Perform. Discovery. Microsoft. Windows. Server. Manager. Server. Manager. Model. Create. Local. ResultRefresh. Type refresh. Type. Microsoft. Windows. Server. Manager. Server. Manager. Model. Internal. Refresh. Model. ResultObject stateStep 3 Copy missing or corrupt files. In order to perform this step, youll need access to a machine which has a working Server Manager. Copy the files listed as corruptedmissing from C windowsservicingpackages on the working machine to the server which is exhibiting the HRESULT 0x. BE error.   You may need to change the ownership of the files on the destination machine to your user account as well as give yourself write permissions on the files before Windows allows you to overwrite them. Once done, start Server Manager and see if that fixes the error. To be doubly sure, check the contents of the C Windowssystem. Server. ManagerCache folder there should be two files there Cbs. Update. Info. bin and Cbs. Update. State. bin. If these files still dont exist after Server Manager starts you havent completely fixed the 0x. BE error. Step 4 Copy all files in C windowsservicingpackages folder. If youre still unable to get Server Manager started, it means that there may be other problems and we need to overwrite all the packages in the C windowsservicingpackages folder. The first step we need to do is take ownership of all the files. To do this, launch a Command Prompt as an Administrator, and I mean right click the Command Prompt icon and select Run As Administrator. At the command prompt execute takeown F c WindowsServicingPackages D y RThe takeown command will give you ownership of the files, but you still need to give yourself write access to the files in order to change them. In the same command prompt window execute the following command replace username with your usernamecacls c WindowsServicingPackages E T C G username FNow copy all the files from the C windowsservicingpackages folder on a working server. Make sure that the source server has been patched to the same level and has the same rolesfeatures installed as the destination server. Step 5 Start Server Manager and check Cache folder. Try starting Server Manager and check if youre still getting the error. In all our tests, the above steps have been able to resolve 9. Server Manger problems related to error 0x. BE and 1. 60. 1.   Jus to be on the safe side, check the contents of the C Windowssystem. Server. ManagerCache folder and see that the two. Conclusion. This article has demonstrated a quick and easy way to solve the errors associated with Server Manager and the 0x. BE and 1. 60. 1 errors that it exhibits when trying to install Roles or Features. If the problem is not resolved by applying Microsoft KB9. Install Clickonce Programmatically there. BE and 1. 60. 1 errors by copying all files in C windowsservicingpackages from anther working Windows Server 2. R2 server. References. System Update Readiness Tool KB9. How to clone, disjoin rename a Windows 2. R2 VM offline, then rejoin domain online. Adding to Nathan Cs answer. The proper supported way of cloning an AD joined computer is by using sysprep. While normally you can safely say that your new machine will get a new RID, microsoft recommends using sysprep. So unless you can be absolutely sure you wont cause any unforeseen issues its generally better to follow the recommendations. However it has since been established and tested quite a few times and the SID is not as important as all that so your procedure will work, and if you utilize it only for testing then you should be fine. Affected services are WSUSSystem Center. KMSIf you use any of these 3 utilities, you will get problems from your current approach that you would not get when sysprepping. These problems normally only affect the newly added machine though, so the answer to Does this procedure affect the original server. Is generally no, it shouldnt. Keep in mind though, youre avoiding microsoft best practices for an easy fix. Which generally does not end well, and definitely isnt long term sustainable.