Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You cannot run a job to transfer data by using Store Connect when different date formats are used in Microsoft Dynamics AX 2012 Retail

You cannot run a job to transfer data by using Store Connect when different date formats are used in Microsoft Dynamics AX 2012 Retail

View products that this article applies to.

This article applies to Microsoft Dynamics AX for all regions.

↑ Back to the top

Symptoms

Consider the following scenario in Microsoft Dynamics AX 2012 Retail:
  • One computer has the head-office side Store Connect component installed.
  • Another computer has the store side Store Connect component installed.
  • Different date formats are set on the two computers.
  • You run a job to transfer some data from the head-office side to the store side.
In this scenario, the job fails. Additionally, you receive the following error message:
System.FormatException: String was not recognized as a valid DateTime.

↑ Back to the top

Resolution

To resolve this problem, you must follow these steps after you apply this hotfix:

Note You must follow these steps for each store that uses a date format which differs from the date format on the head-office side.
  1. On the store side, check the locale settings for the store, and then locate the ISO code for the locale according to the List of ISO country and region codes page.
    Note You do not have to update the store instance of Store Connect.
  2. On the head-office side, set up a new instance of Store Connect.
  3. For the new instance, add the ForceLocale parameter to the SCAXRequestHandler node in the "Store Connect configuration" file (DBServer.exe.config) as follows:
    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
      <!-- NOTE: "configSections" must be the first child of "configuration". Do not move around. -->
      <configSections>
    ...
      <!-- Config settings for AX/SQL request handler bundled with this version of Store Connect. Hot modification is supported: they can be changed and will take effect without restarting Store Connect service -->
     <SCAXRequestHandler ReadByJoinThreshold="100" ForceLocale=”<ISO Code>” />
      <SCSQLRequestHandler SqlCommandTimeout="1200" />
    </configuration>
    Note The <ISO Code> placeholder represents the ISO code that you located in step 1.
  4. Set up a new Store Connect profile for the new instance.
  5. Set up a new AOS profile for the locale and select the Store Connect profile that was generated in step 4.
  6. Start the Store Connect service for the new instance, if it is not running.

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:
https://mbs.microsoft.com/support/newstart.aspx
You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners
https://mbs.microsoft.com/partnersource/support/
Customers
https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htm
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

↑ Back to the top

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:
  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.


For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
893082 How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have Microsoft Dynamics AX 2012 Retail installed to apply this hotfix.

Restart requirement

You must restart the Application Object Server (AOS) service after you apply the hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Aximpactanalysis.exeNot applicable60,28022-May-201202:09x86
Axupdate.exeNot applicable60,26422-May-201202:09x86
Clientoba32.mspNot applicable21,237,76023-Aug-201211:33Not applicable
Clientoba64.mspNot applicable21,237,76023-Aug-201211:33Not applicable
Components32.mspNot applicable18,477,05623-Aug-201211:33Not applicable
Components64.mspNot applicable35,733,50423-Aug-201211:33Not applicable
Helpserver64.mspNot applicable901,12023-Aug-201211:33Not applicable
Objectserver32.mspNot applicable7,286,78423-Aug-201211:33Not applicable
Objectserver64.mspNot applicable9,248,76823-Aug-201211:33Not applicable
Retaildatabaseutility.mspNot applicable421,88823-Aug-201211:33Not applicable
Retailheadquarters32.mspNot applicable806,91223-Aug-201211:33Not applicable
Retailheadquarters64.mspNot applicable806,91223-Aug-201211:33Not applicable
Retailpos.mspNot applicable2,994,17623-Aug-201211:33Not applicable
Retailposplugins.mspNot applicable299,00823-Aug-201211:33Not applicable
Retailstoreconnect32.mspNot applicable450,56023-Aug-201211:33Not applicable
Retailstoreconnect64.mspNot applicable450,56023-Aug-201211:33Not applicable
Retailtransactionservice.mspNot applicable122,88023-Aug-201211:33Not applicable
Setupsupport32.mspNot applicable11,804,67223-Aug-201211:33Not applicable
Setupsupport64.mspNot applicable19,091,45623-Aug-201211:33Not applicable
Traceparser.mspNot applicable442,36823-Aug-201211:33Not applicable
Axsetupsp.exe6.0.1108.18711,378,52815-Aug-201211:19x86
Axutillib.dll6.0.1108.806821,48006-Aug-201213:07x86
Microsoft.dynamics.servicing.operations.dll6.0.888.43635,75222-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491382,84822-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491370,56022-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491374,65622-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491374,65622-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491370,56022-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491378,75222-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491370,56022-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491374,65622-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491370,56022-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491374,65622-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491370,56022-May-201202:09x86
Axsetupsp.resources.dll6.0.947.491407,42422-May-201202:09x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top

Keywords: kberrmsg, kbexpertiseinter, kbexpertisebeginner, kbexpertiseadvanced, kbnoloc, kbsurveynew, kbmbsquickpub, kbmbspartner, kb, kbhotfixserver, kbqfe, kbautohotfix, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2742214
Revision : 1
Created on : 1/7/2017
Published on : 4/11/2013
Exists online : False
Views : 315