Error message when you try to start a server that is running the AOS service in Microsoft Dynamics AX 4.0: "Windows could not start the Dynamics Server$01 on Local Computer"

Applies to: Microsoft Dynamics AX 4.0Axapta Object Server

Symptoms


When you try to start a server that is running the Application Object Server (AOS) service in Microsoft Dynamics AX 4.0, you receive an error message that resembles the following:
Windows could not start the Dynamics Server$01 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the vendor, and refer to service-specific error code 110.
Additionally, the following error message is logged in the System log:
Object Server 01: Internal Error occurred executing stored procedure when creating session for the AOS.
This problem occurs after you update the database on the server that is running the AOS service from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 4.0 with Service Pack 1.

Cause


This problem occurs if the SysServerSessions stored procedure and the SysClientSessions stored procedure do not exist. When this problem occurs, the server that is running the AOS service cannot record the appropriate server information and the appropriate client session information in the Microsoft SQL Server database.

Resolution


To resolve this problem, follow these steps:
  1. On the server that contains the SQL Server database, start the Setup program for Microsoft Dynamics AX 4.0 Service Pack 1 from the installation DVD.
  2. Click to select the Database Server check box, and then click Next.
  3. To create the database, click the named instance of SQL Server.
  4. Type a name for the database, and then click Next.
  5. Follow the appropriate steps depending on the version of SQL Server that you are running.

    In SQL Server 2005
    1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    2. Expand the named instance of SQL Server that you used to create the database in step 1 through step 4.
    3. Expand Databases.
    4. Expand the new database that you named in step 4.
    5. Expand Programmability, expand Stored Procedures, and then locate the following stored procedures:
      • CreateServerSessions
      • CreateUserSessions
    6. Right-click one of these stored procedures, and then click New Query Editor Window.
    7. In the first line of the script, change the name of the database to the name of the database that you upgraded.
    8. To run the script, press F5.
    9. Repeat step f through step h for the other stored procedure.

    In SQL Server 2000
    1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
    2. Expand the named instance of SQL Server that you used to create the database in step 1 through step 4.
    3. Expand Databases, and then expand Dynamics.
    4. Click Stored Procedures, and then locate the following stored procedures:
      • CreateServerSessions
      • CreateUserSessions
    5. Right-click one of these stored procedures, and then click Generate SQL Script.
    6. In the Generate SQL Script window, click Preview, and then click Copy.
    7. In SQL Server Enterprise Manager, click Tools, and then click SQL Query Analyzer.
    8. In the SQL Query Analyzer window, paste the script that you copied in step f.
    9. On the SQL Server Enterprise Manager toolbar, change the name of the database to the name of the database that you upgraded.
    10. To run the script, press F5.
    11. Repeat step e through step j for the other stored procedure.