Intel Visual Fortran 11.1 integration with VS2008

[pennuto]

Hi.
I can't fully integrate VF 11.1 with VS2008 (nor VS2005...) on a WINXP machine:

I can build the project , link, maxe executables, but as I try to access the properties of a Fortran project (just for optimizing the compiler) I get the error message : " Class not registered, looking for object with CLSID:...".

Searching on the Web I followed the link

http://software.intel.com/en-us/articles/troubleshooting-fortran-integration-issues-with-visual-studio/

for attempting a fix of the integration "bug".
Following these instructions I finally tried to use the repairvs08integration.exe patch
But running it I always get the message "Error while registering VFProj.dll: forbidden access", also running the patch as "administrator".

So, How could I fix this problem? I realize from the forums that this integration is causing a lot of troubles to many people, so that I hope Intel (or Microsoft?) should soon find a working and simple solution...

cheers

[Steven_L_Intel1]

Something on your system has changed protections on parts of the registry which denies access to even administrators. It is also possible that the registry is corrupted. I have seen other customers run into this, but it isn't something we can control. Usually it's some less-well-known "security" software that does this.

Unfortunately there is no simple solution to this problem, as it tends to evade normal investigation methods. Some users have resorted to reinstalling Windows, which always solves the problem, but it is a drastic step.

[pennuto]

Thanks Steve! In fact, something changed the permission to some registers in WINXP.

I found a solution to this problem in the following Microsoft patch:

MicrosoftFixit50198.msi

as suggested in the following MS link:

http://support.microsoft.com/kb/949377

This .msi resets the register permissions to the original ones

After running this prog, the repairvs08integration.exe works properly!

cheers

[Steven_L_Intel1]

Thank YOU! I had not known of this article before and it provides a great way to resolve this issue.