Error 3005 trying to open agtvsavector 1.19 from Aglient 89601B 14.23

[phongn]

Thank you "the_red_barone.."

After reloading the library  of VsaVector.tlb, I don't see the " Error -214722116​4. Class not registered" any more.

However, I'm seeing "Error 3005 trying to open agtvsavect​or 1.19 from Aglient 89601B 14.23" as aabd was seeing couple years ago. I'm not sure this error had fixed by somebody.

Can you help to fix this issue?

Or

aaabd,

Had you got this problem solved? Please show how to fix it.

Thank

Phong

[phongn]

H aaabd and Michelle and others,

I'm seeing exactly what aabd was seeing in his attached codes.

Did anyone have solution for this. I've got stuck with this and cannot move on.

I talked to one of the Keysight (Agilent) guy since before I was using Window XP with 89601A VSA and had no trouble launching Labview to controll VSA. Here are what he said:

*Before, I was using DCOM window feature that was available in .NET API programming interface and it was working

(you can check this by typing dcomcnfg in the command prompt, then it will lead to

  component services---->Computers--->My computer---->DCOM Configure

======>we will see the "AgtVsaVector.Application"

*Now, for Window 7 and 89601B VSA, the DCOM window feature is not available in .NET API programming interface any more.

So, we have to use SCPI interface instead

Now, I'm trying to figure out how to use SCPI interface to control VSA.

Thanks

Phong

[WenR]

Hi phong

After looking for information regarding this error, I think that this could be related with the compatibility of the .NET version used by 89601B VSA and the version of LabVIEW that you are using. Error 3005 can appear in several situations where an Activex object cannot be found (either because of incompatibility or corrupted code) I also found the next forum, where I can see you also posted some of your concerns.

https://forums.ni.com/t5/LabVIEW/Use-89600B-VSA-NET-API-in-LabView/td-p/1757352

If you do not find a way to install the .NET requires version and use a LabVIEW version compatible with it, I think the way to go would be SCPI, as the guy from Agilent suggested. 

WenR

[hetsay55@yahoo.com]

Thanks WenR,

Phong