retail store connect technical reference - … · retail store connect technical reference...

Retail Store Connect Technical Reference

Microsoft Dynamics® AX for Retail

April 2011

Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar Microsoft software, automating and streamlining financial, customer relationship and supply chain processes in a way that helps you drive business success.

U.S. and Canada Toll Free 1-888-477-7989

Worldwide +1-701-281-6500

www.microsoft.com/dynamics

This document is provided "as-is". Information and views expressed in this document, including URL and other

Internet Web site references, may change without notice. You bear the risk of using it.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection

is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You

may copy and use this document for your internal, reference purposes.

Copyright © 2011 Microsoft. All rights reserved.

Microsoft, Microsoft Dynamics, SQL Server, Windows, and the Microsoft Dynamics Logo are trademarks of the

Microsoft group of companies.

All other trademarks are property of their respective owners.

http://www.microsoft.com/dynamics

Retail Store Connect Technical Reference Table of contents i

Table of contents

Introduction ..................................................................................................................................... 1 Retail Store Connect service ......................................................................................................... 1 Retail Store Connect Settings ....................................................................................................... 1 Retail Store Connect Pack Viewer ................................................................................................ 1 Transaction Automation Client..................................................................................................... 2

Retail Store Connect Settings .......................................................................................................... 3 Open the Retail Store Connect Settings Wizard ........................................................................... 3 Register Retail Store Connect service page .................................................................................. 3 Service properties page ................................................................................................................ 4 Retail Store Connect specific properties page ............................................................................. 4 Retail Store Connect Properties page .......................................................................................... 4 Server debugging properties page ............................................................................................... 5

Retail Store Connect Pack Viewer .................................................................................................... 7 Save package files for viewing in Pack Viewer ............................................................................. 7 Convert files with Pack Viewer ..................................................................................................... 7

Advanced configuration ................................................................................................................... 8 Set up a Forwarder instance of Retail Store Connect .................................................................. 8 Run multiple instances of Retail Store Connect ........................................................................... 9

Troubleshooting ............................................................................................................................. 10 Retail Store Connect at the head office is unable to read results for a query packet ............... 10 Error codes ................................................................................................................................. 10 Error 0 – Error on sending request ............................................................................................. 11 Error 4096 – Error inserting in system tables ............................................................................. 11 Error 4097 – Remote connection dropped................................................................................. 11 Error 4098 – Canceled because of send and receive size ........................................................... 11 Error 4099 – Cannot find new packet number ........................................................................... 12 Error 4100 – Cannot instance a socket ....................................................................................... 12 Error 4102 – HopCount has exceeded its maximum value ........................................................ 12 Error 8192 – Error in processing request ................................................................................... 12 Error 12288 – An error occurred connecting to Retail Store Connect ....................................... 13 Error 12289 – The connection string was empty ....................................................................... 13 Error 12290 – Could not log in.................................................................................................... 13 Error 12291 – Connection temporarily unavailable ................................................................... 13 Error 12293 – Cannot load plugin dll .......................................................................................... 13 Error 12294 – Plugin version not supported .............................................................................. 14 Error 12295 – Waiting for a previous package ........................................................................... 14 Error 12296 – Error connecting to a database ........................................................................... 14 Error 12305 – Error while sending package information ........................................................... 14 Error 12306 – Error while transferring package ......................................................................... 14 Error 16384 – Error writing file ................................................................................................... 14 Error 16385 – Error creating file ................................................................................................. 14 Error 16386 – Error reading file .................................................................................................. 15

Retail Store Connect Technical Reference Introduction 1

Introduction Microsoft Dynamics® AX for Retail Store Connect is the integrated service that periodically sends data between the head office and stores and their POS terminals. Communications via Retail Store Connect are managed through locations and the Retail Scheduler in Microsoft Dynamics AX for Retail Headquarters.

Retail Store Connect aggregates data into as few packages as possible, thus minimizing the amount of data transmitted over the network. Retail Store Connect multicasts these packages, so that many recipients can receive data at the same time, such as price changes to some or all of the stores.

Retail Store Connect runs as a service and listens for incoming requests or packages. If Retail Store Connect receives a read instruction, it connects to the source database, reads data, and stores the data in a package. (Note that all data transfer requests – sending data to the store or uploading POS sales transactions – are initiated by Retail Scheduler, while Retail Store Connect is only the data transfer mechanism.)

The package can contain data from more than one database table. After the requested data has been read, what happens next depends on the configuration of the Retail Store Connect instances in the organization.

In a basic configuration, as described in "Deploy Retail Store Connect" in the Deployment and Installation Guide, Retail Store Connect at the head office takes data from Microsoft Dynamics AX, creates the data package, and sends it to the store. Retail Store Connect at the store then inserts the data in the appropriate database.

In a Forwarder configuration, as described in Advanced configuration later in this guide, Retail Store Connect forwards the package to another instance of Retail Store Connect. The receiving instance of Retail Store Connect writes the contents of the package into one or more destination databases, according to instructions in the package. The additional instance of Retail Store Connect relieves some of the burden on the first instance, resulting in better performance and scalability.

You can also distribute the communication load at the head office by running multiple head-office instances of Retail Store Connect. For more information about this configuration option, see Advanced configuration later in this guide.

Retail Store Connect service Retail Store Connect (DBServer.exe) is the server feature. It runs as a service on the host computer and handles requests to access different database systems, both Retail POS databases and Application Object Server (AOS).

Retail Store Connect Settings Retail Store Connect Settings (DBServerUtil.exe) is the configuration utility for Retail Store Connect. It launches the Retail Store Connect Settings Wizard, where you can enter information to configure Retail Store Connect instances.

Retail Store Connect Pack Viewer Pack Viewer (DDPackView.exe) is a tool that helps you to examine the data that is included in the packages that Retail Store Connect sends and receives.

Retail Store Connect Technical Reference Introduction 2

Transaction Automation Client The Transaction Automation Client, TransAutomClient.dll, is an OLE COM feature that is included in the Retail Store Connect installation package. It manages communication between Microsoft Dynamics® AX 2009 and the Retail Store Connect service.

Note

TransAutomClient.dll is a prerequisite for Retail Headquarters. This means that Retail Store Connect must be installed on all instances of Application Object Server and on each client computer, even if you do not intend to use those particular instances of Retail Store Connect.

Retail Store Connect Technical Reference Retail Store Connect Settings 3

Retail Store Connect Settings Use Retail Store Connect Settings to manage the Retail Store Connect service. The settings available in the Retail Store Connect Settings Wizard are described in this section.

Open the Retail Store Connect Settings Wizard Click Start, click Programs or All Programs, click Microsoft Dynamics AX 2009, click Retail

Store Connect, and then click Retail Store Connect Settings. (Requires administrator privileges.)

Register Retail Store Connect service page Use this page of the wizard to initiate the Retail Store Connect service.

Server Name – The name of the Retail Store Connect service.

Add – Adds the Retail Store Connect service to the server in the Server Name box and creates the message database.

Remove – Removes the Retail Store Connect service from the server that is selected in the All Servers box.

All Servers – A list of all instances of the Retail Store Connect service on this computer.

Start – Starts the service on the server that is selected in the All Servers box.

Stop – Stops the service on the server that is selected in the All Servers box.

MS SQL Server – Opens the Microsoft SQL Server Plugin dialog box.

If you anticipate transferring large amounts of data, increase the SQL command timeout:

o Click MS SQL Server, and then in the Command Timeout field, type a new time in seconds.

The time you specify depends on the system configuration and the amount of data being transferred. In extreme cases (such as 1 million items), the timeout may need to be set to the equivalent of 1-2 days.

Note

If a job fails with this error, "IDispatch error #3121: Query timeout expired," temporarily set the command timeout to 0 (zero).

Client Controls – Opens the Retail Store Connect Client Settings dialog box for configuring TransAutomClient.

Packet Viewer – Opens the Retail Store Connect Pack Viewer.

View license agreement – Opens the Retail Store Connect license terms.

Important

If you are running more than one service on one server, select the service that you want to configure before you click Next. The remaining pages of the wizard apply to the selected service.


Service properties page Use this page of the wizard to configure the selected service.

Server name – The service instance that you are configuring.

Packet Owner – The server where packages originate. This setting is only available if 2nd Stage Retail Store Connect is selected in the Server Mode box.

Server Mode – The mode that this instance of Retail Store Connect is running under. Select Retail Store Connect if this instance is a primary instance. Select 2nd Stage Retail Store Connect if this instance is a Forwarder instance. For more information about Forwarder, see Advanced configuration later in this guide.

Server Port – The listening port for Retail Store Connect. This setting is not available for a Forwarder instance because in that case the service only forwards packages.

Off – Turns off the server listening port (not recommended).

Telnet Port – The port used by the Retail Store Connect Telnet interface. With this feature, you can use Telnet to monitor the status of Retail Store Connect.

Note

o If you plan to run more than one instance of the service on the same computer, you must change the port values so that they do not conflict with other services.

o If you also run a Telnet server on the computer, assign the Retail Store Connect Telnet interface to another port to avoid conflicts.

Retail Store Connect specific properties page Use this page of the wizard to configure the Retail Store Connect connection and how incoming and outgoing messages are handled.

Server name – The server that you are configuring.

Working Directory – The path to the folder where Retail Store Connect stores temporary files and, if configured to do so, package files. To change this path, click Browse.

Days Messages Exist – The number of days processed incoming or outgoing messages are kept. If you type 0 in this box, the messages will not be deleted.

Timer Interval – The interval at which Retail Store Connect checks for packages that must be reprocessed due to communication errors.

Limit Job Process (cnt) – The maximum number of job records Retail Store Connect processes per connection. The number should be set low when the average package size is high and set higher when the average package size is low. To disable the feature (not recommended), type 0.

This feature enables Retail Store Connect to continue processing even when a heavy load would typically cause it to stop responding. Also, with this feature on, if the first job record in the batch has an error, the rest of the packages are skipped for the run.

Retail Store Connect Properties page Use this page of the wizard to configure how connections are handled.



Hold Connections – The number of connections to the source database that Retail Store Connect should reserve.

Idle Conn. Time – The number of idle minutes before the reserved connections time out and are released.

Thread Timeout – The number of seconds before threads used in connections to remote locations time out.

Max. Forw. Threads – The maximum number of threads that can be used when Retail Store Connect is in Forwarder mode.

Max. Hop Counter – The maximum number of transfers, per package, between instances of Retail Store Connect. This prevents endless loops if the Retail Store Connect instances are not configured properly.

Socket Timeout – The number of seconds Retail Store Connect waits for the network to finish a particular send or receive operation. To prevent Retail Store Connect from shutting down merely because it is waiting for the network, set this value lower than the value in the Thread Timeout box.

Forw. Attempts – The maximum number of attempts that Retail Store Connect makes to forward a packet. This setting only works on a Forwarder instance.

Use Processor – The CPU that the service should run on. Select Any if you want the operating system to allocate a processor based on need.

Disable IPsec – Select this check box to bypass the IPSec requirements of Retail Store Connect. For more information, see "Configure or bypass IPSec" in "Deploy Retail POS" in the Deployment and Installation Guide.

Note

If the Disable IPsec check box is selected for a location in Retail Scheduler, then the Disable IPsec check box in Retail Store Connect Settings should be selected for all instances of Retail Store Connect involved in the communication with that location.

Server debugging properties page Use this page of the wizard to configure what information is logged for each package and how log files are handled.


Keep Package Files – When selected, Retail Store Connect does not delete the temporary package files in the working directory. Do not leave this feature enabled for long because it could cause you to run out of disk space and prevent Retail Store Connect from operating correctly.

Exception Dump – When selected, a memory dump file is created if Retail Store Connect stops working suddenly.

Log/Dump Dir – The folder where log files are saved. Confirm that the folder that you specify actually exists.

Log Mode – When selected, Retail Store Connect operations are logged as specified by the Log Level settings.

Write to Windows event log – When selected, Retail Store Connect will write the logging data to the Windows event log.


Max Lines / Logfile – The maximum number of lines in each log file. Retail Store Connect creates three log files, rotating to the next log file when the maximum number of lines has been reached. On startup, Retail Store Connect makes a copy of the old log files by appending .old to their names. This means that, if the service has been set to automatically restart on failure, the failure appears in the old log files.

Log Level – The amount of error logging that will take place. This number is calculated automatically, based on the logging options that are selected. Generally, Error logging and Main logging are sufficient, but greater detail might be helpful in some cases.

o Error – When selected, all errors reported from Retail Store Connect are logged.

o Main – When selected, the main operations in Retail Store Connect are logged.

o Actions – When selected, detailed information about operations in Retail Store Connect is logged.

o Detail – When selected, very detailed information about operations in Retail Store connect is logged.

o Functions – When selected, highly detailed and technical information about operations in Retail Store Connect is logged. For programmer use only.

Important

Logging as specified in the Log Level settings can only take place if the Log Mode check box is selected.

Retail Store Connect Technical Reference Retail Store Connect Pack Viewer 7

Retail Store Connect Pack Viewer Retail Store Connect Pack Viewer is a tool that helps you to examine the data that is included in the packages that Retail Store Connect sends and receives. Each package contains the database query being used; the data to be inserted, updated, or deleted; or both the query and the data. Pack Viewer converts the package file from binary format into a file that you can open in Notepad or another text editor.

Package files are only available for viewing if you specify in Retail Store Connect Settings that they should be saved. While you can, if you want, save all packages as a message archive, doing so can consume disk space quickly. Typically, you will only save packages and use Pack Viewer as a troubleshooting measure, such as when you are experiencing a synchronization issue or a replication issue.

Save package files for viewing in Pack Viewer 1. Run Retail Store Connect Settings as an administrator, and then select the appropriate

instance of Retail Store Connect.

2. Click Next until you reach the Retail Store Connect specific properties page.

3. In the Working Directory box, type or browse to the folder where you want to save the packages.

4. Click Next until you reach the Server debugging properties page.

5. Select the Keep Package Files check box, and then click Finish.

Convert files with Pack Viewer 1. Click Start, click Programs or All Programs, click Microsoft Dynamics AX 2009, click Retail

Store Connect, and then click Retail Store Connect Pack Viewer.

2. In the File to convert box, type or browse to the path and name of the file that you want to convert.

3. In the Destination file box, verify the path and file name for the XML file that you want to create.

4. If you want the destination folder to open in Windows® Explorer when the conversion is complete, select the Open Folder check box.

5. Click Convert.

6. In Notepad or another text editor, open the destination file.

Retail Store Connect Technical Reference Advanced configuration 8

Advanced configuration Typically, there is one instance of Retail Store Connect at each store and one at the head office. For information about typical deployment of Retail Store Connect, see the Deployment and Installation Guide.

In this section, we discuss some alternative deployment options.

Set up a Forwarder instance of Retail Store Connect Forwarder is a mode that Retail Store Connect can operate in. It is used in a second instance of Retail Store Connect at the head office to stage packages sent from the first instance of Retail Store Connect. This balances the load and keeps Retail Store Connect running optimally. Forwarder is also known as Second Stage Retail Store Connect.

To use the Forwarder mode in Retail Store Connect, you must run two instances of Retail Store Connect at the head office, one as the primary instance and the other as the secondary instance. You can set up the Forwarder on a separate computer, but confirm that the message database where the incoming and outgoing message tables are stored is accessible from there.

The Forwarder instance only handles communication in one direction, from the primary instance of Retail Store Connect to the store locations.

The name that you assign to the forwarder is the name that you use in the Database profiles form to indicate which Forwarder should handle a particular location. The name should also be added to the DNS or Hosts files.

1. Click Retail scheduler > Setup > Store integration > Database profiles.

2. In the Database profiles form for any store or terminal location, specify the distribution server by using the following format:

<Forwarder computer>;<receiver computer>.

Forwarder sends packages to this location.

3. When you configure the Retail Store Connect service on the Forwarder computer, enter the following settings in the Retail Store Connect Settings Wizard:

o On the Service properties page, specify the primary Retail Store Connect server in the Packet Owner box, and then select 2nd stage Retail Store Connect in the Server Mode box.

o On the Retail Store Connect specific properties page, specify the database server and name for the primary instance, and in the Working Directory box, specify the same working directory that is used by the primary instance.

Note

If the primary and forwarder instances of Retail Store Connect are on different computers, type the network path in the Working Directory box.

4. Confirm that the user that the Retail Store Connect service is running as has complete access to the shared Data folder and its contents.

Retail Store Connect Technical Reference Advanced configuration 9

Run multiple instances of Retail Store Connect Instead of using a Forwarder instance, you can run additional primary instances of Retail Store Connect at the head office. First, install and configure the new instance of Retail Store Connect, as described in the Deployment and Installation Guide. When you configure the new instance, use a different port number so that there is no conflict between instances.

The recommended configuration is one instance of Retail Store Connect to send data and another instance to receive data from the stores.

Next, because you can specify only one Retail Store Connect instance per location, set up an additional distribution location for the head office and set that location to use the new instance. This process is described in the following procedure.

1. Create a new location by using the Distribution Location form (Retail scheduler > Common Forms > Distribution Locations > New). Give this location a unique name, such as HQ2.

2. Create an AOS profile and a new Retail Store Connect profile, assign the Retail Store Connect profile to the AOS profile, and then assign the AOS profile to the distribution location created above.

3. Click Functions, and then click Test connection.

4. Open a job. For example, if you want to use the new location for exchanging data with Terminal 0001, open P-Term001.

5. On the General tab, specify the new location as the To Location.

6. Save the job. When you run this job, Retail Scheduler communicates to the store instance of Retail Store Connect that the receiving server is the new head-office location.

Retail Store Connect Technical Reference Troubleshooting 10

Troubleshooting The topics in this section provide information about Retail Store Connect communication issues that may arise. Additional troubleshooting instructions can be found in the following places in other Microsoft Dynamics AX for Retail documents.

For information about troubleshooting location connections, see "Set up locations and connection strings" in "Complete the Retail Headquarters installation" in the Deployment and Installation Guide.

For information about troubleshooting jobs in Retail Scheduler, see the Retail Scheduler Technical Reference.

Retail Store Connect at the head office is unable to read results for a query packet If a job does not succeed and no records are affected in the Retail POS database, perform the following steps to determine the reason for the failure.

1. Confirm that the request from Retail Scheduler reached the head office instance of Retail Store Connect.

2. Confirm that the request packet, also referred to as “I” file (<Retail Store Connect service name>-<sequential number>-I.tmp), was created by Retail Store Connect. This file will be in the work folder if the Keep Package Files check box was selected in Retail Store Connect Settings.

3. Verify that the entry in the incoming message table for this packet has no errors. If there is an error, it could be related to not being able to process the request, meaning no result packet, also referred to as “R” file (<Retail Store Connect service name>-<sequential number>-R.tmp ), was generated. The reason for this could be is that .NET Business Connector is not configured correctly. Run Setup for Microsoft Dynamics AX 2009 and install only .NET Business Connector. At the completion of this installation, details about the AOS instance are supplied. Enter the correct information, and then restart the Retail Store Connect computer.

.NET Business Connector is required on the head-office communications server and on each Microsoft Dynamics AX client computer.

Error codes When a communication issue occurs, an error is returned by Retail Store Connect. You can view Retail Store Connect errors in the following two places in Retail Headquarters:

When testing the connection for a distribution location, in the Infolog dialog box.

For more information about testing location connections, see "Set up locations and connection strings" in "Complete the Retail Headquarters installation" in the Deployment and Installation Guide.

In the Scheduler job form in Retail Scheduler.

Errors can also be found in the message database for each instance of Retail Store Connect.


The errors that are returned by Retail Store Connect are listed in this section, together with the probable cause of the error and suggestions for resolving it.

Troubleshooting tip

When a package is not processed successfully, its blocked status can keep other packages from being sent, even after you have resolved the cause of the error. To resume normal communications, remove the messages related to the blocked package from the message database. On the originating computer, in Microsoft® SQL Server® Management Studio, expand the Databases folder, click the message database, and then click New Query. In the query pane, type delete from dbo.IncomingMessages where PackageNo='nnnn' (where nnnn is the ID number of the failed package), and then click Execute. Any associated messages in the OutgoingMessages table will also be deleted.

If Retail Store Connect was configured to upload status messages to Microsoft Dynamics AX, the error messages can be viewed in Microsoft Dynamics AX for Retail (Retail scheduler > Periodic > Retail Store Connect messages).

Note that messages with errors can be canceled to unblock other data packages.

Error 0 – Error on sending request The distribution server for the location has not been specified in Retail Scheduler.

Possible resolution

Modify the location by specifying the distribution server for the location (Retail scheduler > Common forms > Locations).

Error 4096 – Error inserting in system tables Retail Store Connect cannot write into the incoming or outgoing message tables. The tables might be missing, the user that the service is running as might not have read and write permissions on the message database, or required fields in the tables could be wrong or missing.

Possible resolutions

Assign db_datareader and db_datawriter permissions to the SQL login for the user that the Retail Store Connect service runs as.

Error 4097 – Remote connection dropped The TCP/IP connection was terminated while Retail Store Connect was forwarding a package, or the receiving Retail Store Connect instance was shut down during the transfer.

Possible resolution

Restore the network connection. If the network connection is slow or overloaded, consider increasing the TCP/IP timeout for both Retail Store Connect instances. This is done in Retail Store Connect Settings.

Error 4098 – Canceled because of send and receive size The registered size of the package does not match the actual size of the package. This is most likely caused by a transmission failure.


Possible resolution

Resend the package by running the Retail Scheduler job again.

Error 4099 – Cannot find new packet number Retail Store Connect could not assign a new package number to an incoming package. This is usually caused by an incorrect message database configuration in Retail Store Connect Settings for the receiving instance of Retail Store Connect.

Possible resolution

Confirm that the message database is configured correctly and the Retail Store Connect user has the required privileges.

Error 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.

Possible resolution

Confirm that the TCP/IP protocol is installed and enabled on the computer. For more information about enabling TCP/IP, see "Enable remote connections in SQL Server and start the server" in "Deploy Microsoft SQL Server" in the Deployment and Installation Guide.

Error 4102 – HopCount has exceeded its maximum value A package cannot be transferred because the hop counter for the package has reached the maximum set in Retail Store Connect Settings.

This error can occur when a service name is incorrectly assigned to an IP address. It can also be caused by an inconsistency between the distribution server name for a location and the actual server name for the instance of Retail Store Connect.


Verify the DNS registration of the server name or its entry in the Hosts files on all computers involved.

Confirm that the distribution server name for the location (Retail scheduler > Setup > Store integration > Retail Store Connect profiles) matches the one in Retail Store Connect Settings.

Error 8192 – Error in processing request An unhandled exception has occurred while reading 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 happened on the database level, it is likely that the database has reported the cause of the error in the Event Log.

Check for invalid or incorrect field transfer setup in a subjob.


Error 12288 – An error occurred connecting to Retail Store Connect The Data Client component of Microsoft Dynamics AX 2009 cannot connect to Retail Store Connect. This error occurs when the Retail Store Connect service is not running, when the Data Client is trying to connect to a service that does not exist or does not have a correct IP address associated with it, or when the Data Client is trying to connect to Retail Store Connect on an invalid TCP/IP port.


Start the Retail Store Connect service.

Confirm that the Retail Store Connect service name has an IP address associated with it. This can be checked from the command prompt by typing ping <Retail Store Connect 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 Retail Store Connect Settings and in the Retail Store Connect profile.

Verify that IPsec (if enabled) or the firewall is configured correctly. One way to verify this is to connect to the Retail Store Connect port using telnet.

Error 12289 – The connection string was empty The connection string for the location has not been provided.

Possible resolution

In Retail Scheduler, verify that the database profile is configured correctly.

Error 12290 – Could not log in Retail Store Connect does not have the necessary permissions to log on to the specified company.

Possible resolution

Grant access to the Microsoft Dynamics AX user that is used by Retail Store Connect.

Error 12291 – Connection temporarily unavailable All sessions (servers) that Retail Store Connect is allowed to use are unavailable.

Possible resolution

Wait until Retail Store Connect has released one of the sessions that it is using, or assign more sessions to Retail Store Connect in Retail Store Connect Settings.

Error 12293 – Cannot load plugin dll In most cases when this error occurs, the plugin has been registered and the configuration is correct, but the path to the plugin .dll file is invalid or the .dll file is missing.

Possible resolution

Uninstall and reinstall the plugin to correct the registry setting.


Remove the Retail Store Connect server and then add it again.

Error 12294 – Plugin version not supported This version of the plugin cannot be used with this version of Retail Store Connect. In most cases, the plugin requires a newer version of Retail Store Connect.


Upgrade Retail Store Connect to the same version as the plugin.

Install the version of the plugin that matches the version of Retail Store Connect.

Error 12295 – Waiting for a previous package A previous package belonging to the same JobID has not been processed successfully. Check the job status to determine if the job is waiting or if there is a problem with the job.


Take corrective action so that the package is processed successfully.

Cancel the job.

Error 12296 – Error connecting to a database Retail Store Connect cannot connect to the database.


If the error occurs when Retail Store Connect is trying to generate a package, the connection string for the source database is probably incorrect. Correct the database or AOS profile configuration, and then test the connection. If possible, test the connection on the same computer that is running Retail Store Connect to confirm that all hosts and services are configured correctly.

Error 12305 – Error while sending package information

Error 12306 – Error while transferring package A connection has failed, or the network is unstable.


Retry the operation.

Check all connections.

Error 16384 – Error writing file

Error 16385 – Error creating file Retail Store Connect cannot write to the hard disk. The disk might be full, Retail Store Connect might not have permissions to write to the working directory, or the path to the working directory (as specified in Retail Store Connect Settings) might be incorrect.


Free some space on the disk.


Confirm that the process has the necessary permissions to write to the disk.

Confirm that the path to the working directory is correct.

Error 16386 – Error reading file Retail Store Connect was trying to read a file that does not exist.

Possible resolution

Re-create the file by running the job again.

retail store connect technical reference - … · retail store connect technical reference...

Documents