Applies to Product -FnO Platform
What’s happening?
Users are experiencing 502 and 504 error dialogs when attempting to access modules in Dynamics 365 environments, which may lead to temporary downtime of services.
Reason:
The underlying cause of the errors may be related to AOS (Application Object Server) crashes, potentially triggered by customized components or batch jobs that are running in the environment.
Resolution:
- For environments experiencing 502 and 504 errors, verify the status of the AOS. If it is crashing, identify any customized components or batch jobs that may be contributing to this.
- Temporarily stop any identified batch jobs to determine if they are causing the AOS crashes.
- Monitor the environment for any further occurrences of the errors after stopping the batch jobs.
- If the issue persists, consider enabling specific features or configurations that may help mitigate the stack overflow exceptions or crashes.
- For environments with newly created legal entities, ensure that the deployment settings are correctly configured to allow access to all necessary modules. This may involve:
- Opening the deployment settings and navigating to “Configure Solution Features.”
- Ensuring that the environment is set to allow access to the full set of modules.
- If the issue is related to a custom extension, engage the internal development team to debug the extension causing the problem.