StrataFrame Forum » StrataFrame Application Framework - V1 » Business Objects and Data Access (How do I?) » AccessViolationException in BOM v1.6.5.3

RE: AccessViolationException in BOM v1.6.5.3

Ivan George Borges — Mon, 27 Feb 2012 18:04:47 GMT

Thanks for sharing, Larry.

AccessViolationException in BOM v1.6.5.3

Edhy Rijo — Mon, 27 Feb 2012 18:04:47 GMT

I am getting the following error:

[quote]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)
[/quote]

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

Source : EnvDTE

I get the error when right click a BO in BOM and choose Rebuild, and after the error the BOM Results forms show everything as OK, but the BO classes are not rebuild.

RE: AccessViolationException in BOM v1.6.5.3

Larry Caylor — Mon, 27 Feb 2012 17:37:32 GMT

I thought I'd post my experience with installing InstallAware 2012 on Windows 7 64-bit and VS2010 in case someone else runs into the same issue. After completing the install I received the memory read errors described earlier in this thread when running BO mapper. Running the .Net 2.0 SDK setup program in repair mode fixed the problem. What ever caused this issue in earlier releases of InstallAware is still with us in the latest version.

RE: AccessViolationException in BOM v1.6.5.3

Dustin Taylor — Wed, 28 Apr 2010 16:54:20 GMT

Yeah, I've taken to unchecking the "Visual Studio Add-In" component of InstallAware to avoid any potential issues here. We still haven't gotten official confirmation/denial that would confirm InstallAware as the culprit of these issues, but it follows suit with the experience of most here, as well as Trent and myself.

RE: AccessViolationException in BOM v1.6.5.3

Edhy Rijo — Sun, 25 Apr 2010 13:53:14 GMT

Updated...

After installing VS2010 in Windows 7 x64, I installed InstallAware 8.1 and again the BOM stop working with the same errors explained here.

I had to reinstall the .Net 2.0 "en_net_framework_sdk_20_x64.exe" and that fixed the problem with the BOM.

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Fri, 19 Jun 2009 14:38:03 GMT

[quote]ow that I know what is needed to get back to Kansas[/quote]

LOL...I am glad that you mentioned the InstallAware piece. I had been scratching my head profusely (and slapping myself in the face ever now and then) up until that point! I knew that there had to be some common denominator here.

On a good note, I am actually running, with success, at this point with all installed. So it is possible, just painful :D

RE: AccessViolationException in BOM v1.6.5.3

Edhy Rijo — Fri, 19 Jun 2009 14:33:22 GMT

[quote][b]Douglas Riley (06/19/2009)[/b][hr]... I may just try installing IA to see if I can recreate the error (now that I know what is needed to get back to Kansas :w00t:).[/quote]

Hi Doug,

In your case, if you have the time I may do just that, install IA and do the following:
1 - Test the BOM
2 - Reboot the computer
3 - Test again the BOM

That may give us a better clue. FYI, I am using IA in the same working computer with VS and SF.

RE: AccessViolationException in BOM v1.6.5.3

Douglas Riley — Fri, 19 Jun 2009 14:29:05 GMT

Trent,
Sorry I am just getting back to you. I ended up doing a repair of Visual Studio 2008 (praying I did not have to reformat the machine!). I reinstalled everything (Strataframe and Infragistics NetAdvantage 2009) except InstallAware. Went back to my project, opened the BOM and everything worked!

Now I am a little gun shy about installing InstallAware 9 back on this machine unless I can exclude that VS add-in option (or get a separate machine to create IA packages...ugh!). I may just try installing IA to see if I can recreate the error (now that I know what is needed to get back to Kansas :w00t:).

Doug

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Fri, 19 Jun 2009 12:02:21 GMT

Thanks for the update, Edhy! :)

RE: AccessViolationException in BOM v1.6.5.3

Edhy Rijo — Fri, 19 Jun 2009 12:00:50 GMT

[quote][b]Trent L. Taylor (06/19/2009)[/b][hr]Edhy, if you read this post would you comment if this was after your IntsallAware install as well? Thanks![/quote]
Hi Trent,

I honestly don't remember if I did something with IA at the time of getting this problem, but that may be the case since I also use IA and may have probably install an update which at any case will simple remove the current installation and install the new one :D

In my case re-installing the .Net 2.0 fixed the problem, don't know if IA could mess with that, but at least now we all have another factor in this case "InstallAware". Probably you could setup a VPC and play with this installing IA.

FYI, my version of IA is: 8.01 (Build Ame - Rej.RTM, 110408).

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Fri, 19 Jun 2009 09:01:00 GMT

LOL...yeah, I am not holding my breath! But I think this is starting to shed some light.

Edhy, if you read this post would you comment if this was after your IntsallAware install as well? Thanks!

RE: AccessViolationException in BOM v1.6.5.3

Keith Chisarik — Fri, 19 Jun 2009 08:58:41 GMT

I had this and as I posted a reinstall fixed it, luckily. It was also after an install of the InstallAware trial. I didnt think it a factor at the time, but this post made the lightbulb go off and I figured you would like another data point.

Good luck with Microsoft, after 3 hours on the phone with them trying to troubleshoot a WDAC error on my machine, the fix was of course "reload your OS".

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Fri, 19 Jun 2009 08:39:32 GMT

Sorry for the delay in getting back with you. I actually missed this post. :blush:

Please answer one question for me as it might give us a clue. You have been a user for a while, so what changed on this development machine between when things worked and when it stopped?

This is one of the most frustrating errors that I have seen as I have figured out what piece is failing, but Microsoft could not give me any straight answers (or to this point ... ANY answers). I was excited the other day because I could debug it and I thought I would be able to isolate the issue....but it went away and started working again!

So it is definitely environmental. Because something within my environment changed that allowed be to get to the DTE.

I had the same issue with a Macro that we had created in house. When you create a macro, it hands you the DTE object...so...you would think that VS would give you a valid instance to work with...but in my case it failed. I moved it over to the Add-In and it worked (makes no sense). I also had the issue with the BO Mapper shortly afterwards (the machine I am working on is a new development machine...thus the newness of the issue). But after debugging and changing some things...it started to work. I didn't change any drastic, just rebuilt the extensibility solution several times (maybe like 20).

I will see if I can reproduce again. But this definitely environmental and we have not yet figured out the root of the cause...sorry :( I will see if I can get it to happen again on my side.

RE: AccessViolationException in BOM v1.6.5.3

Douglas Riley — Thu, 18 Jun 2009 10:22:37 GMT

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.

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Thu, 18 Jun 2009 08:11:13 GMT

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

RE: AccessViolationException in BOM v1.6.5.3

Douglas Riley — Thu, 18 Jun 2009 08:03:16 GMT

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

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Thu, 18 Jun 2009 07:56:54 GMT

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.

RE: AccessViolationException in BOM v1.6.5.3

Douglas Riley — Thu, 18 Jun 2009 07:49:17 GMT

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.

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Thu, 18 Jun 2009 07:38:23 GMT

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?

RE: AccessViolationException in BOM v1.6.5.3

Douglas Riley — Thu, 18 Jun 2009 07:36:10 GMT

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

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Thu, 18 Jun 2009 07:27:27 GMT

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.

RE: AccessViolationException in BOM v1.6.5.3

Douglas Riley — Thu, 18 Jun 2009 07:23:35 GMT

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

RE: AccessViolationException in BOM v1.6.5.3

Keith Chisarik — Fri, 13 Feb 2009 23:32:58 GMT

Installing 1.6.7 beta fixed this on my 2nd development machine :)

RE: AccessViolationException in BOM v1.6.5.3

Trent L. Taylor — Mon, 12 Jan 2009 10:09:57 GMT

LOL....well, you know what the Cowboys and a possum have in common don't you?

They play dead at home and get killed on the road. :crazy:

Hopefully they will get their act together for next year....but I am rooting for the Cardinals now! :D

RE: AccessViolationException in BOM v1.6.5.3

Keith Chisarik — Mon, 12 Jan 2009 09:57:41 GMT

I have been avoiding any form of gloating due to fear of my posts mysteriously falling silent :P , but since you mentioned it.

"Hello T.O.? How is the vacation?"