SystemEdge Log File Monitor match traps generate "Error Processing Event 0x116002f" events on the Host_SystemEdge device model.

Document ID : KB000050458
Last Modified Date : 14/02/2018
Show Technical Document Details


Customers that are using process models as resources in services, wanted to have log monitors to have the ability to affect the condition of a process model.

In SPECTRUM version 9.0 we changed SystemEdge Log File Monitoring functionality which now requires customers to configure a "Monitored Process Log File Mapping" which associates a log file to a process and then create a process monitor for that process in SPECTRUM.

If the Monitored Process Log File Mapping is not setup and the process is not being monitored in SPECTRUM customers will seeing the following events in SPECTRUM b/c we are trying to forward the log monitor event to a process model that doesn't exist.

Error processing event 0x116002f - Details: No device
hostname, IP address or mapped target (logfile) could be found. Provided
input string was: "Test " System Host_systemEDGE 0x3dc0000


When setting up Log File Monitors on a SystemEdge host, customers are now required to "Monitored Process Log File Mapping" and map the log file to a process and setup a process monitor for that process.

From the Information tab expand the System Resources -> Monitored Logs and Process Logs:

Click on the "Add" button in the table.

Specify a "Log FIle Name" ie... C:\TEST.txt

Specify a Process Name. ie... notepad.exe

From the Information tab, expand the System Resources ->Running Monitored Processes -> RFC270 -> Monitored Process table.

Add a process monitor for the process associated with the log file "Monitored Process Log File Mapping" table.

If customers don't want to do this they have some other options:

On the SystemEdge host set the "Enable_SouthBoundGateway" attribute to "No" *** This will disable all SouthBound Gateway event forwarding for this host.

Remove the 0x116002f event from the $SPECROOT/SS/CsVendor/Ctron_Gen_Host/Host_SystemEdge/EventDisp file and reload the Event Disposition files.