Error 5 LabView

Hola buen dia!
Actualmente estoy corriendo una prueba la cual recopila diversos datos de presion y tempertura con este equipo:
cDAQ-9178
NI 9205
NI 9435 
NI 9425 
NI 9476
NI 9264 y otros
El problema que he estado teniendo es que a cierto tiempo me aparece este error:
Agredeceria mucho su apoyo para poder darle solucion a este error 
Saludos y muchas gracias!

Que tal deyvid01 Buenos Días:
Estuvimos analizando todo el código y quería comentarte varios puntos que te recomendaría cambiar ya que tiene muchas secciones que te pueden causar problemas.
Estás utilizando muchas Variables Locales lo que está causando condiciones de carrera que causan que tengas datos repetidos o pérdida de datos a través de tu programa ya que no está controlado cuando lees esas variables locales y cuando se escriben. Te recomiendo siempre utilizar Cables y agrupar los datos en Clusters para reducir el tamaño del código.
Existen muchas estructuras "Stack Sequences" que no son lo más recomendable para tu aplicación ya que una vez que entras a las Stack Sequences no puedes modificar el orden de los casos y no te puedes salir de ellos en caso de un error o que tengas que detener el programa. Te recomiendo revisar la arquitectura de Máquinas de Estados. Estas estructuras también van a causar que en algunas ocaciones parezca que el programa no responde, está lento o se traba la interfaz de usuario.
No existe manejo de errores en el código por lo que es muy complicado encontrar el error si no tenemos el setup completo para probarlo ya que la arquitectura no nos permite seccionar el programa para probarlo.
Como te comentaba en los primeros posts y como menciona también Guillermo en la última publicación en la sección de escritura al archivo estás utilizando varios Write to Spreadsheet en tus estructuras y esto se encuentra dentro de un ciclo While. El VI de Write to spreadsheet es un VI de Alto nivel que internamente abre la referencia al archivo escribe o lee y después lo cierra. Esto lo hace cada vez que lo mandas llamar en el ciclo While, esto no es nada eficiente para el programa y puede causar los errores que te están apareciendo de manera aleatoria en lo que corre el programa.
Para un programa que tiene tantas cosas diferentes en cuanto a funcionalidad yo recomendaría que se tomaran los cursos que ofrecemos en los que se cubren diferentes arquitecturas para resolver aplicaciones como la que tu tienes. Estas arquitecturas te darán las herramientas necesarias para resolver los puntos que te menciono anteriormente. (Core 1, 2 & 3).
Lo que podemos hacer actualmente es tratar de reparar la parte que esté fallando pero la aplicación no será escalable, mantenible o legible si se quieren realizar cambios en un futuro.
Para acotar la fuente del error te pido que realices lo siguiente:
Correr el programa pero dejar deshabilitado el botón "Enable" que tienes en la sección de escritura D.5 esto para que no se ejecute la sección dentro del Case Structure. Dejar correr el programa para revisar si aparece el error.
En caso de que no aparezca habilitar el enable y utilizar la estructura "Disable Structure para deshabilitar toda la sección que viene después del primer SubVI llamado Write Characters to File.vi (solo que se encuentra dentro del case structure) en la sección D.5, segundo frame, dentro de la estructura de casos. Dejar correr el programa y revisar si aparece el error.
Realizar la misma operación que el paso 2 pero ahora deshabilitar el código que sigue después del SubVI llamado Write to Spreadsheet File.vi.
Realizar la misma operación habilitando ahora el SubVI, Read From Spreadsheet.vi.
Reportar cuando apareció el error. 
Saludos
Juan Arguello
National Instruments México y Latinoamérica
Applications Engineer

Similar Messages

  • Fatal error Labview.lib not called from a Labview process

    in teststand my vi works fine with adapter set for LV development
    when I configure the LV adapter for runtime, I get fatal error Labview.lib not called from a Labview process
    what is going on?
    how do I fix it?
    thanks.

    Howdy Stephen -
    Are you by chance calling a LabVIEW DLL within your LabVIEW VI which is being called from TestStand?  I know this error occurs when a LabVIEW DLL built in a different version of LabVIEW than the selected Run-time Engine.
    Here is a KnowledgeBase which references the issue:
    KnowledgeBase 203EA3XC: LabVIEW.LIB Error When Calling a LabVIEW DLL Built with VIs That Use Externa...
    If this is the case, you will need to open the LabVIEW DLL source VI in the LabVIEW version you are using and rebuild the DLL.
    Thanks and have a great day!
    Regards,
    Andrew W || Applications Engineer
    National Instruments

  • Teststand generates error ' labview has encountered a problem and needs to close'

    Hi,
    I am using Teststand 3.1 and Labview 7.1.
    My problem is that I have a 1D array of 6 elements in Labview that I need to receive from Teststand.
    If the array size is set to variable in Labview there is no problem but if I set it to what I require ( fixed 6 ) then when I specify module in Teststand an error message appears , ' LAbview.exe has encountered a problem and needs to close '. Then I get an 18001 about ActiveX as labview has closed.
    Why does this happen ?, is it a bug ?

    No bother its attached !
    The vi writes to a global variable.
    The 'Bytes To Send ' 1D array seems to be the trouble, If its set to fixed 6 in LV then Labview crashes from Teststand when I specify module.
    If its set to variable its ok.
    Attachments:
    Global_Write.vi ‏26 KB

  • Fatal error: LABVIEW.LIB was not called from a labview process

    I have built a very simple executable which uses shared variables which should talk to an OPC server. When I try to run it on the target machine, I get this error. Does anyone know what it means?

    If you up/down graded from 8.2 to 8.5 then I would suggest doing a mass compile on the VI's into a new folder (or have a backup of your files somewhere).
    You can do this via LabVIEW > Tools > Advanced > Mass Compile.
    Please let me know how this turns out.
    All the best,
    Message Edited by rsw on 01-08-2008 07:02 AM
    Applications Engineer

  • Deployment teststand error (labview test - sequence context)

    Hello,
    I need help by deploying my workspace to the deployment(target)computer. That is what I have done:
    - i create a workspace, in this workspace are different sequence files and the vi´s which i have created.
    - then i use the deployment tool (teststand) and deploy the workspace to a directory in the network.
    - after that i copy the modified SequentialModel.seq to the target maschine.
    - now if i want start the sequence file an error occured. Teststand can`t start my vi´s because it can`t find files like LabVIEW Test - Sequence Context, TestStand - Set Property Value (Boolean Array). Choosing the path of the file in the search directory doesn`t help.
    Maybe i have made an error with the deployment tool?! How is the right way to deploy in a network without using an installer. Iám using teststand 3.0.
    thankyou
    Schwede

    Hi Schwede
    If you want to deploy your Sequence File and the Processmodell you have to copy first your original Processmodell from the NI folder to the user folder.
    Than open the deploy-tool and load your workspacefile. Mark the point "deploy files in Teststand user directories" and define the image path. Don't mark the "create installer" field.
    You will get and image folder with several subfolder.
    In the target subfolder you can find your sequencefile. In the Teststand subfolder you can find your customized Processmodell or Operator Interfaces. Attention, please use relative paths when you create your workspacefile.
    hope this helps
    Manuel Wielander
    National Instruments

  • Error Labview 2010 installation

    I get an error when i am installing LabVIEW on a System with : WinXP SP3. I tried this by starting the setup. The autorun.exe cannot start (Signature: ErrorEventType : InPageError     P1 : c000003c     P2 : 00000005   )
    I have all the versions (from LV7.0 to LV2009SP1) installed on my Computer.
    Can Anybody Help?? (i have already LV2010 on my laptop with Win7. but i need it on my computer also)
    A million thanks for any help.
    RENN
    Kudos always welcome for helpful posts

    Hi Philip,
    Thanks a lot for your reply!
    could you please explain me why this happens and why should i register this dll.
    Note: after running the command i got another error (Load Library error). dll not found. But its already in System 32.
    RENN
    Kudos always welcome for helpful posts

  • Download PDF, Runtime Error & LabVIEW Crash

    Hello
    I create a VI to download a PDF file with an HTTP request (using WebBrowser). This VI is used in a TestStand application. When it's working, the following Internet Explorer window opens suggesting to Open/Download/Cancel a pdf file. I used this solution because the TestStand execution doesn't stay blocked on this VI until the user make a choice (Open/Download/Cancel) (the execution must continue to next steps without waiting for a user action).
    When it's working fine :
    The problem is that sometimes (executing with labview or teststand) a runtime error or a labview crash (or both) occurs :
    Examples of errors :
    Here I put the block diagram of the VI (the left part enable to build the url) :
    Have you any idea of what cause this error ?
    Or have an other solution to process this operation (a solution where the PDF file is automatically openned would be better !).
    Thanks for your help !

    You can open a PDF within LabVIEW using this VI:
    http://digital.ni.com/public.nsf/allkb/9A6A259EB5A2BEDA86256DD00048C604
    Thoric (CLA, CLED, CTD and LabVIEW Champion)

  • Program Error : Labview.ex​e has generated errors,,et​c? Any Ideas

    I keep getting this error popup titled Program Error.  The message reads, "LabView.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created." 
    This appears to happen randomly including while a program is running, while LabView is sitting idle and even after I've closed Labview. I am running 8.0 on Windows 2000. Any ideas?

    Hello Paul,
    There is actually a great online Knowledgebase that explains where you can find error logs, and I have linked it for you here. If you don't get a prompt from LabVIEW after the crash to "investigate the error" (which simply guides you through the process of submitting your error log), then you can submit your error log directly by going here and choosing "Email NI". Be sure to include a detailed description about how to reproduce the crash or what circumstances increase the frequency of crashes like this.
    Kind Regards,
    E. Sulzer
    Applications Engineer
    National Instruments

  • Installation error: Labview 11/2011 RT deployment

    I am trying to install Labview RT 11 to my PXIe-8133 controller. 
    I go to MAX 5.0, add/remove software to my controller, and select Labview RT 11 only (and all automatic dependencies).  When I do this, installation proceeds fine, the PXI controller reboots and shows the Labview RT status screen with 8 cores and cpu usage, etc.
    When I go to MAX 5.0, add remove software to my controller, and select Labview RT 11 and DAQmx 9.35 (and all automatic dependencies), the installation fails with this error message:
    NI-Generic-DesktopPC-xxxxxxxx (192.168.1.21): The specified file was not found. 
    Local file: C:\Program Files\National Instruments\RT Images\NI-DAQmx\nilesrInstall.ocm
    Remote file: /ni-rt/system/nilesra.ocm
    When I browse to C:\program files\national instruments\rt images\NI-DAQmx, I do not see nilesrInstall.ocm
    I rechecked my installation options from the NI Driver CD, and it seems like I got everything that seems relevant.  What are the prerequisites to install this feature?  Do I need something from the extended development suite or something?
    Solved!
    Go to Solution.
    Attachments:
    nilesrinstall_ocm.png ‏26 KB

    Hi there,
    I would perform a repair of your DAQmx drivers by following along with How Do I Uninstall or Repair National Instruments Software?
    This should replace any files that you are missing.
    If this does not work please let us know.
    Scott A
    SSP Product Manager
    National Instruments

  • Error labview 8.2.1 "unable to open resource files"

    LabVIEW 8.2.1, on Vista 32 bit, was working. Now the student that gets "unable to open resource files" when he tries to launch LabVIEW 8.2.1.
    He tried repair under Add Remove Programs, no change.
    Student then uninstalled LabVIEW so he could reinstall from scratch.
    Before installing he noticed a LabVIEW icon on his desktop.
    He had accidentally move the LabVIEW executable to the desktop from the LabVIEW folder, thus causing the "unable to open resource files" error.
    The question is why did the repair not catch that the LabVIEW executable was missing in the LabVIEW folder and restore it?
    Thank you for your assistance.

    If repairing doesnt work I will reinstall lv.

  • Error: labview run engine 8.5 not found on the system

    Hi,
    I am getting the error attached when ever i click on additional installer. How to resolve this?
    Thanks
    kavitha
    Attachments:
    err.JPG ‏136 KB

    Hi,
    When i try to install it is showing higher version is already installed(attachment 1.jpg) and when  i searched it is showing as in attachement 2.jpg
    Thanks
    Attachments:
    1.JPG ‏172 KB
    2.JPG ‏70 KB

  • NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

    This problem seems similar to the post "Resource not found error in executable on developmen​t machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
    I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards. 
    I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010.  The code was using a custom executive and my task was to rewrite the test using TestStand 2010.  I reused the majority of the old code.  The old code used NI-5660 to control the 5600 and 5620.  When I run my sequence using the LV Development System and TestStand, it runs without any issues.  When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues.  It warns that the nipxi5600u​.dll was not initialized correctly.  Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter.  The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again. 
    I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace.  I also used Dependency Walker to track down the problems with the nipxi5600u​.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32).  I have also performed a Mass Compile to make sure everything was running in LV 2010.  If I skip the steps involving the 5660, my entire sequence runs fine. 
    The previous code was running with the LabVIEW Run-Time Engine without any issues.  Is there just a step I am missing?  Has anyone seen anything like this before?  I can send screenshots of errors to provide more detail if necessary. 

    I have tried some more things and still can't get it to work.  I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs.  This did not change the results. 
    When I try to run my sequence, The first error I get is shown in Error 1445.bmp.  This happens when I try to use the NI 5660 initialize.vi.  If I click ignore, the next error I see is shown in Error -20551.bmp.  When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp.  When I close TestStand, I get the error LabVIEW Fatal Error.bmp. 
    Attachments:
    Error1445.JPG ‏164 KB
    Error -20551.JPG ‏174 KB
    Error loading nipxi5600u.JPG ‏9 KB

  • More than 1 ms MOMO digital IO 7358 in LabView Real-Time 8.5, error downloading EPOS dll file into RT

    Hi all,
    I have several problems here, I tried to google but still I could not solve the problem.
    Here are my questions:
    1. I tried to download an example program of EPOS which require to download a DLL file into the RT, but it failed, here's the error (I attached the picture) 01/02/2008 13:29:50.511 [error] LabVIEW:
    Failed to load shared library EposCmd.dll:_VCS_GetProtocolStackName@16:C on RT target device.
    From the NI.com forum,
    I found a similar problem and it said by installing Network Variable Engine and Variable Client Support into the LV-RT, and I did, but still failed. Any one can help me about this?
    2. I posted a question also in lavag, I think this section is more appropriate. "I
    am trying to use the digital IO of the motion controller of 7358, but then I realized the delay is more that 1 ms (I checked using the oscilloscope), I attached the code (MOMO = Must On Must Off). Is this real, I mean the hardware delay between on-off is as big as this? Anyone knows the solution for this?"
    Note: I am using LV-RT 8.5, PXI-7358 Motion Controller, EPOS 70/10
    Thank you for any help
    Message Edited by bono02 on 01-02-2008 05:47 AM
    Attachments:
    maxon-rt3.JPG ‏120 KB
    momo1.JPG ‏55 KB

    Hello bono,
    1.  From what I have seen, this error is usually caused by one of two things.  The first is the Shared Variable software components not being installed, which is covered in this Knowledgebase.  The other is due to a corruption of the ni-rt.ini file on the Real-Time controller.  You can follow the steps layed out in this Knowledgebase, which gives three possible remedies.  You could also try reinstalling the software (firmware) or create a PXI Uninstall disk from Measurement & Automation Explorer by selecting Tools»Remote Systems»RT PXI Disk Utilities»Create PXI Uninstall Disk.  Boot the PXI Controller from the PXI Uninstall Disk, which will erase the ni-rt.ini and ph_exec.exe on the target.  However, you will need to reconfigure the controller after doing this.
    2.  Due to the nature of the digital I/O on motion controllers, it is not surprising that you are seeing around a 1ms delay.  It deals with the fact that it must update the motion controller with the new value on each control loop.  This Knowledgebase gives a little more clarification regarding the 7350 specs.
    Carlton
    CLD

  • Why does labview generate Dr. Watson error "C0000005 access violation"

    I am running Labview 5.1.1 in Windows 2000 Professional on a machine with the following configuration
    *----> System Information <----*
    Computer Name: ANDANTE
    User Name: Administrator
    Number of Processors: 2
    Processor Type: x86 Family 6 Model 8 Stepping 3
    Windows 2000 Version: 5.0
    Current Build: 2195
    Service Pack: 4
    Current Type: Multiprocessor Free
    I have all of a sudden begun to experience labview crashes. The crash occurs systematically after tens of minutes; not just a few minutes, but not more than an hour or so. I am running a vi but not actively interacting with the machine (no other applications running, not even moving the mouse around). The problem happens even when running a vi that I have run successfully for extended periods of time (overnight) only 3 months ago. I have tried it with two different vis, one that I have recently made a lot of modifications to and another that has not been touched for months (since before the crashes began), and it happens with both vis. They do much different things (communicate with different GPIB or PCI boards, write to different kinds of files in different locations, etc.), so the problem seems to be vi-independent.
    When the crash occurs, I see a dialog appear with the error
    labview.exe has generated errors and will be closed by windows. You will need to restart the program. An error log has been created.
    The Dr. Watson error log is generated and the error is
    Application exception occurred:
    App: (pid=1160)
    When: 4/25/2004 @ 01:57:56.640
    Exception number: c0000005 (access violation)
    I always get the same Dr. Watson error information -- i.e., it is very reproducible. I don't really know how to interpret the rest of the Dr. Watson log, but I include the report on the first thread, which is the one with the "FAULT" in it, at the end of this email.
    Looking around on the web, it may be that a temporary virus infection could have created the problem. In the period since the machines was last successfully used, I have seen two files be infected by the W32.Welchia.B.Worm virus, the files were svchost.exe and WksPatch[1].exe. These files have been quarantined and no other infected files have been found since this error began to appear.
    Any ideas? I've seen on the web that reinstalling Windows 2000 and/or upgrading to Labview 7.0 might solve the problem, but it would be nice to get some confirmation before taking the time/spending the money.
    Here is the state dump for the thread with the FAULT in it, as provided by Dr. Watson:
    State Dump for Thread Id 0x574
    eax=00000062 ebx=00000000 ecx=00000000 edx=00000004 esi=00000000 edi=05692214
    eip=00748236 esp=0012fb28 ebp=0012fb28 iopl=0 nv up ei pl zr na po nc
    cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
    function: StrLen
    00748230 55 push ebp
    00748231 8bec mov ebp,esp
    00748233 8b4d08 mov ecx,[ebp+0x8] ss:00ba9a0e=????????
    FAULT ->00748236 8a11 mov dl,[ecx] ds:00000000=??
    00748238 8d4101 lea eax,[ecx+0x1] ds:00a79ee6=????????
    0074823b 84d2 test dl,dl
    0074823d 7407 jz GetCDReg+0x6f6 (00750c46)
    0074823f 8a10 mov dl,[eax] ds:00000062=??
    00748241 40 inc eax
    00748242 84d2 test dl,dl
    00748244 75f9 jnz CfgRemove+0x44f (0074ae3f)
    00748246 2bc1 sub eax,ecx
    00748248 48 dec eax
    00748249 5d pop ebp
    0074824a c3 ret
    *----> Stack Back Trace <----*
    FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
    0012FB28 00737A74 00000000 00000000 05692214 00000400 !StrLen
    0012FC40 00736A45 050753E4 05692214 0012FC6C 00736724 !SetKeyboardHandlerProc
    0012FC50 00736724 05692214 0012FCB4 05692214 BDBC0000 !SetKeyboardHandlerProc
    0012FC6C 00736627 05692214 0569232C 00000400 00000000 !SetKeyboardHandlerProc
    0012FC98 0074B470 0012FCB4 BDBD0001 00000000 0569E8E0 !SetKeyboardHandlerProc
    0012FCD0 0074ACD0 00000000 0074AC10 0569FFA4 010A2418 !CfgRemove
    0012FCE8 007808D5 00000000 00000000 00000001 00000000 !CfgRemove
    0012FD08 007ACEB6 00000000 00000000 77E18F95 00000000 !ChkOccurrences
    0012FD9C 006033DE 00000001 00000000 77E2ADC1 007A5C80 !WMainLoop
    0012FF24 007B2186 00400000 00000000 00000001 00000001 !WMain
    0012FFC0 7C581AF6 005C0057 0061006C 7FFDF000 C0000005 !inp
    0012FFF0 00000000 007B2030 00000000 000000C8 00000100 kernel32!OpenEventA
    *----> Raw Stack Dump <----*
    0012fb28 40 fc 12 00 74 7a 73 00 - 00 00 00 00 00 00 00 00 @...tzs.........
    0012fb38 14 22 69 05 00 04 00 00 - 16 4d 65 74 68 6f 64 20 ."i......Method
    0012fb48 4e 6f 74 20 49 6d 70 6c - 65 6d 65 6e 74 65 64 00 Not Implemented.
    0012fb58 55 1f f8 77 18 25 f8 77 - 2f a8 fd 74 c4 01 00 00 U..w.%.w/..t....
    0012fb68 05 a5 fd 74 d0 26 ce 01 - 00 00 06 01 10 04 00 00 ...t.&..........
    0012fb78 00 00 00 00 00 00 00 00 - 2e fb 69 05 42 e9 69 05 ..........i.B.i.
    0012fb88 c1 2f 7b 00 00 00 00 00 - 12 04 00 00 11 04 00 00 ./{.............
    0012fb98 30 fb 69 05 12 04 12 00 - bb 35 7b 00 00 00 06 01 0.i......5{.....
    0012fba8 11 04 00 00 00 00 00 00 - 00 00 00 00 2e fb 69 05 ..............i.
    0012fbb8 35 34 7b 00 4c 34 7b 00 - 48 00 06 01 f8 fb 12 00 54{.L4{.H.......
    0012fbc8 10 04 00 00 ec 53 07 05 - 11 04 00 00 08 fc 00 00 .....S..........
    0012fbd8 ee c8 77 00 30 fb 69 05 - 11 04 00 00 00 00 00 00 ..w.0.i.........
    0012fbe8 00 04 00 00 01 00 00 00 - ec 53 07 05 00 04 00 00 .........S......
    0012fbf8 00 38 83 00 1c fc 12 00 - 23 ca 77 00 00 38 83 00 .8......#.w..8..
    0012fc08 40 ff 69 05 01 00 00 00 - 00 00 00 00 2d 00 00 00 @.i.........-...
    0012fc18 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
    0012fc28 00 00 00 00 00 00 00 00 - 00 00 00 00 01 00 00 00 ................
    0012fc38 50 fc 12 00 1a 6a 73 00 - 50 fc 12 00 45 6a 73 00 P....js.P...Ejs.
    0012fc48 e4 53 07 05 14 22 69 05 - 6c fc 12 00 24 67 73 00 .S..."i.l...$gs.
    0012fc58 14 22 69 05 b4 fc 12 00 - 14 22 69 05 00 00 bc bd ."i......"i.....

    For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as supplementary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistently.

  • LabVIEW: Null window error in an application?

    Hi there,
    I just built an application from a vi and I am encountering an error:
    LabVIEW:  Null window.
    The top-level VI "name1.vi"
    was stopped at unknown on the block diagram of "name2.vi".
    The application runs smoothly until the user selects some hotkeys to open a simple subvi briefly during execution in order to check on a file path.  This hot key combination works perfectly when the normal vi is running and the subvi displays the information and then closes and the vi execution continues.  Why would it not work when it has been built as an application??
    Thank-you for any help you can provide!
    Solved!
    Go to Solution.

    Solved my own problem - should have dug a bit deeper before posting - sorry!
    http://digital.ni.com/public.nsf/allkb/D95BDEB7A7E211AE86256EDA005517F4?OpenDocument

  • Problems with Labivew 2013 / 14 install - Ni Variable Engine error and Labview does not close, processes do not stop when I run Vis.

    Hi All,
    I am hoping at all my problems are relateded to a problem I am experancing, when I look into my windows 7 (64bit) event viewer near every time I boot up I get an error regarding the NI Variable Engine which reads.
    The description for Event ID 0 from source NI Variable Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    C:\Program Files (x86)\National Instruments\Shared\Tagger\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.
    and a second which is the same apart fomr the last line
    Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318
    I have tried uninstalling all labview things and I have tried repairing all labivew programs. Along with this I got this error when I installed Labview 2013 so I thougth why not try 2014 and I still get the same problems. I also shoudl point out I use bot 32 bit and 64 bit versions of labivew. I have installed labview on many machines before but never encountered this problem. That being said this was a new clean windows install.
    Along with thiese errors labview heardly ever shuts down properly when I close the program it just freezes and needs forshed shut down.
    Apart form this I noticed that when I run any of my Vis which I have never had problems with in the past and I stop the program somtiems processes keep using CPU such as "lktsrv.exe"
    I really need to get this sorted out because its morstly the crushing and processes not stopping which is rather annoying.
    I shoudl also say that these problems are both in the 32bit and 64 bit versions of labview not difference. and no difference if its 2013 or 2014
    Cheers

    Hi GajanS,
    Thanks for your reply sorry I havetn noticed anybody had replied as I stopped hoping for any responce before then.
    I have attached a screenshot of the four processes that seems to be giving me a problem.
    I have actually managed to find the program causing labivew to crash was in fact my antivirus software which I have now removed and have no more problems with labview crashing on shutdown.
    After removing it I tried the repair feature again for all my labview programs but sadly the one persistant problem remaining is still the four processes using around 13% processor each. I have found out this happens sometime after booting up regardless of if I run labivew or not. So it does not directly seem related to the running of any labview applications but rather a bug in the labview software.
     the processes are:
    lktsrv.exe
    tagsrv.exe
    nidmsrv.exe
    lkads.exe
    as shown in the task manager.
    I would relaly help if I can get this sorted out.
    Cheers
    Attachments:
    Screenshot 2015-03-24 21.50.00.png ‏12 KB

Maybe you are looking for

  • Can't download numbers from icloud

    Numbers spreadsheet not downloading from iCloud

  • Is "Process scoped identity" the same thing as TopLink shared cache?

    Bumped into this thread on my investigation of ORM solutions: http://forum.hibernate.org/viewtopic.php?t=939623&highlight=toplink What I would like to know is whether "Process scoped identity" as Gavin King puts it, is the same as TopLink shared cach

  • Blackberry keeps locking itself

    My blackberry keeps locking itself in the middle of me using it without me even pressing the lock button? its really annoying because it will lock and then i try unlock it and then it locks again and freezes and then the buttons and scrolls stop work

  • How to Change language in spell check for CS4?

    How do I change language in spell check for CS4?

  • One-shot acquisition AVT Guppy

    Dear I'm trying to acquire 1 one image using the trigger input of a AVT Gyppy F-080B camera. In the manual of the Guppy I found the "One-shot" mode to acquire just one image from the camera using the trigger input. So far I have the code attached tha