OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 54
5.4 EMS Message 203
This EMS event is displayed in the primary collector.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000203 OMNI Process
OSR-SRV: Out Of Memory \OMNI.$OSRQ Unable to allocate opsw req context. Pathmon: \OMNI.$OMNIQ
Cause: OSR was unable to allocate space for request context. This is an internal error.
Corrective Action: Contact OmniMessaging support
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000203 OMNI Process
OSR-SRV: Out Of Memory \OMNI.$OSRQ Unable to allocate dll element for opswreq context Pathmon:
\OMNI.$OMNIQ
Cause: OSR was unable to allocate space for dll element. This is an internal error.
Corrective Action: Contact OmniMessaging support
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000203 OMNI Process
OSR-SRV: Out Of Memory \OMNI.$OSRQ Unable to allocate global data block. Pathmon: \OMNI.$OMNIQ
Cause: OSR was unable to allocate space for globals. This is an internal error.
Corrective Action: Contact OmniMessaging support
EMS Message: 02-03-23 17:23:21 \OMNI.$OSSQ TANDEM.NSIM.G06 000203 OMNI Process
OSS-SRV: Out Of Memory \OMNI.$OSSQ Unable to allocate global data block. Pathmon: \OMNI.$OMNIQ
Cause: OSS was unable to allocate space for globals. This is an internal error.
Corrective Action: Contact OmniMessaging support
5.5 EMS Message 205
This EMS event is displayed in the primary collector.
EMS Message: 02-07-02 10:03:49 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 Process OSR-SRV
\OMNI.$OSRQ Initialization Error <error> License file not specified. Pathmon: \OMNI.$OMNIQ
Cause: The pathway parameter NSIM-LIC is not specified for OSR.
Corrective Action: Mention the pathway parameter NSIM-LIC for OSR.
EMS Message: 02-07-02 10:03:49 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 Process OSR-SRV
\OMNI.$OSRQ Initialization Error <error> Verify License Failed. Pathmon: \OMNI.$OMNIQ
Cause: The license file NSIMLIC is corrupted.
Corrective Action: Use an authorized NSIMLIC file.
EMS Message: 02-07-02 10:03:49 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 Process OSR-SRV
\OMNI.$OSRQ Initialization Error <error> SQL Error getting user count Pathmon: \OMNI.$OMNIQ
Cause: There was an error reading the IDALLOTB.
Corrective Action: Contact OmniMessaging support.
EMS Message: 02-07-02 10:03:49 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 Process OSR-SRV
\OMNI.$OSRQ Initialization Error <error> IDALLOTB table has been tampered Pathmon:
\OMNI.$OMNIQ
Cause: IDALLOTB has been tampered.
Corrective Action: Check for illegal access of OmniMessaging.
EMS Message: 02-07-02 10:03:49 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 Process OSR-SRV
\OMNI.$OSRQ Initialization Error <error> Number of users exceeded allowed limit. Pathmon:
\OMNI.$OMNIQ
Cause: The number of users added is more than that allowed by the license file.
Corrective Action: Check for illegal access of OmniMessaging.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 OMNI Process
OSR-SRV \OMNI.$OSRQ Initialization Error <error> Could not find instance status for <instance-name>
Pathmon: \OMNI.$OMNIQ
Cause: OSR could not find the instance status for the <instance-name> mentioned in the pathway
parameter OMNI-OPSW-SERVERS.
Corrective Action: Check if the instance name, <instance-name> given in the pathway parameter
OMNI-OPSW-SERVERS matches to that present in the INSTBS table.