| General errors | |||
| Error Message | Profile Type | Meaning | Solution |
|---|---|---|---|
| Profile type mismatch, expected TRAVELLER, got null | Traveler | Traveller profile was laready deleted from or deactivated in Amadeus | Umbrella support has to remove the record locator so that "save" leads to a new profile creation |
| Publishing failed with the error: soap message header incorrect | Company | Something is wrong with OID or WSAP | Contact Amadeus |
| Duplicate Index | Company | Dupe customer number | Ensure that a customer number is only used/ assigned once or renumber the company customer number in Faces |
| The backend didn't understand the incoming query. Please contact your helpdesk. | Company | Time out in Amadeus or There is a wrong entry in some field i.e. spaces after a line in custom fileds | Save again or Amend entry and save again |
| Invalid external no.:123456 | Company | There is a special character or space in /after the customer number | Amend the customer number and save again |
| Internal error | Traveller/ Company | Special character/ space has been inserted somewhere on the profile | Remove special characters/ spaces and save again |
| Pending Reading from Profile/ Data Truncation | Traveller/ Company | This means that the profile(s) abeing imported have
| Clean up the profiles in CSX by removing special characters, spaces or reducing the AP/ RMs, saving the profile in the GDS again before getting back to Faces to save the profile again. |
| 11 Session | Traveller/ Company | OID has not yet been added to the WSAP | Contact Amadeus to add the OID to your WSAP |
| MAX NUMBER OF OCCURRENCES REACHED | Traveller | Maximum number a line/ a sequence or a command is allowed to be sent to Amadeus has been reached. This occurs when some hardcoded entries are wrongly set up as copies in the agency or company setup, i.e. PIN is set up on the traveller profile |
|
Failed: could not execute batch; SQL [insert into USERLOGIN (ACCEPTED_PRIVACY_POLICY, ACTIVE, CREATEDATE, EMAIL, FAILEDLOGINS, LANGUAGE, LASTLOGINDATE, LASTMODIFIED, LASTMODIFIEDBY, LOCKOUTDATE, PASSWD, PWDCHANGEDATE, PASSWORD_RESET_EXPIRATION, PASSWORD_RESET_TOKEN, SENT_CREDENTIALS, TOTP_RECOVERY_CODES, TOTP_SECRET, TRAVELAGENCY, USERNAME, UUID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; constraint [idx_user_loginfields]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute batch | Traveller read from GDS | Same Travellers with username exist in Faces | change the the usernames of the existing travellers in Faces and import again |
| Errors specific to version "Tenzing" | |||
| SR-DOCS cannot exceed length of 70 chars | Traveller | Due to a long name, the SR DOCs line is then too long (maximum characters allowed are 70 chars) | Only occurs if the agency is using the Tenzing version of Amadeus webservices. This is a Webservice limitation for Tenzing hat does not exist in Amadeus Cental System. To solve this error, the name has to either shortened in Faces or the SR DOCs copy command has to be removed/ deactivated in Faces. The complete SR DOCS line can be separately directly inserted in Amadeus Cental |