Dynamics AX: Connection with the Application Object Server could not be established

Symptom

On a Terminal server, new Dynamics AX users are not able to log into AX client on a workstation. The users are seeing this error when logging into Dynamics AX:

"Logon Error: Connection with the Application Object Server could not be established"

Cause

The user's AX configuration is not correct. The AOS server name contains the wrong server name.  

Resolution

The aos2 string value had the wrong AOS server name from the original install.  Change the value of aos2 in the following key in registry - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dynamics\5.0\Configuration\Original (installed configuration).

Now when a new user logs into the workstation (a terminal server), his/her AX configuration would have the correct value. The user's AX configuration is stored in this key -

HKEY_CURRENT_USER\Software\Microsoft\Dynamics\5.0\Configuration\Original (installed configuration)

The user's AX configuration key is a copy of the same key from HKEY_LOCAL_MACHINE.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×