Troubleshooting XAPI Errors

About XAPI errors

XAPI errors relate to problems connecting to an external Sage 300 database. They can therefore occur with any multi-database product, including:

Inter-Entity Transactions (Loan Account entry automation)
Inter-Entity Transactions (G/L Triggers)
Inter-Entity Transactions (Cash Management)
Inter-Entity AP/AR Trade
Inter-Entity OE/PO Trade

Common XAPI errors and resolutions

Error Message	Resolution
Unable to open XAPI session to Organisation XXXXXX – no available LanPak	Wait for a LanPak to become available before re-processing.
Unable to open XAPI session to Organisation XXXXXX – no available IAP	Deselect “This workstation uses IAPs for external applications” on all workstations. Refer to Turn off IAP Users.
Unable to open XAPI session to Organisation XXXXXX – bad User ID or bad password	Correct the User ID and/or Password for the target company in the IET setup screen. Use: IET Entity Database Mappings for IY Transactions Trade Organisation Setup for IY Trade Tip: In some cases, for example after an upgrade, you may need to delete the existing entries and enter them again.
Unable to open XAPI session to ORGANISATION XXXXXX – cannot create session	Ensure the Database Setup ORGID matches the ORGID in the appropriate IET Setup screen: (IY Txns) IET Entity Database Mappings (IY Trade) Trade Organisation Setup

Re-Processing Error Transactions

After resolving the cause of the error, you should re-process the error transactions using the appropriate Periodic Processing function.

For more info, refer to Introduction to Inter-Entity Errors.

Turn off IAP Users

Using IAP on the workstation is the most frequent reason for receiving the XAPI error message.

We therefore recommend that the setting “this workstation uses IAPs for external applications” must be turned off on all workstations and also on the server (if anyone RDPs to the server and processes transactions on the server).

Note: If users log on through Terminal Server, you need to deselect the setting for each user because this setting is stored in the registry per user per server.

Note: With the installation of new versions of Sage 300, and sometimes with new product updates, this switch can revert back to the default 'on' status.