OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 56
EMS Message: 02-07-02 10:03:49 \OMNI.$OSSQ TANDEM.NSIM.G06 000205 Process OSS-SRV
\OMNI.$OSSQ 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.
5.6 EMS Message 208
This EMS event is displayed in the primary collector.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000208 OMNI Process
OSR-SRV \OMNI.$OSRQ: Server Warning <error> Opener Table was inconsistent. Pathmon:
\OMNI.$OMNIQ
Cause: Opener table management is incorrect. It is an internal error
Corrective Action: Contact OmniMessaging support
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000208 OMNI Process
OSR-SRV \OMNI.$OSRQ: Server Warning <error> Open attempt by an unauthorized PAID Pathmon:
\OMNI.$OMNIQ
Cause: Paid of the opener is not the same as that of the OSR process
Corrective Action: Check the security of all the servers in the pathway environment
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000208 OMNI Process
OSR-SRV \OMNI.$OSRQ: Server Warning <error> OPSW REQUESTOR REQUEST REJECTED Pathmon:
\OMNI.$OMNIQ
Cause: File System error has occurred while communicating with OSR process
Corrective Action: Contact OmniMessaging support
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000208 OMNI Process
OSR-SRV \OMNI.$OSRQ: Server Warning <error> Open process <OSS name> error = <filesystem
error> Pathmon: \OMNI.$OMNIQ
Cause: OSR got file system error while opening the OSS process
Corrective Action: Contact OmniMessaging support
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000208 OMNI Process
OSR-SRV \OMNI.$OSRQ: Server Warning <error> Invalid parameter – OMNI-OPSW-SERVERS : missing
serverName for instance = <instance-name> Pathmon: \OMNI.$OMNIQ
Cause: OSS process name for is missing for the instance
Corrective Action: Mention the OSS process name for the instance
EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000208 OMNI Process
OSR-SRV \OMNI.$OSRQ: Server Warning <error> Error <SQL error> in reading the INSTANCE BASE
table Pathmon: \OMNI.$OMNIQ
Cause: There was an SQL error while reading the INSTANCE BASE table
Corrective Action: If there are no records in the INSTANCE BASE table, add relevant records. If there
are records present in the INSTANCE BASE table, contact OmniMessaging support.
EMS Message: 02-03-23 17:23:21 \OMNI.$OSSQ TANDEM.NSIM.G06 000208 OMNI Process
OSS-SRV \OMNI.$OSSQ: Server Warning <error> Open attempt by an unauthorized PAID Pathmon:
\OMNI.$OMNIQ
Cause: Paid of the opener is not the same as that of the OSS process
Corrective Action: Check the security of all the servers in the pathway environment
EMS Message: 02-03-23 17:23:21 \OMNI.$OSSQ TANDEM.NSIM.G06 000208 OMNI Process
OSS-SRV \OMNI.$OSSQ: Server Warning < error> OPSWSRV SERVER CONNECT REJECTED Pathmon:
\OMNI.$OMNIQ
Cause: File System error has occurred while communicating with OSS process
Corrective Action: Contact OmniMessaging support
EMS Message: 02-03-23 17:23:21 \OMNI.$OSSQ TANDEM.NSIM.G06 000208 OMNI Process
OSS-SRV \OMNI.$OSSQ: Server Warning <error> Missing required parameter : OMNI-INSTANCE-NAME
Pathmon: \OMNI.$OMNIQ
Cause: The pathway parameter OMNI-INSTANCE-NAME is missing.
Corrective Action: Give the pathway parameter