StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>One of the possible reason of an error during loading of ABQSMABasCoreUtils.dll is that some dependency module (inclusive delayed load DLLs) could not be found. Use <em>Dependency Walker</em> (see <a href="http://www.dependencywalker.com/" rel="nofollow noreferrer">http://www.dependencywalker.com/</a>) to examine all dependencies of ABQSMABasCoreUtils.dll.</p> <p>I have two suggestions:</p> <ol> <li>Verify that you can load ABQSMABasCoreUtils.dll with respect of <code>LoadLibrary</code>. You don't need call any function from ABQSMABasCoreUtils.dll. Usage of <code>LoadLibrary</code> I don't see as the end solution. It' s only a diagnostic test. With the test you can verify either you have some general problem of loading ABQSMABasCoreUtils.dll in your program or you have some kind of process initialization problem.</li> <li>If loading of ABQSMABasCoreUtils.dll with respect of <code>LoadLibrary</code> will failed, then use profiling feature of Dependency Walker to protocol of all calls done during loading of ABQSMABasCoreUtils.dll. One other way would be usage of Process Monitor (see <a href="http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx" rel="nofollow noreferrer">http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx</a>) to trace what file and registry operations will be done during loading of ABQSMABasCoreUtils.dll.</li> </ol> <p>If <code>LoadLibrary</code> is not failed, then you have really an initialization problem of DLLs. Typically the problem exist if a DLL inside of DllMain try use a function from another DLL which is not yet initialized (not yet returns from DllMain). Before one start diagnostic of this problem, we should try to exclude a more simple problems with <code>LoadLibrary</code>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload