Basic service call

Summary

A basic call to the Application Object Server (AOS) has failed.

Causes

The service call may fail for any number of reasons • The user account associated with the Microsoft Dynamics AX 2012 administrator account does not have the appropriate privileges to execute services calls. • The Windows Communication Foundation service on the AOS computer may not be running. • The metadata services URI for the AOS cannot be reached. • Required services have not been deployed to the AOS.

Resolutions

• View the event log on the AOS that is used for availability monitoring. This AOS can be found in the Object Diagram for the environment. Select the node in the Object Diagram for the service call monitor. The AOS computer is the computer name in the Name field. • Verify that the account associated with the Microsoft Dynamics AX 2012 administrator account in Operations Manager has been assigned either the Sysadmin or IT admin role in Microsoft Dynamics AX. • Verify that the AOS service is being monitored by Operations Manager, and is running on the AOS computer. • Verify that the required services are deployed from within the Microsoft Dynamics AX 2012 client. In the client, click System administration, in the Setup section, click Services and Application Integration Framework, and then click Inbound ports. • Verify that the metadata services URI is accessible.