Yes Thanks for the heads up.

That's what I thought, but I figured that you would want to know about it.

Daniel,

When you install SQL Server 2005, SQL Server also installs new VsPackages into Visual Studio and has to execute some command line options to install the packages.  The installation probably launched Visual Studio with a different set of environment parameters causing the error in the StrataFrame menu.  You've probably noticed the new VsPackages on the Visual Studio splash screen when it starts up (SQL Server Analysis Services, SQL Server Integration Services, SQL Server Reporting Services).

Since you can still get into the StrataFrame menu, and both the DDT and the BOMapper are launchable, you should be fine; it was most likely a one time error that came up when VS was launched during the install.

Do you get that exception whenever you open Visual Studio?



no, it occured during the sql 2005 install.



Does the StrataFrame menu appear in Visual Studio?



yes



Can you open the Business Object Mapper or the Database Deployment Toolkit?



yes

Do you get that exception whenever you open Visual Studio?

Does the StrataFrame menu appear in Visual Studio?

Can you open the Business Object Mapper or the Database Deployment Toolkit?

I was installing sql 2005 developer edition when the following exception popuped up after a bunch of error configuring strataframe menu dialogs:

Exception

   An error occurred while building the StrataFrame menu.

NullReferenceException

   Object reference not set to an instance of an object.



Source :



Stack Trace:

at MicroFour.StrataFrame.AddIns.AddInManager.OnConnection(Object application, ext_ConnectMode connectMode, Object addInInst, Array& custom)