AX Installation error " Connection with the Application Object Server could not be established"

(0) Share

Report

Posted on by Anurag Singh

155

I am trying to install AX client, Installation is successful but When I am opening AX , getting an error " Connection with the Application Object Server could not be established" i have checked all possibilities like AOS name etc Please help.

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Sohaib Cheema 49,438 User Group Leader on at

Like (1)

Report

check you AOS service in windows Services if that is started or not yet

if not started yet and is in Starting state, wait until it is running, after that start client.

Was this reply helpful? Yes No
Martin Dráb 237,948 Most Valuable Professional on at

Like (0)

Report

Please tell us more. Is your AOS running? Is the port open on Firewall if AOS is on a remote machine? And so on.

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

Can you ping the AOS server from the client machine? You should be able to ping the servername (without having to use FQDN) if ICMP-traffic is allowed and ping is not blocked by a firewall.

Do you have multiple versions of AX client installed on the machine? You may experience the same "error" if it attempts to connect to AX using the wrong version of the client (like connecting AX2012 with AX2009 client).

Was this reply helpful? Yes No
Anurag Singh 155 on at

Like (0)

Report

AOS is running and it is on other machine, the other thing is this that the problem is with only laptop users, for desktop users its fine.

Was this reply helpful? Yes No
Anurag Singh 155 on at

Like (0)

Report

I am able to ping the AOS server, even desktop users are also able to use with out any difficulty, The problem is only with laptop users, It sounds funny but really I am facing this situation.

Was this reply helpful? Yes No
Sohaib Cheema 49,438 User Group Leader on at

Like (0)

Report

A pure network/ administrative person can think here better than us AX guys.

Let's see if somebody with that capacity shares some optimal approach to resolution and reasoning

Was this reply helpful? Yes No
Suggested answer

Umesh Pandit 9,315 User Group Leader on at

Like (0)

Report

support.microsoft.com/.../2288968

It is network problem and you can solve it.

Open host file (c:\windows\system32\drivers\etc\hosts) on the AX Client PC or Terminal Server. Add IP address of AOS server and AOS server name

192.168.1.25 AOSServer

in host file then Run the command nbtstat-R and start Dynamics AX Client.

Was this reply helpful? Yes No
Suggested answer

raelhefn on at

Like (0)

Report

Check connectivity with your AX AOS service server.

Check installed client port number is matched your AOS port number

check if you are using multiple AOS you configured your client to refer to which AOS port and Name

Check Ports number is configured on your Servers firewall.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi All,

I was facing the same issue, i found out the solution for this, it worked for me.

I had installed AX 2009 AOS in my local system. And client in other' system pointing to my local system AOS. If i open the AX, in which system i have installed client, i was getting Connection with the Application Object Server could not be established" error.

Solution is : 1. Both user should be in the same domain, means in which system we will install AOS and in which we will install client both user.

2. The main issue is, there was no communication between the systems, like both can ping and can access one another's ip address and host name.

For this i just turned off my windows firewall in both the systems and checked, then if i open AX, it was working fine. And later i added AX setup to the Trusted application in control panel and turned on the Windows firewall.

Hope this will help for you guys also. . :)

Was this reply helpful? Yes No
AlexCMi 85 on at

Like (0)

Report

Hi all,

in case the AOS service is running, axc configuration is correct and you still face the issue, you should check the table sysserverconfig as it may contain old AOS entry

Regards

Alessandro

Was this reply helpful? Yes No