Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29378 Discussions

Intel Parallel Studio XE 2016 evaluator dll

tiho
Beginner
1,725 Views

I get the following error when I try to debug

"an error occurred while attempting to load an expression evaluator dll"

I tried reinstalling and repairing options but the error persists. Any ideas for resolving it?

0 Kudos
6 Replies
Kevin_D_Intel
Employee
1,725 Views

I have not found any similar reports like this so let’s start with details about debugger related files under:  C:\Program Files (x86)\Microsoft Visual Studio XX.X\Common7\Packages\Debugger

In the folder path above, please substitute “XX.X” for your particular version of Visual Studio (e.g. use “11.0” for VS 2013).

For the files listed below, can you please capture File version details for each by either hovering your mouse over each to view details or using the right-click Properties > Details tab.

cppdebug.dll
FEE.dll
ForDbgEE.dll
ForDbgSW.dll
NatDbgEE.dll

Couple of other questions:

- Did or do you have any earlier version of Parallel Studio XE installed on your system?
- What version of Windows are you using?

0 Kudos
tiho
Beginner
1,725 Views

 

I have 

cppdebug.dll 12.0.21005.1

FEE.dll 16.0.464.1

ForDbgEE.dll 16.0.464.2010

ForDbgSW.dll 16.0.464.2010

NatDbgEE.dll  12.0.21005.1

I did have prior versions Microsoft Visual Studio 10.0, Intel Fortran 12, 13, 14, but all of these are uninstalled. Although some of the unistalls had errors and did not uninstall completely.

This is on Windows 7.

 

 

0 Kudos
Kevin_D_Intel
Employee
1,725 Views

Thank you for those details. I forwarded this and the description to the Debugger team for some assistance. It is possible we may have recently received another issue similar to yours. I need a few more details about your case though.

I should have asked earlier, what version of Visual Studio are you using with the PSXE 2016 release?  

If you are using VS 2013, is that the full version or the VS Shell provided with our product?

You mentioned experiencing this when debugging, is your app Fortran or mixed language, was this error related to host debugging only, meaning there is nothing involving Intel Xeon Phi™ here, correct?

(Internal tracking id: DPD200377383)

(Resolution Update on 11/18/2015): This defect is fixed in the Intel® Parallel Studio XE 2016 Update 1 Release (2016.1.146 - Windows)

0 Kudos
tiho
Beginner
1,725 Views

Yes I am using the 2016 release. Here are the details. Full version provided with the product. The app is pure Fortran, no Xeon Phi. Only host debugging. 

Microsoft Visual Studio 2013 Shell (Integrated)

Version 12.0.21005.1 REL
Microsoft .NET Framework
Version 4.5.50938

Installed Version: IDE Standard

Intel® Parallel Studio XE 2016 Composer Edition for Fortran Windows*     Package ID: w_comp_lib_2016.0.110
Intel® Parallel Studio XE 2016 Composer Edition for Fortran Windows* Integration for Microsoft Visual Studio* 2013, Version 16.0.0046.12

0 Kudos
Kevin_D_Intel
Employee
1,725 Views

Thank you for those details. Those help confirm you are seeing the same issue reported earlier. I just learned the root cause of this debugging issue relates to missing Microsoft Visual C++ redistributables that affect the debugger under the Microsoft Visual Studio 2013 Shell.

Can you please first verify whether you have the Visual C++ 2012 Redist package present on your system (via: Open Start Menu \ Control Panel \ Programs & Features \ search for "C++ 2012 Redist")

If you do not, the version needed can be downloaded from Microsoft here, https://www.microsoft.com/en-us/download/details.aspx?id=30679. Download/install the vcredist_x86.exe. (Note: the x64 version will not resolve the issue.) After installing, please retry the debugging.

In our upcoming PSXE 2016 Update 1, the installation has been enhanced to the check for the presence of these C++ redistributables along with the existing additional check for the Microsoft Windows SDK 8.1 for Windows necessary for using the Microsoft Visual Studio 2013 Shell.

0 Kudos
tiho
Beginner
1,725 Views

This fixed the problem, Thank you.

0 Kudos
Reply