Tuesday, November 25, 2008

Windows Server 2008: Server Manager Broken

You have opened Server Manger only to find that when you click on the 'Roles' or 'Features' option you see 'Error' or 'Collecting Data' with a message at the bottom of the window stating that the 'Latest Refresh: Failed."

After clicking around for a bit and cursing, you find out that the [Error details] say, "Could not discover the state of the system. An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x80070543): Cannot open an anonymous level security token. (Exception from HRESULT: 0x80070543)."

Great, you can now search the web and try to solve the problem. Unfortunately, you keep hitting a dead end.

Here is what worked for my machine, and what could have caused the problem.

Problem:

The server-wide COM security settings have been changed to have a "Default Authentication Level" of 'None.'

Solution:

1. Using elevated permissions, run Dcomcnfg.exe

2. In the "Component Services" window, navigate to ComponentServices->Computers->My Computer.

3. Right-click on "My Computer" and select [Properties] from the context menu.

4. In the "My Computer Properties" dialog, select the [Default Properties] tab.

5. Change the "Default Authentication Level" drop to 'Connect'; if it is set to None.

7. Change the "Default Impersonation Level" to Identify; if it is set to something else.

8. Press the OK button in the "My Computer Properties" dialog.

Now, Close Server Explorer and then reopen it and see if your server's Roles and Features will enumerate. [Note: That it may take a while for the data collection to finish.]

Causes:

Some applications like Avaya or Daemon Tools can change the COM security settings for the machine. It would be a good idea to test these and other applications after following the steps above.

Best of luck.

PS I find it great that the bottom of the 'Roles' section says ['Enable' and 'Error details'] while the bottom of the 'Features' section says ['Error details' then 'Enable'].

5 comments:

Anonymous said...

Excellent post. Thanks!

Anonymous said...

That fixed it! This was one of those "wtf" errors. Thanks for the help!

Seth said...

Man I can't thank you enough. I have been looking for an answer everywhere (but here obviously) I can't say thank you enough times.

S

Unknown said...

-

Nice!

Thank's man!

You saved my day :)

Yuriy said...

Thanks a lot.
I've spent 2 hours looking for solution and only your article helps.