Overview

GFI EventsManager crashes and Microsoft Windows Event Viewer might display error messages in the Application log similar to the following:

Log Name: Application
Source: Application Error
Event ID: 1000
Level: Error
Description:
Faulting application name: esmproc.exe, version: 8.0.0.0, time stamp: 0x4f3a5bce
Faulting module name: mfc100u.dll, version: 10.0.30319.1, time stamp: 0x4ba1f9f5
Exception code: 0xc0000005
Fault offset: 0x001fa4e0
Faulting process id: 0xee0
Faulting application start time: 0x01cd34f64becc7e4
Faulting application path: C:\Program Files\GFI\EventsManager 2012\esmproc.exe
Faulting module path: C:\Windows\system32\mfc100u.dll
Report Id: 51bfcbe6-a0ea-11e1-b3b9-d067e5f004af
Event Xml: .....

Log Name: Application
Source: .NET Runtime
Event ID: 1026
Level: Error
Description:
Application: esmproc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException
Stack: .....

This article provides information on the root cause and a brief description of the resolution to fix the issue.

Environment

• GFI EventsManager 2012
• 64-bit operating system in a VMware virtual environment

Root Cause

GFI EventsManager 2012 requires Microsoft .NET Framework 4.0 to run. Installing .NET Framework on a 64-bit VMware virtual machine may cause .NET crashes and thus the virtual machine might stop responding. This issue has been confirmed to affect ESX/ESXi 3.5, 4 and 5 platforms but we cannot exclude that the issue may appear on other virtual platforms.

Due to these .NET Framework 4.0 errors when running on a 64-bit virtual operating system, GFI EventsManager may not work as expected.

Resolution

It is recommended to install GFI EventsManager on a 32-bit operating system if installing in a VMware virtual environment, or installing on a physical server.