Unable to start program "C:\...."

[Sebastiaan_M_]

Hi,

Within our organisation we have a problem with the Intel Visual Fortran Compiler. When a user tries to compile a program in Debug-mode (F5), the following error occurs:

Unable to start program "C:\<path to project>"

We are using Microsoft Visual Studio 2010 Professional 10.0.30319.1 and Intel(R) Visual Fortran Composer XE 2011 Update 7 Integration for Microsoft Visual Studio* 2010, 12.1.3518.2010

Does anyone know how to solve this problem?

[Steven_L_Intel1]

F5 starts the program under the debugger - it does not compile the program. You haven't built the executable yet, which is what leads to this error. Use F7 to start the build, then use F5 to start debugging. Don't forget to set a breakpoint first.

[Steven_L_Intel1]

There is a setting in Visual Studio that controls this behavior. Tools > Options > Projects and Solutions > Build and Run. Change "On Run, when projects are out of date" to either "Always build" or "Prompt to build".

[Sebastiaan_M_]

I am the IT guy that tries to solve the problem for the employee, so sorry if I say something that is not correct :).

I followed you steps, I first build the exe and then tried to use the debugger. Visual Studio immidiately shows the error message as stated in my first post. So the problem is not solved by this. Do you have some other thoughts?

[Steven_L_Intel1]

Did the program successfully build? Does the EXE file named in the error message exist? Please attach a ZIP of the buildlog.htm file from the Debug subfolder so I can see what happened.  Please also include a screenshot of the error message.

[Sebastiaan_M_]

I included the screenshot with the buildlog in the attachment.

[Steven_L_Intel1]

Hmm - that is very strange. Does the same error occur if you use CTRL-F5 to start without debugging? Can you run the program by double-clicking on it in the folder? (The console window will disappear when the program exits, but you shouldn't see an error.)

What if you create the project in a different folder, say, C:\test ?

[Sebastiaan_M_]

Hi Steve,

We found the solution for this problem. The problem was a script that was executed during deployment of a PC. This script included a command that added some environmental variables (PATH), but in this command there was made a typo which caused the problem. As soon as we corrected the variable, VS debugs without any problem.

Thanks for you help!

[Steven_L_Intel1]

Glad to hear it!