Configuration Troubleshooting

SCOM 2012 – Console Error Microsoft.EnterpriseManagement.Monitoring.Console.exe

Posted on Author stefanroth Comments(2)

There are different ways to install the SCOM console. One way is to install it calling the regular SCOM 2012 setup wizard and choosing the SCOM console option. The other way is executing directly the OMCONSOLE.msi package. The difference is, if you call the regular SCOM setup wizard it will check for pre-requisites. If you just call the OMCONSOLE.msi  there is no logic built-in to check for dependencies. Well, that could lead to a problem…

If you install the console by executing the D:\SETUP\AMD64\CONSOLE\OMCONSOLE.msi everything installs fine (D: is my local drive where the SCOM 2012 ISO is mounted).

If you start the console after the installation there is a chance you will hit these errors (sorry, the screen shots are in German):

clip_image002

If you check the event log you will see event 1000 …

image

and event 1026…

clip_image002[5]

These errors look scary but the solution is easy.

Just install the Microsoft Report Viewer 2010 Redistributable Package and the console will start without any issue.

Happy fixing!

stefanroth
http://www.stefanroth.net

Related Articles
Azure Azure Stack Configuration Testing

Azure Stack – Deploy Azure Stack on Azure VM

Posted on Author stefanr5

At Ignite 2018 a couple of weeks ago, I got the feeling that Microsoft is getting really serious about their hybrid cloud strategy. It may sound strange or weird, because Microsoft always used the terms hybrid cloud and announced tailored products. But in the past years, I wasn’t really sure that Microsoft will hear the […]
Configuration System Center Xplat

SCOM 2016 – What’s New UNIX/Linux Series: File System Discovery e.g. Exclude /tmp

Posted on Author stefanroth

A little pain in SCOM 2012 R2 was, that as soon you installed the UNIX/Linux management packs for your distribution all UNIX/Linux folders were discovered on the file system. This could be lead to a huge list of monitored directories e.g. /tmp, /var… which was not intended to be. To overcome this problem, you would […]
Configuration PowerShell Script System Center

SCOM – Save a Connection String for Use in a PowerShell Script

Posted on Author stefanroth

Sometimes it is necessary to store certain information in a (secure) way, like a connection string, which you might want to use in your PowerShell scripts. The scripts could be then used e.g for the Command Notification Channel. Let’s assume you need to connect to a foreign system and this system provides you with a […]

2 Replies to “SCOM 2012 – Console Error Microsoft.EnterpriseManagement.Monitoring.Console.exe”

  1. I face the issue with scom 2012 SP1 , console keeps crashing and stuck on not responding.
    I have the issue on Managemnet Servers and Workstations as well .

    Microsoft Report Viewer 2010 Redistributable Package is installed on all the machines,

    Some events i see:

    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.0.9538.0, time stamp: 0x50903ed4
    Faulting module name: clr.dll, version: 4.0.30319.296, time stamp: 0x50483916
    Exception code: 0xc0000005
    Fault offset: 0x0000000000198cd8
    Faulting process id: 0x227c
    Faulting application start time: 0x01ce078b3c556b00
    Faulting application path: C:Program FilesSystem Center 2012Operations ManagerConsoleMicrosoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:WindowsMicrosoft.NETFramework64v4.0.30319clr.dll
    Report Id: 06bdcb48-737f-11e2-a067-b4b52fbea8f9
    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.0.9538.0, time stamp: 0x50903ed4
    Faulting module name: nlssorting.dll, version: 4.0.30319.296, time stamp: 0x504835c7
    Exception code: 0xc00000fd
    Fault offset: 0x0000000000001d7d
    Faulting process id: 0x1ac
    Faulting application start time: 0x01ce08134f79b32d
    Faulting application path: C:Program FilesSystem Center 2012Operations ManagerConsoleMicrosoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:WindowsMicrosoft.NETFramework64v4.0.30319nlssorting.dll
    Report Id: c1ce1fbc-7423-11e2-99a1-b4b52fbea8f9
    Application: Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEE9928CD8 (000007FEE9790000) with exit code 80131506.

    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.0.9538.0, time stamp: 0x50903ed4
    Faulting module name: clr.dll, version: 4.0.30319.296, time stamp: 0x50483916
    Exception code: 0xc0000005
    Fault offset: 0x0000000000198cd8
    Faulting process id: 0x227c
    Faulting application start time: 0x01ce078b3c556b00
    Faulting application path: C:Program FilesSystem Center 2012Operations ManagerConsoleMicrosoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:WindowsMicrosoft.NETFramework64v4.0.30319clr.dll
    Report Id: 06bdcb48-737f-11e2-a067-b4b52fbea8f9
    EVent ID 1002
    The program Microsoft.EnterpriseManagement.Monitoring.Console.exe version 7.0.9538.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
    Process ID: 2480
    Start Time: 01cdf490c4fd112a
    Termination Time: 29
    Application Path: E:Program FilesSystem Center 2012Operations ManagerConsoleMicrosoft.EnterpriseManagement.Monitoring.Console.exe
    Report Id: 9b3cbd40-62b6-11e2-9d5f-0050569e7c52
    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.0.8560.0, time stamp: 0x4f20e97a
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2
    Exception code: 0xe0434352
    Fault offset: 0x000000000000caed
    Faulting process id: 0x23a0
    Faulting application start time: 0x01cdd5f671848b4e
    Faulting application path: E:Program FilesSystem Center 2012Operations ManagerConsoleMicrosoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:Windowssystem32KERNELBASE.dll
    Report Id: 05895832-44ec-11e2-bcf0-0050569e7c53
    Application: Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Reflection.TargetInvocationException

    Reply
  2. Pingback: SCOM 2016 console stop working – AllAboutWindowsSL

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.