Skip to main content
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.
Spok

Smart Alert Errors 16xxx - MXPP Errors

MXPP Errors

 


 

The following table lists the Smart Alert errors for the MXPP module.

Error No. Initiated Description Action
16001 MXPP Invalid File The specified initialization file is invalid, cannot be read or opened.
16002 MXPP Invalid Login The specified login sql or module is invalid.
16003 MXPP Invalid Page Structure Memorey could not be allocated for page structure or the page structure is corrupted.
16004 MXPP Invalid Page Packet The message contains unknown or unparsable data.
16005 MXPP Invalid Server Name A valid HOST name was not specified in the initialization file.
16006 MXPP Invalid Connection Connection to the Mobile XML Gateway server was rejected or not established.
16007 MXPP Socket Write Error Writing to the connection socket has failed.
16008 MXPP No Response The Mobile XML Gateway server has not responded to the sent message with a valid response or there was no response at all.
16009 MXPP Invalid XML Parser An XML parser object could not be initialized.
16010 MXPP Message Rejected The message has been rejected by paging or phone carrier.
16011 MXPP Message Failed Message failed at Messenger side.
16012 MXPP Unknown Message Type The specified Message Type is not one that is supported by Messenger.
16013 MXPP Unknown Message Response Message failed at Messenger side.
16014 MXPP Unknown Gateway Name The COS assigned to the pager is not recogized by Messenger as a valid Output Gateway.
16015 MXPP Message Too Big The length of the message exceeds what Messenger can handle.
16016 MXPP Too Many Response Choices The message contains more response choices than Messenger can handle.
16017 MXPP Connection Lost Connection to the MXPP Gateway (Messenger) is lost.
16018 MXPP Connection Re-Established Connection to the MXPP Gateway (Messenger) re-established.
16019 MXPP Heartbeat Link Down A response to Heartbeat requests was not received from the MXPP Gateway (Messenger).
16020 MXPP Heartbeat Link Up A response to heartbeat requests has been received and the link to the MXPP Gateway is up and ready.
16021 MXPP Invalid XML The message that has been sent to Messenger has failed XML validation.
16022 MXPP System ID Too Long The System ID that is defined in the MXPP In Out initialization file is too long.
16023 MXPP Origin Too Long The pager id or origin of the message is longer than what Messenger expects.
16024 MXPP Tracking ID Too Long The auto generated tracking id is longer what Messenger expects.
16025 MXPP Message Type Too Long The Message Type that is defined in the MXPP In Out initialization file is too long.
16026 MXPP ID Not Found The specified Pager ID or Origin is not found in the message or Messenger system.
16027 MXPP No Response from Device No response has been received from the Amcom (Smart Suite) Mobile Connect application for the sent message.
16028 MXPP No Response from User No response has been received from the recipient for the sent message.
16029 MXPP Invalid Destination The specified Pager ID or Destination is invalid.
16030 MXPP Invalid Message The specified message is blank or invalid.
16031 MXPP Invalid Version Length Version has exceeded the max size of 25 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16032 MXPP Invalid Destination Length Destination has exceeded the max size of 50 characters. Add the correct pager id and try again.
16033 MXPP Invalid Device Timeout Value The timeoutDevice tag has an invalid value, this value should be numeric only between -1 - 999999999. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16034 MXPP Invalid User Timeout Value The timeoutUser tag has an invalid value, this value should be numeric only between -1 - 999999999. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16035 MXPP Invalid Device Timeout Length The timeoutDevice value has exceeded the max size of 10 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16036 MXPP Invalid User Timeout Length The timeoutDevice value has exceeded the max size of 10 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16037 MXPP Invalid Message Version Length The messageVersion value has exceeded the max size of 50 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16038 MXPP Invalid Device Id Length The deviceId value has exceeded the max size of 50 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16039 MXPP Invalid Device Type Length The deviceType value has exceeded the max size of 50 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16040 MXPP Invalid Device Brand Length The deviceBrand value has exceeded the max size of 50 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16041 MXPP Invalid Device OS Length The deviceOS value has exceeded the max size of 255 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16042 MXPP Invalid Device Port Length The devicePort value has exceeded the max size of 15 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16043 MXPP Invalid Device Carrier Length The deviceCarrier value has exceeded the max size of 50 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16044 MXPP Get System Info Rejected The getSystemInfo has an invalid value, this value should be either 0 or 1. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16045 MXPP Set Protocol Version Rejected The setProtocolVersion has an invalid version, this version should only be one of the values listed when making a getSystemInfo request. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16046 MXPP Protocol Version Not Set No XML protocol has been negotiated, setProtocolVersion must be called with an appropriate known protocol version. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16047 MXPP Invalid Beep Code Length The beepCode value has exceeded the max size of 1 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16048 MXPP Invalid Encryption Type Length The encryptionType value has exceeded the max size of 1 characters. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16049 MXPP No AMC Core Available Unable to send AMC Core message due to no AMC Core connection being enabled for this gateway. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16050 MXPP No AMC Core Connection Unable to send AMC Core message due to no AMC Core connection being successfully established. Contact Amcom (Smart Suite)'s support to have the issue looked at and resolved.
16450 MXPP No Response from Device
and / or
Spok Mobile Device Specific Error
No response has been received from the Amcom (Smart Suite) Mobile Connect application for the sent message.
and / or
See System Errors, in Smart Center under "Queues and Logs" for details.

KB60180