Hi,
Troubleshoot problems operating the Application Object Server in AX 2012
1. Client cannot connect to an AOS instance
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.
2.AOS instance cannot connect to new 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 database roles db_ddladmin, db_datareader, and db_datawriter.
3. AOS instance does not start after changing databases
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 SQL Server on a different computer, you must manually change or delete the dependency using the SC tool (SC.exe) from the command prompt. To make the AOS dependent on a SQL Server instance, open a command prompt window and type the following command:
sc config AOSinstancename depend= RpcSs/sqlserverinstancename
To remove the AOS dependency, type the following command:
sc config AOSinstancename depend= RpcSs
4. AOS service does not start
If the AOS service does not start automatically, you can attempt to start the service manually in Control Panel > Administrative Tools > Services. If the service still does not start, see the Windows System Event log for error details. If the event log shows an Oracle error (Oracle 12154), then the TNS name being used to connect the Oracle client (the AOS) with the Oracle server is not contained in the tnsnames.ora file that resides with the Oracle client. Contact your Oracle database administrator for assistance.
Reference
Troubleshoot problems operating the Application Object Server in AX 2012
1. Client cannot connect to an AOS instance
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.
2.AOS instance cannot connect to new 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 database roles db_ddladmin, db_datareader, and db_datawriter.
3. AOS instance does not start after changing databases
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 SQL Server on a different computer, you must manually change or delete the dependency using the SC tool (SC.exe) from the command prompt. To make the AOS dependent on a SQL Server instance, open a command prompt window and type the following command:
sc config AOSinstancename depend= RpcSs/sqlserverinstancename
To remove the AOS dependency, type the following command:
sc config AOSinstancename depend= RpcSs
4. AOS service does not start
If the AOS service does not start automatically, you can attempt to start the service manually in Control Panel > Administrative Tools > Services. If the service still does not start, see the Windows System Event log for error details. If the event log shows an Oracle error (Oracle 12154), then the TNS name being used to connect the Oracle client (the AOS) with the Oracle server is not contained in the tnsnames.ora file that resides with the Oracle client. Contact your Oracle database administrator for assistance.
Reference
Comments
Post a Comment