Troubleshoot issues in Synch Service

  • Article

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack

When a communication issue occurs, an error is returned by Commerce Data Exchange: Synch Service. You can view Synch Service messages in the following locations.

Note

Synch Service is required for Retail only in Microsoft Dynamics AX 2012 R2 and Microsoft Dynamics AX 2012 Feature Pack. In Microsoft Dynamics AX 2012 R3, this component is used only to support previous versions of Retail POS while you upgrade (N-1).

Monitoring tool

Description

Synch Service messages

View status and error messages for Synch Service in the Commerce Data Exchange: Synch Service messages form. (Click Retail > Inquiries > Commerce Data Exchange: Synch Service messages.)

To trace the history of a message, select the message, and then click View message tree to open the Commerce Data Exchange: Synch Service message tree form. In this form, you can see the origin and routing of the message.

NoteNote
You must configure an upload profile before messages are available in Microsoft Dynamics AX. Create upload profiles by using the Commerce Data Exchange: Synch Service upload options form. (Click Retail > Setup > Retail scheduler > Channel integration > Commerce Data Exchange: Synch Service upload options.)

Messages are stored in the Microsoft Dynamics AX database. To free disk space, you can periodically delete stored messages.

For more information about one of these forms, open the form, and then press F1.

Microsoft Dynamics AX Infolog

If you run a job manually in Microsoft Dynamics AX, and Microsoft Dynamics AX cannot communicate with Synch Service, an error code is displayed in the Infolog 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.

Synch Service log file

You can configure Synch Service to save error information in a log file. You can specify the location of the log file, the level of logging, and the maximum number of lines in the log file.

For information about how to configure logging for Synch Service, see Configure settings for Synch Service.

Windows event log

Depending on how logging is configured for Synch Service, you may be able to view full logs of Synch Service events in the Windows event log of the host computer.

For information about how to configure logging for Synch Service, see Configure settings for Synch Service.

Troubleshoot error codes in Synch Service

Use the information in the following table to troubleshoot common errors in Synch Service. Errors in Synch Service are typically caused by one of two general issues: an error in communication between Microsoft Dynamics AX and Synch Service, or an error in the processing of a job.

Note

The same error code can represent multiple issues. When you troubleshoot, you should consider both the documentation about the error code and the detailed error message that is displayed together with the error code.

Code

Definition

Suggested resolution

4096

Error inserting in system tables

An error occurred while Synch Service was confirming the data package.

Review the Synch Service error log for more information.

4097

Remote connection dropped

The TCP/IP connection was ended while Synch Service was forwarding a package, or the receiving instance of Synch Service was shut down during the transfer.

Restore the network connection. If the network connection is slow or overloaded, consider increasing the TCP/IP time-out for both Synch Service instances. You can adjust the TCP/IP time-out in Synch Service Settings.

4098

Canceled because of send and receive size

The registered size of the package does not match the actual size of the package. This issue is most likely caused by a transmission failure.

Resend the package by running the Retail Scheduler job again.

4099

Cannot find new packet number

Synch Service could not assign a new package number to an incoming package. Typically, this issue occurs when the message database for the receiving instance of Synch Service is configured incorrectly in Synch Service Settings.

Confirm that the message database is configured correctly, and that the Synch Service user has the required permissions.

4100

Cannot instance a socket

The operating system could not create a Windows TCP/IP socket. TCP/IP might not be installed or enabled on the computer.

Confirm that the TCP/IP protocol is installed and enabled on the computer.

4102

HopCount has exceeded its maximum value

A package cannot be transferred, because the hop counter for the package has reached the maximum that is set in Synch Service Settings.

This error can occur when a service name is incorrectly assigned to an IP address. The error can also be caused by an inconsistency between the server name for a location and the actual server name for the instance of Synch Service.

  • Verify the DNS registration of the server name or the entry for the server name in the Hosts files on all computers that are involved.

  • Confirm that the server name for the location in the Commerce Data Exchange: Synch Service profiles form matches the service name in Synch Service Settings.

8192

Error in processing request

An unhandled exception occurred when Synch Service was reading from or writing to a database. This error is typically not related to the database connection.

  • Check the event log for more information. Because this error occurred at the database level, the database has likely reported the cause of the error in the event log.

  • Check for an invalid or incorrect setup for field transfers in a subjob.

12288

An error occurred connecting to Synch Service

Microsoft Dynamics AX cannot connect to Synch Service. This error can occur in the following situations:

  • Synch Service is not running.

  • Microsoft Dynamics AX is trying to connect to a service that does not exist, or that is not associated with the correct IP address.

  • Microsoft Dynamics AX is trying to connect to Synch Service on an invalid TCP/IP port.

  • Start the Synch Service service.

  • Confirm that the service name for Synch Service is associated with an IP address. To confirm the IP address, at a command prompt, type ping <Synch Service computer name>. If the service name does not respond to a ping command, you must reconfigure your DNS server or Hosts file so that the service name is associated with the correct IP address.

  • Verify that the port numbers match in Synch Service Settings and in the Synch Service profile.

  • If IPsec is enabled, verify that it is configured correctly. Alternatively, verify that the firewall is configured correctly. For example, connect to the Synch Service port by using Telnet.

12295

Waiting for a previous package

A previous package that is part of the same JobID has not been processed successfully. Check the job status to determine whether the job is waiting, or whether there is an issue with the job.

  • Take corrective action so that the package is processed successfully.

  • Cancel the job by using one of the following methods:

    • If an upload profile has been configured and selected for Synch Service messages, select the message in the Commerce Data Exchange: Synch Service messages form, and then click Cancel.

    • Set CancelledByUser=1 in the message database.

12305

Error while sending package information

  • Retry the operation.

  • Check all connections.

12306

Error while transferring package

A connection has failed, or the network is unstable.

  • Retry the operation.

  • Check all connections.

16384

Error writing file

  • Free some space on the disk.

  • Confirm that the process has the required permissions to write to the disk.

16385

Error creating file

Synch Service cannot write to the hard disk. Possible causes include the following issues:

  • The disk is full.

  • Synch Service does not have permissions to write to the working directory.

  • The path of the working directory, as specified in Synch Service Settings, is incorrect.

  • Free some space on the disk.

  • Confirm that the process has the required permissions to write to the disk.

  • Confirm that the path of the working directory is correct.

16386

Error reading file

Synch Service was trying to read a file that does not exist.

Re-create the file by running the job again.

24577

Synch Service system error

Synch Service encountered a system error. This error code represents several issues that might occur with the service.

See the error log for more information.

24578

Synch Service communication error

Synch Service encountered a communication error. This error code represents several communication issues that might occur.

  • Retry the operation.

  • Check all connections.

  • See the error log for error codes that were reported by Windows. Typically, this error is a socket error.

24579

Synch Service job metadata processing error

An error occurred when Synch Service was preprocessing a request package.

See the error log for more information.

24580

Synch Service message database error

Synch Service cannot connect to the message database. Possible causes include the following issues:

  • An incorrect server name is specified in the connection settings for the database.

  • An incorrect database name is specified in the connection settings for the database.

  • Appropriate permissions are not granted to the database.

See the error log for more information.

If Synch Service cannot access the message database, verify the connection string to the database in the following registry setting:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Dynamics \6.0\Retail Store Connect\Servers \SERVICE_INSTANCE_NAME, key: SysConnStr

28673

Error when request handler manager is preparing/packing/unpacking request and processing temp data files

Possible causes include the following issues:

  • The package is corrupted.

  • The channel schema for the distribution location is configured incorrectly. In this case, the error message likely says “Cannot find request handler factory.”

  • Synch Service does not have permission to create the working folder or to write files to the working folder.

  • See the error log for more information.

  • Check all connections.

  • In the Distribution locations form, verify the retail channel schema for the distribution location.

  • Make sure that folder permissions have been set correctly.

  • Retry the operation.

32769

Error when request handler fails to process request

Typically, this kind of error means that data from the channel database or the Microsoft Dynamics AX database cannot be read or written. This issue can occur when the scheduler job is not configured correctly.

Because there are many possible causes for this error code, we recommend that you see the error log for the detailed error message from the database.

Troubleshoot common issues with data packages

Use the information in the following table to troubleshoot issues with data packages. To view the information that is contained in a data package, you must use Commerce Data Exchange: Synch Service Pack Viewer. For more information, see Synch Service Pack Viewer.

Issue

Solution

A package that failed blocks the processing of other packages.

When a package is not processed successfully, its blocked status can prevent other packages from being sent, even after you have resolved the cause of the error. To resume ordinary communications, in the message database, set CancelledByUser=1 for the messages that are related to the blocked package.

If Synch Service was configured to upload status messages to Microsoft Dynamics AX, you can view and cancel error messages in the Commerce Data Exchange: Synch Service messages form. (Click Retail > Inquiries > Commerce Data Exchange: Synch Service messages.)

If Synch Service was not configured to upload status messages, you must use Microsoft SQL Server Management Studio to cancel the blocking messages. On the originating computer, in SQL Server Management Studio, expand the Databases folder, click the message database, and then click New Query. In the query pane, type update dbo.IncomingMessages set CancelledByUser=1 where PackageNo='nnnn', where nnnn is the ID number of the failed package. Then click Execute.

Synch Service at the head office cannot read results for a query packet.

If a job is unsuccessful, and no records were changed in the store database, follow these steps to determine the reason for the failure.

  1. Confirm that the request from Retail Scheduler reached the head office instance of Synch Service.

  2. Confirm that the message database for the head office instance of Synch Service contains a corresponding record in the incoming messages table.

  3. Confirm that the request packet was created by Synch Service. A request packet is also referred to as an “I” file, and the file name is in the form <Synch Service service name>-<sequential number>-I.tmp. If the Keep Package Files check box was selected in Synch Service Settings, this file is in the working directory.

  4. Make sure that .NET Business Connector is installed. .NET Business Connector is required on the communications server at the head office.

  5. Verify that the entry in the incoming message table for this packet has no errors. If Synch Service cannot process a request, it does not generate a result packet, and an error occurs. A result packet is also referred to as an “R” file, and the file name is in the form <Synch Service service name>-<sequential number>-R.tmp]. This issue could be caused by a scheduler job that is not configured correctly. In this case, see the detailed message in the error log for more information.

Synch Service crashes when it processes many transactions.

The default thread time-out for Synch Service is 10800 seconds, but this value may not be sufficient when many transactions are processed. If you are processing more than 200,000 transactions, and Synch Service crashes without synchronizing the data, try increasing the thread time-out.