All Collections
Business System Integrations
Sage X3
Errors
Sage X3 - [ERROR] Cannot connect to X3, please check your connection parameters
Sage X3 - [ERROR] Cannot connect to X3, please check your connection parameters
Micah A. Parker avatar
Written by Micah A. Parker
Updated over a week ago

Product: Sage X#

Error: Cannot connect to X3, please check your connection parameters.


Issue: When attempting to import/export to Sage X3 you receive the error: 'Cannot connect to X3, please check your connection parameters.'

Reason: Your X3 Environment is no longer accepting connections remotely

Solution - Confirm Transaction Manager Server Settings


If you've moved servers, adjusted pool aliases, or made changes to the user logins you may want to confirm these do not need updated in Transaction Manager.

Navigate: Business System β†’ (Company) β†’ Company Configuration β†’ Integration Options

Confirm: X3 Server:Port, X3 Pool Alias, X3 User Logon, X3 Password

Solution - Revalidate & Republish


If you've made changes to your Sage X3 Environment recently - often the source of being unable to connect to Sage X3 through Transaction Manager can be that your environment may need to have its windows/screens revalidated, the App Pool Restarted, or the Web Service republished.

Revalidate: Window Screens

Restart: App Pool

Republish: Web Service

Solution - Verify SOAP Pool Configuration


It's been reported that sometimes the Initialization Size and the Maximum Size on the Soap Pool can get reduced down to 0. Without numbers greater than 0 in these fields, there will be no threads dedicated to run.

Confirm: Initialization size & Maximum Size are populated with an appropriate amount.

Additional Assistance


If you continue to run into issues, you'll need to contact your VAR for assistance as TrueCommerce is unable to restore connection to your Sage X3 environment.

Our support team can only assist in showing you where the Integration Options are located in order to provide you with a way to update hose settings if need be.

rev 12/28/22

Did this answer your question?