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. The data cache is not synchronized between clustered AOS servers sometimes in Microsoft Dynamics AX 2009 Service Pack 1

The data cache is not synchronized between clustered AOS servers sometimes in Microsoft Dynamics AX 2009 Service Pack 1

View products that this article applies to.

This article applies to Microsoft Dynamics AX for all regions.

↑ Back to the top

Symptoms

Assume that you run Microsoft Dynamics AX 2009 Service Pack 1 (SP1) in an environment that multiple Application Object Server (AOS) services exist in one AX instance. After a record in an EntireTable cached table is updated on one AOS server, the other AOS servers display different values. The data cache is not synchronized between clustered AOS servers.
Additionally, the following error message is logged in the Application log on one or more AOS server:
110 Object Server 01: Dialog issued for client-less session 1: Cannot edit a record
in LastValue (SysLastValue). User ID: , AdminUserSetup.
The SQL database has issued an error.

↑ Back to the top

Cause

This problem occurs because an update conflict occurs. The update conflicts on the record in the SysLastValue table that is used by AOS servers to synchronize the data cache.

↑ Back to the top

Resolution

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 2009 Service Pack 1 installed to apply this hotfix.

Restart requirement

You must restart the Application Object Server (AOS) service after you apply this 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
Axupdate.exeNot applicable61,28805-Jan-201218:09x86
Components32.mspNot applicable25,328,64005-Jan-201218:09Not applicable
Components64.mspNot applicable30,695,93605-Jan-201218:10Not applicable
Objectserver32.mspNot applicable5,796,35205-Jan-201218:09Not applicable
Objectserver64.mspNot applicable6,630,91205-Jan-201218:09Not applicable
Axsetupsp.exe5.0.1100.401,656,68005-Jan-201218:06x86
Cabextractor.dllNot applicable18,80005-Jan-201218:09x86
Microsoft.dynamics.setup.reportingservices.dll5.0.1100.9150,44008-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40538,48805-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4517,33608-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40534,39205-Jan-201218:09x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40534,39205-Jan-201218:09x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82408-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40534,39205-Jan-201218:09x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82408-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40538,48805-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82408-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40538,48805-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1500.121216,32008-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40534,39205-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82408-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40542,58405-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4517,84808-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40534,39205-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:09x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40534,39205-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82408-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40534,39205-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40546,68005-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4518,87208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40558,96805-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4520,40808-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40530,29605-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31208-Dec-201022:21x86
Axsetupsp.resources.dll5.0.1100.40526,20005-Jan-201218:08x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4515,80008-Dec-201022:21x86
Cabextractor.dllNot applicable22,38405-Jan-201218:10x64

Validation of the application hotfix installation

To validate the installation of the application hotfix, open the SysHotfixManifest class in the Application Object Tree (AOT). Then, verify that there is a method whose name includes the Knowledge Base (KB) article number of the installed hotfix. Additionally, you can cross-check the affected objects by comparing the KBXXXXXX.txt file against the objects in the AOT. By doing this, you can make sure that the objects are changed correctly in the SYP layer or in the GLP layer.

Note The XXXXXX placeholder represents the KB article number of the installed hotfix.

↑ 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

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

974255 Impact Analysis feature for Dynamics AX 2009

↑ Back to the top

More Information

Each AOS server checks the SysLastValue record where the elementName value equals the EntireTableCache value, to verify that there are updates to the EntireTable cached tables that have to be re-read in the server's own copy of the data cache. There is one single SysLastValue record that all AOS servers use for all the EntireTable cached tables.
The container field on this record contains a structure with every table and a flushId for each one. The flushId is incremented every time that an AOS server makes an update to the corresponding EntireTable cached table. The flushId is also kept in a matching structure in AOS memory.
The synchronization process
Consider the following scenario:
  1. You have a TableA table which is an EntireTable cached table.
  2. You have AOS1, AOS2 and AOS3 servers.
  3. You update a record in the TableA table on the AOS1 server.
    Note The SysLastValue record is updated and the flushId for the table is incremented by one in this situation.
In this scenario, the AOS2 and AOS3 servers check the SysLastValue table one time per minute. When the flushId for the table differs from the one they have in AOS memory, they clear the cache for the table. Additionally, the table will be re-read from the database next time when a user requests it.
If an update conflict occurs in the SysLastValue table, other AOS servers will not be notified of the data change. Therefore, the cached data is out-of-step between AOS servers.

↑ 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, kbnoloc, kbqfe, kbsurveynew, kbhotfixserver, kbautohotfix, kbmbsmigrate, kbexpertisebeginner, kbexpertiseinter, kbmbsquickpub, kb, kbmbspartner, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2661128
Revision : 2
Created on : 2/17/2017
Published on : 2/17/2017
Exists online : False
Views : 414