Troubleshoot issues in Async Server or Async Client

Applies To: Microsoft Dynamics AX 2012 R3

Use the information in this topic to troubleshoot issues with Commerce Data Exchange: Async Server or Commerce Data Exchange: Async Client.

Test connections

Use the Async Client Configuration Tool to test connections between Async Client and other components.

1. Start the Async Client Configuration Tool. By default, the executable file is located at C:\Program Files\Microsoft Dynamics AX\60\CDX\Async Client\<DatabaseName>_Package. Double-click the AsyncClientConfigurationUtility.exe file.

2. Test connections to other components, as shown in the following table.

   Async Client connection	How to verify the connection
   Async Server	On the Async Server connection tab, in the Authentication information section, click Test connection.
   Channel message database	On the Channel configuration tab, in the Channel message database section, click Test connection.
   Channel database	On the Channel configuration tab, in the Channel database section, click Test connection.

Troubleshoot connectivity issues

If connection tests for Async Client are not successful, we recommend that you verify the following information.

• Verify that the URL to Async Server is correct. Double-check the server name, web site name, port number, and protocol that are used.

• Verify that the channel database ID is correct in the Async Client configuration. The value that you set for the channel database ID must match the value that is set in the Channel database form in Microsoft Dynamics AX.

• Verify the user name and password for the connection to Async Server. The user name and password must match the values that were set in the Channel database form in Microsoft Dynamics AX.

• Run the Sync metadata process in the Retail scheduler parameters form. This process synchronizes configuration data for Commerce Data Exchange with the message database at headquarters.

• Make sure that initial data has been distributed to the channel database. In the Channel database form, click Full data sync and then select the distribution schedule that is named Full sync.

• On the location computer, verify that remote connections to Microsoft SQL Server are enabled, and that SQL Server users and permissions are set up correctly. For more information about these requirements, see Configure SQL Server for the Retail databases.

• Use ping, Telnet, or another network utility to verify that the location computer can connect to the Microsoft Dynamics AX computer at the head office. If it cannot, make sure that the firewall at headquarters is open to the required ports or programs. If the firewall is already open, work with the network administrator to correct the network configuration.

Find information about data distribution issues

If there are issues with data distribution, more information is available in the following locations.

Monitoring tool	Description
Download sessions form and Upload sessions form	View information about data distribution jobs that are in progress or have been completed. To open the Download sessions form: Click Retail > Inquiries > Commerce Data Exchange > Download sessions. To open the Upload sessions form: Click Retail > Inquiries > Commerce Data Exchange > Upload sessions. For more information about how to use these forms, see View or cancel retail data distribution sessions. Note To display complete status information in these forms, you must run the batch job that processes status messages for Commerce Data Exchange. For more information, see Process status messages for data exchange.
Download history form	View information about the jobs that were previously run for a selected distribution schedule. A run of a job is referred to as a session.
Batch job history form	If the scheduler job runs as part of a batch, you can view error messages in the Batch job history form. For more information about batch processing, see Process batch jobs and tasks.
Windows event log	Depending on how logging is configured, you may be able to view logs of events in the Windows event log of the host computer.