Error Code: -17004, Could not load DLL or library

Question

Hi All,
I am getting the following error message:
Error loading step 'x' of sequence 'MainSequence' in file 'y'.  Could not load DLL or external library C:\bin\driver.dll
Error Code: -17004, Could not load DLL or library.
Source 'TSAPI"
My main DLL is one written in C in LabWindows.  This DLL calls a second DLL that was written in Visual C++
I am using TestStand 2010 SP1 as well as CVI/LabWindows 2010.  I have WinXP Professioanl SP3.
This same sequence, DLL1, and DLL2 have worked together in previous versions of TestStand!!!!  All I did was upgrade to Developer Suite 2011.......??????
I have reviewed all the posts regarding this problem and have so far done the following:
1.  Verified Both DLL1 and DLL2 reside in the same directory
2.  Copied DLL2 into C:\Windows\system32
3.  Used Dependency Walker to verify that there are no other missing DLL's
4.  Unistalled Explorer 8 and installed Explorer 7 because of somthing I saw in depends and something I read while researching this problem.
5.  Verified the Search Directories in TestStand
I am wits end, as I cannot determine what the problem is and any suggestions would be welcome
Solved!
Go to Solution.

Answer 1

So I did come up with a solution to this problem, but I don't understand why it solves the issue.  Hopefully some of you can provide some insight.
So all my sequences were experiencing the problem described, and all sequences basically call the same dll's over and over.
I have a dll that I use as my "main" dll.  All my sequences use this dll and I continually add more functions as our company designes new products, etc.  This dll uses functions that are from my CommDll.  The CommDll was written in C++, and it is also used in several other dll's that my sequence call's as I use it for all serial/telnet requirements. 
So my test sequences for example calls the following dll's usually in this particular order ---
DbDriver - This dll handles all the database functioanality for our products, and calls libMysql.dll
PwrController.dll - this dll controls a pwrcontroller for all power on/power off, reboot, etc of our product.  This dll calls the CommDll.
CompanyDll - This is the "main" dll that hadles all the cli commands and other test functions that our product requires.  This also calls CommDll.
When the sequence calls are done in the order above, it does not work..  However, if I switch the sequence file to call the CompanyDll before the PwrController.dll everything works fine.  Is there an order of operations here????
I also found that when I compiled my PwrController.dll with CVI 2010, it gave me an error could not load PwrController.dll no matter what order the seqence calls were, leading me to believe that I am missing something when building this particular dll.  As soon as I copy the original, developed and compiled in 2006, everything works again.
Thanks,
greggj