Failed to flush EntireTable cache

[Logger]

Добрый день.

Периодически аос выдает в виндовый лог ошибку
Object Server 01: Failed to flush EntireTable cache. Exception value = 11; Retry count = 6

Но дальше работает и явных проблем незаметно.

Гугл ничего полезного не предложил для решения.
Кто-нибудь лечил такое ?

Ax 2009 Билд 5.0.1600.3596

[Logger]

Таблетка
https://community.dynamics.com/ax/f/33/t/111409

[Logger]

http://web.archive.org/web/201710230.../f/33/t/111409

Solution

Цитата:

Trond Lindløkken responded on 20 Apr 2017 2:49 AM
Hi.

Luckily I documented this change:

Sympthoms:

AOS services occassionaly reports:

Object Server 01: Failed to flush EntireTable cache. Exception value = 11; Retry count = 6

Issue:

ADDRESSCOUNTRYREGION 6059 AXTAB , turned of 23.08.2013, changed to "found"

ASSETDISPOSALPARAMETERS 27723 AXTAB , turned of 27.08.2013, changed to "found"

ASSETLEDGERACCOUNTS 7973 AXTAB , turned of 28.08.2013, changed to "found"

CASHDISC 3978 AXTAB , turned of 29.08.2013, changed to "found"

CUSTLEDGERACCOUNTS 3914 AXTAB , turned of 30.08.2013, 08:54 changed to "found"

CURRENCY 2021 AXTAB , turned of 02.09.2013, 09:13 changed to "found"

ASSETGROUP 2008 AXTAB , turned of 29.08.2013, changed to "found"

We have turned of Entire table caching on these tables as it is not recommended to use it on tables with more than 2000 records.

Remedy.

Contacted MS to clarify the nature of the problem:

MS Response :

a) “The program tries to update the fields of VALUE and RECVERSION for the record whose name is "EntireTableCache" in the table SYSLASTVALUE, about once each minute and the VALUE field of this record stands for the status of dirty updates cached in memory for DB tables. As the design is to do the updating once for a while, it is not necessary to keep a tight trace of the status in database. So one occasional updating failure does no harm to the system, and it would be performed in the next rounds. So this error will not have almost any impact.

b) As a generic measure it is suggested to :

1. Install the latest Kernel build (as I have noticed you are on a

quite low build), as it contains a fix for a different cause of the same

issue: