Execu/Tech Systems, Inc.
Knowledgebase
Search:
850-747-0581 Email Website
Contents
 
:
IndexBookmarkPrint This Article

Home > Interfaces > OTA / HTNG > OTA / HTNG Troubleshooting

    Never manually run the interface applications when the Scheduled Tasks are running! This will cause problems like duplicate reservations, missed reservations, inaccurate inventory, rates, restrictions and duplicate or missed responses to the CRS. It is also likely that the Scheduled Tasks will lock up, requiring a restart before they will work again.

  If you need to run the applications manually, please be sure to stop the Scheduled Tasks first!

Firewall Settings  

 

Resync

 

You can force a resync of all data between the PMS and CRS at any time.

 

Customers using the older style menus should still see similar menu names but the menu is presented in the center of the screen.

  • Select Manager/Setup ("Manager Menu" on some older systems.)


  • Then select Hotel Control Files Set-up ("Room, Charge, Payment Code Set-up" on some older systems.)


  • Then select Resync CRS Availability


  • On the popup message that appears, select Yes.


  • If it was successful you will see this message.


  • You might see this error. This typically means that you are attempting to resync when the resync has already been initiated.

 

If you're missing these items from your menu, you can manually initiate a resync.​

  • In the PMS software folder, delete the file "garimpav.fil"

  • Within 2 minutes, a full resync should begin.

Restart the Interface

 

Sometimes the interface stops working. Follow these steps to restart the interface and get the interface working, again.There are two conditions, described below, that are typically experienced and can be resolved by restarting one of the Scheduled Tasks.

These are the two Scheduled Tasks that perform the duties of sending and receiving messages to and from the CRS. They are described here - OTA / HTNG 2 Way Push

They can be restarted by right clicking the task and selecting 'End', WAIT 30 SECONDS, and then right click again and select 'Run'. 

 

   Any time you restart the interface you must run a resync!  


Reservations Aren't Importing 

  If reservations aren't importing, and show that they've been sent by the CRS, there may be a problem with the Scheduled Task, ETHTNG.

 

  • Check the RQFiles folder and see if there are any pending XML messages to be processed.
    The RQFiles folder is typically located in the same folder as the PMS software.



  • Open the RQfiles folder and look for any pending XML files. If there are any waiting to be processed, they will look like this.



  • IF there are XML files, you should restart ETHTNG.

  • If there are no pending XML files, check the log files to see if the messages have been processed with any errors. OTA / HTNG Logs


  • If there are no logs for the missing reservations, there could be a problem with IIS, which is required to run the web service that receives the messages from the CRS. Restart the server where IIS is installed. If the problem remains after restarting, contact Execu/Tech support so we can determine if there is a permissions problem or if settings need to be adjusted.
    *IIS is not used with The Execu/Suite CRS interface with Vertical Booking. Contact Execu/Tech and we will assist in troubleshooting. 

Inventory and Rates  and Reservation Responses not updating

 

  • If your inventory, rates, restrictions and reservation responses aren't being updated to the CRS, there may be a problem with the Scheduled Task, ETHTNG-Sender. Check the RSFiles folder to see if there are pending messages. If there are, you should restart ETHTNG-Sender. Even if there is nothing pending, it's a good idea to restart it.

  • If there are no pending messages, check the log files to see if the messages have been processed with any errors. You should also check SyncLog.txt for any errors. If you see HTTP errors, please notify Execu/Tech support because it's likely that settings need to be adjusted. For example, an HTTP error 500 probably means there is a problem with the Username, Password or HotelCode. OTA / HTNG Logs

  • Error: Unable to connect to the remote server - This means that either the CRS URL is wrong or something is preventing the interface from connecting to it. Contact your CRS vendor to verify that this URL is correct and that there are no problems on their end. Check your firewall settings to be sure nothing is blocked on your end. Firewall Settings

  • When manually running a resync or running ETHTNG-Sender you see this error:
    File error 91,02 on GARIMPTC.FIL
    COBOL error at 00026F in garimptc.cob
    This file is corrupted or missing. Refer to Set PMS Company Number at the bottom of this page OTA / HTNG Installation and Configuration

  • The resync doesn't seem to be sending rates and availability and the files GARIMPAV.FIL and GARIMPAV.TXT are very small.
    It's possible the PMS company hasn't been set.
    Refer to Set PMS Company Number at the bottom of this page OTA / HTNG Installation and Configuration

 

LoadEntity invoke failed

 

LoadEntity invoke failed

COBOL error at 0025F5 in garimptc.cob

 

This error means that a .NET assembly was unable to be loaded. The most likely cause is an old runtime that isn't compatible with the version of .NET the assembly uses. Contact Execu/Tech for a resolution.

 

Function Test

 

After the interface is configured and communication with the CRS has been established, you should perform a function test.

  1. With ETHTNG-Sender.exe running on the desktop (make sure the scheduled task is STOPPED and it isn't running anywhere else).
    1. Pause and click on the Testing tab.
    2. Check Resend All (not just changes).
    3. Set the End date to 14 days in the future.
    4. Set Message to send? to All.
    5. Click Send Sync.
    6. The PMS will be asked for an update and sync messages will be queued up to send.
      After all messages have been queued, they will begin sending. 
      Successful messages receive an ACK (acknowledged). 
      Unsuccessful messages will receive a NAK (not acknowledged), or an HTTP Error 500.
    7. If you received NAK or HTTP Error 500 responses the most common reason is incorrect Room Types and Rate Codes.
      Verify that the CRS has the correct PMS Room Types mapping.
      Verify that the ETHTNG.exe Remapping tab shows the correct rate codes.
    8. If there were mapping problems, fix them and re-run the test.
    9. Compare the PMS and CRS to verify the rates and availability for this time period match.
    10. If the test was successful, sync for the default number of days expected by the CRS. This is often 365 days.

  2. With ETHTNG.exe running on the desktop (make sure the scheduled task is STOPPED and it isn't running anywhere else)
    1. Leave ETHTNG-Sender.exe running and un-pause it. It's needed to respond to reservation messages. 
    2. Create a reservation in the CRS. 
      1. Within a few minutes the message should be retrieved, processed, and responded to.
      2. Verify that the reservation was accurately imported into the PMS.
      3. Verify that the CRS shows the reservation message was responded to.
      4. Verify that the availability in the CRS and PMS are still in sync.
    3. Modify the reservation in the CRS (Name change, room type change, etc.).
      1. Within a few minutes the message should be retrieved, processed, and responded to.
      2. Verify that the reservation change was accurately imported into the PMS.
      3. Verify that the CRS shows the reservation message was responded to.
      4. Verify that the availability in the CRS and PMS are still in sync.
    4. Cancel the reservation in the CRS.
      1. Within a few minutes the message should be retrieved, processed, and responded to.
      2. Verify that the reservation was cancelled in the PMS.
      3. Verify that the CRS shows the reservation message was responded to.
      4. Verify that the availability in the CRS and PMS are still in sync.

 





Article ID
 ota___htng_troubleshooting
Views
 4488
Last Modified
 6/3/2024 12:33 PM