Have seen a thread today on the TechNet forums about the SCOM Console crashing when running a task. http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/c339c327-1e7d-412b-9d1a-5ae0b8a2e0f8/#9ae059f9-f881-4fa1-9d42-fceed4c4ef2d
We actually also have one issue exactly like that, so it was a nice opportunity to dive into it a bit more. So what happens is that from the SCOM Console you run a task against some agent and while running that task it crashes and takes the SCOM Console along with it. You can get an error like the following:
Alexey Zhuravlev from opsmgr.ru recently found that Internet Explorer 9 seemed to cause the problem in a case he encountered and in this thread the solution was also to remove IE9 to get it working.
To quote him on that part:
Console calls this:
StackTrace:
at System.Windows.Forms.UnsafeNativeMethods.IHTMLLocation.GetHref()
at System.Windows.Forms.WebBrowser.get_Document()
at System.Windows.Forms.WebBrowser.get_DocumentStream()
at System.Windows.Forms.WebBrowser.get_DocumentText()
If I understand the process correct, it uses Mshtml.dll. IE9 replaces this dll (installs it’s own version 9.0.*). And it looks like the new version causes an access violation…
One of the colleagues of mine at a customer location also had these problems since a while, but with certain tasks. It turns out to be the tasks that are run against the agent. So for instance a ping will work just fine because it is running locally, but a task like show processes or start a service will first give a popup for you asking if you want these credentials after running that one it crashes (and takes the SCOM console down with it. So when you do that you get one of these popups:
We tested by uninstalling IE9 and confirming it was now IE8. Tasks ran fine. So we installed IE9 again, but this time from the Microsoft website and not some internal updating process. And yes, it crashed again at running a task.
So the current workaround is to uninstall IE9 to work with this. Hope that it will be fixed soon.
Update 9 June 2011:
Lincoln Atkinson gave an answer to a thread in the Technet Forums about this issue with a remark for a future fix:
The product team is aware of this issue and are looking into a fix. We will be fixing for vNext + if possible backporting the fix in a future cumulative update.
Bob Cornelissen