Open

I found the solution to the problem. Hopefully this will help someone else--these problems can be so frustrating to debug.

The problem was caused by third-party software that had added itself to the path and installed msvcr90.dll in its program folder. In this case, the problem was caused by Intel's iCLS Client.

So... How to find the problem in similar situations?

1. Download Process Explorer here.

2. Start your application and reproduce runtime error R6034.

3. Start Process Explorer. In the "View" menu go to "Lower Pane View" and choose "DLLs".

4. In the top pane, locate your application and click on it. The bottom pane should show a list of DLLS loaded for your application.

5. Locate "msvcr??.dll" in the list. There should be several. Look for the one that is not in the "winsxs" folder, and make a note of it.

6. Now, check the path just before your application runs. If it includes the folder you noted in step 5, you've probably found the culprit.

How to fix the problem? You'll have to remove the offending entry from the path before running your program. In my case, I don't need anything else in the path, so I wrote a simple batch file that looks like this:

path=
myprogram.exe

That's it. The batch file simply clears the path before my program runs, so that the conflicting runtime DLL is not found.