Troubleshooting Dependency Resolution Problems with Proc Mon

Summary

This post contains some notes about how to troubleshoot errors with dependency resolutions with Proc Mon.

Overview

If you ever run into errors with text like "Could not load file or assembly '[some assembly]' or one of its dependencies. The specified module could not be found.", you can use Proc Mon to help identify the offending assembly. To do that, first download Proc Mon

• Download Proc Mon - https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx
• Start ProcMon by double clicking ProcMon.exe

• Setup filters to limit what appears in the Proc Mon log by clicking Filter -> Filter... 

• Setup the following filters then click OK
• Process Name contains (or is) "Name of the process" then Include
• Note, for this example, the name of my process was BasisConsole.exe
• Path ends with .dll then Include
• Result is Success then Exclude
• Result is FILE LOCKED WITH ONLY READERS then Exclude
• Result is BUFFER OVERFLOW Exclude

• Make sure capture trace is active

• Run your process (in my case it was just running BasisConsole.exe from a command prompt)
• Look through the results at what Proc Mon captured. This isn't an exact science and may require some investigation of the results, but in my case I found the issue was with the MSVCR120.dll not being available. I'm not positive of this, but I think you want to start with the results that have a Result of NAME NOT FOUND.