How to remove ActiveX server entries from DCOM when server application no longer exists, error: Open VI Reference no longer matches VIs in memory by filename.

[Moorey]

Background:

• 2014 Wrote a LabView 2014 32-bit application which registers itself as an ActiveX server.
• 2014 Wrote a Delphi XE2 32-bit application to connect to the ActiveX server, GetVIReference and Set/Get ControlValues.  This worked fine and deployed to other PC systems.
• Changed my development system early 2015 to Win 7 64-bit.
• Later in 2015 needed to modify LabView application.
• Decided to do this using LabView 2015 32-bit
• After building modified application, imported resulting type library component to Delphi XE2 and modified code to GetVIReference such that the path pointed to the correct location
• When running Delphi Application the Application launches, but then fails to connect to the main vi in the application indicating that the path to the VI no longer matches.

Having attempted a few re-builds, copying the project to give it a new name I am still getting the same error and suspect that my registry / DCOM ActiveX settings are corrupted ?

Doe anyone know how you can tidy up the registry in order to get rid of older registered servers / type libraries where the application no longer exists?

Or can anyone spot a mistake in my settings ?

Many Thanks

[LJefferies]

Hi Moorey,

What is the error that you are seeing, is it a LabVIEW error or a Delphi XE2 error? Could you send a screenshot of this?

Cheers,

Luke

[Moorey]

Hi Luke,

Thanks for your reply.  Please see attached error...

I think it's a LabView error that just gets passed through to Delphi.

Regards

Ian

[LJefferies]

Hi Ian,

There is a LabVIEW error that has the same message and might be worth having a look at the solution to see if it is applicable.

LabVIEW Error -1445 

http://digital.ni.com/public.nsf/allkb/D2E7F13BB89DB843862570CE00755B03?OpenDocument

Would it be possible to see the LabVIEW code?

Best regards,

Luke

[Moorey]

Hi Luke,

Thanks for your message.  I had a quick look at the other thread and tried stripping out the path in the Delphi app to just specifying the vi name.  This came up with the same error.

So, I have attached the project code and also a link to the client bridge application from Pickering which installs the pickering vi library.

http://downloads.pickeringtest.info/downloads/drivers/Sys60/

Please forgive the size of the block diagram, I should have really converted chunks of it to sub vis to make it more understandable.

The purpose of the application is to switch RF relays and set Digital Outputs on a Pickering LXI unit.  We use this in conjunction with our EMC test software (written in Delphi) to set the appropriate relays for the RF test path.

The first version of the software was working ok.  I then had to build in the Digital Output (on the right of the diagram) and in doing so have broken it.

Multiple things have however changed...

- Changed my PC

- Went from Windows 32-bit to 64-bit

- Changed to LabView 2015 (32-bit) - although originally at first attempted to develop the appication as 64-bit.

- I may have run the original LabView 2014 exe (which would have registered the server)

Thanks and Best Regards

moorey

[LJefferies]

Hi Moorey,

At this stage I am not entirely sure what more I will be able to offer in terms of help/suggestions over the forums and I suspect this may be a better thing to handle if you ring into NI for support. Because you have just updated to LabVIEW 2015 I am assuming that you have standard support. 

If you go to ni.com/ask you should be able to ring into your local NI office and open a service request and hopefully the issue will be solved much faster.

Best regards,

Luke

[Moorey]

Thanks for your time and suggestions Luke...

Best Regards

moorey