Installing 1.6.7 beta fixed this on my 2nd development machine

Keith Chisarik

Is anyone still running into this error? I now have the same problem using 1.6.6.



AccessViolationException

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



Source : EnvDTE



Stack Trace:

at EnvDTE.ProjectItem.get_Name()

at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.ᜁ(Project A_0, String A_1)

at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.ᜁ(String A_0, Project A_1)



I have tried all the suggestions listed (reinstalled Strataframe 1.6.6, installed 1.6.7, reinstalled the frameworks) but still receive the same error. Any help would be appreciated!! I am about out of ideas.



Doug

You know, I ran into this the other day myself. So I am willing to bet that you may be running a 64-bit OS. This is the only time I have ever seen this. And it has to do with accessing the CodeDOM or the DTE2 depending on where it fails. I would be curious if you have tried this on a new project. Just for troubleshooting purposes, if you create a new project, add a new BO, then go into the BO Mapper do you still get the error?



I did a number of things the other day and the error went away when I was not expecting it to. But let's start by troubleshooting this with a new project and solution.

Trent,

Yes, I tried a brand new project and got the same error. I am using Windows XP (32 bit OS).

Doug

Really....I have never seen it happen on a 32-bit machine....until now!



Just for testing purposes, do you have another machine or laptop that you could load SF on to see if you have the same problem? You have been a user for a while so do you know what changed or when the problem started?

Tried a new project on my laptop and everything works fine. This all started on my desktop yesterday evening. Only thing that changed on this PC was an installation of InstallAware Express 9 (on Monday). I had uninstalled it this morning before trying all of these options.

You know what...come to think of it, that is when my problem started! I loaded InstallAware and it added a VS Addin and toolbar...and now that you mention it, that is when I started running into the issue.



I reloaded the extensibility about 20 times (and a number of other things) and gave up...the next day I came in and had forgotten about it, went into the BO Mapper, and it did not have any issue accessing the DTE2 object.



I did track down where it fails through all of this. We tie into the DTE using the IDTE2 interface which allows us to access the VS IDE environment, enumeration projects, solutions, etc. The DTE object itself would get created, however, the internal properties, such as the documents and projects, would show an access violation exception.



There is something within the environment and a very unique set of circumstances that causes this issue. I plan on changing how we get to the CodeDOM and DTE altogether when we rework the BO Mapper before long, but I would sure like to try and figure out what environmental piece is causing this.



I never uninstalled InstallAware as it never dawned on me that my problems started after I loaded that. Now that it is uninstalled, try reloading SF to see if anything gets put back into the GAC and add-in environment correctly.

Ok. Do I need to touch the Strataframe database during reinstallation? Thanks!

Oh, that really shouldn't be part of the formula. But go ahead and let it update the database for good measure.

Uninstalled Strataframe completely (database included) and reinstalled. Received the same error in the BOM. I am out of ideas right now. I'll take any suggestions.