OmniMessaging EMS Operator's Manual 1.8

ManualsBrandsHP ManualsServerHP NonStop G-Series

OmniMessaging EMS Operator’s Guide

Opsol Confidential and Proprietary

OmniMessaging

EMS Operator’s Manual

Version 1.8

Summary of content (86 pages)

PAGE 1
OmniMessaging EMS Operator’s Guide OmniMessaging EMS Operator’s Manual Version 1.
PAGE 2
OmniMessaging EMS Operator’s Guide 1 IMAP EMS MESSAGES..................................................................................... 5 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 2 MTA EMS MESSAGES .................................................................................... 18 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 3 EMS MESSAGE 200 ..............................................................................
PAGE 3
OmniMessaging EMS Operator’s Guide 3.11 3.12 3.13 3.14 4 48 48 48 48 EMS MESSAGE 200 ...................................................................................... EMS MESSAGE 201 ...................................................................................... EMS MESSAGE 202 ...................................................................................... EMS MESSAGE 203 ...................................................................................... EMS MESSAGE 204 .............
PAGE 4
OmniMessaging EMS Operator’s Guide 8 DUD EMS MESSAGES .................................................................................... 69 8.1 8.2 8.3 8.4 8.5 8.6 8.7 9 EMS EMS EMS EMS EMS EMS EMS MESSAGE MESSAGE MESSAGE MESSAGE MESSAGE MESSAGE MESSAGE 200 ...................................................................................... 201 ...................................................................................... 202 .................................................................
PAGE 5
OmniMessaging EMS Operator’s Guide 1 IMAP EMS Messages These EMS Messages are logged by the OmniMessaging IMAP server. 1.1 EMS Message 200 This EMS event is displayed in the primary collector. EMS Message: 02-07-09 12:06:32 \OMNI.$OSRQ TANDEM.NSIM.G06 IMAP4 STOPPED Illegal Address Reference Pathmon: \OMNI.$IMAP7 Cause: IMAP Server has stopped due to illegal address reference. Corrective Action: No Corrective Action. 000200 OMNI Process 1.
PAGE 6
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process IMAP \NSK.$Z4NL I/O Error: File System Error File Name < filename >, Pathmon: \NSK.$IMAP7 Cause: Incompatible IPC versions. Corrective Action: Check up the configuration, and if the problem persists contact Opsol Support. EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process IMAP \NSK.
PAGE 7
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 09:58:47 \S702WEB.$Y1XW TANDEM.NSIM.G06 000203 OMNI Process IMAP : Out Of Memory \S702WEB.$Y1XW Pathmon: \S702WEB.$OMNID Cause: Unable to allocate memory for the user-process. Corrective Action: Check up system configuration. EMS Message: 02-07-02 09:58:47 \S702WEB.$Y1XW TANDEM.NSIM.G06 000203 OMNI Process IMAP : Out Of Memory \S702WEB.$Y1XW < Unable to allocate OPSWREQ context. > Pathmon: \S702WEB.
PAGE 8
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-03 11:46:09 \SSGJ1.$Z6NP TANDEM.NSIM.G06 000204 OMNI Process IMAP4 \SSGJ1.$Z6NP Internal Module Error Module code <__LINE__>, < filename > Pathmon: \SSGJ1.$OMNIK Cause: A module error has occurred in the code. The error is at Line number “__LINE__” and file name “filename ” Corrective Action: Unexpected module code error. Contact Opsol support. 1.6 EMS Message 205 This EMS event is displayed in the primary collector.
PAGE 9
OmniMessaging EMS Operator’s Guide 1.7 EMS Message 206 This EMS event is displayed in the primary collector. EMS Message: 02-07-08 18:33:53 \NSK.$Z1PM TANDEM.NSIM.G06 000206 OMNI Process IMAP4 \NSK.$Z1PM Unexpected network termination IP Address: AssocID: Pathmon: \NSK.$ZLE Cause: Session got closed due to the server getting re-started. Corrective Action: Informational message. Check up with Administrator. EMS Message: 02-07-08 18:33:53 \NSK.$Z1PM TAND EM.
PAGE 10
OmniMessaging EMS Operator’s Guide Cause: Could not create mailbox. The Subcode is the portion of the code where the error occurred. Check the API error code in the API error codes table in Appendix A. Corrective Action: Informational message. EMS Message: 02-09-16 13:44:56 \OMNI.$Z6YG TANDEM.NSIM.G06 000207 OMNI Process IMAP4 \OMNI.$Z6YG API Error Subcode <__LINE__> File Name , Error returned while Mailbox deletion Pathmon: \OMNI.$OMNI2 Cause: Deletion of mailbox failed.
PAGE 11
OmniMessaging EMS Operator’s Guide EMS Message: 02-09-16 13:44:56 \OMNI.$Z6YG TANDEM.NSIM.G06 000207 OMNI Process IMAP4 \OMNI.$Z6YG API Error Subcode <__LINE__> File Name , Error returned by while Selection mailbox Pathmon: \OMNI.$OMNI2 Cause: Error while selecting mailbox. The Subcode is the portion of the code where the error occurred. Check the API error code in the API error codes table in Appendix A. Corrective Action: Informational message. EMS Message: 02-09-16 13:44:56 \OMNI.
PAGE 12
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.$Z4QZ: Server Warning < error > Error returned by Response Formatter Pathmon: \NSK.$IMAP7 Cause: This EMS Message indicates that there was an error while displaying the output of an IMAP command. Corrective Action: Contact Opsol Support EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.$Z4QZ: Server Warning < error > STOP request received.
PAGE 13
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.$Z4QZ: Server Warning < receive error detected in send receive complete proc >Pathmon: \NSK.$IMAP7 Cause: This EMS Message indicates that an error appeared in inter-instance procedures. Corrective Action: Check up the configuration, and if the problem persists contact Opsol Support. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.
PAGE 14
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.$Z4QZ: Server Warning < error > Pathmon: \NSK.$IMAP7 Cause: This EMS Message indicates that an existing tag was passed. Corrective Action: Check up the configuration, and if the problem persists contact Opsol Support. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.
PAGE 15
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.$Z4QZ: Server Warning < Invalid IPC detected in Connection Complete proc > Pathmon: \NSK.$IMAP7 Cause: This EMS Message indicates that an error appeared in inter-instance process. Corrective Action: Check up the configuration, and if the problem persists contact Opsol Support. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process IMAP \NSK.
PAGE 16
OmniMessaging EMS Operator’s Guide Corrective Action: Contact Omni Support. 1.11 EMS Message 210 This EMS event is displayed in the alternate collector. EMS Message: 02-10-29 16:05:38 \OMNI.$Y25L TANDEM.NSIM.G06 000210 OMNI Process IMAP4:\OMNI.$Y25L, Client Error , IMAP Protocol Error, User:? Command:LOGIN Error: BAD Missing parameter , IP Address , Pathmon: \OMNI.$OMNI2 Cause: Invalid command. Part of Protocol error log. Corrective Action: Informational message.
PAGE 17
OmniMessaging EMS Operator’s Guide EMS Message: 02-09-24 18:02:52 \OMNI.$Y4ND TANDEM.NSIM.G06 001001 Login attempt Unsuccessful Association, Inbound Operation IMAP4 Protocol, Account ID:, Authentication Rejected, AssocID:, Mail User Name: , IP Address: Cause: Unsuccessful login. Corrective Action: Informational message. EMS Message: 02-09-24 18:02:52 \OMNI.$Y4ND TANDEM.NSIM.
PAGE 18
OmniMessaging EMS Operator’s Guide 1.17 EMS Message 1006 This EMS event is displayed in the alternate collector. EMS Message: 02-07-12 11:37:06 \NSK.$Z55K TANDEM.NSIM.G06 001006 Acct Sub System:\NSK.$Z55K AssocID: 80442D8, MsgID: <35DBB8B7AC89D4118E98009027B1009B08C4FB9B@ IL27EXM10.cig.mot.com>, Result size: 1083 bytes, Login User: Winson,Flag-Status:\Answered->SET Cause: Change of message-flag status.
PAGE 19
OmniMessaging EMS Operator’s Guide Note : Messages can be from any of the MTA servers viz. MTA, MTAII, MTAR, RELAY, RELAYR, RELAYD. Accordingly, messages will be displayed as OMNI Process MTA or OMNI Process RELAYD etc. 2.1 EMS Message 200 This EMS event is displayed in the primary collector. EMS Message: 01-01-16 12:00:40 \ATMAIL.$M011 TANDEM.NSIM.G06 000200 OMNI MTA STOPPED \ATMAIL.$M011 Pathmon: \ATMAIL.$PNIM0 Cause: MTA Server stopped.
PAGE 20
OmniMessaging EMS Operator’s Guide Cause: I/O error occurred in NDR file open system call. Corrective Action: none. Informational message. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000202 OMNI Process MTA \NSK.$Z4QZ: I/O Error: File System Error File Name , Open RELAY queue file failed Pathmon: \NSK.$IMAP7 Cause: I/O error occurred in RELAY queue file open system call. Corrective Action: The process will abend.
PAGE 21
OmniMessaging EMS Operator’s Guide Cause: I/O error occurred in Inter-instance open call. Corrective Action: none. Informational message. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000202 OMNI Process MTA \NSK.$Z4QZ: I/O Error: File System Error File Name , IPC open Pathmon: \NSK.$IMAP7 Cause: socket could not be created. Corrective Action: none. Informational message. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000202 OMNI Process MTA \NSK.
PAGE 22
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process MTA \NSK.$Z4NL I/O Error: File System Error File Name , SENDMSG WRITEX . Pathmon: \NSK.$IMAP7 Cause: Transient error in file open. Corrective Action: Find out the reason of the file write failure. EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process MTA \NSK.
PAGE 23
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 09:58:47 \NSK.$Y1XW TANDEM.NSIM.G06 000203 OMNI Process MTA: Out Of Memory \NSK.$Y1XW Unable to allocate message list control block Pathmon: \NSK.$OMNID Cause: Memory could not be allocated to a block. Possible memory leak. Corrective Action: The server will abend. Pass the saveabend to the OmniMessaging representative. EMS Message: 02-07-02 09:58:47 \NSK.$Y1XW TANDEM.NSIM.G06 000203 OMNI Process MTA: Out Of Memory \NSK.
PAGE 24
OmniMessaging EMS Operator’s Guide Cause: The value passed to parameter MAX_RECV_ASSOCIATION was out of range. Corrective Action: The server will shutdown after giving this message. Correct the value passed to the parameter MAX_RECV_ASSOCIATION and start the server again. EMS Message: 02-07-02 10:03:49 \NSK.$Y1YA TANDEM.NSIM.G06 000205 Process MTA \NSK.$Y1YA Initialization Error The max send associations value out of range. Pathmon: \NSK.
PAGE 25
OmniMessaging EMS Operator’s Guide Cause: Error occurred during DB operation. Corrective Action: Please take corrective action based on error reported. 2.8 EMS Message 208 This EMS event is displayed in the primary collector. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning STATISTICS counters have been reset Pathmon: \NSK.$IMAP7 Cause: The statistics counters have been reset. Corrective Action: None. EMS Message: 02-03-23 17:23:21 \NSK.
PAGE 26
OmniMessaging EMS Operator’s Guide Cause: Due to a file system error, transaction is aborted. Corrective Action: Find out the reason of the abort transaction. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning ABORTTRANSACTION error Pathmon: \NSK.$IMAP7 Cause: Due to a file system error, an abort transaction call was unsuccessful. Corrective Action: Find out the reason for the abort transaction. EMS Message: 02-03-23 17:23:21 \NSK.
PAGE 27
OmniMessaging EMS Operator’s Guide Cause: Programming error. Internal tag value mismatch was found in one of the routines. No external effect. Corrective Action: Inform OmniMessaging representative. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process RELA YR \NSK.$Z4QZ: Server Warning IIS open for MTAR timed out. Pathmon: NSK.$IMAP7 Cause: RELAYR was trying to start communication with MTAR. The attempt timed out. Corrective Action: none. EMS Message: 02-03-23 17:23:21 \NSK.
PAGE 28
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTAII \NSK.$Z4QZ: Server Warning IIR open timed out. Pathmon: NSK.$IMAP7 Cause: MTAII/MTAR was waiting to receive a connection from MTA/RELAYR but the operation timed out. Corrective Action: none. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process RELAY \NSK.$Z4QZ: Server Warning IIS open complete context NULL Pathmon: NSK.
PAGE 29
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning < error > Closing socket failed while canceling request Pathmon: NSK.$IMAP7 Cause: Cancel request system call failed. Corrective Action: none. Informational message. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning < error> Connect failure E D Domain Pathmon: NSK.
PAGE 30
OmniMessaging EMS Operator’s Guide Corrective Action: Contact Opsol representative. EMS Message: 02-08-02 00:51:29 \NMA004.$STBC TANDEM.NSIM.G06 000208 OMNI Process RELAYD \NMA004.$STBC: Server Warning Server abending: Relay Recipient doesn't exist Pathmon: \NMA004.$IMAP6 Cause: Servers abended because relay recipient does not exist. Corrective Action: Contact Opsol representative. EMS Message: 02-06-19 15:34:09 \NITRO.$IVMH TANDEM.NSIM.G06 000208 OMNI Process RELAYD \NITRO.
PAGE 31
OmniMessaging EMS Operator’s Guide Cause: This is an informational message. Corrective Action: Contact OmniMessaging support EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 \NSK.$Z4QZ: Server Warning Error in getting space Pathmon: NSK.$IMAP7 Cause: Error in getting space Corrective Action: Contact OmniMessaging support 000208 OMNI Process MTA EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.
PAGE 32
OmniMessaging EMS Operator’s Guide Cause: Transient kind of error in SENDMSG Library processing. Corrective Action: Refer to EMS log for further information. Informational message, no action. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning error SENDMSG Q File Open/Write/Close transient Error. Pathmon: NSK.$IMAP7 Cause: Q file operation failed.
PAGE 33
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning error SENDMSG PERMANENT ERROR: NULL Msg Context. Pathmon: NSK.$IMAP7 Cause: SENDMSG Library internal transient error informational message. Corrective Action: none. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning error SENDMSG Internal Error, Message Context invalid. Pathmon: NSK.
PAGE 34
OmniMessaging EMS Operator’s Guide normal relay. Pathmon: NSK.$IMAP7 Cause: Maximum Send threads specified in the server configuration has been fully utilized. Corrective Action: Informational Message. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 \NSK.$Z4QZ: Server Warning Pathmon: NSK.$IMAP7 Cause: Open on MBM queue failed. Corrective Action: Please take corrective action based on error code. 000208 OMNI Process MTA EMS Message: 02-03-23 17:23:21 \NSK.
PAGE 35
OmniMessaging EMS Operator’s Guide Cause: MTA could not send the email, hence writing retry record for relay to try at specified scheduled time. Corrective Action: Informative message. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning Illegal action code being sent to MBM...Taking no action Pathmon: NSK.$IMAP7 Cause: Internal process flow error. Corrective Action:Report to omniSupport. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.
PAGE 36
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.$Z4QZ: Server Warning NULL Message Context passed to mem-to-DB module Pathmon: NSK.$IMAP7 Cause: During process flow, unexpected error has occurred. Corrective Action: Please report to omnisupport with required details as per shown in EMS. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process MTA \NSK.
PAGE 37
OmniMessaging EMS Operator’s Guide EMS Message: 02-09-27 14:19:11 \NSK.$Y6BJ TANDEM.NSIM.G06 000209 OMNI Process MTA: Message Store Error - \OMNI.$Y6BJ Module Error Module code 0 File Name Pathmon: \OMNI.$OMNI2 EMS Message: 02-09-27 14:19:11 \NSK.$Y6BJ TANDEM.NSIM.G06 000209 OMNI Process MTA: Message Store Error - \OMNI.$Y6BJ Module Error Module code 0 File Name Pathmon: \OMNI.
PAGE 38
OmniMessaging EMS Operator’s Guide ERROR from Disk Process [73]: The table or record is locked. Pathmon: \NMA003.$IMAP0 Cause: SQL lock error occurred. Corrective Action: Informational message. EMS Message: 02-08-27 14:45:45 \NMA003.$SE33 TANDEM.NSIM.G06 000209 OMNI Process RELAYD: Message Store Error - \NMA003.$SE33 Module Error 252 Module code 0 File Name Delete relay recepients, ERROR from SQL [-8300]: File system error occurred on \NMA003.$D0002.IMAP1101.RLYRCPTB.
PAGE 39
OmniMessaging EMS Operator’s Guide Process MTA: Client Error - \NITRO.$MA11 Error SMTP Protocol Error, User: Command:RCPT TO:ZETTAIINAIYUZA@DOMAIN.COM Error: 550 user unknown Client Name 16.175.135.130 Pathmon: \NITRO.$NSMWK Cause: Unknown local user in rcpt command. Corrective Action: Informational message. 2.11 EMS Message 1004 This EMS event is displayed in the alternate collector. EMS Message: 02-05-08 15:08:02 \NITRO.$MA11 TANDEM.NSIM.G06 MTA:\NITRO.
PAGE 40
OmniMessaging EMS Operator’s Guide EMS Message: 02-06-25 20:24:56 \ATOM.$FL16 TANDEM.NSIM.G06 001014 MTA:\ATOM.$FL16 Transfer message in for a user on remote domain /other instance user MsgID: <200206251124560471960001FL16@imap.com> Size: 665 AssocID: 803EAD8 Originator: <> Cause: Mail for a user on either remote domain or on a different node has been received by MTA. Corrective Action: Informational message. 2.15 EMS Message 4000 This EMS event is displayed in the alternate collector.
PAGE 41
OmniMessaging EMS Operator’s Guide 3.2 EMS Message 201 This EMS event is displayed in the primary collector. EMS Message: 02-07-09 12:06:32 \OMNI.$OSRQ TANDEM.NSIM.G06 LDS STARTED \OMNI.$OSRQ Pathmon: \OMNI.$OMNIQ Cause: LDS Server has started. Corrective Action: No Corrective Action. 000201 OMNI Process 3.3 EMS Message 202 This EMS event is displayed in the primary collector. EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process LDS \NSK.
PAGE 42
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process LDS \NSK.$Z4NL I/O Error: File System Error File Name < =LDS^QTW^Q^FILE >, < SETMODENOWAIT > Pathmon: \NSK.$IMAP7 Cause: Error in setting the timeout value in the QTW Queue File Recovery: Find the cause of the error from the file system error and take the necessary action. EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process LDS \NSK.
PAGE 43
OmniMessaging EMS Operator’s Guide Cause: Error in writing to the QTW Queue File. Recovery: Find the cause of the error from the file system error and take the necessary action. EMS Message: 02-03-23 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process LDS \NSK.$Z4NL I/O Error: File System Error File Name < p_QTW_BKUP_QUEUE_FILE>, < WRITEX > Pathmon: \NSK.$IMAP7 Cause: Error in writing to the QTW Backup Queue File.
PAGE 44
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 10:03:49 \S702WEB.$Y1YA TANDEM.NSIM.G06 000205 Process LDS \S702WEB.$Y1YA Initialization Error < License file not specified> Pathmon: \S702WEB.$OMNID Cause: The license file was not specified as a startup param. Recovery: Specify the license file as a startup param and restart the server. EMS Message: 02-07-02 10:03:49 \S702WEB.$Y1YA TANDEM.NSIM.G06 000205 Process LDS \S702WEB.$Y1YA Initialization Error < SQL Error> Pathmon: \S702WEB.
PAGE 45
OmniMessaging EMS Operator’s Guide Cause: Unexpected MSAPI Error during call to get information of mailbox by id. The Subcode is the portion of the code where the error occurred. Check the API error code in the API error codes table in Appendix A. Recovery: Check returnCode to find out the cause of the DB error and act accordingly. EMS Message: 02-09-16 13:44:56 \OMNI.$Z6YG TANDEM.NSIM.G06 000207 OMNI Process LDS \OMNI.
PAGE 46
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process LDS \NSK.$Z4QZ: Server Warning pMaxRetryCountReachedMsg Pathmon: \NSK.$IMAP7 Cause: Corrupt records in LDSQUEUE, REDQUEUE, NDRQUEUE and QTWQUEUE. These records will be retried for 3 times before they are written to the respective backup queues. Recovery: Analysis of the backup queue records to find the cause of corruption. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.
PAGE 47
OmniMessaging EMS Operator’s Guide Recovery: Look into the PCOL to find the cause of the failure and correct the same. EMS Message: 02-06-26 16:35:44 \ATOM.$FL16 TANDEM.NSIM.G06 000208 OMNI Process LDS \ATOM.$FL16: Server Warning Record reached maximum retries Pathmon: \ATOM.$SPMG Cause: If a Record in the primary queue is corrupted, it will be tried 3 times before writing into the backup queue. The above message is generated when all the retries have exhausted.
PAGE 48
OmniMessaging EMS Operator’s Guide Cause: Message for the specified user stored in the user’s mailbox. Corrective Action: Informational message. 3.11 EMS Message 1008 This EMS event is displayed in the alternate collector. EMS Message: 02-07-09 05:13:06 \NSK.$Z1PR TANDEM.NSIM.G06 001008 Non Delivery Report Generated for kapil@zlemail.com AssocID: 803CDB0 MsgID: 0b7d01c22645$94d2ff50$1b1fa110@COMPAQ20 Result size: 794194 bytes Originator:
PAGE 49
OmniMessaging EMS Operator’s Guide 4.1 EMS Message 200 This EMS event is displayed in the primary collector. EMS Message: 01-01-30 22:26:55 \ATMAIL.$B011 TANDEM.NSIM.G06 000200 OMNI MBM STOPPED \ATMAIL.$B011 Pathmon: \ATMAIL.$PNIM0 Cause: MBM server has stopped. Corrective Action: Check EMS messages before this EMS message to find cause for the server to stop. 4.2 EMS Message 201 This EMS event is displayed in the primary collector. EMS Message: 02-07-09 12:06:32 \OMNI.$OSRQ TANDEM.NSIM.
PAGE 50
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 10:03:49 \S702WEB.$Y1YA TANDEM.NSIM.G06 000205 Process MBM \S702WEB.$Y1YA Initialization Error Pathmon: \S702WEB.$OMNID Cause: License file not specified in the server configuration. Recovery: Specify license file in the server configuration. EMS Message: 02-07-02 10:03:49 \S702WEB.$Y1YA TANDEM.NSIM.G06 000205 Process MBM \S702WEB.$Y1YA Initialization Error < SQL Error> Pathmon: \S702WEB.
PAGE 51
OmniMessaging EMS Operator’s Guide 02-09-16 17:35:35 \NSK.$Z1K8 TANDEM.NSIM.G06 000208 OMNI Process MBM \NSK.$Z1K8: Server Warning RESUMETRANSACTION error Pathmon: \NSK.$OMNIM Cause: Resume Transaction failed. Recovery: Contact Opsol Support. EMS Message: 02-09-16 17:44:26 \NSK.$Z24H TANDEM.NSIM.G06 000208 OMNI Process MBM \NSK.$Z24H: Server Warning ABORTTRANSACTION error Pathmon: \NSK.$OMNIM Cause: Abort Transaction failed. Recovery: Contact Opsol Support.
PAGE 52
OmniMessaging EMS Operator’s Guide 4.8 EMS Message 209 This EMS event is displayed in the primary collector. EMS Message: 02-08-12 11:39:04 \NMA002.$BP70 TANDEM.NSIM.G06 000209 OMNI Process MBM: Message Store Error - \NMA002.$BP70 Module Error -8222 Module code 0 File Name MSAPI, ERROR from SQL [-8222]: More than one row would satisfy a SELECT request with an INTO clause or a subquery. Pathmon: \NMA002.$IMAP6 Cause: SQL select query returns error 8222. Corrective Action: Data -base error.
PAGE 53
OmniMessaging EMS Operator’s Guide EMS Message: 01-01-16 12:00:40 \ATMAIL.$M011 TANDEM.NSIM.G06 000200 OMNI OSR-SRV STOPPED \ATMAIL.$M011 Pathmon: \ATMAIL.$PNIM0 Cause: OSR Server stopped. Corrective Action: Check EMS messages preceding this EMS message for details. 5.2 EMS Message 201 This EMS event is displayed in the primary collector. EMS Message: 02-07-09 12:06:32 \OMNI.$OSRQ TANDEM.NSIM.G06 OSR-SRV STARTED \OMNI.$OSRQ Pathmon: \OMNI.$OMNIQ Cause: OSR Server has started.
PAGE 54
OmniMessaging EMS Operator’s Guide 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.
PAGE 55
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \OMNI.$OSRQ TANDEM.NSIM.G06 000205 OMNI Process OSR-SRV \OMNI.$OSRQ Initialization Error Could not find failovercap for Pathmon: \OMNI.$OMNIQ Cause: OSR could not find the fail over capability for the instance mentioned in the pathway parameter OMNI-OPSW-SERVERS.
PAGE 56
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 10:03:49 \OMNI.$OSSQ TANDEM.NSIM.G06 000205 Process OSS-SRV \OMNI.$OSSQ Initialization 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.
PAGE 57
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \OMNI.$OSSQ TANDEM.NSIM.G06 000208 OMNI Process OSS-SRV \OMNI.$OSSQ: Server Warning Illegal instance name : Pathmon: \OMNI.$OMNIQ Cause: The home instance name mentioned in pathway configuration is incorrect. Corrective Action: Mention the correct value for the home instance name. 5.7 EMS Message 400 This EMS event is displayed in the primary collector. EMS Message: 02-06-18 17:55:18 \S702WEB.$X90V TANDEM.NSIM.
PAGE 58
OmniMessaging EMS Operator’s Guide 6.1 EMS Message 200 This EMS event is displayed in the primary collector. EMS Message: 01-01-16 12:00:40 \ATMAIL.$M011 TANDEM.NSIM.G06 000200 OMNI POP3 STOPPED \OMNI.$POP3 Pathmon: \OMNI.$OMNI2 Cause: POP Server stopped. Corrective Action: Check EMS messages preceding this EMS message for details. 6.2 EMS Message 201 This EMS event is displayed in the primary collector. EMS Message: 02-07-09 12:06:32 \OMNI.$OSRQ TANDEM.NSIM.G06 POP3 STARTED \OMNI.$POP3 Pathmon: \OMNI.
PAGE 59
OmniMessaging EMS Operator’s Guide EMS Message: 02-11-14 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process POP3 \NSK.$Z4NL I/O Error: File System Error File Name , < MaxReplyCount is too small.> Pathmon: \NSK.$OMNI2 Cause: The size of response buffer to a manager process request like Stats, Graceful stop Exceeds maximum response for that request. Recovery: Informational Message. EMS Message: 02-11-14 18:30:49 \NSK.$Z4NL TANDEM.NSIM.G06 000202 OMNI Process POP3 \NSK.
PAGE 60
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 09:58:47 \S702WEB.$Y1XW TANDEM.NSIM.G06 000203 OMNI Process POP3 : Out Of Memory \S702WEB.$Y1XW < Unable to allocate OPSWREQ GLOBAL CONTEXT> Pathmon: \S702WEB.$OMNID Cause: The application encountered memory shortage while allocation OPSWREQ global context. Corrective Action: Check swap space. 6.5 EMS Message 204 This EMS event is displayed in the primary collector. EMS Message: 02-07-02 10:09:38 \S702WEB.$Y1YP TANDEM.NSIM.
PAGE 61
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 10:03:49 \S702WEB.$Y1YA TANDEM.NSIM.G06 000205 Process POP3 \S702WEB.$Y1YA Initialization Error Pathmon: \S702WEB.$OMNID Cause: The NSIM-SERVER-CLASS param is missing. Corrective Action: Specify the NSIM-SERVER-CLASS param in the server configuration. EMS Message: 02-07-02 10:03:49 \S702WEB.$Y1YA TANDEM.NSIM.G06 000205 Process POP3 \S702WEB.
PAGE 62
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-08 18:33:53 \NSK.$Z1PM TANDEM.NSIM.G06 000206 OMNI Process POP3 \NSK.$Z1PM Unexpected network termination < recv operation timed-out.> IP Address: AssocID: Pathmon: \NSK.$ZLE Cause: Unexpected network termination Corrective Action: Contact Opsol support. 6.8 EMS Message 207 This EMS event is displayed in the primary collector. EMS Message: 02-09-16 13:44:56 \OMNI.$Z6YG TANDEM.NSIM.G06 000207 OMNI Process POP3 \OMNI.
PAGE 63
OmniMessaging EMS Operator’s Guide EMS Message: 02-11-15 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process POP3 \NSK.$Z4QZ: Server Warning < error > < STOP request received. Going to stop.> Pathmon: NSK.$OMNI7 Cause: Graceful stop request invoked. Corrective Action: Informational message. EMS Message: 02-11-15 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process POP3 \NSK.$Z4QZ: Server Warning < error > STATISTICS counters have been reset. Pathmon: NSK.$OMNI7 Cause: Stats have been reset.
PAGE 64
OmniMessaging EMS Operator’s Guide 6.12 EMS Message 211 This EMS event is displayed in the primary collector. EMS Message: 02-11-27 13:00:56 \OMNI.$POP2 TANDEM.NSIM.G06 000211 OMNI Process POP3: Client Warning \OMNI.$POP2 Error POP3 command line too long. Client Name 192.168.1.230 Pathmon: \OMNI.$OMNI2 Cause: Command too long. Corrective Action: Specify valid command. 6.13 EMS Message 400 This EMS event is displayed in the primary collector. EMS Message: 02-11-27 10:50:39 \OMNI.$POP2 TANDEM.NSIM.
PAGE 65
OmniMessaging EMS Operator’s Guide EMS Message: 02-11-27 11:00:44 \OMNI.$POP3 TANDEM.NSIM.G06 Terminated POP3 Protocol, AssocID: 800BE78, Remote: (192.168.1.230) Cause: Network connect terminated. Corrective Action: Informational Message. 001007 Network Connect 6.17 EMS Message 5000 This EMS event is displayed in the primary collector. EMS Message: 02-11-27 11:00:44 \OMNI.$POP3 TANDEM.NSIM.G06 005000 OMNI Process POP3 \OMNI.$POP3: ABORTTRANSACTION Called Successfully Pathmon: \OMNI.
PAGE 66
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process Recovery \NSK.$Z4QZ: Server Warning Error in space allocation for temp file Pathmon: NSK.$IMAP7 Cause: Error in allocating space Corrective Action: Contact OmniMessaging support EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process Recovery \NSK.$Z4QZ: Server Warning Error in starting transaction Pathmon: NSK.
PAGE 67
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process Recovery \NSK.$Z4QZ: Server Warning Space allocation for sending message failed Pathmon: NSK.$IMAP7 Cause: Space could not be allocated for sending the message. Corrective Action: Contact OmniMessaging support EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process Recovery \NSK.
PAGE 68
OmniMessaging EMS Operator’s Guide Cause: There was an error in ending the filename search. Corrective Action: Contact OmniMessaging support EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process Recovery \NSK.$Z4QZ: Server Warning Unable to allocate memory from heap for context Pathmon: NSK.$IMAP7 Cause: Not enough memory heap available for context allocation Corrective Action: Contact OmniMessaging support EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.
PAGE 69
OmniMessaging EMS Operator’s Guide EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process Recovery \NSK.$Z4QZ: Server Warning Could not initialize sendmsg library Pathmon: NSK.$IMAP7 Cause: The sendmsg library could not be initialized Corrective Action: Contact OmniMessaging support 8 DUD EMS Messages These messages are generated by the OmniMessaging DUD server. 8.1 EMS Message 200 This EMS event is displayed in the primary collector. EMS Message: 02-11-16 12:00:40 \OMNI.
PAGE 70
OmniMessaging EMS Operator’s Guide 8.4 EMS Message 203 This EMS event is displayed in the primary collector. EMS Message: 02-07-02 09:58:47 \S702WEB.$Y1XW TANDEM.NSIM.G06 000203 OMNI Process DUD : Out Of Memory \S702WEB.$Y1XW Pathmon: \S702WEB.$OMNID Cause: Memory allocation failed Corrective Action: Check up system configuration. EMS Message: 02-07-02 09:58:47 \S702WEB.$Y1XW TANDEM.NSIM.G06 000203 OMNI Process DUD : Out Of Memory \S702WEB.
PAGE 71
OmniMessaging EMS Operator’s Guide Cause: DUD Process was attempted to be opened by unauthorized process Id. Corrective Action: Find out if this occurs frequently. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process DUD \NSK.$Z4QZ: Server Warning Domain is marked down for sec.Pathmon: NSK.$IMAP7 Cause: This is an informative message indicating that DUD has marked domain down. Corrective Action:None. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.
PAGE 72
OmniMessaging EMS Operator’s Guide 9.2 EMS Message 201 This EMS event is displayed in the primary collector. EMS Message: 03-06-11 17:22:00 \OMNI.$Z735 STARTED \OMNI.$Z735 Pathmon: \OMNI.$OMNI5 Cause: ZLE ADAPTOR Server has started. Corrective Action: No Corrective Action. TANDEM.NSIM.G06 000201 OMNI ADAPTOR 9.3 EMS Message 202 This EMS event is displayed in the primary collector. EMS Message: 03-06-11 17:05:39 \OMNI.$Z6SV TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.
PAGE 73
OmniMessaging EMS Operator’s Guide Corrective Action: Contact OmniMessaging support. EMS Message: 02-03-23 17:23:21 \OMNI.$Z6SV TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.$Z6SV I/O Error: File System Error File Name , MTP_Reply failed. Pathmon: \OMNI.$OMNI5 Cause: Interprocess communication failed. Corrective Action: Contact OmniMessaging support. EMS Message: 02-03-23 17:23:21 \OMNI.$Z6SV TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.
PAGE 74
OmniMessaging EMS Operator’s Guide EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.$X3H4 I/O Error: File System Error File Name , Invalid forward message flag Pathmon: \OMNI.$OMNI1 Cause: While forwarding a message using zle adaptor, the forward message flag specified was invalid. Corrective Action: Zle adaptor supports header only or full forward message flags. If unspecified, full forward message flag is assumed.
PAGE 75
OmniMessaging EMS Operator’s Guide EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.$X3H4 I/O Error: File System Error File Name , Process Handle Decompose failed Pathmon: \OMNI.$OMNI1 Cause: Guardian call for process handle decompose failed. Corrective Action: Contact OmniMessaging support. EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.
PAGE 76
OmniMessaging EMS Operator’s Guide Cause: Zle adaptor could not write to the temporary file created for retrieving attachment of the message. Corrective Action: Contact OmniMessaging support. EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.$X3H4 I/O Error: File System Error File Name , Could not write correct len to att Pathmon: \OMNI.
PAGE 77
OmniMessaging EMS Operator’s Guide EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.$X3H4 I/O Error: File System Error File Name , Boundary string not found Pathmon: \OMNI.$OMNI1 Cause: While forwarding a message, zle adaptor could not retrieve the original boundary string. Corrective Action: Contact OmniMessaging support. EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.
PAGE 78
OmniMessaging EMS Operator’s Guide Corrective Action: Contact OmniMessaging support. EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.$X3H4 I/O Error: File System Error File Name , Text/Plain Content type not found Pathmon: \OMNI.$OMNI1 Cause: While retrieving a message, zle adaptor could not parse the Text/Plain content type in the header of the message. Corrective Action: Contact OmniMessaging support. EMS Message: 03-06-12 02:00:31 \OMNI.
PAGE 79
OmniMessaging EMS Operator’s Guide ADAPTOR \OMNI.$X3H4 I/O Error: File System Error File Name , SMTP data headers not found Pathmon: \OMNI.$OMNI1 Cause: While retrieving the WAP encoded message, zle adaptor could not find the SMTP data headers. Corrective Action: Contact OmniMessaging support. EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.
PAGE 80
OmniMessaging EMS Operator’s Guide EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.$X3H4 I/O Error: File System Error File Name , Sendmsg Quit failed Pathmon: \OMNI.$OMNI1 Cause: The Sendmsg Quit call failed. Corrective Action: Contact OmniMessaging support. EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process ADAPTOR \OMNI.
PAGE 81
OmniMessaging EMS Operator’s Guide EMS Message: 02-07-02 10:03:49 \S702WEB.$Y1YA TANDEM.NSIM.G06 000205 Process ADAPTOR \S702WEB.$Y1YA Initialization Error The max-sessions value out of range. Pathmon: \S702WEB.$OMNI5 Cause: Invalid maximum session value in server param. Corrective Action: Check up the server configuration, and correct the NSIM-ZLEADAPT-MAX-SESSION param. The maximum sessions supported is 100. EMS Message: 02-07-02 15:06:15 \SSGJ1.$Z6NA TANDEM.NSIM.G06 000205 Process ADAPTOR \SSGJ1.
PAGE 82
OmniMessaging EMS Operator’s Guide Corrective Action: Retrieve the temporary files created by the zle adaptor from the server’s default $VOL.SUBVOL location. Else specify the required guardian location in the OMNI -TEMP-FILE-LOC param to create temporary files. EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process ADAPTOR \NSK.$Z4QZ: Server Warning Extension missing in attachment name Pathmon: \NSK.
PAGE 83
OmniMessaging EMS Operator’s Guide Appendix A API Error Codes API Error Codes 0 1 Constant Name Explanation MSE_SUCCESS The call is successful MSE_SUCCESS_DOMAIN_IP_FORMAT 2 MSE_SUCCESS_END 3 MSE_SUCCESS_PARTIAL 4 MSE_SUCCESS_WAIT 5 8 10 11 12 13 14 15 16 17 20 21 22 23 24 25 MSE_SUCCESS_NULL Call successful, but domain in IP format rather than more usual domain name.
PAGE 84
OmniMessaging EMS Operator’s Guide 58 70 71 72 80 85 90 MSE_DOMAIN_TYPE_INVALID Domain type invalid MSE_FILE_LOCKED Enscribe file is locked out, e.g. a Queue file. MSE_FILE_NAME_DUPLICATE File already exists MSE_FILE_NOT_OPEN MSE_GUARDIAN_ERROR File not open for write, etc. Unexpected Guardian error returned. MSE_ID_TYPE_INVALID The ID type is not of expected type.
PAGE 85
OmniMessaging EMS Operator’s Guide 165 166 167 MSE_MSG_NOT_IN_MAILBOX The message is not in specified mailbox MSE_MSG_POOL_NONE_FOUND Pool number for the message not found MSE_MSG_SIZE_EXCEEDED 168 180 MSE_MSG_RET_PERIOD_INVALID The maximum size for a single message has been violated Retention period limit specified is invalid 182 183 MSE_NAMESPACE_NAME_DUPLICATE 184 MSE_NAMESPACE_UNUSABLE 185 186 MSE_NAMESPACE_MAILBOXES_EXIST 187 188 190 200 210 215 220 MSE_NAMESPACE_STATUS_INVALID Account
PAGE 86
OmniMessaging EMS Operator’s Guide 281 290 291 292 293 300 MSE_SUBSCRIPTION_DUPLICATE Mailbox is already subscribed MSE_SERVICE_DOESNT_EXIST Service package is non-existing or inactive MSE_SERVICE_DUPLICATE Service package already exists MSE_SERVICE_NONE_FOUND MSE_SERVICE_STATUS_INACTIVE Service package not found Service package is inactive MSE_THRESHOLD_EXCEEDED 301 310 320 321 322 323 324 325 326 MSE_THRESHOLD_INVALID The amount of mail in the users personal mail store is greater than the conf