When you port your application to a different platform (e.g. x32 to IA64) or an alien application try to adapt for your platform you may encounter problems related to DLL loading. General loader information is not enough to investigate the problem. If the problem is caused by the DLL initialization routine there's no way to find it except to debug or to enable loader snaps.

To enable loader snaps you have to create a registry key:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Name Execution Option\<your application name.exe>

and put the following value in it:

GlobalFlag = REG_DWORD:0x2

Now you can attach the debugger without source code or Dependancy Walker and read loader log.

There's more information on debugging LoadLibrary failures on the MSDN blog. You can also use Gflags utility to do the registry modification for you.