Dynamics Ax 2009 Retail Error Messages & Possible resolutions

Error Code	Title	Error Description	Possible Resolution
0	Error on sending   request	The distribution   server for the location has not been specified in Retail Scheduler.	Modify the location   by specifying the distribution server for the location (Retail scheduler >   Common forms > Locations).
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.	Assign   db_datareader and db_datawriter permissions to the SQL login for the user   that the Retail Store Connect service runs as.
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.	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.
4098	Cancelled 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.	Resend the package   by running the Retail Scheduler job again.
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.	Confirm that the   message database is configured correctly and the Retail Store Connect user   has the required privileges.
4100	Cannot instance a   scoket	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. 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.
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.
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.
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.
12289	The connection   string was empty	The connection   string for the location has not been provided.	In Retail   Scheduler, verify that the database profile is configured correctly.
12290	Could not log in	Retail Store   Connect does not have the necessary permissions to log on to the specified   company.	Grant access to the   Microsoft Dynamics AX user that is used by Retail Store Connect.
12291	Connection   temporarily unavailable	All sessions   (servers) that Retail Store Connect is allowed to use are unavailable.	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.
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.	Uninstall and reinstall the plugin to correct the registry   setting.   Remove the Retail Store Connect server and then add it again.
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.
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.
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.
12305	Error while sending   package information	A connection has   failed, or the network is unstable.	Retry the operation.   Check all connections.
12306	Error while   transfering package	A connection has   failed, or the network is unstable.	Retry the operation.   Check all connections.
16384	Error writing 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.
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.
16386	Error reading file	Retail Store   Connect was trying to read a file that does not exist.	Re-create the file   by running the job again.