Install Reporting Extensions on a named instance of SQL Server

Install Reporting Extensions on a named instance of SQL Server:

Installing Reporting Extensions on a default instance of SQL Server is a straightforward step but installing Reporting Extensions on a named instance is a little bit of a challenge. If you install Reporting Extensions from the GUI then you need to go and make some modifications on the registry but here I have used the Ax Management Shell and deployed the reports.

Note: I have installed three instances of Reporting Services on the same box.           Based on this setup, i have installed reporting extensions on the named           instance of SQL Server 2014 Reporting Services.

  1. The first step is to use the cmdlet AxReportInstanceExtensions and ReportServerInstance with the Install command. The generic format is

Install-AxReportInstanceExtensions – ReportServerInstance  <Nameoftheinstance>  -Credential <logindetails>

Featured image

    2.  This will automatically create the Report Server configuration ID under the          System Administration section. The Report Server Configuration is available          under System Administration -> Setup -> Business Intelligence -> Reporting         Services -> Report Servers

 Featured image

           This will open the Reports Server Configuration ID window. The configuration             ID is already created because the installation task is done through the Ax            Management Shell.


3.  The next step is to create the DynamicsAx Folder where the reports will be      deployed. Validate the settings of the DynamicsAx folder and this will check the      connection string and if the connection is successfully established the following      message will be displayed.

Featured imageFeatured image 4.  On successful deployment, the message Deployment completed must be       displayed.

Featured image

Featured image


Changing company logo on an Enterprise Portal page in Microsoft Dynamics Ax 2012

1. After installing Enterprise Portal, the home page and all the pages have the      Microsoft Dynamics Ax Logo set, by default.

Featured image

2. To change the company logo on the Enterprise portal page and to replicate the     changes on all the EP pages, please refer to the file defaultax.master.aspx file. This     is a .aspx file. The default location of this file is as mentioned below.

<%systemdrive%>:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\FEATURES\DynamicsAxEnterprisePortal

    At the above mentioned location, you will find a defaultax.master.aspx file. Edit     the line highlighted below.

Featured image    Before changing the logo, add the new image file to the location mentioned below.

 <%systemdrive%>:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ep\images

     For example, if you have created .png image file by the name      newdynamicslogo.png , then paste it to the image folder available under

         C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ep\images

     Now, replace the following line of code in the defaultax.master.aspx

Featured image

3.   Refresh the Enterprise Portal page, after the changes are saved on the       defaultax.master.aspx and the changes will be instantly reflected on the       Enterprise Portal site collection.

Featured image

Cumulative Update 8 for Microsoft Dynamics Ax2012 R3

With release 3 of Microsoft Dynamics Ax 2012, Microsoft has released Cumulative Update 8. Cumulative Update 8 is available through the link mentioned below.;EN-US;2998197

This KB 2998197 article highlights the bunch of issues resolved through CU8.

Hotfix Description Build numbers
Cumulative Update 8;EN-US;2998197 6.3.1000.309
Ax Kernel level build 6.2.1000.1437

Recently, a new kernel level build has been launched for Microsoft Dynamics Ax 2012 R3. The new kernel level build is available on Lifecycle services.

This build is used to fix Excel add-ins issues.

With Microsoft Dynamics Ax 2012 R2, the latest build numbers available are Cumulative Update 7 and Cumulative Update 6. Cumulative Update 6 and Cumulative Update 7 can be downloaded through the links below.



Build numbers

Cumulative Update 7;en-us;2885603 6.2.1000.4051
Cumulative Update 6;en-us;2850972 6.2.1000.1437

Note:   While upgrading from Cumulative Update 6 to Cumulative Update 7 on Microsoft Dynamics Ax2012 R2, just                          ensure that you backup the model store database, because at times the model store crashes post CU7 upgrade.

Feature Pack 1 has released for Microsoft Dynamics AX2012. This build of AX2012 is called Build 6.0.1108.xxxx. For industrial solutions the Feature Pack is shipped as 6.1.1108.xxxx (Process Industries, Service Industries, and Public Sector). There are situations where Feature Pack 1 is not applied but the Cumulative updates 1,2 or 3 are deployed. In such situations, the build of AX2012 will be applied as 6.0.947.xxxx, where xxxx stands for the patch updates or version of the binary patch update.

All patches applied to these build will be binary files and this will be represent the xxxx.  This applies same for build 6.0

Feature Packs and Cumulative Updates 1,2 and 3 for Microsoft Dynamics AX2012 can be downloaded from PartnerSource through the link mentioned below. Also remember, that Feature pack will update the Application database and Cumulative Update 2 will update the model store database.

Feature pack 1 for Microsoft Dynamics AX2012:;EN-US;2709934

Cumulative Updates for Microsoft Dynamics AX2012:

  •  Cumulative Update 1:,en-us,2579565

  • Cumulative Update 2:,en-us,2606916

  •  Cumulative Update 3:;EN-US;2709934

Enable Best Practices check on X++ Code in Microsoft Dynamics Ax

1.  The first step to follow before enabling best practices check in Microsoft Dynamics      Ax 2012 is to Go to Tools -> Options and select Best Practices.

Featured image2.   In the next step, select the Best Practices option in the Tools window and ensure       that the best practices are set across all the nodes in the table.

Featured image

Featured image

3.  The next step is to set the Diagnostic Level to Level 4. This will trigger the best          practice check in the MorphX framework.

Featured image4.  Under Diagnostic level, choose Level 4.

Featured image

How to resolve the AxActionPane SharePoint.dll error in AX2012 Enterprise Portal Details page??

AxActionPane control is used to display the ActionPane at the top of a Web Page in Enterprise Portal. The figure depicts the Microsoft Dynamics AxActionPane control.

AxActionPane can be added through Visual Studio, either through code or as a Web Part called “Action Pane” in your Microsoft Dynamics AX Site Collection.  After adding the Web Part, the web part will be named as AxActionPaneWebPart.  To add it through a web part is a little easier but at times, there are possibilities where the pack() and unpack() functions do fail while loading the Details page. Hence, it is always better to add the ActionPane through ASP.NET code on your Visual Studio project for the Details page.

The ActionPane called as AxActionPaneControl requires a reference to a dll file while loading the control in the details page. This control uses Microsoft.Dynamics.Framework.Portal.SharePoint assembly. To register this assembly, one needs to ensure that the following is added into the Web user control file.

1. The First step is to open the Visual Studio project through the Visual Studio Projects -> Web Application Projects -> <nameoftheProject>.sln file.  Ensure that the Visual Studio project is opened through the AOT. This improves the refresh rate i.e. the end result of any change being made to the Visual Studio project can be immediately noticed on the Web Browser.

2.  The next step is to add the following line of code

Registering the assembly file Microsoft.Dynamics.Framework.Portal.SharePoint

3.    Once you register the assembly file and try to execute the code, the compiler will not be able to find the Library Microsoft.Dynamics.Framework.Portal.SharePoint.  You will receive the following error. Remember that the Web Menus are created are defined before adding the AxActionPaneControl. Web Menus can be defined under Web node through Web -> Web Menus. Ensure that the DataSource and the Datamember property of the AxActionPaneControl are set correctly.

SharePoint.dll error

This is because the reference to the assembly file is not being added under the References section of the VisualStudio solution <nameofTheProject>.sln. This reference is not found under the SharePoint assemblies section. SharePoint assemblies are available under <%systemdrive%>\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI.


The reference to Microsoft.Dynamics.Framework.Portal is available under <%systemdrive%>\Program Files (x86)\Microsoft Dynamics AX\60\Client\bin\Microsoft.Dynamics.Framework.Portal.SharePoint.dll. To add this file go to the Solution Explorer Window in Visual Studio and add the reference to the project and now compile the details page project.

4.   Now, compile the project and you are all set to run the AxActionPaneControl on your Details Page.

Note:   This is still an issue with Microsoft Dynamics Ax2012 R1 and R2, but has been fixed in Microsoft Dynamics Ax 2012              R3.

Unable to Contact Server Name

Unable to contact Server Name http://<servername>/DynamicsAX6HelpServer/HelpService.svc:

1. The first requirement is to setup .NET Framework 4.0, version 4.0. Even, after installing .NET Framework 4.0, ASP.NET 4.0 is not recognized by ApplicationHost.config. This is one issue where the Windows Process Activation Service (WAS) is not able to recognize .NET framework 4.0.
ApplicationHost.config is found under the section,

To ensure that ApplicationHost.config recognizes .NET Framework 4.0, we need to run the following command:
Aspnet_regiis.exe /iru
The above mentioned command needs to be run in the following section
<%systemdrive%>/windows/Microsoft .Net/Framework64>

2. The next possible reason for the issue could be browsing of Content Directory and there is a possibility that Directory Browsing is not enabled on the Help Server website. This is very critical.

Enable Directory Browsing to browse the Virtual Directory
Enable Directory Browsing to browse the Virtual Directory where the Help Server content is stored.

This will allow one to browse the contents stored in the virtual directory of Help Server.

Enable Directory Browsing
Enable Directory Browsing

3. The final step is to install Indexing Services Role (if it is not installed) which is available under Administrative Tools -> Server Manager -> File Services -> Indexing Service

Once Indexing Service is installed go and enable the Indexing option on the Content directory for the Help Server. Go to Control panel and in Control Panel search for the Indexing option.

Indexing Options
Indexing Options

On the Indexing options window, select the directory on which indexing needs to be enabled. Browse to the content directory in the virtual directory of the HelpServer website and ensure that the content directory is indexed as shown in the screenshot below.

Enabling the Indexing Option on the Content Directory in the Help Server

If the Help Server is not connecting even after enabling all these services, then re-installing the Help Server should solve the problem.

Microsoft Dynamics Ax7/Ax2015

The Microsoft Dynamics Ax team has revealed its statement of direction in Partnersource, where the team has clearly stated that the next version of Ax will be targeted towards HTML5/XAML.

The Statement of Direction for Microsoft Dynamics Ax has been released and you can download it from Microsoft Dynamics PartnerSource. The future of Microsoft Dynamics Ax will target HTML5/XAML.

Microsoft has streamlined its architecture for Windows Phone 8, Windows 8 and soon it will be streamlining its architecture considering the idea of natural user interfaces for products like Windows, XBox etc…

Visual Studio LightSwitch which is the limelight of Visual Studio 2012 and Visual Studio 2013 helps create Line of Business Applications that target any device concept with UI specific features in the future for Microsoft Metro UI. Using LightSwitch, it will become easier for developers to develop lightweight applications that are device independent. One can have the same UI applicable across all platforms.

“Three screens and a cloud” was revealed by Microsoft CEO Steve Ballmer while evangelizing Windows Azure around Fiscal Year 2011 but now its true. The vision of Three Screens and a cloud is finally taking shape at Microsoft