XTR: Calamity error 66 displayed during XYGATETR install

XTR: Calamity error 66 displayed during XYGATETR install

A XYPRO support professional can check the Installation/upgrade log for successful installation.
If everything looks fine with the installation, error 66 can be ignored.
It is helpful to send XTR_SYNTAX_CHECK and XTR_VERSION to XYPRO support for verification that the installation was successful.

If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.

    • Related Articles

    • XTR: XYGATETR command socket read error: 4106

      This error happens when a non-XTR application attempts to connect to an XTR port. An EMS message with command socket read error: 4106 will show. If you are unable to locate the solution needed or if you need additional assistance, please Click Here ...

    • XTR: Error encountered when running XTR_SYNTAX_CHECK

      Was there a recent XTR install or upgrade? The XTR_FINISH_INSTALL macro may not have been run on completion of the install/upgrade. 1. RUN $<vol>.XYGATETR.XTR INSTALL ($<vol> is the disk volume where XTR is installed) 2. XTR_FINISH_INSTALL If you are ...

    • "License is Bad" error received for XTR portion of install when using IWIZARD to install XUA using XUABIN

      IWIZARD needs a single license for two products - one for XTR and one for XUA This "double license" must be located in the distribution subvolume (P25DSDST) prior to running IWIZARD and that license must also include XTR. The license should be name ...

    • XUA: Install script execution failed with error

      Without the ?run? in-front of any macro/object execution then, TACL macro execution goes through the #pmsearchlist path for looking for the object/macro. If the #pmsearchlist does not have #defaults in it, the object/macro won?t be found. We have the ...

    • XTR: No Match Found For Task Name

      This error can be caused by a missing block of statements in the TRACL file of XTR. This problem can be resolved by reviewing your TRACL and comparing to the manual's example TRACL File found in APPENDIX B1 to find any missing blocks or by reverting ...