I encountered an interesting problem:
An error "UnsatisfiedLinkError" with the message "The specified procedure could not be found"
Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\Test\TestJNI.dll: The specified procedure could not be found
Whilst the JNI dll was happily being detected, it turns out that an incorrect version of a dependent dll was also being attempted to be loaded from a different directory in the library search path, triggering the above error message.
So my question is: Short of checking all directories for the presence of this incorrect version of a dll, is there a way to determine which directory the dll was attempting to be loaded from?