Retrieval Errors: The Following Codes Are Returned in Field 421 of Message Retrievals
The document lists numeric codes returned in field 421 of message retrieval responses. Codes indicate issues like an encrypted message with no key provided, an unauthorized requester, missing text or history due to system recovery, invalid retrieval criteria, exceeding retrieval limits, and retrieval report problems.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
57 views
Retrieval Errors: The Following Codes Are Returned in Field 421 of Message Retrievals
The document lists numeric codes returned in field 421 of message retrieval responses. Codes indicate issues like an encrypted message with no key provided, an unauthorized requester, missing text or history due to system recovery, invalid retrieval criteria, exceeding retrieval limits, and retrieval report problems.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1
Retrieval Errors
The following codes are returned in field 421 of message retrievals:
000 Message has no text block 002 Message was encrypted and no key or the wrong key was supplied by the user 003 Empty report (no messages found) 004 Logical terminal is not authorised to retrieve the message, that is the requester is neither the sender nor the receiver of the original message 005 Text lost due to Slice Processor recovery 006 History lost due to Slice Processor recovery 007 Target message is a retrieval report (MTs 021 or 023) 010 Invalid MT received by Slice Processor pseudo logical terminal (system) 011 Invalid <application-id> received by Slice Processor pseudo logical terminal (system) 012 Invalid date in retrieval criteria tag (system) 013 Invalid time in retrieval criteria tag (system) 014 End daytime before start daytime 015 Target message older than 124 days (for range retrieval, daytime used) 016 <branch-code> is not 'XXX' 018 Invalid destination for report (tag 102). The logical terminal must have the same destination as the sender of the retrieval request or be a SWIFT logical terminal, and must be enabled for the application in which the retrieval message is to be sent 019 Invalid input retrieval by receiver or output retrieval by sender (only single message input reference/message output reference allowed) 020 Invalid synonym retrieval (synonym is not sender or receiver of message) 021 Unknown target logical terminal 022 Request received at wrong Slice Processor (system) Chapter 2 Numeric Codes 20 July 2017 9 023 Could not retrieve message input reference in message output reference retrieval (system) 032 No delivery attempt in message input reference retrieval by receiver 033 On-line text read error (system) 034 On-line history read error (system) 035 Text read error from archival (system) 036 History read error from archival (system) 037 Partial report - major system recovery in progress 038 Unable to retrieve text and history from archival because of system problems 040 The limits for group retrieval (99 messages in one request) have been exceeded 041 Message could not be decrypted (system) 043 The logical terminals in the beginning message input reference/message output reference and the ending message input reference/message output reference in a range retrieval request are not the same, in tag 252 (message input reference range) or 254 (message output reference range) 044 Illogical use of field 152 <1st-isn> or field 153 <1st-osn>. input sequence number or output sequence number already included as component in message input reference(s) or message output reference(s) 045 Message text not retrievable (message not successfully delivered) 046 Off-line retrieval not allowed for Test and Training messages 047 The text of local test mode messages is not retrievable 048 Retrieval message too long 049 Retrieval period specified exceeds 10 days 099 Retrieval report problem. Contact your Customer Support Centre