Dynamics Community Forum Thread Details

On-premises D365FO environment AOS causes SQL errors

Hello all,

We have our live production on-premise environment. Sometimes AOSs machines restarts mostly on weekend due to e.g.

Hardware maintenance
Windows update
Activating financial dimensions due to which we need to activate maintenance mode etc.

After that we make sure all AOSs are up and service fabric is all green with no warning on any application or node. But sometimes during working hours user complains random issues like

They cannot open customer transaction or vendor transaction form
- It throws cannot access tempDB.table error while opening
Cannot filter on grid columns

so we track those users on Online users form and see that all of these users are using particular AOS e.g. AOS1 or AOS2. We inform users to stop using environment via email and restart its node from Service fabric and it resolves the problem.

My question is: what is the standard way to handle this issue or are we missing something? My concern is that we may lose some valuable data due to restart if any user keeps working.

Quick Links