AX 2012, SQL Server 2012 & AlwaysOn - Issue with AOS Install

I wanted to spend a little time today talking about a specific setup issue I recently encountered with a client in setting up Microsoft Dynamics AX 2012 with SQL Server 2012 AlwaysOn technology. The focus around SQL Server 2012, AlwaysOn technology is around enabling an active-active high availability options for AX customers. You can find out more about this, here.: AX 2012 - New High Availability Options with SQL Server 2012



This is a very interesting issue actually, one that does not have much public coverage yet it would seem. Actually not sure what the combination of setup & settings that causes such a state, however this is an issue directly related to setting up an AOS that points to the Virtual Name of a Synchronous SQL Server 2012 - AlwaysOn Active-Active node.



What we run into is, the AOS reports as if the install took place. However in looking at the setup log, you will see something similar to the following.:

"Granting AOS account access to database [DatabaseName] on server [Virtual SQL Server Name.]

*******************************

Component installation task stopped due to an error.

*******************************

The network path was not found.

*******************************

System.IO.IOException: The network path was not found.

S260FinishedInfo"

Now, the above is not the full error message at all, but it is the keywords that most people would search on, to reach this post - and therefore reach the solution!. When faced with this scenario, it would seem the issue is the installation program running into an issue with the resolution of the Virtual SQL Server 2012 name, to the current primary node of the AlwaysOn Group for the Dynamics AX 2012 Database.

The path around this issue, at least at the time of this writing is to target the node name of the primary SQL Server 2012 instance, for the AX 2012 database. This targeting should be as part of the install process when selecting which SQL Server, and corresponding database in which the AOS should connect to. In doing this, you can then have a successful install of your new AOS.

After having a successful run at installing your new Microsoft Dynamics AX 2012 AOS, you can now use the server configuration utility, specify the virtual SQL Server 2012 name, restart the AOS and everything should be working correctly.

There is a community post about a similar issue to this, in error reported from the installation process. You can find that here.: AOS installation issue (Remote Registry service). As the name states, this was directly related to the Remote Registry Service of the targeted SQL Server box not running. This could be the issue your facing, if your not trying to use AlwaysOn for SQL Server 2012, and get the above type errors.

Finally, let me add a recently updated Microsoft TechNet article on supported SQL Server topology for AX 2012.: (TechNet) SQL Server topology [AX 2012]. Here we can see the supported scenario's, in which the Synchronous for SQL Server 2012 is one of those. I do also welcome any further feedback, and specific details if anyone has anything else to add to this topic. At the very least you can use the above to be able to easily get past such installation woes, but still use the desired SQL Server 2012 topology.

Well that's all I have for this post, check back soon as a whole lot more to come, including more focuses around Putting your data to work for you while driving towards Creating Systems of Engagement with Microsoft Dynamics AX 2012! Till Next Time!


Visit Hillstar Business Intelligence (www.HillstarBI.com) in order to truly unlock your data trapped in your Microsoft Dynamics investment. With our value driven business intelligence strategy Hillstar help you transform into a data informed company.


Follow Me @:
    

"Visit the Dynamics AX Community Page today!"