none
Operations Manager Console Crash

    Question

  • hi I have a problem with  Operations Manager 2012 r2  Console - when I navigate "windows computers" on monitoring view console crashes :

    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.1.10226.1239, time stamp: 0x57bd213f

    Faulting module name: ntdll.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e

    Exception code: 0xc0000374

    Fault offset: 0x00000000000f1b70

    Faulting process id: 0x15bc

    Faulting application start time: 0x01d22573c3e46b2a

    Faulting application path: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: 8af2bdbd-9167-11e6-80c2-00155d0ad523

    Faulting package full name:

    Faulting package-relative application ID:

    Thursday, October 13, 2016 5:13 PM

Answers

  • Don't think it's the Silverlight update.
    My money's on a .Net patch. I'm getting the same .Net error as Mc2102, and the stack trace shows Windows Forms Errors.

    Patch cycle yesterday installed KB3186208. Can someone confirm the same?

    Thx&Rgds,
    M.


    Correction - just saw the other thread. KB3185331 is the problem.
    Uninstalled - works.
    • Edited by amosmax Thursday, October 13, 2016 10:46 PM
    • Proposed as answer by Stoyan ChalakovMVP Friday, October 14, 2016 7:57 AM
    • Marked as answer by Ramixes Sunday, October 16, 2016 2:43 PM
    Thursday, October 13, 2016 10:28 PM
  • Its now official

    https://blogs.technet.microsoft.com/germanageability/2016/10/13/october-2016-windows-patch-kb3192392-might-cause-scom-2012r2-console-to-crash/

    • Marked as answer by Ramixes Sunday, October 16, 2016 2:43 PM
    Friday, October 14, 2016 9:38 AM
  • +1 on this. 
    Try uninstalling the above mentioned KB and restarting. 
    Afterwards it should work again.

    Regards,


    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!)

    • Marked as answer by Ramixes Sunday, October 16, 2016 2:43 PM
    Friday, October 14, 2016 7:58 AM

All replies

  • That's funny that this is the first post I find after opening this forum because I have exactly the same issue. I am not sure if that is related to any patches which were released yesterday and I installed on the server however I am running Windows Server 2008 R2. I see in the Application Log the errors below and I tried to uninstall and reinstall the Console several times. I also verified that the Report viewer is installed. So far I have not found any solution for this.

    In the Application Log I see the errors:

    ========================================================
    Log Name:      Application
    Source:        .NET Runtime
    Date:          10/13/2016 2:20:25 PM
    Event ID:      1026
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      nms1.customcall.us
    Description:
    Application: Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
    Stack:
    ========================================================

    and

    ===============================================
    Log Name:      Application
    Source:        Application Error
    Date:          10/13/2016 2:20:26 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      xxx.xxxx.xxx
    Description:
    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.1.10226.1239, time stamp: 0x57bd213f
    Faulting module name: ntdll.dll, version: 6.1.7601.23543, time stamp: 0x57d2fde1
    Exception code: 0xc0000005
    Fault offset: 0x000000000004eef1
    Faulting process id: 0x1708
    Faulting application start time: 0x01d22586c45bc96e
    Faulting application path: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 17b7a7c4-917a-11e6-a8f9-00221924fca9
    ===============================================

    Thursday, October 13, 2016 7:31 PM
  • Same issue...  The console started crashing today around 10AM.  I noticed the a Silverlight update was applied to our W2K12 R2 server yesterday.  I did not have any issues with the SCOM console yesterday or days prior as I have been using it daily for the past several months.  I uninstalled Silverlight, but still have the issue.  I repaired the SCOM console, but that did not fix the issue.  I uninstalled/reinstalled the SCOM console and that did not fix the issue.  I installed the SCOM console on a separate W2K12 R2 server and get the same SCOM console crash on that server as well.
    Thursday, October 13, 2016 8:40 PM
  • Don't think it's the Silverlight update.
    My money's on a .Net patch. I'm getting the same .Net error as Mc2102, and the stack trace shows Windows Forms Errors.

    Patch cycle yesterday installed KB3186208. Can someone confirm the same?

    Thx&Rgds,
    M.


    Correction - just saw the other thread. KB3185331 is the problem.
    Uninstalled - works.
    • Edited by amosmax Thursday, October 13, 2016 10:46 PM
    • Proposed as answer by Stoyan ChalakovMVP Friday, October 14, 2016 7:57 AM
    • Marked as answer by Ramixes Sunday, October 16, 2016 2:43 PM
    Thursday, October 13, 2016 10:28 PM
  • +1 on this. 
    Try uninstalling the above mentioned KB and restarting. 
    Afterwards it should work again.

    Regards,


    Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!)

    • Marked as answer by Ramixes Sunday, October 16, 2016 2:43 PM
    Friday, October 14, 2016 7:58 AM
  • Its now official

    https://blogs.technet.microsoft.com/germanageability/2016/10/13/october-2016-windows-patch-kb3192392-might-cause-scom-2012r2-console-to-crash/

    • Marked as answer by Ramixes Sunday, October 16, 2016 2:43 PM
    Friday, October 14, 2016 9:38 AM
  • it works Thanks a lot ...
    Sunday, October 16, 2016 2:43 PM
  • Does anyone have any idea of when Microsoft will fix this?

    Thanks in advanced

    Monday, October 17, 2016 12:49 PM
  • I have SCOM installed on 2012 SP1, the latest Security Update was KB3185332. I removed this and rebooted, the SCOM console is stable again.

    MSFT - what now? Looks like we can have EITHER secure servers OR stable SCOM consoles but not both on the same server!

    BTW - thanks for posting

    Tuesday, October 18, 2016 3:31 AM
  • By the way, the problem is every where the SCOM console is install.

    I had the remove the KBs on all my RDS servers and SCVMM servers to have the console working.

    I placed a call to MS and they are aware of the issue but have no solution for now.

    Tuesday, October 18, 2016 3:02 PM
    • Proposed as answer by rob1974 Wednesday, October 19, 2016 8:50 AM
    • Edited by rob1974 Wednesday, October 19, 2016 9:04 AM
    Wednesday, October 19, 2016 8:50 AM
  • Hello,

    KB3194798/3192392/3185330/3185331

    https://blogs.technet.microsoft.com/germanageability/2016/10/17/october-2016-windows-patch-kb3192392-might-cause-scom-2012r2-console-to-crash/

    There   is a partial fix as it does not cover all operating systems...

    https://support.microsoft.com/en-us/kb/3200006

    Thanks,

    Dom


    Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Monday, October 24, 2016 3:37 PM
  • Exception code: 0xc0000005 means no access....
    Wednesday, October 26, 2016 11:45 AM
  • Uninstalling kb3192392 worked like a charm. Uninstalling kb3185331 did not work.

    Thanks!


    Edit: Actually, reinstalling KB3185331, recreates the issue even if KB3192392 so in my environment I have to uninstall both KB3185331 and KB3192392.
    • Edited by Andreas Hole Thursday, October 27, 2016 11:27 AM
    Thursday, October 27, 2016 9:30 AM
  • I reinstalled all the bad patches and added the new one KB3200006 and everything works !!!! :)

    Thanks,

    Dom


    Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    • Proposed as answer by Felyjos Thursday, October 27, 2016 1:14 PM
    Thursday, October 27, 2016 1:14 PM