LV5 as ActiveX automation server

Hello,
I hope that somebody here is able to help me. I have a question about using
LabView 5 as ActiveX automation server. This works fine for me when I build
an C++ application based on the examples I got with LabView. But all
examples I found make use of MFC.
Now I have a C application that is based on pure Win32 API. My question: How
can I implement calls to LabView-automation server using Win32 API without
MFC?
Thanks for your help in advance!
Martin Schellenberger.

Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
-Doug

Similar Messages

LabVIEW Run Time Engine and ActiveX Automation Server

Hi,
I have a question related to LabVIEW Run Time Engine and ActiveX Automation Server:
We have a tool developed in LabVIEW and TestStand. End user interface is a LabVIEW GUI (it's an executable) which executes TestStand sequences. Some TestStand sequences call lower level LabVIEW VIs.
Everything works fine with LabVIEW installed, but I was wondering if I could run this tool on deployment machine with only LabVIEW run time engine installed. We are using LabVIEW 6.1 and with only the run time engine installed, I get the error message: "Unable to launch the 'LabVIEW.Application' ActiveX automation server ".
BTW, we are planning to upgrade the versions soon.
Is it possible to make things work only with the run time engine?
Thank you.

Thanks for the response, Brian.
I did upgrade to LabVIEW 8.0 and TestStand 3.5. Everything works fine on the development computer where LabVIEW and TestStand is installed. On the target computer in the lab, I installed LV RTE 8.0 and TestStand 3.5, and now when a VI is called in a sequence file, I get the following:
RunState.PreviousStep.Result.Error.Code -18002
RunState.PreviousStep.Result.Error.Msg "LabVIEW: The VI is not executable"
So, the executable opens and works fine (which means that the LV RTE is installed properly), but when a sequence calls a low level VI, it does not make it through.
comments/suggestions are appreciated. Thanks.

ActiveX Automation server error on deployed TestStand

I'm trying to deploy TestSTand 2.0 + LabVIEW 6.1 on a PC under Win-2K.
I created and deployed TS Engine and Operator Interface for LV.
I try to deploy the "Auto.seq" test from the TS exemples.
Of course, it works on my Development system.
On the deployed system, I got an error : -18351; An error occurred reading an ActiveX Automation server type library.
Step 'Read Database Option - Construct' of sequence 'Get Database Options' in 'SequentialModel.seq'
Step 'Read Database Option - Read Options' of sequence 'Get Database Options' in 'SequentialModel.seq'
After having ignored those 2 errors, the tests goes on normally and the report looks fine.
I also get this error opening the database configuration:
Step 'Read Database Option - Construct' of sequence 'Edit Database Options' in 'Database.seq'
From answers already given for similar subjects, I've checked that TsDBOptions.dll is present and registered (done regsvr32...) on the PC.
Can someone help ?
Note: upgrading to more recent TS + LV versions is not a solution!

Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
-Doug

ActiveX Automation Server Error -18351

I wrote a program using TestStand Version 4.5.1 and ran into this error code as soon as I initialize it.
Error loading type library/DLL.
Error Code: -18351; An error occurred reading an ActiveX Automation server type libarary Step 'Read Database Otion - Construct' of sequence 'Get Database Options' in 'SequentialModel.seq'
Bottom line, I'm not using or planning to use any form of database with my program. I just want it to run.
There was another document with ID 4IE7CCM6 that addressed this issue. Tried it, didn't help. I also went to the related links referring to the Knowledgebase document with ID 1HBAMMSR, didn't help either.
How do I fix this?
Attachments:
errors_activeX.docx ‏200 KB
errors_activeX.docx ‏200 KB

Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
-Doug

ActiveX automation server return "Error Win32"

Has anybody meet this problem: I click on the' ActiveX automation server'
in the CVI project window 'Tools' menu (CVI5.01) and then it starts to
scan all the registered components but after a while it returns an error
message like "Error Win32" so I can't work with the ActiveX components,
I tryed uninstall and reinstall the CVI and the problem remains the same.
The OS is Win NT 4.0

Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
-Doug

Error accessing Activex Automation server code -18001

hi guys
i am trying to call a labview generated DLL   thr' a labview VI   "newread_dll.vi"     which i call in teststand
but   labview kind of hangs loading it  &
"error accessing Activex Automation server   code -18001"
the VI runs without issues in Labview
only in teststand the isssue exists ??
Attachments:
seq_dll_error.PNG ‏208 KB

Hi aparab,
did you follow the instructions in the error message? See screenshopt for configuration details.
Below a link which describes, why error code .18001 could occur:
http://digital.ni.com/public.nsf/allkb/5C692ACB049D0D30862575710051601F?OpenDocument
Best Regards, Fabian
Attachments:
S1.PNG ‏22 KB

-18001: An error occured accessing the LabVIEW ActiveX automation server

Hi,
I'm currently investigating a problem with a Teststand 2.0 sequence. The
sequence makes use of VI's that call methods of an ActiveX. After a few
successful loops through the test sequence the error "-18001: An error
occured accessing the LabVIEW (6.1) ActiveX automation server" is brought up
in Teststand. I think that somehow the ActiveX automation server is dying
during the execution of the sequence but I don't know where to start
searching...The problem does not seem to lie within the ActiveX istself, but
I'm not sure. Using the same ActiveX within a Visual Basic Application and
performing the same commands several times does not produce a failure. Has
anybody an idea what could be the problem
Thanks, Sven.

Thanks, but I already know these entries from the Knowledge Base. I found no
help in there and my error text is also not mentioned there.
JRA schrieb in im Newsbeitrag:
[email protected]..
> There is actually a few Knowledge Bases on NI's website which deals
> with this exact issue. You will probably want to start there.
> 1. >
"http://digital.ni.com/public.nsf/websearch/55574CB4E0F326DF862567FD0077E303
?OpenDocument">-18001
> ...
> 2. >
"http://digital.ni.com/public.nsf/websearch/D8690EC8044C7B3586256C63005D4D84
?OpenDocument">Why
> do ...

Using LabVIEW RTE vs. LabVIEW ActiveX Automation Server (TestStand LVRTS) for a TestStand Deployment and experienceing Unabel to Launch LabVIEW.Application ActiveX Automation Server Error 18001

I am developing in TestStand 4.2.1 and LabVIEW 2009, I have accomplished the following:
1. Deployment package is built and deployed on PC
2. PC has activated TestStand Deployment License
3. LabVIEW 2009 RTE was selected as the adapter for the sequence and thus I believe the deployed testexec.ini contains this.
I am experiencing the following error: "see attachment".
Is the LabVIEW RTE the right selection?
Is there something I may have missed in building the deployment?
Do I need to register the ActiveX server.
THere seems to be conflicing solutions based on Version of TestStand and LabVIEW!!
Thanks!!
Attachments:
TS_LV ActiveX Error.doc ‏77 KB

Howdy mobiux,
Please consider KnowledgeBase 4V58058Z: -18001 Errors in TestStand. If you're using Vista or Windows 7, then this may apply as well. You might also consider ensuring you have the proper LV version active in the TS Adapter Options.
Warm regards,
pBerg

-17702; An error occurred accessing the CVI ActiveX automation server.

I am now getting this error consistently whenever I try to debug my dll. I was able to successfully debug earlier, but it has degraded. I tried shutting down teststand and labwindows and restqarting them, but the error persists. I am using teststand 4.1.1 and labwindows/cvi 9.0.0 (348).
Anyone have any ideas? This has me stalled.

Hello,
Pretty old post, but I have a similar problem...How can I fix this issue ?

Error launching the 'LabVIEW.Application" ActiveX automation server [Error Code: -18001]

Hello,
I have TestStand 2010 and LabVIEW 2010 development systems.
In the TS LabVIEW adapter is configured to use Development System.
Till today everything worked properly.
Today I tried to run TS sequence (which worked yesterday) and got error -18001.
I changed LV adapter configuration to use LVRTE and then back to Development System - and got error -18001 again.
Please see the image below.
LV2010 development system exists and I can use it: edit and run VIs.
How can this problem happen and how to resolve it?
Thanks in advance!
Attachments:
TSError_LV_App_ActiveX.JPG ‏135 KB

Hi,
there are multiple possible causes why you could encounter this error. Have a look in this KB:
http://digital.ni.com/public.nsf/allkb/5C692ACB049D0D30862575710051601F
cheers,
cheggers
Sascha E.
Group Leader Applications Engineering
National Instruments Switzerland

-18001; And error occurred accessing the LabVIEW ActiveX automation server.

I installed a revised TS deployment, and got this error.
For other deployments, when this error occurred, there was a simple solution - change the Adapter in TestStand.
This time, if I change the Adapter, I cannot reload the test vi's in the test sequence, so that doesn't work.
Any help would be appreciated.
TS 4.2.1
LV 2010

Jauron,
This knowledgebase article here: http://digital.ni.com/public.nsf/allkb/D577B50A1235A088862570FA004BDD63 seems to have a solution for the issue.
Regards,
Kyle Mozdzyn
Applications Engineering
National Instruments
Regards,
Kyle M.
Applications Engineering
National Instruments

OLE Automation Server

Hi all.
I've been asked to help in a project where the main portion of it is
being written using labview (G), which I'm not familiar with.
I've had a quick browse through the various labview manuals, and really
don't want to go off at a tangent from what I need to do, meaning that I
don't have time to become proficient with labview - the current
"developer" does not describe himself as a "programmer", which is why he
chose labview.
Anyway, the job requires me to interface a Thompson Frame Grabber card
(FGT) with labview. Thompson supply an SDK and the source for a
Microsoft Visual Studio sample program. Unfortunately, no source for the
SDK DLL/driver.
Reading their French-glish manuals, the way they expect you to control
the FGT card is via a supplied DLL. They do supply some guidance on how
to do this, but the problem I have is that the DLL requires various low
level capabilities to allow things like an overlay window, callbacks,
etc. Given that such info seems to be rather difficult (tedious) to
extract or have labview perform, I've decided I should write (using
Delphi or C++) another component to talk directly to their DLL, and have
labview control the new component that I write.
Looking through the various manuals, I see that labview supports
ActiveX, but I'm unsure wether that is restricted to just ActiveX
controls specifically, or wether labview can interface with an
Automation Server (OLE and ActiveX are built upon COM) ?
If so, how does one "import" the Automation server's interface into the
labview environment/IDE, so my "non-programmer" client to easily
interface with an Automation Server ?
The reason that I want to go with a standalone, out-of-process (OOP...?)
Automation Server, as opposed to an in-process server, or an ActiveX
control, is that (naive) attempts thus far with interfacing labview with
the FGT DLL has lead to serious side effects, such as crashing the
system. However, trivial trials using Borland C++ Builder to interface
with the FGT DLL produced none of those stability problems.
Another reason is that if I make an ActiveX control, the possibility of
multiple use rears it's head, which the DLL and overlay functions do not
support, nor make sense for it to.
I will shortly install a temporary copy labview (5.1 ?) on my Dual boot
Win98/Win NT4 system here, just to experiment with labview. But my
client is using NT4 SP6, with a dual processor Xeon system (although
we've removed one of the CPU's due to various weirdities with labview).
Any additional pointers or confirmations would be most helpful.
//)) //))| Richard RUDEK. MicroDek. Chatswood, Sydney. Australia. |
//\\ //\\ |http://microdek.homepage.com/ |
|________________________________________________________|

> Reading their French-glish manuals, the way they expect you to control
> the FGT card is via a supplied DLL. They do supply some guidance on how
> to do this, but the problem I have is that the DLL requires various low
> level capabilities to allow things like an overlay window, callbacks,
> etc. Given that such info seems to be rather difficult (tedious) to
> extract or have labview perform, I've decided I should write (using
> Delphi or C++) another component to talk directly to their DLL, and have
> labview control the new component that I write.
>
> Looking through the various manuals, I see that labview supports
> ActiveX, but I'm unsure wether that is restricted to just ActiveX
> controls specifically, or wether labview can interface with an
> Automation Server (OLE and ActiveX are built upon COM) ?
>
> If so, how does one "import" the Automation server's interface into the
> labview environment/IDE, so my "non-programmer" client to easily
> interface with an Automation Server ?
>
> The reason that I want to go with a standalone, out-of-process (OOP...?)
> Automation Server, as opposed to an in-process server, or an ActiveX
> control, is that (naive) attempts thus far with interfacing labview with
> the FGT DLL has lead to serious side effects, such as crashing the
> system. However, trivial trials using Borland C++ Builder to interface
> with the FGT DLL produced none of those stability problems.
>
> Another reason is that if I make an ActiveX control, the possibility of
> multiple use rears it's head, which the DLL and overlay functions do not
> support, nor make sense for it to.
>
> I will shortly install a temporary copy labview (5.1 ?) on my Dual boot
> Win98/Win NT4 system here, just to experiment with labview. But my
> client is using NT4 SP6, with a dual processor Xeon system (although
> we've removed one of the CPU's due to various weirdities with labview).
>
If you inflate any arrays or strings before calling the DLL, then
there shouldn't be any problem calling into the DLL. This is how
the NI drivers are built. If you would rather, then you can use
the ActiveX client functions. LV can contain controls, and can
access any automation server. The function for importing is the
Automation Open function. Its in the ActiveX palette. Popup on
it to create an automation refnum, and type it to be the server
that you are creating and registering.
As for problems with the Dual processor, I now of a number of
LV users that use dual processor machines with no problem. If
you have problems, it is more likely to be a problem with a
driver. If it is anything reproducable, then please report it
to NI.
Greg McKaskle

Reload automation server doesn't work for all steps

Hi all,
I'm creating ActiveX Servers using Visual Basic 6. In TestStand 3.1 I have steps that call methods from an automation server and I have steps that get properties of an automation server.
When I create a new version of an automation server, I open one of the steps that use the automation server and press "Reload", so that is uses the latest version. TestStand Automatically updates all the rest of the steps that use the same automation server, but for some reason it only updates the steps that call a method and not the steps that Get a property. Why is this?

Frank -
When you configure a TestStand step to call an automation server, it stores the specific ID information for the server and the class and method/property that you are calling. If the server is created with MSVB the compatibility mode of the project defines whether MSVB alters this information after each recompile of the project. TestStand tries to find the server, class and method/property after you compile the project each time. If you take a look at the Compatibility Options for Visual Basic section in Chapter 5 of the TestStand 3.x Reference Manual you will find more information on this. The section describes the various compatibility modes Visual Basic projects. In a nut shell, it is recommended to use Project Compatibility while developing code and switch to Binary Compatibility when you release a system. When you switch to Binary Compatibility you should keep it there and only add new methods or classes. You should not change the names or prototypes of existing methods or properties for this breaks binary compatibility. In my previous development, it would have been nice if VB exposed the control of these IDs, but they do not.
Scott Richardson
National Instruments

ActiveX Automation Reference getting corrupted when sharing with Teststand

I am using ActiveX Automation to interact with a 3rd Party Software. I use LabVIEW Functional Global to store the activeX reference. I have some low-level APIs with the Automation Refnum In and Out and few high level APIs which use the reference from Functional Global. I am also using these APIs in Teststand. When I store the Automation Reference in the Teststand Local Variable and pass it to the low-level APIs, It was working fine. But when I pass the Reference from the Teststand Local Variable to the Functional Global and use it afterwards, the reference is getting corrupted and I am getting error.
I have created a prototype of the situation using ActiveX call to Skype from LabVIEW. The attached file has 3 Teststand sequences explaining the situation.
Debug1.seq : Passes the reference from TS Local to LV Functional Global : Generates error
Debug2.seq : Uses the reference from TS Local alone : No error
Debug3.seq : Uses the reference from LV Functional Global alone : No error
Can anyone suggest why is the reference loses its validity or any solutions?

Hello, Nandini,
I am using the WinXP and I am calling the DLL provided by Pirouette for their chemometrics software. I just solved the error -2147467262, but the new error comes out is :
Error code: -2147467259 Exception occured in IxAsObjs.CoSIMCAPredict.1, Language Server QueryInterface failed: No such interface supported.
Here is a few word for the problem from priouette:
" just a few more words that might help you understand the nature of the problem. your LabView client talks to AlgSuite.dll using IDispatch interfaces AlgSuite.dll communicates with the language server on an IUnknown interface.
Your client knows nothing about the internal workings of AlgSuite.AlgSuite communicating with objects that do not have IDispatch interfaces should be irrelevant to your client."
Since the VB demo works fine in my machine, so they though it is percular to labview. Any comments? I appreciate it.
LvvL

Error -2147467262 "No such interface supported" when open an ActiveX automation reference to proprietary DLL, why?

I got the error -2147467262 "No such interface supported" when open an ActiveX automation reference to a proprietary DLL. I check the forum which suggested solutions related to comcat.dll and IE6.0. I also tried to re-reqister the dll by regsvr32.exe, still does not work. However, I did nto get any luck. I was told that the DLL support iDispatch interface and should work ok with ActiveX in labview. Any suggestions? I appreciate it.

Hello, Nandini,
I am using the WinXP and I am calling the DLL provided by Pirouette for their chemometrics software. I just solved the error -2147467262, but the new error comes out is :
Error code: -2147467259 Exception occured in IxAsObjs.CoSIMCAPredict.1, Language Server QueryInterface failed: No such interface supported.
Here is a few word for the problem from priouette:
" just a few more words that might help you understand the nature of the problem. your LabView client talks to AlgSuite.dll using IDispatch interfaces AlgSuite.dll communicates with the language server on an IUnknown interface.
Your client knows nothing about the internal workings of AlgSuite.AlgSuite communicating with objects that do not have IDispatch interfaces should be irrelevant to your client."
Since the VB demo works fine in my machine, so they though it is percular to labview. Any comments? I appreciate it.
LvvL

LV5 as ActiveX automation server

Similar Messages

Maybe you are looking for