I have installed the ESB Management Console on a server that does not have Visual Studio installed and I got this error when I tried to open the ESB Management Console on the local host.
http://social.msdn.microsoft.com/Forums/ar-SA/biztalkesb/thread/16f6fcbe-ffd6-4fbf-a92f-a97726292256 talks about the same error but none of the solutions in this thread solved my problem.
Eventually I discovered that if i added the http://local host to my local intranet sites the ESB management console now displays without error. (Note added 4/04/2013 You can also grant read WMI Security access to the BizTalkServer branch)
Now if I try open site from a browser that is not on the local server, I get challenged and enter the credentials for the same user as above then I get the same error. In this case adding the http://<server> to the intranet or trusted sites does not solve the issue. What is really weird is that if I enter credentials for the administrator who installed the server then the the ESB Management Console is displayed
I decided that I was not seeing the real error because the user cannot write the error to the event log on the web server. I gave this user full access to the event log by running the following from a command prompt where the bolded text is the the SID of my user.
C:\Windows\system32>wevtutil sl Application /ca:O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x3;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573)(A;;0x3;;;S-1-5-21-1832726700-257789682-1899323428-1000)
Now I see the following error written to the event log;
Method: Void .ctor()
Error Source: System.Management
Error TargetSite: Void ThrowWithExtendedInfo(System.Management.ManagementStatus)
Error StackTrace: at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementScope.InitializeGuts(Object o)
What permissions or policy am i missing?
http://qa.social.msdn.microsoft.com/Forums/en-US/biztalkesb/thread/2a1519c1-bab3-40fb-a645-a7e54f606b22 describes a workaround where you put the username password in tot he web.config but thus is just hiding the problem. I want to find out what permission or setting is missing.