Error 5008 at Automation Open with ActiveX in LabVIEW

I am using an Automation Open VI to communicate with an ActiveX server in LabVIEW.  I have selected the ActiveX class I created in my Automation Refnum. When I run my code, I get the following error:
What can I do to solve this issue?

rfv3rt wrote:
An ActiveX Server is a stand alone application which exposes an ActiveX type library 
Your kidding, right? You have about 500 ActiveX Servers on your computer in a recent Windows installation and that is before you install any custom software. So it is quite relevant to know more details than that it is just SOME random ActiveX server.
For one not all ActiveX servers out there are the same, some are hobby projects that have been created by pretty unknowledgable people, some are an afterthought of a company to be able to claim they have support for any Windows application for their hardware and some are properly developed by a knowledgeable person. Assuming that your ActiveX server is flawless is not very realistic.
Also it is helpful to know which software and even version you try to use. You don't go to a car shop and ask him to diagnose your problem by telling him your car at home makes some strange noise but you are not going to bring it there so they can take a proper look!

Similar Messages

  • Unable to prepare project for publishing the project could not be prepared for publishing because an error occurred. (file already open with write permission)

    Get this message when I try to publish my iMovie project.  "unable to prepare project for publishing the project could not be prepared for publishing because an error occurred. (file already open with write permission)"

    See the discussion here:
    https://discussions.apple.com/message/16784714#16784714

  • Problems with automation open for activex control

    Hi,
    I want to open an ActiveX Control (.ocx-file) with the Automation Open function. This .ocx file was successfully registered by using regsvr32.
    The VI is working fine after using Automation Open and all the contained classes are accessible.
    However, after saving the VI and opening it again the error 2147221164 appears and the program failes - referencing the object new at the Automation Open functions solves the problem, but only till the next reopening of the VI.
    Hope somebody has a solution for this "instability"... 
    Sorry for bothering and thanks for any help!!!

    Hi smercurio_fc,
    originally i had a dll written in c++ which contained classes - i wrapped this in a activex control to have access via labview. Im calling the activex control with the automation open function in same VI in which i am also using property nodes and invoke nodes to have access to the classes and methods...
    But as i told before, it happens that Automation Open fails, when starting the VI again after closing(saving), even so it was working perfectly fine before...
    Thanks for your response... 

  • Error 1 occurs at open file+.vi in labview 8.5

    Hi,
    I keep getting an Error 1 message whenever I try to run a part of this program. The program is very large but the problem is concentrated to a specific part in the IPCE case where I try to read from a file that is already saved on the computer. Essentially, I run the IPCE calibration once, save the calibration data and then run the program again only this time selecting IPCE instead of IPCE calibration. It is supposed to read from the reference spreadsheet I have already saved as well as the newly saved calibration data but Its telling me that the path is an invalid input. This is confusing since I can see the files right there, saved where they should be. Originally I thought it was a formatting error on my part but I have tried several different configuratins with no luck. Any help would be appreciated.
    I have attached the program as well as the reference data that is already saved.
    Thanks in advance
    Solved!
    Go to Solution.
    Attachments:
    Framework w FT.vi ‏582 KB
    Reference IPCE (upstairs).txt ‏1 KB

    C:\Documents and Settings\All Users\Documents\My Gamry Data\IPCE data\reference data\Reference IPCE (upstairs)
    is a protected path on Windows 7  save program data in C:\ProgramData\
    Jeff

  • Framegrabber board control with ActiveX through LabView

    I have a framegrabber board that is not from National Instruments. It is
    from a
    company called Coreco. The name of the board is the Bandit board. I have
    been
    trying to determine how to control it through LabView. Several weeks ago
    I found
    the ActiveX control for the Bandit board on the Coreco website (www.coreco.com).
    I installed the control so that LabView could control the board. However,
    I have not
    been able to get image acquisition. I have read the instructions for the
    ActiveX control,
    but everything I try still does not start image acquisition. Does anyone
    have experience
    with both LabView and the Coreco Bandit ActiveX control. I would also consider
    some other approach to controlling
    the Bandit board. Thank you for any help
    that
    you can give.
    Sincerely,
    Trinity Ellis

    >
    > I have a framegrabber board that is not from National Instruments. It
    > is
    > from a
    > company called Coreco. The name of the board is the Bandit board. I
    > have
    > been
    > trying to determine how to control it through LabView. Several weeks
    > ago
    > I found
    > the ActiveX control for the Bandit board on the Coreco website
    > (www.coreco.com).
    > I installed the control so that LabView could control the board.
    > However,
    > I have not
    > been able to get image acquisition. I have read the instructions for
    > the
    > ActiveX control,
    > but everything I try still does not start image acquisition. Does
    > anyone
    > have experience
    > with both LabView and the Coreco Bandit ActiveX control. I would also
    > consider
    > some other approach to controlling the Bandit
    board. Thank you for any
    > help
    > that
    > you can give.
    >
    > Sincerely,
    >
    > Trinity Ellis
    >
    Try to use the Windows-DLL with is delivered with your board. I had used a
    Matrox-Genesis board and had the same problems. The dll's worked. Gruß,
    Tobi.

  • Error -214746726​2 "No such interface supported" when open an ActiveX automation reference to proprietar​y 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

  • I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 profession​al. The create new report VI opens Excel but throws error (-21471672​62- from automation open VI) when I try to open MS word. please help...

    I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

    Hi Leo22,
    Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
    Jeremy L.
    National Instruments
    Jeremy L.
    National Instruments

  • Need help solving Error 3005 using activex server and automation open.

    Hi,
    I am trying to use a master vi to call a slave vi by using the activex server option. The steps i have taken are:
    1. In the slave vi, go to advanced tab in build options and check enable activex server.
    2. After building the .exe go to the command prompt and type the path to the .exe followed by /RegServer. Ex: C:\slavevi\applicatoin.exe /RegServer. This will add it to the activex plugin list.
    2.a restart labview if it was open.
    3. In the master vi use automation open, create a constant for the automation refnum and right click it. Select browse. Browse to the name you chose in the enable activex server field from step 1. Choose “show creatable objects only” and pick the _application one.
     4. use an invoke node and connect automation open to it. Choose getVIReference. This will drill down to the actual vi you want to control.
    5. The path will be the install path + the vi name. Ex: \slavevi.exe\mainviname.vi.
    These steps actually worked on the machine that I built the vis on but if I build the exes and transfer them to another computer I get error 3005 when it tries to open the slave.exe program. In each instance the master and slave vis are both local (not trying to go through a network or anything). I have registered the slave.exe and .tlb file on the new computer, rebooted etc and nothing seems to work. I also tried running the master vi as source code but that didn't work.
    The master vi was originally built in labview 7.1 and the slave is built in LV 9.01 but I have since upgraded the master vi to 9.01 to try and resolve the problem.
    Is there something that happens during a build that needs to be replicated on the new computer?
    Thanks for any help.
    Solved!
    Go to Solution.

    Help needed ..
    am also getting this error 3005 in automation open in LV.
    i am trying to design a GPS software by integrating Google Earth Application in LV. i am successful in that. but when i am trying to use its properties like drawing a pilygon or point at particular longitude and latitude am getting error.
    I read that mass complie thing was for older LV versions.
    am using LV2009.
    Attached is the part of code thats creating trouble.
    Attachments:
    GE.JPG ‏19 KB

  • Automation Open (CoCreateInstance) with BlackMagic DeckLink frame grabber

    I am trying to interface BlackMagic frame grabber hardware that has a COM driver. The C++ demos for the driver work flawlessly, but I fail to access the COM components from LabVIEW. The driver is initiated in C++ with 
    CoCreateInstance(CLSID_CDeckLinkIterator,NULL,CLSCTX_ALL,IID_IDeckLinkIterator,(void**)&pIterator);
    As far as I understand the corresponding LabVIEW command should be to use Automation Open with either CDeckLinkIterator or IDeckLinkIterator as automation refnum. However for both refnums LabVIEW returns an error when executing Automation Open: Error 3005 occurred at Automation Open: Object specified is not creatable.
    When I look at the demo code provided with the COM driver, there are really two COM commands that are executed before the CoCreateInstance
    AfxWinInit(::GetModuleHandle(NULL), NULL, ::GetCommandLine(), 0)
    CoInitialize(NULL)
    Does anyone have a clue why the Automation Open might be failing in LabVIEW but CoCreateInstance is not failing in C++. Is there a possible workaround? I have tested this with both 64- and 32-bit LabVIEW 8.6.1.
    Tomi
    Tomi Maila

    Hi,
    I made some progress...
    I found a response to my first question in the forum, with a link to :
    http://digital.ni.com/public.nsf/allkb/6EC98441BFAF93A486256DCD000179A2?OpenDocument
    so the solution of this problem is in snipet decklink1
    My remaining problem is about the configuration of the callback. It doesn't seem to work like in LV examples, or forum examples, as I cannot reference my callback VI as the callback function, and I get no event in the  'register for event' node.
    Phil
    Message Edité par Ficare le 03-19-2010 12:11 PM
    Attachments:
    decklink 1.png ‏29 KB

  • Error message when finalizing...file already open with write protection

    I just created my first movie in i Movie. It's about 9 minutes long. When I tried to finalize it it worked for a couple of hours and then came up with a message "unable to prepare project for publishing because an error occurred (file already open with write protection)". What does this mean? I thought I had closed all the files I was using. There was no error number. I tried it 3 times and got the same message. Any thoughts would be greatly appreciated.

    AppleMan, I just checked that and it looks like Time Machine isn't open. I checked it by going to finder>applications>R click on time machine. It gave me the option to "open" which makes me think it's already closed. Is there somewhere else I need to be looking?
    I made another movie that was just a couple of clips and it finalized fine. On that movie, I had some MTS clips and I converted them to mp4's so iMovie could read them.
    In the one that didn't work I did clip one of the movies before I imported it into iMovie. It saved as a .mov instead of a .mp4. Would that make a difference? I checked all of the files and none of them are listed as locked, so I really don't get the "write protected" aspect of this error.

  • IMovie error when trying to export-file open with write privilege

    When trying to export an iMovie, after about two hours, I got a message - error - a file is open with write privilege.  Any idea what might be causing this error or what the error message means?

    Ask the users in the iMovie forum: https://discussions.apple.com/community/ilife/imovie?categoryID=141

  • Error 7 occurred at Open File+.vi:Open File,NI-488: Nonexistent GPIB interface

    I did some clean-up of my computer and have been having issues ever since.
    I'm not the one that did the programming; the person who did is long gone.
    The VI loads fine but when I hit run I get:
    Error 7 occurred at Open File+.vipen File
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
    =========================
    NI-488:  Nonexistent GPIB interface.
    All the necessary VIs are available and I've tried changing all the file calls in the VIs to the new locations but the error is the same.
    Any suggestions?
    Thanks.

    Error 7 is a generic file not found.  If it is happening after cleaning up files, more than likely you moved some subVIs called in a main VI to a new location on your computer.  If all the VIs are in a project, a possible solution would be to remove the vis in the project directory and add them back to the project as they may be pointing to a previous location where the files were once stored.  Perhaps this is what Anon123123123 meant by "linking".  Hope this helps.
    Regards,
    Isaac S.
    Regards,
    Isaac S.
    Applications Engineer
    National Instruments

  • Error -2147024894 when trying to use ActiveX Automation Open

    Hello,
    I use the Automation Open on an ActiveX Class (which is creatable when I choose it from the list). When I do this I get the error:
    Error -2147024894 occurred at The system cannot find the file specified.
    Does anyone know what this error means?
    Thanks a lot,
    Laurent

    Hi Laurent,
    This is usally caused by registration problems of your activeX server with Windows. This is usally done while you install a ActiveX capable application but it could fail. for more information see the attached Knowledge base. This deals with LabWindows/CVI and MS Excel but this is more a general issue.
    http://digital.ni.com/public.nsf/websearch/7139D4FDE76185EE86257195007118EC?OpenDocument
    Hope this helps
    Thanks
    Karsten

  • Automation Open error - "ClassFact​ory cannot supply requested class" (-21472212​31)

    I am trying to use a third party COM object.  I have been provided with a comobject.DLL file and I have registered the object.
    I have been able to use the COM object with no problems using a VB script.
    Now, I need to be able to use the COM object from LabVIEW.
    I created an Automation Open function ( Functions > Connectivity > ActiveX > Automation Open ).
    I then selected my ActiveX class from the Automation Open menu and created a Refnum.
    Unfortunately, when I execute the VI, I get the following error:
    "ClassFactory cannot supply requested class in activextest.vi"
    I am using LabView 8.2 on Windows XP.
    NOTE: I am able to create an InvokeNode function and see the available methods for this COM object.
    Any help is greatly appreciated.
    Thank you in advance.

    If that fails to work, then it was not properly made or completed. It should boot the computer to a screen similar to that of a Recovery HD. Without a Mavericks installer of your own there is no way to restore Mavericks because it can no longer be downloaded. You have the option of Mountain Lion to purchase or Yosemite which is free. You might try fixing your Yosemite system.
    Install or Reinstall OS X from Scratch
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Erase the hard drive:
      1. Select Disk Utility from the main menu and click on the Continue button.
      2. After DU loads select your startup volume (usually Macintosh HD) from the
          left side list. Click on the Erase tab in the DU main window.
      3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
          the Security button and set the Zero Data option to one-pass. Click on
          the Erase button and wait until the process has completed.
      4. Quit DU and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Install button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
               because it is three times faster than wireless.

  • Error 3005 occurred at Automation Open: Object specified is not creatable

    I was able to integrate Google Earth Application in labview successfully. And am also able to access its features. Now I want to create a polygon or a point at certain position on the map. But I am facing problem with the portion of code I am attaching in this post.
    Its Giving Error in Automation Open. I have no clue what's wrong with it.
    Help needed.
    Any reading material, or quick help will be really appreciated .
    Thanks,
    Regards.
    Attachments:
    GE.JPG ‏19 KB

    Hi,
    you've chosen the wrong forum - this one is dedicated to LabWindows/CVI. You should repost your question in the LabVIEW forum here: http://forums.ni.com/t5/LabVIEW/bd-p/170

Maybe you are looking for