OXI Message Status - Known Holidex Errors

Holidex Response Error	Direction	Module	Explanation	Resolution
ACTION INVALID FOR INN	OPERA>Ext	Reservation	The rate code might not be in Holidex CRS.	Check that the rate code is configured in Holidex CRS.
ACTION/STATUS CODE	OPERA>Ext	Reservation	The rate code might not be in Holidex CRS.	Check that the rate code is configured in Holidex CRS.
A valid country code must be entered for the address	OPERA>Ext	Enrollment	The country code conversion table in OXI is not setup properly.	Resolution is to have the Country Codes inserted that have the Alpha and Numeric equivalents needed. This is handled in the Holidex Utilities icon, which is a separate icon on your desktop. The ‘Country Codes’ button allows you to replace old values with the Alpha and Numeric values that Holidex requires for enrollment. To correct this manually for country code US: Go to OXI>Interface Configuration>Conversion Code>select Country Codes and find the US country code. There should be 3 entries: 1) US = 0001, Y for ext default and Y for OPERA default 2) US = UNITED STATES, Y for ext default and N for OPERA default 3) US = US, Y for ext default and N for OPERA default
AIB_parse->ORS- 06502:PL/SQL: numeric or value error: character to number conversion error	Ext>OPERA	Reservation resync- AIB resync response for reservation	Error is given due to characters sent instead of number for OPERA Field.	Request sent carries data: BU BP:B/74065/FILEE/12May05/10 Response carries this data and information: BH:G/BU 65/12MAY.... or BR:G/BU 65/12MAY05... and or BH:V/BU 65/12MAY0... The third position is incorrect it should reflect the value of the request's third position value. See above; 74065 is sent and the response are showing BU 65. This is incorrect. OXI will not be able to link the data correctly and the AIB screen will be unresolved and messages will fail upon download. Holidex CRS will have to correct issue. Call IHG Helpdesk to resolve issue.
Can’t initialize interface session for external property 'XYZ' with null interface ID.	OPERA>Ext	Reservation Comparison	Form issue. Package might not be compiled.	Call OPERA Support. Have to checked the OXI schema and recompile any invalid objects or packages.
CANNOT ADD DUPLICATE ROOM TYPES	OPERA>Ext	Group	Group Allotment details is sent to Holidex. Errors because the message is carrying duplication of room types.	Maker sure that there is no multiple room type mapping. Holidex is to be setup with 'one-to-one' room type mapping.
CHECK FORMAT	OPERA>Ext	Validation, Reservation, Enrollment	Holidex cannot read something in the OPERA -> Ext message due to invalid characters or unrecognized spaces.	1) Check that last name, first name contains no numbers or special characters. 2)Check that first name is sent in message, as Holidex does not accept empty first names. 3) Check that phone no starts with '+' and has no other special characters. 4) Check also for Middle Initial fields that carry more than just 1 character. Other characters that Holidex does not like: (invalid character ~!@#$%^&*()_+`=:";'<>?,./{}[]\|\ 1234567890)
CHK NBR SUBFLDS	OPERA>Ext	Reservation	AH or AB segments might be empty or have only a name.	It should not happen that an ad segment is sent blank. Try to retrigger the message in OPERA and check whether the address is correct.
COMBINE NAMES or COMBINE SIMILAR NAMES	OPERA>Ext	Reservation	Holidex does not understand two similar names in the same message.	This can be a problem if your reservation has sharers with the same last name, as Holidex will consider this as duplication of the same name. This is a known issue and has been reported to IHG.
CRS confirmation number not available for multiple segment reservations.	OPERA>Ext	Reservation	Reservation booking using specific Rate Code. Response from Holidex gives this warning and will not give CRS confirm number.	We have received the explanation for the res failure and Holidex response from IHG: The CRS rate category 'ABC' (i.e. ILCORUOT) is not available in Holidex for that room type and date. Therefore Holidex responds with such a lengthy proposal to show other rate categories that could be used instead. Resolution: The hotel needs to do one of two things: a) Go into Holidex and update the rate cat ILCORUOT to cover all desired dates and room types) b) Select one of the rate categories proposed by Holidex in the reservation instead.
Default value for conversion code AVAILABILITY_TYPE not found	Ext>OPERA	All messages	Reservation is successful or failed. Low- level warning given T type, for missing default.	This missing value can cause messages to fail. Check OXI>Interface Configuration>Interface Defaults>Others> Maximum Availability In Advance and set default values.
Default value for conversion code MAX_AVAIL_IN_ADVANCE not found	Ext>OPERA	All messages	Reservation is successful or failed. Low- level warning given T type, for missing default.	This missing value can cause messages to fail. Check OXI>Interface Configuration>Interface Defaults>Others> Maximum Availability in Advance and set default values.
DUPE CONV/GRP CODE	OPERA>Ext	Block	This indicates that Holidex already has a block with that block code for the time span and therefore rejects another new block with that block code for the same inventory week. It needs to be determined why these blocks are dupes. Usually the group was deleted and recreated for the same date.	The deletion message if done will go to the CRS and probably fail in Holidex with error (Cannot delete as active reservations found.) This means that the reservation cancellation or deletion from OPERA have not gone through to the CRS successfully. The solution to this: If necessary call OPERA support.
'E' type message 1- Post_hxMessage returned error : ERROR: 531 Unknown reason<HTML> <HEAD><TITLE>Unknown reason</TITLE></HEAD> <BODY> Unauthorized Client. [No SAI configuration for property] </BODY> </HTML> 2- ORA-01401: inserted value too large for column 3- Checked URL: http://10.173.197.12/pls/LAFIN/hx_tpi.TpiMsgServer got the error that the DAD is not configured 4- Check the URL: http://hmi.hiw.com/Holidex/SAIMessageServer checks the communication between SAI and OXI. Got error confirmed for the Unauthorized Client. [No SAI configuration for property]	Both Ways	New reservations, Enrollment, Validation	Communication problem with Holidex/FMDS	Check communications upload: Check the URL: http://10.173.197.12/pls/INNCODE/hx_tpi.tpimsgserver The PMS Post message screen shows up is okay. Check the URL: http://hmi.hiw.com/Holidex/SAIMessageServer checks the communication between SAI and OXI. Check the URL: http://hmi.hiw.com/mqsservlet/TPIDiagsPrototype shows the last successful processed message to hotel. Check Communications download: Checked URL: http://10.173.197.12.pls/INNCODE/hx_tpi.TpiMsgServer If you get the error that SAI is not configured for the property, you will also get message for the download check that the DAD is not configured. The DAD when checked is configured. Do not delete. Found that the issue was on the IHG side and the SAI and other servers may have gone down. A solution for the hotel to try: Back all the way out of their accesses to the Holidex "Reflections" CRS application and try to log back in. If they still cannot establish connection have them call Holidex Support and have them check the SAI sever for the property;.
ECHO FIELD MISSING-CF:	OPERA>Ext	Reservation	Reservation was confirmed in OPERA and has CRS confirmation number. The OXI reader for messages is off.	Call the OPERA Support to report issue.
ENTER RM DATA	OPERA>Ext	Block	Block message will not go up and details for room is empty. Holidex returns this error.	This error is received when Holidex cannot create a block as rate amounts are missing from room types. The rate code used for the block needs to be checked. Go to OXI>Interface Configuration>Interface Defaults>Block defaults and check that the default block rate code is set and has dates spanning the desired block dates. Also there are rates assigned to all room types of the hotel.
ERR ACTION/STATUS CODE	OPERA>Ext	Block	Group is not found in Holidex CRS	Resync Block to Holidex though the OXI Resync option. Go to OXI>Utilities>Resync>Block tab.
ERROR ACCOMMODATION DATE	OPERA>Ext	Reservation	Room type or rate codes are not converted. They might be null in AC segment. OXI has to raise an exception for this.	Check and correct the OXI conversion setup if missing. Be aware of case sensitivity. All values are Upper Case. Go to OXI>Interface configuration>Conversion Codes.
ERR CONV/GRP CODE	OPERA>Ext	Block	This occurs when Holidex receives an IU or GU message for a room type or even a block code that does not exist in Holidex.	The original block message from OXI with all room types and their default rates has not successfully updated the inventory in CRS and that is why Holidex does not recognize inventory changes for room types and rates now. Check that you have a default block rate code in the OXI Block defaults. This rate code must be configured for the entire inventory time span and for all room types. Once this is corrected, resend the block to Holidex.
ERR CONV/GRP CODE	OPERA>Ext	Block	Error comes when making a reservation against a block. The CRS has not received the block correctly or cutoff date is in the past, and when the block is resynced it fails. It is possible that the group name has (/) backslash or that the block code has more than a 3- characters.	1) Correct block code and then resync group. If the block is starting in future, change the block header name (remove the /) and then resync it from OXI. 2) Other invalids that Holidex does not like: (invalid character ~ ! @ # $ % ^ * ( ) _ &+ ` = : " ; ' < > ? , / { } [ ] \| \ ). 3) If block has reservations we may have to cancel/recreate it in OPERA or cancel the OPERA block and create a new block in Holidex. All active reservations in the soon to be deleted block must have block code removed and then they can be linked up to new created block, eliminating the need to cancel those reservations. 4) If the group Cutoff date is in the past. Holidex does not like dates in certain messages that are not current business date. If block is updated and cutoff date is in the past, messages will fail. Work around is to remove the cutoff date and resync the group. The cutoff date could also be moved to the current business date and resync will be successful. As of OXI version 2.0.45.13, OXI will default a past cutoff date to the end date of the block.
Error connection timed out	OPERA>Ext	Reservation Compare, 14- Day Availability and Reservation Confirmation	Request for the data gives time out message. Too many records are in the message being sent from the CRS to the OXI. Or Holidex CRS is not available.	Reservation Compare and 14-Day Availability, check the OXI>Interface Configuration>Comm Method. For OPERA to Ext SAI the Timeout fields if set around 30 seconds, increase to 120. Save this change then go to Stop/Restart the Processor. For a Reservation that does not get a confirmation number the communication to Holidex SAI interface may be off- line/down. Wait a while and it may come back. If not available for long period of time (hour), call Holidex Support to report issue. Once the Holidex SAI is back up and confirmations are being given a Resync of Reservations for the day can be done. Go to Utilities>Resync>Reservations> select Reservations without external confirmation number only.
Error: Failed to Connect to Holidex Server	OPERA>Ext	Reservation	This indicates a communication failure and Holidex does not respond.	You can either wait for some time to see if the connection is re-established or contact your Holidex Support desk.
Error From int_ProcessAllotment.ConvertToPMS ->E -1 Block end date exceeds last date of CRS inventory. OPERA API error.	Ext>OPERA	Block	New Block is sent from CRS to OPERA. End date of the block inventory exceeds the inventory available.	This should not occur, call OPERA Support to report this issue if you receive it.
Error: New Block is sent from CRS to OPERA. End date of the block inventory exceeds the inventory available.	OPERA>Ext	Block	New Block is sent from CRS to OPERA. End date of the block inventory exceeds the inventory available.	This error should not happen in Holidex CRS. Inventory should be booked.
Errors and Warnings: ProcessNewRes.: Reservation_be returns no data Elements.	OPERA>Ext	Reservation	Data was not complete in the message and failed to upload.	Check the reservation if confirmation is available from the Message Status screen. Correct the reservation and fill in all required Highlighted fields.
ERR DATE	OPERA>Ext	Block	This has to do with the fact that the block in OPERA and Holidex have different start and end dates. This happens when a date change messages is not uploaded or OPERA user has shifted block.	Do a resync of the block from OXI and also remove/change the cutoff date. Go to OXI>Utilities>Resync>Blocks.
ERR DATE NOT IN INVENTORY	OPERA>Ext	Reservation	The arrival date has a past Holidex system date.	Maximum Availability in Advance Defaults are not set or are incorrect. Correct settings in OXI>Interface Configuration>Interface Defaults>Other defaults
ERR NBR NIGHTS	OPERA>Ext	Reservation	Reservation cannot be accepted by Holidex as rate change nights are not the same as originally booked.	Issue is that the reservation has rate changes updated in the booking that do not match up to the original set of rate changes done initially. The update amount of nights has to be the same for each segment of the change as was originally done to be accepted by Holidex CRS.
ERR INVLD FOR CONV/GRP	OPERA>Ext	Block	Group Block is failed in OXI starting with the creation of the Block as NEW.	Reason is that the Holidex is not accepting the Groups as this; (Local INV bit) is not flipped on. Call IHG Helpdesk to report issue. After this is activated, then Resync Groups to the Holidex. Then do a Resync for reservations.
ERROR FORMAT- PRIORITY CHECK-IN	OPERA>Ext	Reservation	OPERA’s Time Format in Property Details must be in 24 Hour Military format.	OPERA time format in property details must be in 24 Hours Military format.
ERROR NewBkHd : ORA-01843: not a valid month	OPERA>Ext	Block	This happens when a reservation picked up expands the block dates.	The problem is that the update block header business event in this case does contain a data element that shows a different date format than what is configured in the OPERA Property details. Due to this, OXI generated an error for date conversion. This has already been fixed in OXI. If you receive this error, report it to OPERA Support.
ERR NBR ROOMS	OPERA>Ext	Reservation	Reservation booking cannot be accepted. Room inventory might not be available.	Check and Solution: 1) Check the reservation that has failed. Is the conversion of Rate Code correct in OXI conversion? Misspells can cause failure. 2) Have hotel check in the Holidex CRS side if the room type has enough inventories. User may have to use OXI utility Reservation Comparison to balance inventory. 3) Restriction could also be in place on Holidex side that causes the reservation to not be accepted.
ERR_RATE	OPERA>Ext	Reservation	Holidex does not accept rate code sent for group reservation. Rate category is not active for this hotel in Holidex.	Check the rate code setup in Holidex and add the rate code if not present for this block or property.
ERR ROOM TYPE	OPERA>Ext	Reservation	The room type does not exist in Holidex Plus.	Add the room type to Holidex CRS.
ERR ROOM TYPE FOR REQ INN’	OPERA>Ext	Block	Room Type is not setup in Holidex at all. The Room Type was added after the initial block was created.	Hotel must delete the entire block and re- create or avoid using that new room type for that specific block. This is a Holidex restriction. OXI always sends all room types that exist in PMS for a block, even if they are not allotted in the block. This allows later borrows and moves of reservations into different room types. If Holidex sends a rejection like this, it means that it did not receive the message containing all room types with default rates from OXI. Check that you have a default block rate code in the OPERA column in OXI Block defaults. This rate code must be configured for the entire inventory time span and for all room types. Once this is corrected, resend the block to Holidex.
ERR SINGLE ITM	OPERA>Ext	Reservation	NM segments in the OPERA> Ext message must be flagged to (C) as Holidex already has these names and will only accept changes that are sent with action type (C)	It seems that OXI sends new names where Holidex already has these names stored with the reservation. You can attempt to synchronize the reservation with the reservation comparison tool in OXI.
ERR SINGLE ITM	OPERA>Ext	Reservation	If the guest has a PC number in OPERA, all profile details must be sent as FG segment and no additional NM, AH, AB, PH segments must be sent.	If you encounter that OXI sends either NM, AH, AB, PH segments together with the FG segment in the same message, contact your OPERA Support desk.
Errors and Warnings: E -1 Upload to Holidex Failed : ERROR: 500 Server Error<HTML><HEAD><TITLE>Server Error</TITLE></HEAD> <BODY><H1>Server Error</H1> This server has encountered an internal error which prevents it from fulfilling your request. The most likely cause is a misconfiguration. Please ask the administrator to look for messages in the server's error log. </BODY></HTML>	OPERA>Ext	Reservations & Groups	This indicates a communication failure between the HMI and Holidex CRS. -OR- Upload messages are failed from Holidex and if you do a resync the message go.	You can either wait for some time to see if the connection is re-established or contact your Holidex Support Desk. -OR- The reason is the Comm Methods URL communication needs to be checked in OXI. Go to OXI>Interface Configuration> Comm Methods. 1. Check that the URLs are exactly the same and nothing is misspelled. 2. Stop/Restart the services if you updated the information. 3. Do a test reservation or group. If all goes up successfully then do a resync of information to balance the hotel.
Errors and Warnings: > E -1 Post_hxMessage returned error: ERROR: 540 Unknown reason<HTML> <HEAD><TITLE>Unknown reason</TITLE></HEAD> > <BODY> > Bad Response Format. [Error parsing response message from host] > </BODY> > </HTML> > E -1 Post_hxMessage returned error: ERROR: 540 Unknown reason<HTML> <HEAD><TITLE>Unknown reason</TITLE></HEAD> > <BODY> > Bad Response Format. [Error parsing response message from host] > </BODY> > </HTML>	OPERA>Ext	Reservation	"When the TPI package in Holidex application processes guest data, it gets EBA000 as a work area for 104 bytes. But sometimes if the guest data, particularly the address field, is longer than that it could corrupt the following data field which is used as a header portion for Ext> OPERA messages. This causes a parsing error. This is a Holidex error which is being worked on. "	A resolution is being worked on by Holidex development.
'E' type message 1- Post_hxMessage returned error : ERROR: 531 Unknown reason<HTML> <HEAD><TITLE>Unknown reason</TITLE></HEAD> <BODY> Unauthorized Client. [No SAI configuration for property] </BODY> </HTML> 2- ORA-01401: inserted value too large for column 3- Checked URL: http://10.173.197.12/pls/LAFIN/hx_tpi.TpiMsgServer got the error that the DAD is not configured 4- Check the URL: http://hmi.hiw.com/Holidex/SAIMessageServer checks the communication between SAI and OXI. Got error confirmed for the Unauthorized Client. [No SAI configuration for property] .	Both Ways	New Reservations, Enrollment and Validation	Communication problem with Holidex/FMDS	Check communications upload: Check the URL: http://10.173.197.12/pls/LAFIN/hx_tpi.tpimsgserver The PMS Post message screen shows up is okay. Check the URL: http://hmi.hiw.com/Holidex/SAIMessageServer checks the communication between SAI and OXI. Check the URL: http://hmi.hiw.com/mqsservlet/TPIDiagsPrototype shows the last successful processed message to hotel. Check Communications download: Checked URL: http://10.173.197.12/pls/LAFIN/hx_tpi.TpiMsgServer If you get the error that SAI is not configured for the property, you will also get message for the download check that the DAD is not configured. The DAD when checked is configured. Do not delete. Found that the issue was on the IHG side and that the SAI and other servers may have gone down. A solution for the hotel to try: Back all the way out of their accesses to the Holidex "Reflections" CRS application and try to log back in. If they still cannot establish connection have them call Holidex Support and have they check the SAI server for the property.
Error Message: "2404 the hotel mnemonic has not been transmitted/341114- 10"	Ext>OPERA	Validation, Enrollment	Users are unable to establish a connection to the LTU terminal to access the application for Priority Club for Holidex.	This is the error message that the Holidex 3270 or Reflection web access CRS application gives a user trying to enroll to PC Membership while in the Holidex CRS. Call IHG Support desk.
Error: Send Failed [HTTP][10.163.11.12][0.406][INVENTORY][Unknown Reason][535][]	OPERA> Ext	All messages	Upload messages are status of ‘NEW’ in OXI. Receiving system does not even get them.	Call IHG Helpdesk to check that SAI and TPI servers are receiving information. They could be down.
Extension of block will cause duplication of block within an inventory week. Cannot extend the block.	OPERA>Ext	Reservation	User is picking up reservation from block and gets this error. Can also happen during block res check in.1 - Inactive block with same block code is entered for the same week as the active block. Holidex does not allow multiple same block codes during the same inventory week. 2 - Due to this, the block did not go to Holidex.	1) Inactive block with same block code is entered for the same week as the active block. Holidex does not allow multiple same block codes during the same inventory week. 2) Due to this, the block did not go to Holidex. If far enough in advance the block could be completely deleted by hotel user and reentered again. If not enough in advance OPERA Support needs to dial in and update the table ALLOTMENT_HEADER.
For the inventory week (MAY/27/03, May/27/01), more than one block (A04) exists in PMS	Ext>OPERA	Group Inventory	Message downloaded and found that there is more than on group with same block code.	Interface cannot update the correct Group. Verify group information, as this could be a duplication.
FORMAT	OPERA>Ext	Reservation	Message is failed due to information within the message is incorrect or carries unacceptable characters.	1) Check the Last Name for any numeric values and remove. Check the First Name is carrying numeric and remove it. If the First Name is empty, enter an initial or full name. 2) Check the Phone number it could have non-numeric values (+ or period); remove them.
GTD INFO	OPERA>Ext	Reservation	Reservation guarantee is required in Holidex.	1)Update the reservation guarantee in OPERA so reservation will be accepted. 2) Check the reservation type conversion in OXI. Try to resend the reservation.
GUEST DATA ITEM NOT FOUND	OPERA>Ext	Reservation	Has happened earlier when PH:D and PH:A were OPERA> Ext together	Should not occur anymore in OXI Holidex versions TW9.4 and higher.
GUEST DATA ITEM NOT FOUND	OPERA>Ext	Reservation	When breaking a share from an existing reservation for records with 3 or more names, it fails in OXI. Could not find a matching record in Holidex to make the change.	It appears the message generated is combining a NM:D segment on the same line as a NM:A. This should not occur anymore, as fixed in OXI Holidex TW45.13.3.
HOTEL DOES NOT PARTICIPATE	OPERA>Ext	Reservation	Certain rate codes are linked to a program that the hotel doesn't participate within the date range of the reservations	Check your rate code conversion and the CRS rate defaults in OXI. Go to Rate Code, Interface Configuration>Conversion Codes>Rate Code. To go to defaults Interface Configuration>Interface Defaults>Reservations and check the OPERA>Ext column.
HOUSING MUST BE Y/N	OPERA>Ext	Block	Block group name has (/) backslash in the name. Causes message to be off and Holidex is reading incorrect values.	Remove the (/) from the name of the Group and resend as resync so that the block can be created in Holidex. Go to Resync, Utilities>Resync>Block.
HX Response Error : ER ER:74062/INVALID SELL ACTION CODE	Ext> OPERA	AIB- Automatic Reconciliation	Request for reconciliation using 'Reservation’ option button. Error occurs	Error was from Holidex CRS. This has been corrected.
HX Respnse Error: ERROR: 500 Server... This server has encountered an internal error which h prevents it from fulfilling your request. The most likely cause is a misconfiguration. Please ask the administrator to look for messages in the server's error log.	OPERA>Ext	Communication	This indicates a communication failure between the HMI and Holidex CRS.	You can either wait for some time to see if the connection is re-established or contact your Holidex Support Desk.
HX Respnse Error: ERROR: 530 Unknown Reason, Time out [Timeout waiting for host response]	OPERA>Ext	Communication	This indicates a communication failure between the HMI and Holidex CRS. -OR- Upload messages are failed from Holidex and if you do a resync the message go.	You can either wait for some time to see if the connection is re-established or contact your Holidex Support Desk. -OR- The reason is the Comm Methods URL communication needs to be checked in OXI. Go to OXI>Interface Configuration> Comm Methods. Check that the URLs are exactly the same and nothing is misspelled. Stop/Restart the services if you updated the information. Do a test reservation or group. If all goes up successfully then do a resync of information to balance the hotel.
HX Respnse Error: ERROR: 531 Unknown reason<HTML><HEAD><TITLE>Unknown reason</TITLE></HEAD><BODY>Unauthorized Client. [No SAI configuration for property] Or error includes: [invalid source address for property]	Both Ways	New reservations, Enrollment, Validation	Communication problem with Holidex/FMDS	1) Communication Test from OPERA to Holidex CRS Use the following URLs to test the connectivity from the OPERA property to the Holidex system: a. http://hmi.hiw.com/Holidex/SAIMessageServer or http://165.2.58.12/Holidex/SAIMessageServer b. http://hmi.hiw.com/mqsservlet/TSTMessageServer or http://165.2.58.12/mqsservlet/TSTMessageServer If you get the error that SAI is not configured for the property, you will also get message for the download check that the DAD is not configured. The DAD when checked is configured. Do not delete. Issue on the IHG side and that the SAI and other servers may have gone down. A solution for the hotel to try:Back all the way out of their accesses to the Holidex "Reflections" CRS application and try to log back in. If they still cannot establish connection have them call Holidex Support and have they check the SAI server for the property. 2) Communication Test from Holidex CRS to OPERA Use the following URL to test the connectivity from the Holidex system to the OPERA property: http://server-name/pls/DAD name/hx_tpi.TpiMsgServer Call OPERA Support if this communication is down. 3) Invalid Source address means that Holidex CRS has not set the BITS for the hotel property. Call Holidex Support to verify and activate.
HX Respnse Error: ERROR: 533, Host Path Unavailable. [No host path session available]	OPERA>Ext	Communication	The connection is interrupted and the host Holidex is not available at this time.	You can either wait for some time to see if the connection is re-established or contact your Holidex Support desk.
HX Respnse Error: ERROR: 534, Host Path Failure. [Timeout reading data from proxy]	OPERA>Ext	Communication	This indicates a communication failure and Holidex does not respond.	You can either wait for some time to see if the connection is re-established or contact your Holidex Support desk.
HX Respnse Error: ERROR: 538, Blocked Pending Output. [Message timeout waiting for TPI input mode]	OPERA>Ext	Communication	This indicates a communication failure and Holidex does not respond. This has occurred after loads of block messages were sent	You can either wait for some time to see if the connection is re-established or contact your Holidex Support desk.
HX Respnse Error: ERROR: 540 Unknown reason<HTML> <HEAD><TITLE>Unknown reason</TITLE></HEAD>> <BODY>> Bad Response Format. [Error parsing response message from host]> </BODY>> </HTML>> E -1 Post_hxMessage returned error: ERROR: 540 Unknown reason<HTML><HEAD><TITLE>Unknown reason</TITLE></HEAD>> <BODY>> Bad Response Format. [Error parsing response message from host]> </BODY>> </HTML>	OPERA>Ext	Reservation	When the TPI package in Holidex application processes guest data, it gets EBA000 as a work area for 104 bytes. But sometimes if the guest data,particularly the address field, is longer than that it could corrupt the following data field which is used as a header portion for Ext> OPERA messages. This causes a parsing error.	A resolution is being worked on by Holidex development.
IE A VALID ZIP CODE IS REQUIRED FOR THIS COUNTRY	OPERA>Ext	Enrollment	The enrollment message was sent for country Canada and had the wrong zip codes linked to the Canadian states.	Verify and correct the country/state/zip code setup in the OPERA profile.
IE BOTH PRIMARY PHONE AND PHONE TYPE MUST BE FILLED IN TOGETHER	OPERA>Ext	Enrollment	OXI has to send primary phone indicator and type in the enrollment message. This seems to be blank.	Check that the primary phone flag is selected for the phone type entry in the guest profile that you try to enroll.
IE ERR4002 ++ D.B. ADMINISTRATOR ERROR.	OPERA>Ext	Enrollment	The employee ID sent by OXI as part of each enrollment message is not recognized in Holidex	Check with Holidex Support desk what employee IDs are valid for your property.
IE LANGUAGE WRITTEN CODE MUST BE ENTERED	OPERA>Ext	Enrollment	The language code in the enrollment message is not correct.	Check your language code conversion in OXI. Go to OXI>Interface Configuration>Conversion Codes>select Language.
INN DOES NOT ACCEPT CREDIT CARD	OPERA>Ext	Reservation	Credit Card value is given error, either due to expire date or the hotel does not accept it.	Holidex either needs to be updated to not take the card if property does not take it, or property needs to add the card to their configuration.
INN RQRS ADV DEP	OPERA>Ext	Reservation	Holidex setting is that the hotel had advance deposits set for non credit card guarantee reservations.	Change the reservation to have deposit information or update the Holidex setting so that the reservations can be accepted.
INSUFFICIENT DATA	OPERA>Ext	Block	The first block with CA segment did not contain all room types and rates, which is the reason that following IU messages may be rejected with this error.	OXI should always send the initial block from PMS with a (CA:A) segment containing all room types and rates. In case the block was sent by CRS, OXI would respond with a (CA:M) containing all room types and rates. Check that you have a default block rate code in the PMS column in OXI ‘Block defaults’. This rate code must be configured for the entire inventory time span and for all room types. Once this is corrected, resend the block to Holidex.
INV CHNG-SEG PAST DATE-SELL NEW RESV	OPERA>Ext	Reservation	New Reservation is sent and rejected. Or OXI sends a change to a checked in reservation	1) Reservation goes beyond inventory availability in CRS. Check availability for future. 2) Holidex rejects a change to a reservation where the arrival date lies in the past. This error cannot be prevented at this time.
INVALID ACTION CODE	OPERA>Ext	Reservation	The rate code is not recognized by Holidex	Check your rate code conversion and CRS rate default in OXI
INVALID ACTION CODE/SP EVENT	OPERA>Ext	Reservation	Holidex does not have that rate code sent in AC segment.	Correct rate code conversion or CRS default rate code in OXI. Checks for misspelling .All values are case sensitive, use UPPER CASE.
INVALID AUTH COUNT(S)	OPERA>Ext	Block	The PMS user has changed the block status to pickup in OPERA. OXI is sending the wrong number in the ‘contract rooms’ column	This should no longer occur after OXI has been corrected. Contact your OPERA Support desk in case you encounter this error.
INVALID CC NBR	OPERA>Ext	Reservations	Reservation has invalid credit card number.	Credit card number is either incorrectly entered or is not accepted on the Holidex CRS side. Update accordingly.
INVLD CONF/CANCL NMBR	OPERA>Ext	Reservations	Confirmation number for reservation is not recognized in Holidex. Cancellation of the reservation is not recognized.	Check for duplication of the reservation in Holidex, as it is possible that the reservation was created and canceled but cancellation message did not get to OPERA. Cancellation of reservation will not work, as original booking did not go to Holidex. Check Holidex to make sure reservation by name exists.
INVALID CLUB IDENTIFIER	OPERA>Ext	Reservations	Club membership is incorrect and not accepted in Holidex CRS	Check the OXI conversion for membership types. Edit the CRS column value correctly. To go to conversion, go to OXI>Interface Configuration>conversion Codes> select Membership Type.
INVALID DEP AMOUNT or INVALID GTD/DEP IND	OPERA>Ext	Reservation	Arrival type ‘D’ in AR segment is not accepted without a deposit amount. Deposit value insufficient or Res Type Deposit was used	This is a Holidex restriction requiring that a deposit amount is sent in message if reservation type (received deposit) has been chosen and if that converts into arrival ND in the upload message. Check your reservation for the deposit amount or change the reservation type and send again. Work around: in the OXI Reservation Type conversion table, set all external system values to (I) for INN for those res types that deal with deposits in the OPERA value. Ext->OPERA default will be (N) OPERA->Ext default will be (Y).
INVALID FOR GTD	OPERA>Ext	Reservation	This happens if the reservation is sent with Arrival type TA in AR segment and the TA segment shows as follows: TA:#######	This indicates that either the Travel Agent profile linked to the reservation in PMS has no valid IATA number, or the reservation type used is converted into arrival type (TA) for upload and no TA profile is attached. Verify your TA profile contents or the reservation type and resend the reservation. Also check the reservation type conversion. To go to Reservation Type, OXI>Interface Configuration>Conversion Codes>Reservation Type.
INVALID HDX CF NBR	OPERA>Ext	Reservation	This is the Holidex response to a manufactured CRS number that was used through TPI for a reservation. If a change is then sent it either replicates a CRS number that has been used or is numerically out of sync with the Holidex system right now.	This can happen if the user has changed the upload message content manually in order to have it successfully processed. The message has to be corrected.
INVALID MEMBERSHIP	OPERA>Ext	Profile Validation	The PC or alliance code number sent is not valid	Verify the number with the guest and re- enroll if necessary
INVALID ROOM TYPE FOR ‘XX’	OPERA>Ext	Configuration	Room type in message is giving the warning.	Room type needs to be added to the OXI room type conversion table. Check also that Holidex accepts the room type. Go to OXI>Interface Configuration>Conversion Codes>Room Type.
INVALID SEQUENCE NUMBER	OPERA>Ext	Reservation	An existing reservation that was from the Global 2 import of reservations. It is modified in OPERA and sent to Holidex.	Message error for sequence of the reservation. OXI issue fix in OXI Holidex version TW45.13.2
INVALID SOURCE OF BUSINESS	OPERA>Ext	Reservation	Source Code is not in Holidex CRS.	Update the OXI source code conversion table. Go to OXI>Interface Configuration>Conversion Codes>Source code.
INVALID UPDATE CODE	OPERA>Ext	Reservation	The rate codes in OXI conversion may have been modified for testing purposes. It can also be that the rate codes you had from earlier Holidex masters are no longer viable rate codes in Holidex.	Check the current valid rate codes in Holidex and correct the OXI rate code conversion table.
INVLD	OPERA>Ext	Reservation	The TA IATA number of that message is invalid in Holidex	Validate the TA profile again in reservation or correct the IATA number and resend the reservation.
INVLD	OPERA>Ext	Resv No Show	Upload during Night Audit process, reservations that have not canceled or come in are flagged as No Show. Message is sent to Holidex to inactivate that booking.	A RES RESPONSE message should come down from Holidex confirming the inactivation of the reservation on their side. If INVLD, this can be due to the Reservation is canceled already in CRS or has been made No Show already and cannot make a change to an already Cancelled or No-Showed reservation so it fails. This would be a normal Fail message and can be ignored.
INVLD	OPERA>Ext	Block	Check for invalid characters that the Holidex CRS does not like. Message will be rejected.	1) Check the message for any Last Name with numbers in it. That will need to be removed. 2) If the First Name is missing entirely that field will need to at least have initial or full name. 3) The phone number could have non- numeric characters, like (+); these need to be removed. Other characters that Holidex does not like: (invalid character ~!@#$%^&*()_+`=:";'<>?,./{}[]\|\ 1234567890)
INVLD	OPERA>Ext	Block	Update of block inventory. Message has (GU) in the beginning of the CRS message. Check to see if the Group Rate Code is valid	1) Check the Rate Code for the Groups that are used in the OXI Group Default screen. Make sure that the Rate Code has a End Sell Date that is far enough in the future to not cause the group to fail due to the date being expired before the groups arrival. 2) Also check that there are rate amounts available for all the room types that are in this rate code. Any room type that is missing will cause message upload of that specific room type for that group to fail in the OXI Upload Message Status screen. Then when this is fixed do a resync.
INVLD	OPERA>Ext	Block	Update of block inventory. Message has 'IU' as prefix. Cause for failure is that the update is sent the day after the business date it is slotted to update for.	1) Check for past cutoff dates in the block before attempting a resync. Remove or replace the cutoff date with the current business date. Then resync the Block header and details will now upload. 2) Check that group name has no special characters. 3) Check the OXI default block rate code. Make sure that this rate code has an End Sell Date that is far enough in the future to not cause the block to fail. 4) Also check that there are rate amounts available for all the room types of the property.
INVLD	OPERA>Ext	Block, Resync Block or Update Block information	Upload of IU, inventory update message. Room Sold count is being lowered	1) heck for the processed messages before and after this failed message. Reason for fail upload message can be due to this scenario- If there is room move from KNGN to KVUN room type business events are fired to send update to Holidex for Update Block Grid on KVUN to accept the move, send Update Block Grid to decrease rooms sold on old room type and then Update Reservation message that will update group inventory. With this scenario, the update message to reduce the rooms sold in Holidex will be failed since the Holidex recognizes that existing rooms sold cannot be less that what is accounted for (reservation held) until reservation is actually updated and Holidex does the change. This failed upload message is unavoidable and can be ignored since the Update Reservation message will balance the Inventory at the end.
INVALID	OPERA>Ext	Reservation	Credit card expiration date has expired in reservation	Correct the credit card expiration date.
LAST CHAR IN NAME INVL	OPERA>Ext	Reservation, Profile Validation, Enrollment	The first name is empty or has special characters. Or Profile cannot be created if the first name is missing.	The first name can never be empty when sending data to Holidex. Correct the guest profile.
MODIFY	OPERA>Ext	Profile/Resv	New, Update of Email from guest profile is sent to Holidex but rejected.	Holidex PLUS is supposed to accept this value in v4.0.
MODIFY	OPERA>Ext	Reservation	Segment number mismatch in AC segment	Can be resolved by using the Reservation Comparison tool in OXI. Go to OXI>Inventory Balance>Reservation Compare.
MSG TOO LONG	OPERA>Ext	Reservation	The comment text in AR segment and element CC must not exceed 25 characters.	OXI should truncate the comment after the 25th character. In case you still encounter this error, truncate your reservation comment to maximum 25 characters.
NEED ACCOM SEG	OPERA>Ext	Reservation	Message sent to the Holidex CRS is rejected.	Checking the CRS AR segment of the message shows that the message is missing this section. Should not happen but indicates that there is an issue with the OXI reader. Call the OPERA Support and report this issue.
NBR NIGHTS	OPERA>Ext	Reservation	Reservation does not have the required number of nights to be accepted by Holidex CRS.	Check the restrictions in Holidex and modify reservation as required.
NBR ROOMS	OPERA>Ext	Reservation	Reservation cannot be accepted. Room inventory might not be available.	Check in Holidex CRS if the room type has enough inventory. User may have to use OXI Reservation Comparison to balance inventory.
NO ACTV ACCOM	OPERA>Ext	Reservation	CRS cannot find accommodation components. Probably segment number mismatch after a response from Holidex has not been updated successful.	Try to synchronize using the Reservation Comparison tool in OXI.
NO CONV/GRP ITEMS	OPERA>Ext	Group & reservation	Block is not accepted.	Check for the OXI block default rate code. Make sure that the rate code selected has all room types linked to it and all room types have rate amount in the Rate Code setup in OPERA.
NO ECHO FIELD FOUND	OPERA>Ext	Configuration	Room type or rate code is not converted. The message might have NULL/empty spot in =CD: segment of message being sent.	Check the message in the OXI Message Status screen. In the CD: line the room type or rate code is missing. Check that the OXI conversion codes for Room Type and Rate Code are setup correctly.
NOT ACTIVE	OPERA>Ext	All Messages	Check that the Holidex CRS has the INN code for the hotel active.	Call Holidex Support desk.
ORIGINAL START DATE INVALID	OPERA>Ext	Block	Holidex expects that the original start date in PMS block is equal to the current start date in Holidex.	If the block start dates in PMS and CRS are out of sync it is difficult to fix from the front-end. We suggest recreating the block.
ORIGINAL START DATE INVALID	OPERA>Ext	Block	Block dates shift if a reservation expands the block dates into one day earlier than before. In this case the block had originally started on the 01st April and a reservation extends it now to start on the 31st March.	The reason for this is that the business events UPDATE RATES and UPDATE BLOCK HEADER are fired by OPERA at the same time and both events have the original start date as 01st April and block start date as 31st March. OXI first sends the UPDATE RATE event as rate message to Holidex. This rate update message already contains the block header date changes, which are accepted by Holidex. Next, OXI sends the second business event in form of a block header update with the same details again. Since Holidex has already changed the dates from the rate update, it no longer accepts the old original start date that is sent in the block message again now. The message fails.
PC CK-IN NOT AVAILABLE TO GUEST	OPERA>Ext	Reservation	This indicates a problem in AR segment - Priority Check IN Field.	This is defaulted by OXI to (N). The value is stored in RESERVATION_NAME table UDFC30 column. In case you receive this error, Call OPERA Support to change the UDFC30 value to (N) and try to resend the reservation.
RATE_CODE_VALIDATION	Ext>OPERA	Reservation	Rate code is not validated by OPERA.	Rate code conversion can either be missing or misspelled. Check the OXI conversion table and make sure if there are multiple mappings for the same rate code that at least one mapping has a default OPERA>Ext and one mapping has a default Ext>OPERA.
RESTRICTED	OPERA>Ext	Reservation	Booked Reservation with a PC number and rate code. It Failed uploading to Holidex with error: 'RESTRICTED". Changed rate to $0 and it uploaded.	Contact IHG Helpdesk to see if issue is: with the SAI communication. Site might not be logged in internally as a Super User.
RESTRICTED	OPERA>Ext	Reservation, Profile Validation	More than one FG segment is sent or OXI sends profile changes in a NM segment instead of FG segment. This applies to guests with PC or SCC number. Specific room type does not have a rate built for the specific Rate Category.	Verify that guest’s membership details are still correct and valid. If the guest is a PC or SCC member, OXI should send profile changes in the FG segment only and should not send any NM, AH, AB, PH segments. This error also occurs if all membership details are correct and PMS user changes the profile in OPERA. OXI will send this as FG segment and Holidex will reject, as it does not accept changes to PC members from PMS. In this case there is nothing that can be prevent the error and user can ignore it. IHG is aware that these profile changes fail in Holidex. Check the rate code/room type combination in Holidex.
RESTRICTED DUTY CODE	OPERA>Ext	Block	The block code is numeric.	Holidex does not allow all-numeric block codes. Add the format picture in OPERA>Setup>Application Settings>Block, the OPERA block application setting called BUSINESS_BLOCK_TEMPLATE: Axx. This will ensure that only three-letter block names are used and they always start with an alpha letter.
RM TYPE NOT IN GENERAL INVENTORY	Ext>OPERA	Group	Group sent from OPERA to Holidex CRS has room types that are not recognized as inventory in Holidex.	Verify that the room types in OPERA PMS are the same 'one-to-one' values. Or, that the PMS room types are mapped 'one- to-one' rooms in Holidex CRS in the OXI Conversion Code table called 'ROOM TYPES'.
R:/NO HDX MATCH - CHECK GII CF NUMBER	OPERA>Ext	Reservation	The Global 2 reservation seems very old as can be seen on the CF: command line. IHG assumes that the reservation dated out in Holidex after a while as this was made in June 2002, and that the record was removed in Holidex.	The hotel can only cancel and rebook in OPERA in order to get the booking properly back into Holidex.
SUB MIN FLD2	OPERA>Ext	Reservation	The Last name field must have at least 2 characters. The Address1 or 2 must have at least 2 characters.	Check that the last name has at least 2 characters and that he address lines 1 and or 2 have at least 2 characters as well.
SUBFLD MAX 37	OPERA>Ext	Reservation	This is due to the length of Address line 1 exceeding 37 characters in length.	The address line should not include the name and street address all in one. Modify the address and the reservation will go up correctly.
UNA RTRV MEMBER FILE	OPERA>Ext	Profile Validation	Member number sent in FG segment is not found in Holidex.	The member number of guest has expired or is no longer valid. Check with guest that number is correct or re-enroll guest in OPERA.
UNA TO RTRV GNR	OPERA>Ext	Reservation	Holidex is unable to retrieve GNR or CRS Number sent.	Record does no longer exist in Holidex or not with the same CRS/segment number. Use reservation comparison in OXI to synchronize
UNABLE TO PROCESS	OPERA>Ext	Reservation	Segment number mismatch in AC segment.	Can be resolved by using the reservation comparison tool in OXI
UNABLE TO PROCESS	OPERA>Ext	Reservation	AR segment is sent with arrival type ‘D’ but no AH segment is sent.	If the reservation is guaranteed by deposit as indicated in the arrival type (D), Holidex expects a home address as well, which must be sent in the AH segment. If you don’t have a home address for the guest, change the reservation type into something that does not convert into arrival type (D) in this case.
UNABLE TO PROCESS	OPERA>Ext	Reservation	a “+” exist within the phone number.May also be other characters not acceptable by Holidex.	Correct the phone number or remove any special character from the reservation.
UNABLE TO PROCESS	OPERA>Ext	Block	Block reservations are not going to Holidex.	Block reservations are failing due to incorrect Reservation Type set in OXI default. Make sure there is a default for Reservation Type in Res Defaults for the OPERA>Ext column. Check to make sure Reservation Type conversion codes are all setup. Go to OXI>Interface Configuration>Interface Defaults>Reservation tab.
UNIDENTIFIABLE DATA	OPERA>Ext	Reservation	The TPI message contains characters that Holidex doesn't recognize.	Could be comments sent to Holidex containing carriage returns within the comments. Segment-Number mismatch Check for Space After First Segment in message. Ex :( RA)
UNUSED INV. RETURN DATE INVALID	OPERA>Ext	Block reservation	Inventory message update for block failed.	Return of the inventory had a past business date and cannot be processed. So the message failed. Warning message will alert you and you may ignore the message or select it REVIEWED. Once selected as Reviewed upon the next refresh of the screen the message will be hidden.
Upload to Holidex Failed : ERROR: 534 Unknown reason<HTML> <HEAD><TITLE>Unknown reason</TITLE></HEAD> <BODY> Host Path Failure.[Timeout reading data from proxy] </BODY>	OPERA> Ext	AIB- Sync- Request	Inventory resync for Blocks or Reservations has failed to upload. Host Path Failure on SAI response from OXI to Holidex side is down.	SAI connection is down. Try again later to request or if the connection stays down contact IHG Helpdesk to report issue. Also, if this happened then even normal messages going to Holidex may be failed. Check and if so, call IHG Helpdesk to resolve.
Upload communication object is null. Can't send message.	OPERA>Ext	All Messages delivered	For Holidex CRS: Communication Method for Upload has not been populated. Messages are failing in upload or have status 'NEW' and are not delivered.	Messages are being sent and the OPERA to External Communication Method has not been set when the Processor for has been turned on. When setting Communication Methods, if you have Upload and Download the population of say Download is done first. If user goes to the Upload next, the value populated already from Download is displayed. When this happens, you need to remove the value and cut/past same value or type in the value; then SAVE. Then the error will not be displayed in the OXI processor log. The messages that have failed in Upload cannot be reprocessed. Use of the Reservation Comparison for Reservations will have to be used. In the event there are other messages such as ‘Allotment’ messages then suggest using the Block Resync to balance.
ZERO AVAILABLE	OPERA>Ext	Reservation	Reservation sent up and failed.	Reservation is sent for room type that is out of inventory or oversold in Holidex. Change the reservation Room Type.
ZERO ROOM RATE IS INVALID	OPERA>Ext	Block	Holidex response to block resync created in the past. There are room types in the message that do not have a rate. Found that the main reason is that the default block rate code is not extended to cover the dates in the future for which the block was created. Invalid rate codes can be another reason.	In OPERA, extend the end sell date for the rate code header and details for all roomtypes.