17415, time stamp: 0x545040c8įaulting application start time: 0x01d4dda0228d1e17įaulting application path: C:\Windows\system32\ServerManager.exeįaulting module path: C:\Windows\system32\wmidcom.dll 17238, time stamp: 0x53d0b3e7įaulting module name: wmidcom.dll, version. In the Event Viewer I found the following error:įaulting application name: ServerManager.exe, version. I found that on this server Server Manager would just spin when opened. Now connect to the Session Host you found that is causing the issues.If deleting the file did not work you may need to delete your user accounts Windows Profile. Now launch Server Manager and start to add back your session hosts until one crashes the console.Delete the Server Manager list file from: C:\Users\\AppData\Roaming\Microsoft\Windows\ServerManager\.To find the session host causing the issues i needed to: The exception unknown software exception (0xe0434352) occurred in the application at location 0x00007FFAF3A84048. The error we were getting in Server Manager was:
(We are in the process of upgrading.) After doing the lastest round of Windows Updates we were unable to manage RDS in Server Manager. It is currently running Windows Server 2012R2 session hosts and Windows Server 2016 connection brokers. I currently manage a large implementation of Remote Desktop Services (RDS).
0 kommentar(er)
