OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 55
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 failovercap for <instance-name>
Pathmon: \OMNI.$OMNIQ
Cause: OSR could not find the fail over capability for the instance <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. Also check the FAIL_OVER_CAPABILITY
column for the instance, <instance-name> in the INSTBS table.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 OMNI Process
OSR-SRV \OMNI.$OSRQ Initialization Error <error> Invalid Instance Name : <instance-name> Pathmon:
\OMNI.$OMNIQ
Cause: An invalid instance name, <instance-name> is given in the pathway parameter OMNI-OPSW-
SERVERS
Corrective Action: Correct the instance name, <instance-name> in the pathway parameter OMNI-
OPSW-SERVERS
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 OMNI Process
OSR-SRV \OMNI.$OSRQ Initialization Error <error> The OMNI-HOST-NAME parameter must be specified.
Pathmon: \OMNI.$OMNIQ
Cause: The pathway parameter OMNI-HOST-NAME is not mentioned for OSR.
Corrective Action: Mention the pathway parameter OMNI-HOST-NAME for OSR.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 OMNI Process
OSR-SRV \OMNI.$OSRQ Initialization Error <error> The MAX-OPENS value out of range. Pathmon:
\OMNI.$OMNIQ
Cause: The value for pathway parameter OMNI-OPSWREQ-MAX-OPENS is not between 1 and 40.
Corrective Action: Correct the value for the pathway parameter OMNI-OPSWREQ-MAX-OPENS for OSR.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 OMNI Process
OSR-SRV \OMNI.$OSRQ Initialization Error <error> The OMNI-INSTANCE-NAME parameter must be
specified
Pathmon: \OMNI.$OMNIQ
Cause: The pathway parameter OMNI-INSTANCE-NAME is not mentioned for OSR.
Corrective Action: Mention the pathway parameter OMNI-INSTANCE-NAME for OSR.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 OMNI Process
OSR-SRV \OMNI.$OSRQ Initialization Error <error> Invalid Home Instance Name : <instance-name>
Pathmon: \OMNI.$OMNIQ
Cause: Invalid home instance name given in pathway parameter OMNI-INSTANCE-NAME
Corrective Action: Mention a correct value for pathway parameter OMNI-INSTANCE-NAME.
EMS Message: 02-07-02 10:03:49 \OMNI.$OSSQ TANDEM.NSIM.G06 000205 Process OSS-SRV
\OMNI.$OSSQ Initialization Error <error> License file not specified. Pathmon: \OMNI.$OMNIQ
Cause: The pathway parameter NSIM-LIC is not specified for OSS.
Corrective Action: Mention the pathway parameter NSIM-LIC for OSS.
EMS Message: 02-07-02 10:03:49 \OMNI.$OSSQ TANDEM.NSIM.G06 000205 Process OSS-SRV
\OMNI.$OSSQ 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.$OSSQ TANDEM.NSIM.G06 000205 Process OSS-SRV
\OMNI.$OSSQ 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.$OSSQ TANDEM.NSIM.G06 000205 Process OSS-SRV
\OMNI.$OSSQ Initialization Error <error> IDALLOTB table has been tampered Pathmon: \OMNI.$OMNIQ
Cause: IDALLOTB has been tampered.
Corrective Action: Check for illegal access of OmniMessaging.