Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
45 Views

The procedure entry point could not be located in dynamic link library

Jump to solution

Hi,

I wrote a fortran program using vs comunity 2013 and intel parallel studio 2017

when I run the code inside the IDE (using ctrl+F5) the program works fine ( both debug/release) but when I go to the release ( or debug) folder, both x86 and x64,  and try to run the exe file I get this error:

"the procedure entry point mkl+serv_point_verbose_info could not be located in the dynamic link library mkl_sequential.dll"

I am wondering if any body can explain to me why I get this error and how to fix it?

Also I want to know why the code runs inside the IDE and dosent work using the very exe file IDE produced?

Thank you all in advance

 

0 Kudos

Accepted Solutions
Highlighted
45 Views

When you run from inside the

Jump to solution

When you run from inside the IDE, PATH is set up with the correct paths for the version you're using. If you run from outside the IDE (or a compiler build command prompt), you get whatever is in the system PATH environment variable. The MKL DLLs are not automatically added to the system PATH when the product is installed.

You probably have an old MKL folder in the system PATH environment variable and should update it.

Retired 12/31/2016

View solution in original post

0 Kudos
3 Replies
Highlighted
Black Belt
45 Views

What do you mean by "go to

Jump to solution

What do you mean by "go to the release ( or debug) folder"? If you simply opened a command window and changed to one of those folders as the working directory, or used the Windows Explorer to open the directory, and then attempted to run the EXE by typing its name or by double clicking its icon, the MKL runtime DLLs may not be on the execution path. Open a command prompt configured for Intel Parallel Studio, and run the EXE from that console.

0 Kudos
Highlighted
46 Views

When you run from inside the

Jump to solution

When you run from inside the IDE, PATH is set up with the correct paths for the version you're using. If you run from outside the IDE (or a compiler build command prompt), you get whatever is in the system PATH environment variable. The MKL DLLs are not automatically added to the system PATH when the product is installed.

You probably have an old MKL folder in the system PATH environment variable and should update it.

Retired 12/31/2016

View solution in original post

0 Kudos
Highlighted
45 Views

Thank you both very much

Jump to solution

Thank you both very much

I checked the path and as Steve mentioned MKL was not there!

 

0 Kudos