-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

Similar Messages

-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 ...

-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 ?

-18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.

Hello,
I have this error when i want to get a VISA session refnum from a viSession handle.
This error occured when the specified class is IviFgen.
The device concerned is a PXI-5402/PXI-5412 (i need to get the model with a property node - Inherent IVI Attribute... from the refnum)
It also occured during a cast (if the class specified is niFgen).
Could somebody help me ?
Thanks !
Attachments:
ErrorLVRT_TestStand.png ‏11 KB

Hi Ggraindo,
This error occured during deployment? Which is the LabVIEW adapter version that you are trying to use, is it the 9.0.1? Do you have other LabVIEW or TestStand versions installed in your computer? This error only occured when you try to used the class IviFgen, or even just with a simple VI?
What is the result of the error cluster from LabVIEW?
Also, can you post a simple exemple to reproduce this issue?
Regards,
Rémi D.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Les rencontres techniques de NI - Mesures et acquisition de données : de la théorie à la mise en ...

Error -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL. TS 4.2.1 / LV 2010

When I try to run a VI that is reentrant in parallel execution, I receive this error. The details of the error is: LabVIEW: The property or method is not supported in this version of LabVIEW.
This is run under the Simple Operator Interface in LV 2010. The TestStand engine is version 4.2.1 using LV 2010 run-time engine adapter.
If I save for previous version to LV 2009 SP1 and set the TS adapter to 9.0.1 (2009 SP1), this works.
Can anyone reproduce this error (bug?) ?
Solved!
Go to Solution.

have you got the latest updates for TestStand using LabVIEW 2010?
http://digital.ni.com/public.nsf/allkb/7D728B70F167CE088625776E00582C7B?OpenDocument
Regards
Ray Farmer

A reflection error occurred accessing the object.-- Error

I am trying to update from default field value to some other value by using the script definition, however system is throwing the "A reflection error occurred accessing the object."
If anyone has any idea/solution please help me.
regards
Sumanta

Hi Devesh,
I wrote a Field Validation Script and as per your guidelines i update the script,however got the different error.
new changed script
doc.getExtensionField("CURRENCY").get().setDisplayName("AOA");
and also tried with
doc.getExtensionField("CURRENCY").get().setDisplayName("-2147483442:601:AOA");
and the error message received is like
Error executing script: Sourced file: inline evaluation of: ``doc.getExtensionField("CURRENCY").get().setDisplayName("AOA"); . . . '' : target exception.
It is not allowing to modify/update the existing field value by using script.
Please let me know if you have any suggestion.
Regards
Sumanta

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

Getting run time error when accessing the file from frontend server using F4.....?

Category               ABAP Programming Error
Runtime Errors         CONVT_NO_NUMBER
Except.                CX_SY_CONVERSION_NO_NUMBER
ABAP Program           ZMM_MIGO_GOODS_ISSUE
Application Component Not assigned
Date and Time          26.05.2014 14:28:30
Short Text
     "C:\Users\SAP\Desktop\MIGO\MIGO.xlsx" cannot be interpreted as a number
What happened?
     Error in the ABAP Application Program
     The current ABAP program "ZMM_MIGO_GOODS_ISSUE" had to be terminated because
      it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception has occurred which is explained in more detail below. The
     exception is assigned to class 'CX_SY_CONVERSION_NO_NUMBER' and was not caught
      in procedure
     "%_SEL_SCREEN_P_FNAME_V" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated this

HI CHIRUI,
I have changed and tried but still i a getting the same thing..
otherwise please check this i am using some class method i am not getting short dump,but excel file is not getting uploaded.
REPORT ZMM_MIGO_GOODS_ISSUE NO STANDARD PAGE HEADING.
DATA : BEGIN OF IT_DATA OCCURS 0,
         ID(10),
         BLDAT(10),                             " Document Date
         BUDAT(10),                             " Posting Date
         REF_DOC_NO(16),                        " Material Slip No
         DEL_NOTE(16),                          " delivery note
         MATNR TYPE MSEG-MATNR,                 " Material Number
         ERFMG(13) TYPE C,                      " Quantity
         BWART TYPE RM07M-BWARTWA,              " Movement Type
         SOBKZ(1),                              " Special Stock
         WERKS TYPE RM07M-WERKS,                " Plant
         LGORT TYPE RM07M-LGORT,                " Storage Location
         PS_POSID TYPE PS_POSID,                " WBS Element
         COST_CENTER TYPE KOSTL,                " cost center
         ORDER TYPE AUFNR,                      " order number
         SERNR TYPE RIPW0-SERNR,                " Serial Number
        END OF IT_DATA,
        BEGIN OF IT_HEAD OCCURS 0,
          ID(10),
          BLDAT(10),                            " Document Date
          BUDAT(10),                            " Posting Date
          REF_DOC_NO(16),                       " Reference document number
          "HEADER_TXT(25),                       " Header Text
          BWART TYPE RM07M-BWARTWA,             " Movement Type
        END OF IT_HEAD,
        BEGIN OF IT_ITEM OCCURS 0,
          ID(10),
          "ID1(10),
          WERKS TYPE RM07M-WERKS,               " Plant
          LGORT TYPE RM07M-LGORT,               " Storage Location
          VAL_TYPE TYPE BWTAR_D,
          MATNR TYPE MSEG-MATNR,                " Material Number
          ERFMG(13) TYPE C,                     " Quantity
          CHARG TYPE MSEG-CHARG,                " Batch
          BWTAR TYPE BWTAR_D,
          PS_POSID TYPE PS_POSID,                 " WBS Element
          ERFME TYPE MSEG-ERFME,                  " Unit
          COST_CENTER TYPE KOSTL,                " cost center
          ORDER TYPE AUFNR,                      " order number
          CUSTOMER TYPE EKUNN,                    " Account Number of Customer
          SERNR TYPE RIPW0-SERNR,                 " Serial Number
          AMOUNT_LC TYPE BAPI_EXBWR,
          SOBKZ(1),
        END OF IT_ITEM,
          HEADER   LIKE BAPI2017_GM_HEAD_01,
          CODE     LIKE BAPI2017_GM_CODE,
          ITEMS    LIKE BAPI2017_GM_ITEM_CREATE OCCURS 0 WITH HEADER LINE,
          SERIAL   LIKE BAPI2017_GM_SERIALNUMBER OCCURS 0 WITH HEADER LINE,
          RETURN   LIKE BAPI2017_GM_HEAD_RET,
          RET      LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE,
          TESTRUN LIKE BAPI2017_GM_GEN-TESTRUN,
          IT_TAB   TYPE FILETABLE,
          GD_SUBRC TYPE I,
          L_FILE   TYPE RLGRAP-FILENAME,
          IT_RAW   TYPE TRUXS_T_TEXT_DATA,
          COUNT(2) TYPE N,
          TEXT_C(30).
DATA: DATA     LIKE TABLE OF IT_ITEM WITH HEADER LINE.
DATA: IT_TEMP LIKE TABLE OF IT_ITEM WITH HEADER LINE.
DATA: IT_TEMP1 LIKE TABLE OF IT_ITEM WITH HEADER LINE.
DATA: IT_ITEM1 LIKE TABLE OF IT_ITEM WITH HEADER LINE.
SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETERS : P_FILE TYPE RLGRAP-FILENAME.
*             p_test AS CHECKBOX.
SELECTION-SCREEN: END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
   CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
     EXPORTING
       WINDOW_TITLE = 'SELECT FILE'
     CHANGING
       FILE_TABLE   = IT_TAB
       RC           = GD_SUBRC.
   READ TABLE IT_TAB INTO P_FILE INDEX 1.
START-OF-SELECTION.
   PERFORM GET_EXCEL_DATA.
   PERFORM GET_HEADER_ITEM.
   PERFORM UPDATE_DATA.
*&      Form GET_EXCEL_DATA
*       text
* --> p1        text
* <-- p2        text
FORM GET_EXCEL_DATA .
   CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
     EXPORTING
       INPUT = P_FILE
     IMPORTING
       OUTPUT = L_FILE.
   CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
     EXPORTING
       I_LINE_HEADER        = 'X'
       I_TAB_RAW_DATA       = IT_RAW
       I_FILENAME           = L_FILE
     TABLES
       I_TAB_CONVERTED_DATA = IT_DATA
     EXCEPTIONS
       CONVERSION_FAILED    = 1
       OTHERS               = 2.
   IF SY-SUBRC <> 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.
ENDFORM. " GET_EXCEL_DATA
*&      Form GET_HEADER_ITEM
*       text
* --> p1        text
* <-- p2        text
FORM GET_HEADER_ITEM .
   DATA : FLAG(1).
   LOOP AT IT_DATA.
     CLEAR FLAG.
     IF IT_DATA-ID IS NOT INITIAL.
       AT NEW ID.
         FLAG = 'X'.
       ENDAT.
     ENDIF.
     IF FLAG = 'X'.
       MOVE-CORRESPONDING IT_DATA TO IT_HEAD.
       APPEND IT_HEAD.
     ENDIF.
     MOVE-CORRESPONDING IT_DATA TO IT_ITEM.
     APPEND IT_ITEM.
   ENDLOOP.
   DATA[] = IT_ITEM[].
   IT_TEMP[] = IT_ITEM[].
   IT_TEMP1[] = IT_ITEM[].
ENDFORM. " GET_HEADER_ITEM
*&      Form UPDATE_DATA
*       text
* --> p1        text
* <-- p2        text
FORM UPDATE_DATA .
   DATA : COUNT1(10),
          L_QTY TYPE I,
          DAT(10).
   CONCATENATE SY-DATUM+6(2) '.' SY-DATUM+4(2) '.' SY-DATUM(4) INTO DAT.
   LOOP AT IT_HEAD.
     ON CHANGE OF IT_HEAD-ID.
       CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
         EXPORTING
           DATE_EXTERNAL       = IT_HEAD-BUDAT
           ACCEPT_INITIAL_DATE = 'X'
         IMPORTING
           DATE_INTERNAL       = HEADER-PSTNG_DATE.
       IF SY-SUBRC <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
       CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
         EXPORTING
           DATE_EXTERNAL       = IT_HEAD-BLDAT
           ACCEPT_INITIAL_DATE = 'X'
         IMPORTING
           DATE_INTERNAL       = HEADER-DOC_DATE.
       IF SY-SUBRC <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
       MOVE : '2'                TO HEADER-VER_GR_GI_SLIP,
              'X'                TO HEADER-VER_GR_GI_SLIPX.
*      IF r1 EQ 'X'.
       MOVE '05' TO CODE-GM_CODE.
       HEADER-REF_DOC_NO = IT_HEAD-REF_DOC_NO.
       "HEADER-HEADER_TXT = IT_HEAD-HEADER_TXT.
*      ELSEIF r2 EQ 'X'.
*        MOVE '04' TO code-gm_code.
*      ELSEIF r3 EQ 'X'.
*        MOVE '04' TO code-gm_code.
*      ENDIF.
*      IF p_test = 'X'.
*        MOVE 'X' TO testrun.
*      ENDIF.
     ENDON.
     IT_ITEM1[] = IT_ITEM[].
*delete it_item[] where werks = '' and id = it_head-id.
     DELETE ADJACENT DUPLICATES FROM IT_ITEM COMPARING ID MATNR.
     LOOP AT IT_ITEM WHERE ID = IT_HEAD-ID.
*      ON CHANGE OF it_item-id1.
       COUNT1 = COUNT1 + 1.
       CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
           INPUT = IT_ITEM-MATNR
         IMPORTING
           OUTPUT = ITEMS-MATERIAL.
       MOVE : IT_ITEM-WERKS TO ITEMS-PLANT,
              IT_ITEM-LGORT TO ITEMS-STGE_LOC,
*             it_item-lgort1 TO items-move_stloc,
              IT_ITEM-CHARG TO ITEMS-BATCH,
*            IT_ITEM-VAL_TYPE TO ITEMS-VAL_TYPE,
              'FRESH' TO ITEMS-VAL_TYPE,
              IT_HEAD-BWART TO ITEMS-MOVE_TYPE,
              IT_ITEM-SOBKZ TO ITEMS-SPEC_STOCK,
              IT_ITEM-ERFMG TO ITEMS-ENTRY_QNT,
              IT_ITEM-ERFMG TO ITEMS-ENTRY_QNT,
*            it_item-erfme TO items-entry_uom,
*            it_item-sgtxt TO items-item_text,
*            it_item-exbwr TO items-amount_lc,
              IT_ITEM-PS_POSID TO ITEMS-WBS_ELEM,
              IT_ITEM-PS_POSID TO ITEMS-VAL_WBS_ELEM,
              "IT_ITEM-CUSTOMER TO ITEMS-CUSTOMER,
              IT_ITEM-ERFMG TO L_QTY,
              IT_ITEM-AMOUNT_LC TO ITEMS-AMOUNT_LC,
              IT_ITEM-COST_CENTER TO ITEMS-COSTCENTER,
              IT_ITEM-ORDER TO ITEMS-ORDERID.
*             items-SPEC_MVMT = 'R'.
       CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
         EXPORTING
           INPUT = ITEMS-WBS_ELEM
         IMPORTING
           OUTPUT = ITEMS-WBS_ELEM.
       CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
         EXPORTING
           INPUT = ITEMS-VAL_WBS_ELEM
         IMPORTING
           OUTPUT = ITEMS-VAL_WBS_ELEM.
*      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
*        EXPORTING
*          input = it_item-lifnr
*        IMPORTING
*          output = items-vendor.
       APPEND ITEMS.
*      ENDON.
     ENDLOOP.
     DELETE ADJACENT DUPLICATES FROM IT_TEMP COMPARING ID MATNR.
     DELETE IT_TEMP1 WHERE ID <> IT_HEAD-ID.
     DELETE IT_TEMP WHERE ID <> IT_HEAD-ID.
     DATA: MAT_ITM TYPE MBLPO,
           SERNP TYPE SERAIL.
     MAT_ITM = '0001'.
     LOOP AT IT_TEMP.
       SELECT SINGLE SERNP FROM MARC INTO SERNP WHERE MATNR = IT_TEMP-MATNR.
       IF SERNP IS NOT INITIAL.
         LOOP AT IT_TEMP1 WHERE ID = IT_TEMP-ID AND MATNR = IT_TEMP-MATNR.
*    MOVE : it_item1-id TO serial-matdoc_itm,
*     MOVE : mat_itm TO serial-matdoc_itm,
           SERIAL-MATDOC_ITM = MAT_ITM .
           SERIAL-SERIALNO   = IT_TEMP1-SERNR.
           APPEND SERIAL.
           CLEAR IT_ITEM1.
         ENDLOOP.
         MAT_ITM = MAT_ITM + 1.
       ENDIF.
       CLEAR IT_TEMP.
     ENDLOOP.
     CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
       EXPORTING
         GOODSMVT_HEADER       = HEADER
         GOODSMVT_CODE         = CODE
         TESTRUN               = TESTRUN
*       GOODSMVT_REF_EWM      =
       IMPORTING
         GOODSMVT_HEADRET      = RETURN
*       MATERIALDOCUMENT      =
*       MATDOCUMENTYEAR       =
       TABLES
         GOODSMVT_ITEM         = ITEMS
         GOODSMVT_SERIALNUMBER = SERIAL
         RETURN                = RET
*       GOODSMVT_SERV_PART_DATA =
*       EXTENSIONIN           =
     CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
       EXPORTING
         WAIT = 'X'
*   IMPORTING
*       RETURN        =
     IF NOT RETURN IS INITIAL.
       WRITE :/ 'Material Document Number Generated: ' ,RETURN-MAT_DOC,RETURN-DOC_YEAR.
     ELSE.
       LOOP AT RET.
         WRITE : RET-TYPE,    RET-MESSAGE.
*      log-index = sy-index.
*      log-matnr = header-material.
*      log-message = ret1-message.
*      APPEND log.
       ENDLOOP.
     ENDIF.
     REFRESH : ITEMS,RET.
     CLEAR : HEADER,RETURN.
     CLEAR: TESTRUN ,
            RETURN,
            ITEMS[],
            SERIAL[],
            RET[],
            HEADER,
            IT_TEMP[] ,
            IT_TEMP1[].
     IT_TEMP[] = DATA[].
     IT_TEMP1[] = DATA[].
   ENDLOOP.
ENDFORM. " UPDATE_DATA
Regards,
Suresh bheema

An error occured after the installation of SQL Server 2014 Enterprise Edition

As you can see, only the Analysis Services was installed successfully, the rest are failed.
Well, I'm using a 64-bit Windows 8 Single Language, and my ISO file was a 32-bit installer. But why on my other 64-bit PC, it was successfully installed, no such errors like that.
Just in case you need the installation log file, here's the link.

Hello,
I found the following error on the log file you shared:
Error 1406. Could not write value to key \SOFTWARE.
System error . Verify that you have sufficient access to that key, or contact your support personnel.
Please perform the following steps:
1. Open the registry editor.
2. Right-click the HKLM\SOFTWARE key.
3. Select Permissions.
4. Click Advanced.
5. On the Owner tab, select the Administrators group, and then check the "Replace owner on subcontainers and objects"
check box.
6. Click Apply.
7. On the Permissions tab, check the "Replace permission entries on all child objects with entries shown here that
apply to child objects" check box.
8. Click OK.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Processing data for a remote command failed with the following error message: Error occurred during the Kerberos reponse.

Hi!
We have 5 Exchange 2013 servers and when I’m trying to run a script that includes the cmd-let Get-MessageTrackinglog with StartDate = the first of the month and with EndDate = the end of the month I get the following error message after
a couple of hours. The script is run on the server SERVER01 and goes through the Message Tracking logs of all Exchange servers. I have tried the script on other servers and get the same result.
Processing data for a remote command failed with the following error message: Error occurred during the Kerberos reponse.
[Server=SERVER01, TimeStamp = 918/2014 19:32:34]
For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo
: OperationStopped: (server01.domain.com:String) [], PSRemotingTransportException
    + FullyQualifiedErrorId : JobFailure
    + PSComputerName
: server01.domain.com
I have gone through “about_Remote_Troubleshooting Help topic”, but can’t find anything related to my issue. There is nothing in the Application or the Windows PowerShell log either.
/Henrik

Hi Henado
Check the time on your Exchange server(s) relative to the DCs and ensure they are in correct sync
Use another account which is assigned the Organization Management permission and log to to the server run the command in shell and see the results
Run
Add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.E2010
Set-Adserversettings -ViewEntireForest $True and then run message tracking command and see the results
If none of the above helps you may need to remove and re-install the WinRM and see the results
Good Luck :)
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

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

"an error occurred saving the activex control"

I'm trying to compile an executable in Labview 5.1. When I run the build app, it gets about half way done then pops up the error:
"an error occurred saving the activex control"
After clearing the error message, it proceeds to go through the motions of compling the app, but no exe is generated.
The design mode progam run operates fine, and it saves fine as well in design mode.
Thanks!

wawatts,
Though Brian and I got a broken arrow because we didn't have the necessary ActiveX component installed, I imagine you get no errors on the development system because you do have the component.
This problem would be much harder to pin down on your side given the lack of development-environment errors and the sprawling design of the main VI. One possible troubleshooting approach would be the LabVIEW Find functionality (Edit >> Find). ActiveX functionality typically involves the use of Property Nodes and Invoke Nodes, so if you search for any Invoke Nodes (Select Object, then Functions >> Communication >> ActiveX >> Invoke Node) in the scope of your main VI and its subVIs, you could perhaps have turned up some hits that take you to the subVI that has the control that is presumably causing the problem.
Unfortunately, I fear that finding the problem area doesn't solve the problem. It seems to me that either the LabVIEW app builder or the ActiveX component is doing something unexpected or nonstandard that is leading to the error message.
I'm going to stick to my "upgrade the software as much as possible" guns:
1. Install the LabVIEW 5.1.1 patch I linked to above, if it isn't already installed. There were fixes to the development environment and changes to the app builder that might resolve your problem. This is a free patch.
2. Consider upgrading the ActiveX control. I think that the latest version is called IntuiLink for 54600-series Oscilloscopes, Version 3.1, and it's available here on the Agilent site.
It was easy to do a simple test using your Xezgetsetup.vi on my system (LabVIEW 7.1.1, XP) with the updated ActiveX control. First, I installed the Agilent software. Then, I right-clicked inside the ActiveX control on the front panel of Xezgetsetup.vi, chose Insert ActiveX Object, and selected Agilent 54600 Scope Control from the list. Then I had to go to the block diagram and relink a few of the property and invoke nodes by just left-clicking on broken nodes and re-selecting the items that your code was already displaying. That fixed the VI so that it would run again.
Then I built that VI into an EXE and got no errors.
Perhaps all this proves is that you would have clear sailing if you upgraded to LabVIEW 7.1 and got the most recent Agilent ActiveX control--and maybe this is a good reason to bite the bullet and do that upgrade now--but it's certainly possible that you can do the same thing in 5.1 and solve your problem. Worth a shot.
Hope that helps,
John

"An error occured saving the ActiveX control"

I pulled up an old LabVIEW program today
that I used to work on under Win-NT.
Now I use Win-XP.
We're talking about LabVIEW 5.1.1 on this program.
The program suddenly throws
"An error occured saving the ActiveX control"
when I try to save the program.
Never saw this under NT.
Anybody knows what this is about ?
Martin

Thanks for posting but we need more information.
Do you have activeX controls in the VI? Are you using 3d graphs? Does the VI run on XP? What version of LabVIEW do you have?

An impersonation error occurred using the security context of the current user. -- Report server is on remote server and file share folder is on local server

I have deployed a report on the server (e.g. remoteserver\reports) from my local machine. I opened the report in browser in my local machine and created a new subscription with windows file share delivery option.
But its giving an error "Failure writing file \\localserver\subscriptions\Report1.xls : An impersonation error occurred using the security context of the current user." Here "subscriptions"
is the folder which I have created in my local machine.
I followed the instructions found in the link "http://msdn.microsoft.com/en-us/library/ms157386.aspx"
Please help to solve this issue.

Hi,
Thank you for your reply.
I have followed the same process. The credentials which I have given are same as my PC. But I am getting the same error. Can you please clarify the statement "Service
account that is using for file share subscription should have write access to shared folder."
given in the above link?
I am the one who created the folder and subscribing the report, so probably I have the full write permissions to the shared folder. What is the service account in this context?
I think the problem is, I am deploying the report on the server and creating the shared folder in the local machine. I tried giving shared folder permissions to the user on the server. But my local machine is in local domain and I cant access the users on
the remote server. Do I need to create a shared folder on the server? I am new to SSRS. Please help me.
PS: I have assigned with all roles viz. Browser, Content Manager, Publisher, Report Builder etc. and My Role name (WEBSERVER\User)
is different from my local user name (domain\username) in domain.

I had to reinstall my itunes, and it wont reinstall, instead saying there was "an error occurred during the installation of assembly microsoft.vc80.crt.type = win32 version 8.0.50727 6195 public key token 1fc8b3b9a1e18e3b processorarchitecture = x86.

i had to reinstall my itunes, and it wont reinstall, instead saying there was "an error occurred during the installation of assembly microsoft.vc80.crt.type = win32 version 8.0.50727 6195 public key token 1fc8b3b9a1e18e3b processorarchitecture = x86.
I have taken all apple products off my computer per other suggestions, I have run malwarebytes with no viruses found, and have even tried installing itunes as a different user on my computer but get the same message everytime.

See Troubleshooting issues with iTunes for Windows updates.
tt2

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

Similar Messages

Maybe you are looking for