Troubleshoot problems operating the Application Object Server
This topic provides information about how to troubleshoot issues encountered when running or connecting to an Application Object Server (AOS) instance.
To help Microsoft solve problems with AOS instances, if you are experiencing fatal errors in an instance of the AOS, in the Microsoft Dynamics AXServer Configuration Utility (Start > All Programs > Administrative Tools > Microsoft Dynamics AX Server Configuration Utility) you can select the Automatically send information about fatal errors in any Application Object Server service instance to Microsoft option to send information about any fatal error in an AOS instance to Microsoft.
If you enable error reporting, information is sent over a secure (https) connection to Microsoft, where it is stored with limited access. Microsoft uses the reports only to improve Microsoft Dynamics AX, and treats all information as confidential.
When a client cannot connect to an instance of the Application Object Server (AOS), one of the following may be the cause.
AOS is starting
The first time you start a client after the AOS has been installed, the AOS service may still be starting up. On the AOS computer, use the Services manager to determine whether the service has started.
Port is not open
If the Application Object Server is installed on a computer with a firewall, be sure that the port you are trying to connect to is open. The default port is 2712, but additional instances may install on ports 2713, 2714, and so on.
MDAC components are not the same version
If different versions of the Microsoft Data Access Components (MDAC) are installed on the client, Application Object Server (AOS), and database, you may experience client connection failure or sporadic disconnection of the client, AOS, or database.
If you are trying to connect to a database that was not created by Setup, the AOS account (the domain account or Network Service account associated with an AOS instance) may not have appropriate rights in SQL Server. The AOS account must be a user in the database and be assigned to the following database roles db_ddladmin, db_datareader, and db_datawriter.
When an AOS instance and SQL Server database are installed on the same computer, Setup creates a dependency—the AOS instance does not start unless the SQL Server database is running.
If you change the AOS instance to use a SQL Server on a different computer, you must manually change or delete the dependency using the SC tool (SC.exe) from a command prompt. For more information about SC commands, see the SC topic in the Microsoft Windows Server TechCenter.
To make the AOS dependent on the new SQL Server instance
Open a Command Prompt window and type:
sc config AOSinstancename depend= RpcSs/ sqlserverinstancename
To remove the AOS dependency on SQL Server being started
Open a Command Prompt window and type:
sc config AOSinstancename depend= RpcSs
