Troubleshoot installation issues with client components [AX 2012]

Updated: February 1, 2013

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic provides information that can help you troubleshoot issues that you may encounter when you install the Microsoft Dynamics AX client components.

If you are not a user in the system, the client returns the following error: “User not recognized.” An administrative user can add you to the system as a user, and then assign you to the appropriate security roles. The person who installed Microsoft Dynamics AX is the first administrative user. For more information, see the Microsoft Dynamics AX Technical Library on TechNet.

You can access the Microsoft Dynamics AX Configuration utility from the Administrative Tools menu. On computers that run Windows 7, Administrative Tools is an item in Control Panel.

When you try to start the client, you may receive the following error: “Connection with the Application Object Server cannot be established.”

This error can indicate that the Microsoft Dynamics AX Object Server service is not running. On the server computer for Application Object Server (AOS), verify the status of the service by using the Services control panel. (Click Start > Administrative Tools > Services.)

If you specified a shared configuration file when you installed the client, you might receive this error the first time that you start the client. To resolve this issue, click OK to close the client, and then restart the client.

Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).