still cant get MKL to work

[WSinc]

I installed parallel Studio 2018, update 3, and it gave me the VS 2013 shell, which I used

to run this simple program. However, it still found a missing entry point, although it DID

try to use the MKL library. 

Obviously, something is wrong with the way the LINKER is used here.

So what is this entry point it could not find ? I dont know the purpose of this. Does anyone ?

BTW, I tried all 3 choices for the QMKL choice, as to which MKL libary to attach.

But none of them worked - I got a missing entry point for all 3 choices.

see screen shot.

[WSinc]

I cant get that WMIC command to do anything.

This is why we need remote assist.

[Steve_Lionel]

Bill, you're not going to get remote assist here. File a support ticket against MKL if you want official support (though that's no guarantee of remote assist.) I'll comment that it's not Intel's responsibility to walk you through using your computer, which it increasingly sounds like what you're asking for. You're also using a 2-year-old version of MKL, but have a newer one installed (from the error message you posted earlier). As more than one of has noted, MKL has been willing to break compatibility in new releases.

[WSinc]

Well, the forum people ASSUME that we know all the ins and outs of navigating thru all these system commands.

For instance, mejec4 tried to get me to use that WMIC command, but when I tried it, it got absolutely nowhere.

Would have helped if he told me to open the COMMAND window first. Well, at least I knew about that.

Is this the level of support we should expect ?

That's why the remote assist is so important - - - 

It saves a lot of time on BOTH ends. We are not all systems GURUS like you are.

This used to be really easy to work with - - 

now its a godawful complicated mess.

BTW, the missing entry point is also seen with later versions of VS, like 2013.

and they told me to uninstall it - that why I am back to VS 2010.

I just want something that works. Is that expecting too much ?

[WSinc]

Here is that BSENV. txt file you wanted.

Please see attached.

---------------------------------------------------------------------------------------------------------------------------------------

I asked several times, what is the purpose of that missing entry point ?

That would give a valuable clue as to whats going on.

apparently in the (verbose) BUILDLOG, I dont see that it's even searching for that entry point,

so that raises the question of why its even needed to start with.

Is that a BUG ? Does anyone know the answer ?

arent we entitled to have something that works ?

[mecej4]

Thanks for finally sending the environment information. I can see from that information that you had, at one time or another, Parallel Studio 2013SP1, 2016U4, 2017U1 and 2018U3. If one or more MKL DLLs from 2013SP1 got used in place of the same DLL from a later version of Parallel Studio, the "missing entry..." error could occur. Even if you do not currently have all these versions installed, remnants of the installations may still exist and cause problems.

Inside a command window, type wmic /output:InstallList.txt product get name,version and press the Return key. The program may take a minute or two to run; please wait until the command completes, and attach the resulting file installList.txt to your reply.

You asked several times, "what is the purpose of that missing entry point?" Libraries such as MKL and IMSL often have lots of "internal" subroutines and functions that are not covered in the user documentation. The MKL DLLs are interdependent, and there may be calls to such entry points in one MKL DLL from the code in another MKL DLL. External users, such as you and me, have to be content with the general description of their purpose as "to make things work". Even if you were to obtain the "insider information" on these entry points, there is nothing that you can do using that information to fix the problem.

If you have a consistent and coherent software installation, you should never see these "missing routine xxx in yyy.dll" messages. See the last paragraph of #2. 

[WSinc]

OK, here is the output from the WMIC command.

-------------------------------------------------------------------------------------------

How do we know what is "consistent and coherent" ?

Even when I do the uninstall and reinstall steps, I get the same result.

This was at the direction of your forum advisers, BTW.

If it is not consistent and coherent, shouldnt it tell me why ?

Why doesnt anyone know what that missing routine does ?

[mecej4]

Thanks for the WMIC output. It shows that you still have various parts of Composer XE 2013 SP1 installed. 

Do you (or any other users of your PC, local or remote) use them? Do you use any third party packages (some FEA program such as ANSYS, Abaqus, etc.) that use Composer XE 2013 SP1?

If not,  uninstalling these parts of Composer XE 2013 SP1 (you take responsibility for the consequences of uninstalling) may solve the problem. As I stated in #13, this old version, which I still have on my PC, has MKL DLLs that lack some of the entry points that are present in the MKL contained in Composer XE 2016.

If the Composer XE 2013 SP1 components are required to be retained, we can explore alternative courses of action.

[WSinc]

i AM THE ONLY USER, AND i DONT USE ANY OF THOSE OTHER software items.

However, when I revert back to VS2010, I still get the same error message.

In other words, by uninstalling VS 2013. How do I know if it is completely gone, though ?

I looked, and did not see any pathways to VS 2013. But you still think I have some of those components ?

[mecej4]

I did NOT ask you to do anything to VS2013 or any other version of Visual Studio. Visual Studio is a Microsoft product (a subset "shell" is packaged with Parallel Studio/Intel Fortran Composer by Intel for customers who do not already have Visual Studio).

It is Intel Composer XE 2013 SP1 Update 6 for Windows* that I recommended you to uninstall. And "uninstall" means the following in Windows 10: Start Menu → Apps→ Settings → Apps & features; select "Intel Composer XE 2013 SP1 Update 6 for Windows*", then press the Uninstall button.