OmniMessaging EMS Operator's Manual 1.8
OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 45
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.$Z6YG API Error <error> Subcode <__LINE__ > File Name < Account
information>, < Unexpected MSAPI error. > Pathmon: \OMNI.$OMNI2
Cause: Unexpected MSAPI Error during call to Account information. 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.$Z6YG API Error <error > Subcode <__LINE__ > File Name < Get
Username by mailbox >, < Unexpected MSAPI error. > Pathmon: \OMNI.$OMNI2
Cause: Unexpected MSAPI Error during call to Get Username by 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.
Recovery: Check returnCode to find out the cause of the DB error and act accordingly.
EMS Message: 02-06-25 23:30:39 \NMA001.$LD13 TANDEM.NSIM.G06 000207 OMNI
Process LDS \NMA001.$LD13 API Error <error > Subcode <__LINE__> File Name MSAPI, Unexpected
MSAPI error. Pathmon: \NMA001.$IMAP0
Cause: An unexpected error was encountered in the MSAPI call. 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: Check msError to find out the cause of the DB error and act accordingly.
EMS Message: 02-06-25 23:30:39 \NMA001.$LD13 TANDEM.NSIM.G06 000207 OMNI
Process LDS \NMA001.$LD13 API Error <error > Subcode <__LINE__> File Name < Get Username by
mailbox>, Unexpected MSAPI error. Pathmon: \NMA001.$IMAP0
Cause: An unexpected error was encountered in the MSAPI call. 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: Check msError to find out the cause of the DB error and act accordingly.
EMS Message: 02-06-25 23:30:39 \NMA001.$LD13 TANDEM.NSIM.G06 000207 OMNI
Process LDS \NMA001.$LD13 API Error <error > Subcode <__LINE__> File Name < Log msg of auto
reply>, Unexpected MSAPI error. Pathmon: \NMA001.$IMAP0
Cause: An unexpected error was encountered in the MSAPI call. 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: Check msError to find out the cause of the DB error and act accordingly.
3.7 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 LDS
\NSK.$Z4QZ: Server Warning <error> Open rejected Pathmon: \NSK.$IMAP7
Cause: A server outside the omni system tried to open.
Recovery: No recovery, as we support an open only within the system.
EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process LDS
\NSK.$Z4QZ: Server Warning <error> Routine: initialize, CALL: PRIORITY, priority not changed Pathmon:
\NSK.$IMAP7
Cause: The priority of the process was changed to a value greater than 199.
Recovery: No recovery needed as this is a warning message.
EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process LDS
\NSK.$Z4QZ: Server Warning <error> STATISTICS counters have been reset Pathmon: \NSK.$IMAP7
Cause: Informational message conveying a request for stats reset to the manager process.
Recovery: No recovery as this is an informational message.
EMS Message: 02-03-23 17:23:21 \NSK.$Z4QZ TANDEM.NSIM.G06 000208 OMNI Process LDS
\NSK.$Z4QZ: Server Warning <error> Manager request rejected Pathmon: \NSK.$IMAP7
Cause: Corruption in the request header to the manager process. It can be due to an invalid request type
or invalid request count or an invalid header version.
Recovery: Restart the server and try again.