Microsoft Dynamics AX Intelligent Data Management Framework 2.0 released

We are happy to announce release of "Microsoft Dynamics AX Intelligent Data Management Framework 2.0" tool.

The Microsoft Dynamics AX Intelligent Data Management Framework (IDMF) lets system administrators optimize the performance of Microsoft Dynamics AX installations. IDMF assesses
the health of the Microsoft Dynamics AX application, analyzes current usage patterns, and helps reduce database size.

Supported products:

Microsoft Dynamics AX 2012 R3 and R3 CU8

Microsoft Dynamics AX 2012 R2

Microsoft Dynamics AX 2012 Feature Pack

Microsoft Dynamics AX 2012

Microsoft Dynamics AX 2009


Download link:


Document link:



New update released on LCS version (dated April 29th 2015)



Issues Description


During IDMF Post install step - check MSDTC enabled failing -  Package Error: CheckMSDTCEnabled" - Failed to acquire connection  "ProductionDB" - Error Code 0x8004D00E

This issue happens when there are two versions of SQL Server components installed for eg.11.0 and 12.0. But IDMF is having the SQL Server Integration services 11.0 only.

 During the PostInstallation tasks the application will try to execute the SSIS packages using the Microsoft.SqlServer.ManagedDTS(12.0) dll, which is creating the problem as SQL Server Integration services 12.0 is not present on this machine.


The changes in the hotfix ensures to check which version of SSIS is installed in the machine and load the dll of that particular version to execute the SSIS package.

 The fix will now load the versions of SSIS supported by IDMF from the config file and will check which version of MsDtsServer is installed in the machine through registry. Then it will load only the dll corresponding to the version installed in Registry


 Issues with Purging using IDMF  2.0 - Exception while executing PurgeStep 'Delete' for node 1 - Could not load file or assembly

The issues was due to incorrect version number mentioned for the dlls in the file GlobalAssemblyInfo.cs, which resulted in the build dlls not getting the version, which is creating the problem.


The dlls pointing in the App.config are of version, but the dlls generated during dll build were of version

 The changes in the hotfix to have the correct version at all places i.e