but this client cache
is it ax 2009 or AX 2012
+31 6 147 989 53
3905 PE - Veenendaal
OTHER CONTACT INFORMATION
If it's AX 2009 and flushing the cache doesn't solve your problem you might want to try KB2661128:
try to stop AOS Services from booth servers, delete the .AOI file from the application folder and start the AOS services again
Dont forget to mark this as answer!
Francisco Silva | | http://fsilvajunior.blogspot.com.br
This posting is provided "AS IS" with no warranties, and confers no rights.
Thank you for replay.
Is it bug?
Are there any correct configuration?
We can't stop AOS, SLA is 24H.
Many table is set cachelookup on sys layer.
I think it is not resolve root cause of this...
Did flushing the cache on AOS2 by force worked for you?
My blog | PBC
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
No, I didn't flush.
But I confirmed that AOS2 has been flushed automatically today.
We cannot understand why...
I don't have a multiple-AOS environment on hand to test this... can you try flushing the caches from AOS1 (by copy a set of menuitems and set them to run at server - chaituax.wordpress.com/.../cache-mechanism-in-dynamics-ax) and see if it helps refresh the cache on AOS2 also?