I've seen several posts regarding this, mostly related to XP, Vista or Windows 7. We are experiencing the SCOM console crash on Windows 2008 R2 SP1 Terminal Services Farm, so I would imagine it's a similar issue as with Windows 7 (64 Bit) Clients. Issue: SCOM console crashes randomly when one console is open If a 2nd SCOM console is opened, it crashes consistently shortly after the 2nd console is launched, many times without even doing any action. Sometimes immediately. No one action seems to cause the crash other than just clicking on the GUI Console is Run from Terminal Server Farm (3 Servers built the same): Windows Server 2008 R2, SP1 (64Bit) Both SCOM console icons (pointed to 2 different management groups) are set to use /Clearcache switch IE8 installed .NET 3.5 installed .NET 4.0 installed - (for other internal application needs) NOTE: we had this issue before we installed .NET 4.0 also. SCOM 2007 R2 Console - with CU2 applied We can have 15-25 Concurrent SCOM Console connections across the entire TS Farm (3 servers) We are getting Event ID 1001 on the Terminal Server App Event logs. ====================== Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: microsoft.mom.ui.console.exe P2: 6.0.4900.0 P3: 4a04f2c6 P4: System.Drawing P5: 2.0.0.0 P6: 4ca2bad4 P7: 43d P8: 28 P9: System.InvalidOperationException P10: Attached files: These files may be available here: D:\Users\username\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_microsoft.mom.ui_a9cfdf467447e56e325961531561e3a9dda2786_16947669 Analysis symbol: Rechecking for solution: 0 Report Id: 8e460b0e-a030-11e0-bea2-005056bb005f Report Status: 0 ====================== I've read this is known MS issue ans supposedly fixed in SP1, have not found any fixes for it yet, other than a re-install of the SCOM console and possibly a re-install of .NET. http://support.microsoft.com/kb/971541. But I've read people are still having this problem as well as us. I've also read the following articles but do not see a good resolution, unless I'm overlooking it. http://social.technet.microsoft.com/forums/en-us/operationsmanagergeneral/thread/7DFF0A71-1B7F-4EB6-A5AF-4B362AC2EF4B http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/0371e6b9-3885-4a17-a9b8-d47e102c4aa8 http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/74d8b215-a3c2-4dba-8d44-b8724758459f http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/79efc53d-360e-4f8d-a444-8a8943fda724 Any additional thoughts or fixes out there? Thanks, Terry

Hi Terry, May I know if this is a newly installed SCOM server? If the issue didn’t occur previously, were there any changes? Regarding the error, please try the method in the following Knowledge Base article: The System Center Operations Manager 2007 console fails to launch after upgrading to System Center Operations Manager 2007 R2 http://support.microsoft.com/kb/2023227 Meanwhile, please ensure the required hotfixes have been applied: Which hotfixes should I apply? http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx In addition, you can also try applying CU4 and see if it works: OpsMgr 2007 R2 CU4 rollup hotfix ships – and my experience installing it http://blogs.technet.com/b/kevinholman/archive/2011/02/01/opsmgr-2007-r2-cu4-rollup-hotfix-ships-and-my-experience-installing-it.aspx If the issue persists, please check the Event Log on the problematic server; if there are any related errors, please let us know the details. Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Nicholas - Thanks for the information. Background: Our install is a default SCOM 2007 R2 install, not an upgrade. We do have CU2 applied in our env to our SCOM servers and agents. This is an existing install (1.5 yrs) and we have seen this occur from or orignal install with our 1st management group. It really seems to be more an issue now that we have multiple management groups as it ocurrs more often when the 2nd management group console is opened. Again it really is not one specific thing that makes the console crash for individuals. Many times it crashes (and closes both consoles) as soon as you open the 2nd management group. I reviewed Kevin's post on "Which Hotfixes Should I Apply" and see that he suggest skipping CU4 (if I undertand his note correctly) and CU3 broke some things fixed by CU4, so I'm leaning towards waiting for CU5 as we have over 6000 agents across our management groups and don't need any more potential risks for Agents to restart. I did review HotFix 951327 http://support.microsoft.com/kb/951327/ and I will confirm that I do not have this or Server 2008 SP2 applied. If not I will apply SP2 (as it includes this Hotfix) and see if this helps. As far as event logs, we do get errors as noted above when the console crashes. We are getting Event ID 1001 on the Terminal Server App Event logs. ====================== Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: microsoft.mom.ui.console.exe P2: 6.0.4900.0 P3: 4a04f2c6 P4: System.Drawing P5: 2.0.0.0 P6: 4ca2bad4 P7: 43d P8: 28 P9: System.InvalidOperationException P10: Attached files: These files may be available here: D:\Users\username\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_microsoft.mom.ui_a9cfdf467447e56e325961531561e3a9dda2786_16947669 Analysis symbol: Rechecking for solution: 0 Report Id: 8e460b0e-a030-11e0-bea2-005056bb005f Report Status: 0 ====================== Thanks, Terry

ADDITIONAL INFO: Event 1001 just happend to me today at 1:38 PM ==================== EVENT ID: 1001 Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: microsoft.mom.ui.console.exe P2: 6.0.4900.0 P3: 4a04f2c6 P4: mscorlib P5: 2.0.0.0 P6: 4ca2b851 P7: 20c8 P8: 143 P9: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB P10: Attached files: These files may be available here: D:\Users\MyUserID\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_microsoft.mom.ui_9a98305245a05adf21e6830be3b38323b212a74_66ad35a0 Analysis symbol: Rechecking for solution: 0 Report Id: 957d4aee-a33f-11e0-bea2-005056bb005f Report Status: 0 ==================== Event 2004 also ocurred about 3 minutues priror at 1:35 pm related to Microsoft.MOM.UI.Console.exe consuming most of the memory on the Terminal Server I was logged into ==================== EVENT ID 2004: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Microsoft.MOM.UI.Console.exe (16616) consumed 838881280 bytes, Microsoft.MOM.UI.Console.exe (7280) consumed 807358464 bytes, and Microsoft.MOM.UI.Console.exe (4512) consumed 683220992 bytes. ====================

ADDITIONAL INFO TO LAST POST: This terminal server at the time had approx 8 Mom consoles open concurrently when the crash on MY console ocurred.

Hi, Thank you for your updates. Please try increasing the virtual memory on the server and see how it works. Please also refer to the following thread which is about the similar issue and see if it helps: SCOM 2007 R2 management configuration service terminating http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/a643659c-c810-4480-be6c-e24f5d9fab86 Thanks. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Have you tried to install the 32 console version if possible? I don't know if it will work (never tried), but on the installation media you could try to install from the i386 directory (from an elevated command prompt). If this works, you can at least see if it is 64bits related or not.Regards, Marc Klaver http://jama00.wordpress.com/