App built with PSXE 2016 fails on target system with PSXE 2016 redist and vc_redistx64.exe installed

[Lars_H_]

Steve, we have a code that worked when built with the previous version of the compiler using Visual Studio 2010 Shell.  It also works on the latest version2016.0.110 using the Visual Studio Community 2015 but only when run on the on the computer where the Intel 2016.0.110 is installed.  It acts up when opening a simple file (Form="FORMATTED") on other computers whether using status="NEW", or Status="REPLACE", or Status="UNKNOWN".  On the other computers, I have installed the redistributable files ww_ifort_redist_intel64_2016.0.110.msi and vc_redist.x64.exe because a vcruntime140.dll was needed. Are there other files I need to install (or update) on other computers for them to run the code built with 2016.0.110?.  Thank you, Lars

[Kevin_D_Intel]

I am not aware of additional packages that are required for what you described having tried. I also don’t have a matching environment immediately available to test this.

Can you provide some additional details about how is it failing exactly?

[Lars_H_]

Yes I have found the same problem has been reported by other on another Intel forum "bug with open statement".  It is related to system resources available when opening a file which leads to error code 30 and which is also listed as forrtl: FormatMessage failed for system message number 1450.forrtl.

The effect is that a file is created but with zero length and no content as soon as the error message occurs.

I am hoping for a fix soon and in the meantime will need to back to the previous version of the compiler.

[Kevin_D_Intel]

Ok, the other post titled “bug with open statement” is here, https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/590293. I just posted an update there about the underlying defect (DPD200375683) being fixed in the upcoming PSXE 2016 Update 1 that is due to be released in a couple of weeks. I am hoping to test the fix myself soon.

There's a few other threads with related discussions on this defect, another is here.

[Kevin_D_Intel]

Lars, I confirmed test cases for the other reports of the problem you experienced are fixed by the Intel® Parallel Studio XE 2016 Update 1 now available from the Intel® Registration Center.

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