web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Error: Server is unava...
Microsoft Dynamics AX (Archived)

Error: Server is unavailable on installing AX 2012 R3 on a new machine

(0) ShareShare
ReportReport
Posted on by Raghavendra M Rao 45

Hello Everyone,

I am installing AX 2012 R3 on a Server machine. All pre-requisites are installed. Databases are installed. AOS is installed and services are STARTED. When I install the client and try opening the client on the same machine; I get an error that says "The server is unavailable. Please check your configuration and network settings"

Having said that, I have checked the firewall which is not enabled.
I have checked the port and it is open.
I have verified that the Configuration is correct and that it is pointing to the right AOS. I only have one AOS instance on my machine.

However, when I look into the Event Viewer, I see error logged when I start and stop the AOS.
When I start the AOS, below error is registered:
Object Server 01: RPC error: Failed to register service principal name (SPN)
When I stop the AOS, below error is registered:
Object Server 01: RPC error: Failed to unregister service principal name (SPN)

Am have looked into many articles but I have not been able to resolve the connectivity issue. Have attached the screenshots for your reference.

AOS-Services-start-error.jpg

 

AOS-Services-stop-error.jpg

Any help on this would be highly appreciated.

*This post is locked for comments

I have the same question (0)
  • Denis Macchinetti Profile Picture
    Denis Macchinetti 16,444 on at

    Hi

    Give a try.

    On the AX Client Configuration, try to use the Server IP instead of the DNS.

  • Suggested answer
    Arturo Medina Profile Picture
    Arturo Medina 696 on at

    Raghavendra, Please take a look at the account used to start the AX service (Microsoft Dynamics AX Object Server 6.2$01-AXDB). For instance my demo environment uses a domain admin account (Yes, I know I should be using a managed account).

  • Raghavendra M Rao Profile Picture
    Raghavendra M Rao 45 on at

    Hi Denis,

    Thank you for your response. As you suggested, I created a new Client Configuration with Server IP instead of the DNS, regenerated WCF configuration without any errors.

    However, when I try opening the AX client with the new config file; I get the following error: "The Application Object Server name or port number is incorrect. Check the values in the Microsoft Dynamics AX Server Configuration Utility, and try again"

    I have used the default port numbers TCP/IP being 2712 and WSDL port being 8101. I have attached the below screenshot for your reference. Please let me know if you have any suggestions.

    Server-IP.jpg

  • Raghavendra M Rao Profile Picture
    Raghavendra M Rao 45 on at

    Hi Arturo,

    Thank you for your response. The account that am using to the start the AX service is a domain account which has full administrative rights. I have done the same in earlier installations and had no issues with it. Unable to figure out what might be the issue.

    Thanks,

    Raghu

  • Vincent Nguyen Profile Picture
    Vincent Nguyen 290 on at

    Same issue here, any solution?

  • Suggested answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    The Server Principal Name (SPN) registration requires the AX AOS execution account to be granted access by an Active Directory Domain Administrator to register/delete SPNs for the error to go away.

    In majority of the cases the problem is with the AX AOS configuration for the client connections, like if you provide the wrong ports, or you did not use the default instance name and you have provided one (like the above screenshot), they could all cause connection failure.

    Also they may have used a fixed AXC file as configuration within the AX executables' shortcut, and if that points to the wrong AOS instance, it does not matter what you have in the registry (which is the one by AX client configuration utility), it is the AXC file which needs to be updated.

  • Suggested answer
    Vincent Nguyen Profile Picture
    Vincent Nguyen 290 on at

    AOS server name was more than 15 char and got truncated for some reasons. Renamed it to 9 char fixed my issue, AX client now can connect and retrieve the AOS server.

  • rrizwann Profile Picture
    rrizwann 675 on at

    Hi I had faced the same issue I just restart the server and it worked 

    Please follow this link

    msaxcrm.blogspot.com/.../the-dynamics-server-could-not-be.html

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 26

#2
imran ul haq Profile Picture

imran ul haq 8

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 4 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans