- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
After installing Fortran XE2016 from the setup file: "parallel_studio_xe_2016_composer_edition_for_fortran_setup.exe" (ran as administrator), three versions of Visual Studio will not start: VS2015 Enterprise, VS2013 Professional and VS2012. If it helps, I also have Intel Parallel Studio XE 2015 Update 2 installed and was integrated into VS2013 and VS2012. Intel Composer XE 2013 SP1 Update 3 is also installed, but not integrated into VS.
After installing VS2015 and restarting, I checked that VS2015 worked by opening and running a "hello world" C# project. Then I ran the Fortran XE2016 installer and gave the successful message: "Intel Parallel Studio XE 2016 Composer Edition for Fortran Windows is now installed". Starting VS2015 shows the splash screen, then a few seconds later closes (no message), and I hear the system alert "ding". Starting VS2013 gives the error: "A problem occurred when loading the Microsoft Visual Studio menu. To fix this problem, run 'devenv.exe /resetsettings' from the command prompt. Note this command resets your environment settings" (I have not tried this yet) and closes. And starting VS2012 gives the message: "Exception has been thrown by the target of an invocation" and closes.
I have checked the items Steve describes in his article about troubleshooting the Fortran integration: https://software.intel.com/en-us/articles/troubleshooting-fortran-integration-issues-with-visual-studio. The 4 DLL integration files are present in each VS directory and have what looks like the correct version for XE2016. For example in "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Intel Fortran\VFPackages" the VFProj.dll has version 16.0.46.14, which seems correct.
My laptop has Win7 SP1 x64, 16GB RAM, on the hard drive 142 GB is available out of 916 GB total.
I would like to get Fortran XE2016 installed and working with VS2015, so fixing VS2013 and VS2012 wouldn't be important. An alternative would be to integrate Fortran XE2016 into the older VS2013 so that maybe VS2015 would work for C# projects.
Is there further diagnosis I could do? Is there a Fortran installation log file that I could check?
Thanks for your help.
Greg
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The installation log file should have been left in your temp folder. It isn't always informative but it's a start. There really shouldn't be a problem installing the 2016 ifort into any or all of those vs versions alongside psxe2015. The last 2 updates of psxe2015 work with vs2015 as well. It might make sense to remove the old psxe2015 first then install the current components of psxe2015 and 2016 you want, only 1 version of tune.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I’m sorry to hear about these problems and the inconvenience, Greg. I sent you a private reply with information on the location of the installation log files that you can provide us in private so I can have our installation and IDE integration Developers inspect them for possible clues about what has gone wrong and what is needed to can get your environment working again.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Tim, Kevin,
Thank you for your replies and information. I have provided the folder of installer log files to Kevin.
After reading another new article "path pretty much hijacked" https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/595341 I checked my system path and it is very long. I copied it from the system control panel into Notepad++ to check its length, and Notepad++ gives a length of 2570 characters. Could it be that after installing Fortran XE2016 that some of the system file path has been truncated, leading to visual studio not starting as expected if it cannot locate some program files?
Regards,
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Possibly. Can you capture your current environment settings using a command like: set > c:\temp\vars.txt 2>&1 executed under a normal (i.e. non-Intel compiler) command-prompt window and also under an Intel Complier initialized command-prompt window and post those in a private reply to me. Be sure to use differently named files so the second use of this command does not overwrite output from the first.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Kevin,
I will capture the two sets of environment variables.. The basic cmd.exe gives a system path of 3060 characters. Using the Intel XE2016 VS2015 x64 initialized command window gives a path of 4918 characters. I will post the files to you separately.
Regards,
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've resolved my Visual Studio problem by running the Fortran XE2016 installer and used "modify". That allowed me to remove the Fortran XE2016 integration from VS2015 and from VS2012. I then ran the VS2015 installer using "repair", so VS2015 will start and I can build a C# project (no Fortran integrated). I ran the previous Fortran XE2015 installer using "modify" to integrate it into VS2012 so that I'd have fall back setup for current Fortran projects. That leaves VS2013 for me to get Fortran XE2016 integrated. I found that after running the Fortran XE2016 using "modify" to choose integration into only VS2013 caused VS2013 to not start. I reran the VS2013 installer as "repair" and now it starts and I can use Fortran XE2016.
Has anyone had success installing Fortran XE2016 and integrating it into several version of Visual Studio at the same time? Did you need to run the Visual Studio installer repair?
Regards,
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have had success with this. I recently setup a system with VS2012, 2013, and 2015. I installed the C++ and Fortran Composer XE 2013 SP1 (update 5 only), PSXE 2015 (all updates) and integrated both of these PSXE releases (with 14.x and 15.x compilers) into both VS 2012 and VS 2013. I then installed the PSXE 2016 and integrated this with all three VS versions. At no point in all these installations was it required to perform any Visual Studio repair.
I am hoping we will find something in the logs you provided to help better understand what happened in your case. I will include the details of your most recent steps in the internal tracking id also.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Greg,
With your resolving the syntax coloring, related to this thread, do you have the desired versions of PSXE 2015/2016 integrated with the desired Visual Studio versions and are all versions now working?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Kevin,
Yes. I checked again this morning and it is all working. I have Fortran PSXE2016 integrated into VS2013, Fortran text is colorized, and it is building projects. I also have Fortran PSXE2015 integrated into VS2012 to access current projects until I get them migrated to XE2016. I have left VS2015 for C# only, no Fortran integration at this point.
Thanks you for checking on my status. And thanks again for all the help.
Regards,
Greg

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page