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".

Keith Chisarik

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



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.

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.

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

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

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.

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.

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?

Trent,

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

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.