| Symptom | Investigation | Action |
| Unable to login to FIN | FIN logical error received, for example, L33 or S33 (Login or Select sequence number error) |
Correct the error according to the error description and send another Login. |
|
Communication problem with the USE card reader |
Check the card reader display and the related events in the CBT. Correct the problem and send another Login. See Card Readers User Guide - Appendix B: Troubleshooting Guide on the CD, and the FIN CBT documentation from the vendor. |
|
| FIN CBT error |
Check the error message and the related events. Correct the problem (for example, disk space error) and send another Login. See the FIN CBT documentation from the vendor. |
|
| FIN CBT connectivity to SWIFTNet |
Check the events in the CBT and check the connection to the next component. Continue with the SWIFTNet Link section in this guide, or with the customer network section in case an Alliance Gateway is used. |
|
| FIN session is being aborted |
APC or FIN abort error received in the CBT logs, for example, A90 |
This problem may occur due to an intervention at SWIFT. We recommend that you activate the Auto Re-connect feature, in order to minimise the duration of the disconnection. See SWIFT User Handbook - FIN Error Codes, and SWIFTNet Link error codes - SWIFTNet FIN errors |
|
SWIFTNet FIN protocol errors in the CBT logs, for example, FS012, SA100, SS100 |
See SWIFTNet Link error codes - SWIFTNet FIN errors In case of frequent aborts, check the FIN CBT connectivity to SWIFTNet. Continue with the SWIFTNet Link section in this guide, or with the customer network section in case an Alliance Gateway is used. |
|
| FIN messages are rejected with a NAK error code | Message format errors, for example, T13 or H20 (Text error or Header error) | NAKed messages are kept in a message correction queue for manual correction. Check the FIN error code in field 405 of the NAK message. The message can be corrected and can then be re-sent later on. See SWIFT User Handbook - FIN Error Codes |
| Bilateral Key Exchange (BKE) fails | MT 964 or MT 965 with ERF code |
There has been a problem with the exchange of bilateral keys. See SWIFT User Handbook - BKE Troubleshooting, or the help on MT 964 / MT 965 |
| FIN messages are queued up in the FIN CBT | FIN CBT not ready | Ensure that all the FIN LTs are fully logged in (see above) |
|
Verify the size of the components |
Check the system specifications with the recommended sizing See SWIFTNet Connectivity Packs |