Rahul Sharma

Solutions Architect - Microsoft Dynamics AX | Azure

Blog
This is a technology blog covering Microsoft Dynamics AX, Microsoft Dynamics CRM, Microsoft Azure, IoT, .Net, SharePoint, SQL Server, SSRS, SSAS, SSIS, Apache Cassandra, MongoDB, and related technologies. Join this blog on facebook {Rahul Sharma}, to start a discussion !!! NOTE: My employer is not responsible for the content published here.

Index | MS Dynamics AX | MS Dynamics CRM
View blog as >> Magazine | Sidebar | Flipcard | Mosaic | Snapshot | Timeslide

Publish Dynamics AX client as RemoteApp on Remote Desktop Services

It is a normal practice to give users access to Dynamics AX either by installing the AX client on their computer or providing Remote Desktop so that they can connect to the computer which already has AX client installed.

We can provide more robust and rich experience to users that will give them the feel of a local application and ease of remote desktop by publishing AX client to RemoteApp server. It is same as using remote desktop services to connect to a desktop but instead of the desktop user will connect to the AX client only, giving him the experience as if it is locally installed on the user's machine.

Once AX client is published to RemoteApp server, user can access the client using the RDP connection via Remote Desktop Web Access portal or via a MSI file to install an AX icon on the desktop that will have a connection to access RemoteApp.

Dynamics AX 2012 & SQL Reporting Services 2012 Reporting Extensions Error

You might come across to this error when installing Dynamics AX 2012 Reporting Services extensions on a fresh install where you never had SQL Server 2012 installed before.

We prepared a separate server for SQL Server Reporting Services 2012. We used a slipstreamed Dynamics AX 2012 Feature Pack setup to include the AX CU3 update and SQL Server 2012 Compatibility Hotfix KB2680186 . We went ahead to install Dynamics AX 2012 Reporting Services extensions on this server but installer did not finish and complained about few missing .NET assemblies.

An error occurred during setup of Reporting Services extensions.
Reason: Could not load file or assembly 'Microsoft.SqlServer.BatchParser, Version=10.0.0.0 ...

Or

An error occurred during setup of Reporting Services extensions.
Reason: Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=10.0.0.0 ...


This error can be easily resolved by installing Microsoft® System CLR Types for SQL Server® 2008 R2
X86 Package(SQLSysClrTypes.msi)
X64 Package (SQLSysClrTypes.msi)
IA64 Package(SQLSysClrTypes.msi)

Discuss this on facebook.

Join me on facebook and feel free to post your comments / feedback / queries.

Claims-Based Flexible Authentication in Dynamics AX 2012

Dynamics AX 2012 provides a new way to authenticate users in AX, called claims-based / flexible authentication. In this approach, you don't have to create users in Active Directory first to give them access to use AX Enterprise Portal / AIF. And this is really a very nice and a way to go approach for giving AX access to external users who are not part of the organization's Active Directory structure. For example; now you are no longer required to create vendors and customers in Active Directory to have them access vendor self-service portal or customer self-service portal respectively.

Dynamics AX for Retail POS Development - Code Samples

In this post, I am going to share some .Net POS code samples to get you going with Retail POS coding.