Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
You might need to restart the interactive Application Object Server (AOS) for several reasons. Here's an overview of these reasons:
Routine maintenance activities – Routine maintenance activities, such as patching, might temporarily interrupt AOS services. To understand the effect of maintenance activities and access known maintenance schedules, see the following articles:
- Operating System Maintenance Schedule – Learn more about planned operating system maintenance schedules.
- Experience during the nZDT Maintenance Window – Gain insights into system behavior during the nZDT maintenance window.
Interactive AOS server failures ("crashes") – Failures on interactive servers might occur because of application services that are currently running. Detailed failure information is available in Microsoft Dynamics Lifecycle Services. For more information about how to monitor failure information, see Monitoring and telemetry using Application Insights.
Infrastructure failover – Restarts can occur if infrastructure issues lead to an internal failover. The system uses autoscaling and capacity management to ensure optimal environmental performance and availability.