Consider the following scenario:
In this scenario, you may over time see a steady increase of elements and headers when you examine the Application log. This is indicated by Event ID 684. This event indicates an increase in the MNGCLI.EXE component.
Additionally, you may see an Application log fault that resembles the following:
- You are running Microsoft Host Integration Server 2013 for 3270 Mainframe access.
- You are also running either Host Integration Server Windows Management Instrumentation (WMI) scripts or the Host Integration Server 2013 Management Pack for Systems Center Operations Manager.
In this scenario, you may over time see a steady increase of elements and headers when you examine the Application log. This is indicated by Event ID 684. This event indicates an increase in the MNGCLI.EXE component.
Additionally, you may see an Application log fault that resembles the following:
Log Name: Application
Source: Application Error
Date: 1/1/2015 8:00:00 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords: Classic
User: N/A
Computer: <FullyQualifiedServerName>
Description:
Faulting application name: wmiprvsNe.exe, version: 6.3.9600.16384, time stamp: 0x5215f9c9
Faulting module name: mngbase.dll, version: 9.0.2102.0, time stamp: 0x5211a1c8Exception code: 0xc0000005
Source: Application Error
Date: 1/1/2015 8:00:00 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords: Classic
User: N/A
Computer: <FullyQualifiedServerName>
Description:
Faulting application name: wmiprvsNe.exe, version: 6.3.9600.16384, time stamp: 0x5215f9c9
Faulting module name: mngbase.dll, version: 9.0.2102.0, time stamp: 0x5211a1c8Exception code: 0xc0000005