Error during installation of Intel Fortran 10.1

[julienx2k2]

Hello,
I have MS Visual Studio 2005 pro edition installed on my laptop (Vista Home Premium). When I install Intel Fortran 10.1, at the end of the procedure two pop ups warn me:
"failed to create the configuration file for Intel C++ Compiler for 32-bit applications"
and
"failed to create the configuration file for Intel Visual Fortran Compiler for 32-bit applications"

the ifortvars.bat and ifort.cfg are in addition empty files. Fortran is not implemented in VS either...
Does anybody have an idea of how to fix this issue?

Thanks a lot
J

[TimP]

Do you have MS C++ installed?
Did you log in as administrator for installation of both VS and Intel compilers?

[julienx2k2]

Quoting - tim18

Do you have MS C++ installed?
Did you log in as administrator for installation of both VS and Intel compilers?

Hi,

-yes, it comes with VS 2005
-yes
I have just spent the whole afternoon uninstalling and reinstalling both applications, with frequent restarts and software updates, but still it does not work.

[julienx2k2]

Hi again,

I had to reinstall Windows on my workstation (Vista Enterprise, 64 bits). When trying to reinstall the programs I bumped into the same error as previously mentionned on my laptop (32 bits, Home Premium version).
When installing the IA-32 bits version I get:
"failed to create the configuration file for Intel C++ compiler for 32-bits applications"
"failed to create the build environment file for Intel Visual Fortran compiler for 32-bits applications"
and when installing the 64 bits version the messages become:
"failed to create the configuration file for Intel Fortran compiler for applications running on Intel 64"
"failed to create the build environment file for Intel Fortran compiler for applications running on Intel 64"

Nobody at my IT support knows how to deal with this. Nothing can be found by googling the keywords. I have no idea how to fix this and I need Intel Fortran to run Abaqus, ie to do my job... Where can I find help?
Thanks a lot

[Steven_L_Intel1]

I see that you have an evaluation license for Compiler Suite 11.0 - is that what you're using in this latest attempt? I will ask one of our Startup Support specialists to help you - I can't find a reference to this error in past support requests.

Are you installing onto your C: drive? As an experiment, try temporarily disabling any antivirus software while doing the install.

[julienx2k2]

Hi and thanks,
I haven't tried with the evaluation copy yet, that is just to check if the problem comes from the installation files I have access to. My IT dpt just had an idea to test and have scheduled some software installations this night, I will get the result tomorrow morning when back to the office.
Yes I am installing on the C: drive. I'll try the antivirus trick as well.
J

[Steven_L_Intel1]

I'm going to make a wild guess and say that it's the specific antivirus software you're using. It may be blocking attempts to write to an existing file under Program Files. If that turns out to be the case, which AV are you using?

[julienx2k2]

Ok the error is solved both on the laptop and workstation! I found the solution this night...
The trick is to run the .msi files from an elevated command window. I don't understand why it doesn't work when double clicking on the installation files when logged in as an administrator.

For those who do not know how to do it:
-start, all programs, accessories, right-click on "command prompt" and select "run as adminstrator", confirm
-then go to the installation folder, and type
msiexec.exe /i "name_of_the_msi_file.msi" and enter.
-do this for the compiler, the integration in VS, and the debugger.

Thanks for your help!

[Lina_L_Intel]

Quoting - julienx2k2

Ok the error is solved both on the laptop and workstation! I found the solution this night...
The trick is to run the .msi files from an elevated command window. I don't understand why it doesn't work when double clicking on the installation files when logged in as an administrator.

For those who do not know how to do it:
-start, all programs, accessories, right-click on "command prompt" and select "run as adminstrator", confirm
-then go to the installation folder, and type
msiexec.exe /i "name_of_the_msi_file.msi" and enter.
-do this for the compiler, the integration in VS, and the debugger.

Thanks for your help!

Thank you for your providing this workaround. It is exactly correct.

Here are some information added:
If Visual Studio installed, then this workaround can be used (if doesnt have it thenplease install PPE). The only thing that needs to be done before using this workaround is putting the license to proper place so that compiler will find it. This can be done for example by running setup.exe, entering Serial Number and pressing Next. Then customer may cancel the installation and use this workaround. This is for future reference in case other customers enounter the same problem.

------
Lina