Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics AX forum
Answered

Changed the default order stopped to non-stopped, but system still alert it was not ready when create purchase orders

Posted on by 25

We have many AOS servers, loading balance point to one AOS instance, I think we are using the loading balance in dynamics ax 2012 R3 CU13, I don't know what happened.

totally 15 AOS servers ,and divided into 3 clusters, if I changed the item from stopped to non-stopped on cluster3 , the other user on cluster3 could not use it immediately,  but If I logon to other cluster AOS servers, it could create purchase order for that item. Have anyone faced the same issue? is it caused by AX caches , and how can I solve it?

Categories:
  • Deane Shen Profile Picture
    Deane Shen 25 on at
    RE: Changed the default order stopped to non-stopped, but system still alert it was not ready when create purchase orders

    Thanks for you answer,Yes, I can see one 117 error, what did that mean?

  • Suggested answer
    RE: Changed the default order stopped to non-stopped, but system still alert it was not ready when create purchase orders

    Adding to Andre's reply, check on the AOS server event logs to see if you are getting event id 110 and 117 warnings or errors every minute.

    The event log details may indicate a cache sync issue.

  • Deane Shen Profile Picture
    Deane Shen 25 on at
    RE: Changed the default order stopped to non-stopped, but system still alert it was not ready when create purchase orders

    Hello Andre,

    Many thanks for the feedback, you know we have so many AOS servers,  which server AOS should I logon to clean the caches, actually I have done this action , not logon every server to clean it, it did not work.

    The tricky thing is user logon the cluster 3, AOS 13  to enable the item , but the other user can't use it on AOS13, instead, they could logon cluster 1, AOS 01 to use it. I am wondering is it possible the cluster 3, the new created cluster was not implemented perfectly.

  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 287,989 Super User on at
    RE: Changed the default order stopped to non-stopped, but system still alert it was not ready when create purchase orders

    Hi Deane,

    It could be indeed related to caching. You can refresh some caches using the menu from the Development Workspace: Tools > Caches > Refresh data. It is also possible to flush caching with help of some with x++ coding.

Helpful resources

Quick Links

Replay now available! Dynamics 365 Community Call (CRM Edition)

Catch up on the first D365 Community Call held on 7/10

Community Spotlight of the Month

Kudos to Saurav Dhyani!

Congratulations to the June Top 10 community leaders!

These stars go above and beyond . . .

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 287,989 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 225,588 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans