XMA: Error compiling CNVRTIP when upgrading to XMA 2.41

XMA: Error compiling CNVRTIP when upgrading to XMA 2.41


Purging CNVRTIP from the XYGATEMA subvol and running XMA_MANAGER again will allow the upgrade to proceed as expected.
 
TACL> VOLUME <XMA INSTALLATION VOLUME/SUBVOLUME>
TACL> XMA INSTALL
TACL> XMA_VOLUME
TACL> FUP PURGE CNVRTIP
TACL> XMA_MANAGER

        
Note: If the following error is observed when re-running XMA_MANAGER during the upgrade, it can be ignored:
 Moving PATHMAIN file to $<vol>. <subvol> ... ERROR - $<vol>.<subvol>.PATHMAIN: ERR 11 *ABEND*


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

    • XMA: Error 73

      This is a known issue that has been addressed in our current XMA Version 2.65. We therefore recommend upgrading to XMA 2.65 in order to address this error. Softdoc entry for this issue: * XMA-1329 Addresses a latency issue when retrieving messages ...

    • XMA: XMA_MANAGER macro fails with [Check_SQLCompileNeeded] error

      The XMA SQL database needs to be recompiled for this error to be resolved. 1) stop XMA XMA_PWSTOP 2) Update the database statistics and re SQLCOMPILE all the XMA programs XMA_SQLCOMPALL 3) Start XMA XMA_PWCOOL If you are unable to locate the solution ...

    • XMA: SLSENDER fails to start after upgrading to Merged Audit 2.65

      There is a known issue where SLSENDER will not start after upgrading to XMA 2.65. If the customer cannot start SLSENDER after upgrading, the post upgrade steps below can be used. If we know a customer will be upgrading to XMA 2.65, pre-upgrade steps ...

    • XMA: The SQLXPress mover fails with error 48 (security Violation).

      Start SQLEXpress with the same user id that started XMA, or re-secure the object shown in the error message for access by the user id that started XMA. If this article did not provide a solution, please open a case with our support team by sending an ...

    • XMA: SLSENDER - Steps to follow for SLSENDER When Upgrading to XMA 2.65

      The upgrade to XMA 2.65 makes changes to the SYSLOGQ table. Consequentially, this could cause fatal errors for SLSENDER when it it initially started following the upgrade. This is due to outstanding TMF transactions that remains until they are ...