Shortly after installing the RTM the server manager was working just fine. I changed the PC name and put in a static IP and rebooted it. Now the Server manager starts but the crashed stating it stop working. Has anyone see this recently? Thanks. Info on the crash on the screen: Problem Event Name: CLR20r3 Problem Signature 01: servermanager.exe Problem Signature 02: 6.2.9200.16384 Problem Signature 03: 50107b22 Problem Signature 04: PresentationCore Problem Signature 05: 4.0.30319.17929 Problem Signature 06: 4ffa6e63 Problem Signature 07: 1f2e Problem Signature 08: 56 Problem Signature 09: System.Windows.Markup.XamlParse OS Version: 6.2.9200.2.0.0.272.7 Locale ID: 1033 Additional Information 1: c462 Additional Information 2: c46227b7184757efcedebec678434095 Additional Information 3: 14fa Additional Information 4: 14faec7ae452809757a5fbab5714ce01

Hi, 1. This specific Server Manager crash is caused by a code defect in Beta (since fixed) that assumed here would never be two same-named event logs. When you install AppFabric, that creates an event log called "Setup". There is already another built-in event log called Setup that is used to show you servicing events, like installing a hotfix, that was first added in Windows Vista. 2. Even when you uninstall AppFabric, it leaves that extra Setup event reference around in the registry here: Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Setup Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Setup\AppFabric_Setup Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Setup\Setup The workaround here is to delete that top level Setup registry key and restart the server. Server Manager will stop crashing on startup. Regards, Martin Credit: (NedPyle) If you find my information useful, please rate it. :-)