IDMF Post Installation Issue : ODBC Connection

After the installation of the IDMF there are some post installation steps to do. One of them is to populate the IDMF Management database with data from the Cross Reference.

To do this, some job has to be run on the production database that makes connection to the IDMF database by ODBC. When I tried to do this I get the error that the connection failed. Therefor I have made a little change to the classes responsible for the population.

The DMTPopulateManagementDBcreateConnection method is altered to work with a DSN (for some reason it did not work for me if not using a DSN) (And please don’t mind the hard coded name J)

For this to work, we need to create a system DSN on Windows to point to the SQL Server database. So we create one:

But there is one issue here: On a 64-bit 2008 Server, the dynamics client will not find the 64-bit DSN created, so we have to start the 32 bit version of the ODBC Tool.

When the 32 bit DSN is created, it worked for me.

5 thoughts on “IDMF Post Installation Issue : ODBC Connection

  1. Hi Kenny,

    This error can occur when you’ve installed the AX client in combination with SQL2008 client components. The IDMF framework apparently needs the “SQLCLI.DLL” ODBC driver from SQL Server 2005 setup in order for the AOS to communicate with the IDMF database.

    Creating a system DNS is one way to solve this… Another is simply to install “SQLNCLI.MSI” (32-bit OS) or “SQLNCLI_64.MSI” (64-bit OS) from the installation media (\Servers\Setup folder).

  2. Nice one Geert! 🙂
    I’ll remember this one when installing the 2009 version of the IDMF.

    I was actually glad to see that this is not needed anymore when installing the Dynamics Ax 2012 version of the IDMF. A lot of the setup went more smoothly then before 🙂


  3. Hi While doing the post installation steps in IDMF , after the completion of metadata Synchronization i have encountered an error while importing summation XPO. \Classes\DMTVirtualSummaryTrans\updateVirtuelTransferClosing – The wrong number of arguments has been specified for the method. Anyone seen this before or any ideas what needs to be done.. This is on AX2012 BTW.

Leave a Reply

Your email address will not be published. Required fields are marked *