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!"

Report Development Basics in AX 2012 - Debug Query & Code based reports

Today, I wanted to take some time and continue this focus we have around Report Development Basics in AX 2012. This is a continued theme really, building block parts of helping understand how to Create a System of Engagement for AX 2012 customers. Today's focus is around one that I think everyone planning to do any report development, the correct way, in AX 2012 should fully understand. That is Debugging Query & Code based report objects.



First I will say that this post assume you have an understanding of the two types of AX-SSRS report development options. This is either via a Modeled Solution, aka Query Based, or Code based solution, aka Report Data Provider based. You can learn more about these concepts in the following post.: AX 2012 - AX-SSRS Report Design Concepts


Model Driven Solution Diagram

First lets start with how to debug a modeled, or query based report. The idea is that you have a query you have created, and now your not getting the data you think you should. The best way I have found, for debugging such a report data source, is via an X++ job.

The following is an example job that can be used, for doing just that.:

static void TestQuery(Args _args)
{

/*
Example job used to test query results with.:
*/

QueryRun queryRun;
Counter totalRecords;

// Table Variables:

VendTable vend;
VendCertification VendCert;

queryRun = new QueryRun(queryStr(queryVendCertInfo));

if (queryRun.prompt())
{
while (queryRun.next())
{
vend = queryRun.get(tableNum(VendTable));
info(Vend.AccountNum);

VendCert = queryRun.get(tableNum(VendCertification));
info(VendCert.CertificationNumber);

totalRecords++;
}
}

info(strFmt("Total Records : %1", totalRecords));

}

Now to break this down a bit. We have a QueryRun object that points to our desired query. In this case, it's one I created called queryVendCertInfo. This query references the VendTable, and further has a relation to the VendCertification table.

I'm able to execute the query, and the prompt call even brings forth the SysQueryForm for Dynamic Filters can be applied. Having this, you can now successfully test in query, as well as any query that is a bound data source for an AX-SSRS report dataset.


Code Driven Solution Diagram

Moving right along, the next area of focus for report debugging is a code driven AX-SSRS element. This is a report object, that as it's bound data source is a Report Data Provider class. There is a nice How to, posted by Microsoft you can find here.: How to: Configure the Debugger to Debug a Report Data Provider Class [AX 2012]

Let me state here that this assumes your working in the development mode, where everything is contained within a single server role. Meaning that for the developer, you have your own AOS, SSRS, SQL Server, as well as Visual Studio 2010, AX client, etc. With that assumption aside, you can then easily debug a report, that is based on a Report Data Provider class.

Since there is a nice how to, I have no need to re-hash those steps. I will say that you need to make sure that the AOS Service account is in the Microsoft Dynamics AX Debugging Users group.



After doing this, and making sure that you have an AOS configuration that enables global break points, the next steps are placing a Breakpoint; keyword in the processReport() method and then having the MorphX IDE Debugger open.



After doing this, you can then debug a code based report, either when executed from within the AX 2012 work space, or from within Visual Studio 2010. One thing that you will notice, when debugging from within VS2010 is after the preview action runs through the debug process once, it stops from running through the debug process again.

There is a process however that you can employ, that will allow you to reload the VS2010 project, and therefore allow multiple debug runs, without having to close out of VS2010 each time.



As the above screen shot suggests you need to unload the VS2010 project. In doing that, the next step would be to reload the VS2010 project that contains the AX-SSRS report elements.



With the above information you should have what you need to help debugging most AX-SSRS reporting development scenarios. That's all for this post, check back soon as more to come, including the continue Freaky Tech Friday series tomorrow! Till Next Time!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

Report Development Basics in AX 2012 - Drill Through Options

Today I wanted to take some time and start back focusing on BI & Report Development topics for Microsoft Dynamics AX 2012. This is one area that helps us shape Microsoft Dynamics AX 2012, into a true System of Engagement for customers.

Today I wanted to talk about the ability to perform a drill through action from one report, to another source in AX 2012.



This is a popular possibility, that enables one to create an engaging report experience for launching from a more summarized report data - into the details such summarized reporting represents.

We see this in action with AX 2012, via Web Parts for Enterprise Portal. These are most always hosting AX-SSRS chart based report objects, or other forms of grouped and summarized data. Usually clicking on the details of the value being summarized in the report, will take you to a more detailed transaction view of the data it is meant to represent.

There are two options, when we look at the Drill Through possibilities, either Report Drill Through Action or URL Drill Through Action. As the names imply each will either launch another report, or launch a new browser directed at the specific URL to be viewed, when clicked by the user.



In order to work with a targeted Report for drilling through too, it has to be referenced either within the same model project - of opened within the same solution design space. You can see this with the two report objects I have shown above.



Doing this will enable for you to have a source, or drill from, as well as a target or drill through report objects. We can see in the above image that I have a selection of either Report1 design or Report2 design. Since Report1 is my source object, I will select Report2 Autodesign.



Having done this, as you see above, I now have my Report Drill Through Action along with parameters that I need to set. Usually the auto-generated parameters like company, report culture, etc can be passed through from the source report object. However this is where a target report object, of the drill through action, can have it's report output shaped by context of the data from the source.

Moving right along from here, we have the URL Drill Through Action. As with the report drill through action, the URL is added from the fields on the design of a report. In doing this, we see in the following options for our URL Drill Through Action.



As the above image suggests, we have the ability to pass any number of URL's, along with parameters that can be dynamically driven from the source report object. A good example would be a report that had tracking information, and you wanted to automatically fire into UPS site from the report, and have it show the status of a package.

All-in-all, the drill through actions we have when talking in terms of report development for Microsoft Dynamics AX 2012 help us create more engaging reporting experiences for users. This is the ultimate goal, to engage the user with needed and critical information, for solid execution of their roles responsibilities.

That's all for this post. Check back soon however as a lot more to come! Till Next Time!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

AX 2012 - Understanding & Extending the Organization Model

I wanted to take the time today, and point out some great resources around the concept of extending the Organization Model in Microsoft Dynamics AX 2012.



Before we dive right into the mix of common task that are typically associated with customer implementations of Microsoft Dynamics AX 2012, I would first like to point out a great learning webinar around the topic of Modeling Your Organization with AX 2012. What I'm speaking about can be found here.: Modeling your Organization: Microsoft Dynamics AX 2012

The above link will take you through a nice webinar that really gives you a feel for the thought process of modeling an organization with AX 2012. This is the 'unified natural models' that Microsoft speaks about a lot. I should correct that really and say one of the unified natural models. See.: Enabling Agility through Unified Natural Models



When we start to think about extending the organizational model that comes out-of-the-box in AX 2012, there are two common task that are typically done for customers. The first task is around adding custom Operating Units. Microsoft has a done a good job at creating the following walk through.: Walkthrough: Create and Use a Custom Operating Unit Type [AX 2012] I will add that this walk through does leave out specifics, for example if you want the new Operating Unit to appear under the GL > Setup > Organization for management of said new custom operating unit.



The second most common extension that takes place for customers is around the creation of custom purposes. The following resource from Microsoft is a nice walk through as well, for this topic.: How to: Create a New Purpose [AX 2012]



Adding a new custom purpose for organization hierarchies helps further shape and allow customers to truly model AX as they run their business. Purposes for hierarchies can help relate policy and reporting needs.

With all of this one of the best resources for understanding how to implement and extend the organization model for AX 2012 can be found here.: Implementing and Extending the Organization Model in Microsoft Dynamics AX 2012

Update: I wanted to take the time and update this post, to include the fact that InformationSource located at InformationSource.Dynamics.com has some good resources on this topic as well. This includes some video's, which the webinar is based on. Further a specific PowerPoint artifact that I would like to point out.:



The above PowerPoint has some good information around understanding the concepts of organization modeling, as well as common task involved with the process. Further it has common task typically associated with extending the organization model offering for AX 2012. It mentions further task around Security with XDS, and relating Master as well as transaction data.

Now With the above information and resources, someone familiar with Microsoft Dynamics AX 2012 can extend the organization model(s) for a customer. Further, if your an ISV there could be good reason to include in your IP offering extensions to the organization model offerings. Keeping in mind that a customer could have a need for several organization hierarchies in their instance. Powering everything from Operations, reporting, relating to security, workflow approvals and more.

That's all for this post, but check back soon as I will continue with my focus around BI for AX, extending the reach of AX with Office 2013 and more! Till Next Time!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

AX 2012 - EP Warranty Management - AOT, Package & Deploy

I hope everyone is off to a great start. I wanted to continue our series today, on Enterprise Portal Design & Development, with the functional scope of Warranty Management. So far, we have had two post that has really started this EP dive. First, we focused around creating a new page on our EP instance for warranty management. From there, we were able to move forward, and add the warranty page to the navigation of our EP instance.



So far we have focused our efforts on specific task around SharePoint for page management, as well as task within the AOT for adding our Warranty Page to the Home Web Module, as a sub-Web module. This had both SharePoint and AOT specific task to complete. It's important to understand as we press forward with the focus around our EP journey that management of different aspects happen either within SharePoint or the AOT. What's also important, is that we always try to do whatever we can within AOT. This allows for correct placement of things like business logic, and further allows for us to focus on management and deployment of such created artifacts.



With that in mind, the first part of today's post will focus on adding our EP page, to the AOT itself. The biggest reason for doing such a task, is to enable promotion, version control and deployment options of EP custom artifacts from Microsoft Dynamics AX 2012.

I always like to point out existing resources that help us build upon a topic of focus, and this specific one is not different. We have, on MSDN a nice walk through of adding custom pages for EP to the AOT. How to: Import Pages into the AOT [AX 2012].

From the article.:
"If a page in Enterprise Portal will be packaged and distributed to other Enterprise Portal installations, a copy of the page definition must be imported from SharePoint into the AOT. From the AOT, the page can be packaged for distribution to other Enterprise Portal installations."

As the above states, and why we care to focus on this point, in order to package and deploy a custom page from one instance of AX 2012 to another, we need to have the page's definition living as a part of the AOT. This is a paint point that existed before with EP, and now with AX 2012 - packaging and deployment of EP pages has become easier. Lets now take the time, and do a walk through for adding our custom idbWarrantyManagement page definition into the AOT.

This is a very straight forward task, and it builds upon having successfully tied a URL Web Menu Item, to our custom page. Having done this, we simply need to highlight our URL Web Menu item, right click and then left click on import page.



Having done this, we should now see our page living under the AOT / Web / Web Files / Page Definitions. Keeping with best practice's for Microsoft Dynamics AX we need to make sure and create a new project group, and place our page definition within our idb project, as shown below.



From this point, we are now able to promote the page, along with any other scope we create for our Warranty Management Enterprise Portal Solution. This allows for ease of deployment, to help close our this post we have another MSDN walk through.: How to: Deploy Pages from the AOT [AX 2012]

To finish this then, once we moved our project, via Model File, Model Store or XPO - to a target instance of AX 2012, we can simply highlight the page definition, right click and left click on deploy. It will use the web site information we have setup for Enterprise Portal, contained within the System Administration module.



That's all I wanted to cover on this part of the Enterprise Portal post. We will continue with this series, as we move forward and add tables, classes, and web forms in a View-Edit design pattern choice. This will be to manage our Warranty Management master & reference data. I hope everyone has a great and productive week. Check back soon as more to come! Till Next Time!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"