Using Fuslogvw.exe to Find Missing Referenced DLLs in Microsoft Dynamics AX 2012

Posted on: April 17, 2017 | By: Jarrod Kraemer | Microsoft Dynamics AX/365

Authored by: Craig Leska – Senior Technical Consultant

Recently, I faced an issue where a clean compile could be generated on one AOS, but not another one in the same environment due to missing referenced DLL.  In this blog, I will walk you through the process to use to find out what DLLs are being referenced and whether they load or fail.

After we made some changes and our compile finished, there were several errors that were being reported back to.

The errors present are related to the same missing reference DLL.

 

Screenshot of the error when trying to open the Analysis Server form.

 

After looking in the /bin folder, it appeared that the Microsoft.Dynamics.AX.Framework.Analytics DLLs were present on both AOS servers with the same versions.  The obvious error was eliminated and the next step would be to use the fuslogvw.exe tool.

Fuslogvw is an assembly log viewer and part of the .NET framework. The location on my machine is “C:Program Files (x86)Microsoft SDKsWindowsv7.0ABin.” The actual location on your machine may vary.  Fuslogvw is ran through an elevated command prompt or through explorer and run as administrator.

We will want to configure logging. Click Setting and then select “Log bind failures to disk” and check enable custom logging path I like to use C:Tempfuslogvw, as in my example and click OK. Do not close the log viewer at this point

 

Next we will need restart the AOS service and then click Refresh in the assembly log viewer. This will log all the failed bindings that AX service is calling.

Don’t be surprised if you see more displayed in the log file, but you should check it out. I am not using retail in my setup. Your mileage may vary and it wouldn’t hurt to check out all events being returned.

We see there is an entry for Microsoft.Dynamics.AX.Framework.Analytics, this is what we are looking for simple double click that entry or click the “View Log” button to open the logging for it.

Here we see the binding error, a look on Bing.com shows that the Microsoft.AnalysisServices.DLL is part of prerequisite SQL Server Analysis Services Management Objects.

 

You can use this same process to fine any missing reference DLL in AX, further digging may be necessary, but it will pinpoint what DLL the issue is with and what location it is expecting it, even if it fails due to a missing version.

In the logging entry, we see what DLL the system is expecting and from here we can act to correct the problem and get a clean compile. The action I took was to re-apply the ADMO prerequisite.

The lesson learned is to make sure you can run a clean compile on ALL AOSs in the environment. A lot of the time you are dealing with third party software and those components should be applied to all AOS in the environment, which sometimes get missed. As in one of my previous blogs, there are no shortcuts in AX.  You must thoroughly review all your AOSs in your production environment to ensure your system is functioning at an optimal level.  

For additional information please feel free to reach out to us at info@loganconsulting.com or (312) 345-8817. 

All the best! 
Logan Consulting 
www.loganconsulting.com

25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics
25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics

Free Download:

25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics

Download the guide ›

Top 10 Inventory & Operations Decisions Distributors Are Making Blind
Top 10 Inventory & Operations Decisions Distributors Are Making Blind

Free Download:

Top 10 Inventory & Operations Decisions Distributors Are Making Blind

Download the guide ›