Meas Studio VS 2006 C++ Extender Provider failure

[vv]

Suddenly, after Measurement Studio 8.5 has been fine under Visual Studio 2005, C++, I get errors when I try to Add Variable to any Measurement Studio object.  In the Resource view, I click on a MS object such as CNiGraph, right-click and select Add Variable. VS reorpts via an error window: A runtime error has occured, line 1211, the extender provider failed to return an extender for this object. 

I ran a 'repair' using Add or Remove Programs on Measurement Studio for 2005, rebooted and still the same inability to create a variable that will reference any of the Measurement Studio objects.

Does any one have any ideas on what may be going on?

Thanks,

Val Veirs

Professor of Physics 

[vv]

Here are some more details on this difficulty.

 I created a minimal Meas. Studio VS 2005 project (under Windows XP Prof.).  Put a CNiGraph on it and right-clicked on

photo 1  Add Variable

 VS returned

photo 2  Runtime Error

I clicked on 'Yes' and selected VS 2005 as the debugger which opened another copy of VS2005 and produced

photo 3  Extender Failed

I clicked on Break and added a watch on oTypeLib and got the following which suggests that cwui.oca is at issue

---more screen shots in next post ---

[vv]

And here is the rest of the story --

photo 4  cwui.oca

Clicking on the run button yields

photo 5 unknown exception

Then closing the debugger returns control to the original VS 2005 with a Library not Registered error shown in

photo 6 library not registered

[nickb]

Hello Val,

It's interesting that your project is linking to cwui.oca.  The .oca file is created when an ocx control is added to the toolbox in VB6, as described here. The first thing that I would try in your case is to close out Visual Studio, go to C:\Windows\System32 and delete the cwui.oca file.  (If you are using VB6, it will be regenerated when VB6 opens next time).  I would then unregister cwui.ocx, by calling regsvr32 /u cwui.ocx from the command line, and then registering the same control, again calling regsvr32 cwui.ocx.  Then try creating the variable from another simple test app, and let me know if that does not fix it. 

Thanks,

NickB

National Instruments 

[vv]

Well, NickB, you hit that nail right on the head.  Removing the oca file and re-registering the ocx file did the trick.

Thank you *so* much.

Val