In our programming department we have some programs still in VB6. And every now and then an error will popup after compiling a dll. The error just states "Error in loading DLL." No error number or anything.
From then on every time we try to open the dll project that error pops up. We have checked all the references for the project and they are fine. The issue seems to be with VB6 wanting to open the DLL of the project.
So far sometimes restoring from a backup of the project fixes it for a while, sometimes re-registering it fixes it for a while.
I looked at MSDN and found code to use the LoadLibrary API function and ran it on the most recent offending dll and it gave the error code 0, which means "System was out of memory, executable file was corrupt, or relocations were invalid."
I checked the machine and there as no memory issue. As for the other 2 options, I am not sure how to check for those.
Any help would be appreciated.