VS2005 Pro: Fails to create fortran vfproj and sln

[vortic]

VS2005 Professional, SP1, English

Intel Fortran Compiler 10.0.026 for IA32 with VS integration (evaluation edition).

WinXP SP2

When trying to create any fortran project in the IDE, I always end up getting the following error message, evidentlywhen the wizard is trying to create the project (after I enter the project name, etc.):

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

I have uninstalled and reran the fortran installer, but get the same error. I also have VS2003 academic edition installed, in case that could be a problem. In addition, I found an ifortfixme.bat download from the Intel site that supposedly fixes a similar problem in non-english versions of VS, but running this to get the wizard/project.zip filesinto "1033" directories (the installer put them in directories named "0") does not help

I very much need to buy the Intel Fortran compiler, and really want the VS2005 integration, but Idon't want to buy it if it won't integrate with the IDE.

Does anyone have any insight into solving this problem? I can't seem to login to premiere support to report this, so I am trying here.

Thanks for any help,

Cheers

[vortic]

Some more info on this: It actually does create a .vfproj file just before it crashes the ide. Upon trying to open the .vfproj, if crashes again, but when it pops up the window to send the error report to Microsoft, I hit the debug button, and then look at the info it is sending. I'm not sure exactly how to interpret that info, but it looks like the error is associated with vfproj.dll.

Perhaps this is an VS IDE bug. My next step will be to uninstall VS2005, reinstall it and update it to SP1 (man, I am not really looking forward to that), unless someone has an idea of the real problem.

Thanks!

[Steven_L_Intel1]

The "fix" you found is not applicable to English versions of VS.

I suggest first uninstalling the Intel Fortran integration and reinstalling SP1 for VS2005, then reinstalling the integration. See if that helps. Some VS component on your system is corrupted.

Another thing you might try is to boot into Safe Mode and see if the problem is still there.

VS2005 integration does work.

[vortic]

Hi Steve,

Thanks for the help. Unfortunately it did not work in my case. Uninstalled all IVF stuff, uninstalled SP1 for VS2005Pro, re-installed SP1, re-installed IVF. I get the exact same message.

I've been having SO much fun the last 4 hours uninstalling and installing, I'm going to try uninstalling all of VS2005 and reinstalling. In fact, I'm going to uninstall my VC++2003 Standard as well.

As a side note, I'm running an iMac Core Duo with BootCamp. I don't think this should be an issue though (it hasn't been for anything else). My VS2005Pro is an Academic edition, but this should not be an issue either.

Cheers,

The Re-install addict

[vortic]

I did complete uninstalls and reinstalls, and still get the error.

The only conclusion I can come up with is that theIVF VS2005 integration does not work for VS2005 Professional (Academic edition) running on WinXP SP2 on an iMac with Core Due processor. Any other ideas?

[Steven_L_Intel1]

I don't see why that shouldn't work. We have a bunch of people here running Boot Camp on Macbooks. Please report this to Intel Premier Support and we'll work with you.

[vortic]

I would report this to Premier Support, if I could. Everytime I try to login I get a message saying my account cannot be authenticated. So, I try re-registering, but I get a message saying I have already downloaded the maximum number of evaluations, so I cannot get to the step 4 (as indicated in my original download email) where I can re-register for Premiere support.
I can't really say much for this whole debacle. btw, I tried installing on another machine with my VS2005Pro and IVF 10.0.026, and I get exactly the same error. This leads me to suspect 10.0.026 is not compatible with the Academic Edition of VS2005Pro, or that my IVF download is botched (but then again, I can't re-download it to test that!).

Whatever happened to good old telephone #'s where you can actually talk to someone?

[Steven_L_Intel1]

You got a serial number when you downloaded. Go to the Intel Registration Center and reguster it, making sure you check the box that you want support. Then you'll be able to log in to Intel Premier Support and file an issue.

Whatever problem you're having, it's not a compatibility issue with VS. It MAY be a side-effect of your using Boot Camp. We have experience in working through these issues so please do contact Intel Premier Support.

[dtinkham7]

Thanks Steve. I've made contact with Premiere Support. I'll report back here the fix when it is found.

I do not think it is a Boot Camp issue now. I failed to mention that the other computer I installed on is a plain IBM PC running WinXP SP2 and I get the exact same error (so it is not a Boot Camp issue). My guess is I have a corrupted download, but let's wait to hear the final word from support.

Cheers

[praxis13]

I have the EXACT same problem as vortic. I'm using VS2005 and Intel Fortran Compiler v. 10.1.011. It is the compiler itself that is the problem (not VS) as all my other VS project types create etc. (thank goodness).

But I believe that the problem is the compiler doesn't install properly (completely). I managed to get it to install on a separate machine, created (rather migrated) a project and tried to load the project on the problem machine and the compiler didn't seem to even be there. I was asked to convert the projects to C++ (but they were vfproj already!). And there was no capacity to convert them by right clicking as there usually is.

Anyone else with this problem? I'm imagining there is a conflict with another piece of software somewhere on my machine but am not sure how to troubleshoot. Install supposedly went Ok. An oversight by Intel perhaps (as all other compilers seem to function OK).

Thanks for any help.

[Steven_L_Intel1]

Are you also using Boot Camp on a Mac? Is your VS2005 the one provided with the compiler or a separately purchased one?

There's not enough information here to help you. Please submit an issue with Intel Premier Support and supply as many details as you can.

[aagaard]

I'm having the same problems (tried both Visual Studio 2003 & 2005 - and even the 2005 version delivered by intel). After advice from Premier support, I did a manual registration of the dll's found in the VFPackages folder. The result was that the VFToolOpt.dll could not be registred due to some error situation. I have reported this to Premier support and wait's for a new "hint". My guess is that some other installation or Microsoft update have updated som underlying dll's and this in some way conflicts with the VFToolOpt.dll.

I will post any other findings here.

Allan

[Steven_L_Intel1]

Try running the attached program from a command prompt window and not any errors it reports.

[aagaard]

Hi Steve

Just run the repair program. The result is:

Visual Studio 2005 installed at C:Program FilesMicrosoft Visual Studio 8
Successfully unregistered VFAVwin.dll
Successfully unregistered VFFortSvc.dll
Error while unregistering VFProjConvert.dll:
Error accessing the OLE registry.

Could it be a access right issue ? I'm having Administrator rights.

Allan

[Steven_L_Intel1]

Yes, that's almost certainly the problem. We have seen this before - somehow certain registry keys get set to "nobody can write". I'll have to look up the tips for how to figure out which keys are the problem. This link outlines the general process. The link in on that page for Regmon is broken - use this instead.

[aagaard]

Thank's for the links and hints.

I have tried to register the VFToolOpt.dll and running both REGMON and FILEMON.

REGMON creates a lot of information. It's a bit difficult to dissect the log, but I have tried to walk through the entries related to regsrv32. There are no obvious culprit keys - I don't any access problems only some Keys not found. It looks as if a number of keys are created and set with "intel" related information - but after all this the same keys are removed again.

This led me to the conclusion (I may be completely wrong here), that it wasn't the registry that was the problem, but some dll dependencies that prohibited the dll from loading.

So I have inspected the VFToolOpt in dependency Walker tool - only problem listed is for the following dll's: DWMAPI.DLL, MPR.DLL & SHLWAPI.DLL.

Tried via FILEMON to see if any of these dll's was loaded during registration of VFToolOpt - but this seems not to be the case.

So I'm still in the dark - haven't a clue on what's causing the problem for registering the Intel dll

Allan

[Steven_L_Intel1]

Try this:

Get ProcessMonitor.

Occasionally the permissions for a few of the Windows registry keys were set to disable "write" (even read) access, even for administrators. We do not know the cause of this but are researching it.

For example, one user found that the registry keys that need correction were:
HKCR.f
HKCR.f90
HKCR.fi
HKCR.for
HKCRVisual Studio.idl.8

Use the Process Monitor as follows to correct them:

(a) Run Process Monitor from the command line, passing the argument "/Noconnect" (not including quotation marks). Passing this argument ensures that Process Monitor will not monitor the system until explicitly told to do so. If you do not do this, Process Monitor will quickly hose the computer as the list box attempts to fill with millions of entries.

(b) Set the filter to "Include" only those events where the column "Result" is equal to "Access Denied".

(c) Once out of the Filter dialog, press Ctrl-E in Process Monitor to begin monitoring the system and collecting data.

(d) Run the "fixup" program from the command line

(e) Wait for the success/failure window to appear.

(f) Return to Process Monitor and press Ctrl-E to stop collecting data.

(g) To view the results, toggle "Options->Enable Advanced Output". Toggling it from one state to the other causes Process Monitor to refresh the list of previously recorded events according to the filter.

Following the above steps reveals, one at a time, the registry keys that are causing the problem. The above steps (3)-(7) need to be repeated until regsvr32 succeeds, once per problematic registry key.

[aagaard]

Tried this out - both for your fix program (repair .. etc) and regsrv32.

I don't have any Access Denied results at all from the process mon.

I have inspected the result, but get no denied, but some "Name not found", "Path not found" etc.). I'm unable to spot the place where registry access fails in such a way, that the repair... and regsrv32 fails.

regsrv32 VFToolOpt.dll returns the error 0x80020009 which should be a DISP_E_EXCEPTION - don't exactly what this mean in the registration process.

Allan

[aagaard]

Was a bit too fast to post - I intended to attach the logfile from process mon.

Allan

[adhishor]

I've got the same problem, and I don't know what to do.. Please help me too

[Steven_L_Intel1]

Allan,

I agree that I don't see anything obvious in the log. I see that you're pursuing this through support and I'm following it there.