Network Variable Engine in application started in autorun

Using CVI 2009 SP1 I developed an application that uses Network Variable Engine:
At the beginning of main I wait in a do-loop until the Variable Engine is running
t_start = Timer();
do {
CNVVariableEngineIsRunning(&running);
if (!running) {
t_rem = 20.0 - (Timer() - t_start);
if (t_rem > 0.) Sleep(100); //100 ms
} while (!running && (t_rem > 0.));
 Then I create a buffered subscriber, previously checking that the process exists and is running
CNVProcessExists (processName, &exists);
if (!exists) {
CNVNewProcess (processName);
CNVProcessIsRunning (processName, &isRunning);
if (!isRunning) {
CNVStartProcess (processName);
CNVCreateBufferedWriter (NetVarPathname, ConnTransferredCallback,
ConnStatusCallback, NULL, 10, 10000, 0, bufferedWriter);
This application works perfectly when I launch it as standalone application.
But If I launch it at the Windows boot time through Start >> Programs >> Startup, CNVCreateBufferedWriter( ) returns -6337 (The network variable process was not found or is not responding).
Does CNVStartProcess( ) need a delay time?
How can I avoid this annoying error?
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

CNVProcessIsRunning only checks if the process is configured to run when the Variable Engine is started...
I think this advice should be added to the function help.
But in cases where this function is called during system startup, it is unreliable because the Variable Engine could still have not loaded...
As I write in the first message, the first function I call in my application is CNVVariableEngineIsRunning( ), then I wait until it returns "is running". Why does the NVE could still have not loaded after "is running" has been returned?
A workaround for this problem and correct indicator of the availability of the process is to programmatically browse to the process:
CNVBrowser browser;
CNVCreateBrowser(&browser);
CNVBrowse("\\\\localhost\\your-process-name");
CNVDisposeBrowser(browser);
If CNVBrowse succeeds, then the process is running. Please let us know if you run into issues with this workaround.
Done. After this, I've never seen the error anymore... but I'll check again.
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Similar Messages

  • Shared Variable Engine not always started

    I'm experiencing an intermittent problem with the LabVIEW variable engine.  The National Instruments Variable Engine service is configured to start automatically with Windows but that doesn't seem to always be the case.  Every now and then I'll load my application only to find red LED indicators on all of the controls accessing my shared variables.  I'll bring up the variable manager and stop/start the service, restart my application and then they're all green LEDs and everything works.  Any idea what might be causing this?
    Thanks,
    - Kevin Handy

    Hi Kevin.  I don't know what causes the problem, but I have seen it on our systems as well.
    Our solution was to have our application stop and then start the variable engine every time
    it launches.  Stopping might not be ok for you depending on how your applications are
    architected, but for us it is fine.
    We use two System Exec.vi calls, with the following strings:
    net stop "national instruments variable engine"
    net start "national instruments variable engine"
    Haven't had any instances of the application coming up w/o the variable engine since
    we added this initialization step.
    Matt

  • [Forum FAQ] Why does Office 2013 cost more network flow when the application starts by default?

    Recently, we’ve heard that our customers encounter high network traffic since they large-scalely deploy Office 365/2013 within the domain/site. Does this behavior relate to the new Office? Or does Office 365/2013 cost more network resources in this case?
    To troubleshoot this, we consider to analyze what happened during the process by Network Monitor tool. 
    Start a new capture first and launch Office Word 2013, get the following things as the screenshots:
    According to the information above,
    in addition to the network authentication flow, we could notice that the Word.exe would download a lot of PNG files from the link “/en-us/templates”. What about those PNG files?
    Let us try to directly visit them via IE:
    http://office.microsoft.com/en-us/templates/TM103463086.png?ts=AOLhIeGIzwg
    Beyond question, they are the thumbnails of the Office template which are downloaded while the Office application starts by default.

    In
    some certain circumstances,
    we might disable it by Office option or Group policy.
    Disable Start Screen by Office 2103 UI:
    Open Office 2013 application, go to File in Ribbon > Options tab > General page > under the section of Start Screen options, uncheck the options "Show the
    Start screen when this application starts"
    Disable Start Screen by Registry key:
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\General
    DisableBootToOfficeStart (DWORD): set the value
    to 1
    Disable Start Screen by Group Policy:
    Disable Start Screen by OCT:
    That's all. If you have any questions or concerns about this topic, feel free to post here.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

  • Deploy Shared Variable Engine in localhost

    I need to talk to multiple RTs using single computer. It seems
    obvious to deploy shared variable engine (libraries) in localhost instead of
    RT. However, the problem is the shared variables (read) used in localhost VIs
    are not being updated from RTs. But when I am using another local VI to update
    the shared variable, it is working just fine. The variable path of the RT looks
    like "\\My Computer\Local NPSVlvlib\Test
    Data". I think this is the problem why the values are not being updated
    because RT cannot resolve the network path ("\\My
    Computer\Local NPSVlvlib\Test Data"). Also, I tried to change the shared
    variable path in RT but I could not do it. Help Needed!!!!
    Solved!
    Go to Solution.

    Thanks for your reply. I found in this link http://zone.ni.com/devzone/cda/tut/p/id/9900#toc2 that host computer can host the shared variable library and RT does not need the shared variable engine. See below
    If your application includes a single host computer and a single or multiple RT targets it is recommended to host the library on the host computer. This will save memory and processor time on the RT targets. Also, by hosting the library on the host computer instead of the RT target, you can reduce the software install footprint on the RT target. The RT target will not need the Network Variable Engine, but will still require Variable Client Support. The Network Variable Engine allows hosting, the Client allows communicating with libraries on other machines. You can see a RIO target with these installed in Figure 4.
    That exactly what I am trying to do. Any comments? 

  • -1950679023 Shared Variable Engine and the NI 9148

    I'm running an RT application on a cRIO-9074 that calls I/O from a connected cRIO expansion chassis (NI 9148). At some point some digital input variables throw he following error
    -1950679023, The connection to the server was disconnected.
    What's strange is that its only some of the inputs that have this problems. Other variables on the same module work just fine. What's going on here and how can I get my system to recover from this error once throw?
    I'm running RT 2011.0.1  and Network Variable Engine 1.8.1
    Craig

    Hi Craig,
    Do you see these same problems if you place the two offending modules in the 9074's chassis instead of an expansion chassis? If you do make this switch do you then see errors on other modules?
    Have you tried programmatically reading the variables instead of using shared variable nodes? You can find an example of this if you're not familiar with it here, https://decibel.ni.com/content/docs/DOC-12548. 
    When you see these errors does your application stop running, or do you just see the errors being carried through the variables as it continues to run? Also, just to double check, you're seeing these errors intermittently not every time you run correct? Also is there anything noticeable happening when this error occurs other than the error itself?
    Finally, could you post a little bit of your code, or some screenshots of where you're accessing these variables and how often you're doing so? 
    Thanks,
    Miles G.
    National Instruments
    Applications Engineer

  • NI Variable Engine closes on boot up.

    I am new to LabVIEW and installed the 8.6 Evaluation DVD on my XP computer.  Now, whenever I boot up, I get the message.  "NI Variable Engine has encountered a problem and needs to close.  We are sorry for the inconvenience.... Please tell Microsoft about this problem..."
    Please tell me how to fix this.   (If I need to execute a System Exec.vi call to stop/start the variable engine, please be explicit in telling me how to do it.)
    Thank you.
    Solved!
    Go to Solution.

    Hi Don,
    Thanks for the post, I noticed you haven't had any support. 
    I have seen this error before. Unfortunately there is not one simple solution.
    It has been resolved for some customer due to a conflict with measurement studi. Please see this forum link. 
    Also it seems that this is most likely due to a corrupt installation. Windows
    typically gives this type of error for corrupt installs, and the fact
    that both machines that installed from the same disk experience the
    error compounds my belief. The error happens at start up because
    LabVIEW automatically launches the Shared Variable Engine (SVE) at
    start up. We have two options to stop this from happening:
    (1) Re-install the shared variable engine by installing the NI DAQ driver again
    (2) Turn off the feature that automatically starts the SVE at start up
    Method
    (1) takes care of the problem with your SVE, and will make it usable in
    the future, but will take a long time to do. Uninstalling the current
    version of NI DAQ that you have, and then installing it again, or
    installing a newer version can take a very long time. If you feel like
    doing this, here is a link to the newest version compatible with
    LabVIEW 8.5:
    http://joule.ni.com/nidu/cds/view/p/id/965/lang/en
    Method
    (2) does not fix the fact that the SVE does not work properly, but if
    you are not going to use it then this is no concern. Also, it is much
    quicker and easier to do. Here is a link to how to do it:
    http://digital.ni.com/public.nsf/allkb/2DD852E2B9C​DF7578625707E006641A5?OpenDocument
    Let me know what you think,
    Kind Regards,
    Kind Regards
    James Hillman
    Applications Engineer 2008 to 2009 National Instruments UK & Ireland
    Loughborough University UK - 2006 to 2011
    Remember Kudos those who help!

  • Deploying an RT app with Network Variables

    David Thomson Original Code Consulting
    www.originalcode.com
    National Instruments Alliance Program Member
    Certified LabVIEW Architect
    There are 10 kinds of people: those who understand binary, and those who don't.

       Oops - the message got posted before I even wrote it - sorry!
       I'm working on a simple RT daq app that acquires 32
    channels of AI and pops them into a network variable for a host program
    to read several times a second.  I build and deploy the app as a
    startup so that it starts every time the PXI RT system boots.  I
    want to move the RT box to another computer that has LV, but not LV-RT.
       I first tried using the variable server on the host. 
    The LV box boots and the app starts.  I start my program on the
    host, and it connects.  Everything is fine.
       However, to make the transition to another computer
    easier, I would like to host the network variables on the RT box. 
    Then I don't have to deploy them to the network variable engine on the
    new computer.  When I write the program this way, the RT half
    still boots and runs.  Using the variable monitor program, I can
    see that the variables are hosted on the RT box and are being
    updated.  So I open the host program in LV and start it.  It
    has to deploy some sort of connection to the network variables, so a
    deploy dialog pops up.  It finds out that the RT box already has
    an app running and says that if I continue to deploy, that app will be
    stopped.  If I cancel, the host app doesn't run.  If I don't
    cancel, the RT app stops.  I have to connect to the RT box again
    and redeploy the RT app.  Then both are running and I get data.
       Is there a way to host the variables on the RT box, and
    have the RT program start automatically on bootup, and have LV for
    Windows start a program that gets the variables off the RT box from a
    Windows machine that doesn't have RT?
    Thanks,
       Dave
    David Thomson Original Code Consulting
    www.originalcode.com
    National Instruments Alliance Program Member
    Certified LabVIEW Architect
    There are 10 kinds of people: those who understand binary, and those who don't.

  • Shared variable engine with pro-face touchscreen windows 2000 professional

    hello,
    who has some experience with the shared variable engine from LabView 8.5 and a touchpanel from Pro-Face?
    We try to deploy shared variables from the touchpanel but it doesn't work. Additionally the windows service ni shared variable engine dosn't start and we can't start it manually .
    The touchpanel is a PS3701A from Pro-Face with Windows professional 2000 for embedded, Pro-Face told us that we have the full service of Windows 2000 professional on a regular PC.
    Many thanks in advance
    derN

    Hi Andrew,
    Thanks for the feedback!  Your feedback will help us to improve LabVIEW for our customers.  This bug has been reported to R&D (#45493) and they are currently investigating this issue.  For now, the best workaround appears to be using a different OS, as this seems to only occur in Windows 2000.  Thanks for the feedback!

  • Shared variable engine network published source issue

    Hello,
    I am attempting to use the shared variable engine to share some simple stings over a network between a Windows 7 computer and a Windows XP computer. 
    I got through the shared variable example just fine and can share variables between VIs on a single computer. When I open the shared variable engine, it shows the client and server variables that are shared on the local computer. I then create a new process, and attempt to define a new variable, and the Shared Variable Property screen comes up. I attempt to "Bind to Source" and click browse, and see the computer name I am attempting to connect to. However, when I click it, it stalls and I cannot expand the computer to find the variable I am trying to bind to. What am I missing?
    Thanks, Arron

    Arron,
    This document may be useful in helping to setup your network shared variables. Take a look at this and see if you have followed all the outlined steps in setting up a network shared variable.
    http://zone.ni.com/devzone/cda/tut/p/id/4679
    Let me know how this works for you.
    -Nick-
    Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

  • The engine failed to start before timeout. Restart the application (HDB 10005)

    Hi everyone,
    I experienced many times this type of error starting a SAP Lumira Document (version is 1.17, but even trying with the new version 1.19, right after the installation):
    "An Error Occured: Data Source creation failed .The engine failed to start before timeout. Restart the application. (HDB 10005)".
    I've already found (also in this community) some solutions, but they seems to me like temporary fixing, because sometimes I have to deal with this problem again. Can someone please explain me why this problem happens, and if a definitive fixing is in the works?
    Thank You.

    I am working on Lenovo Helix with Intel i5 processor and 4 GB of fixed memory. And before setting the virtual memory size (paging size) on my laptop it was switched off (no paging). So maybe this was the root cause of the issue for me.
    /Marcin

  • Appear to lose connection with the Shared Variable Engine

    Have been through the boards, but with no success regarding the specifics of my problem.
    I am running a real-time application on a PXI-8108.  The host software is taking care of user interface, etc.  Information exchange is handled using Unbound Network Shared Variables (located on the host, though problems occur no matter where the variables are located).  Everything deploys fine.  Software runs swimmingly.  I have backed off the DAQ/communication processes until the RT cores are at <10% busy.  However, occassionally while running, I get a popup "Waiting for Real-Time Target xxx to respond..."  If this message stays up for long enough, then the target's attempts to read the Shared Variables start erroring out with an error -1950679035.  As the variables have already been deployed and used prior to this instant, I find this curious.  If I filter out the error, eventually the real-time software comes back up and everything progresses as though nothing happened.  However, this is a potential deal-breaker for the users who can be impatient with having to wait a few seconds for the software to respond.
    Any idea what is happening?  I'm not pumping huge amounts of data over the network, no threads should be starving.  Kinda confused.
    Dan M. 

    The shared variables are being used much like how a queue would, directing each loop to perform an action should the host require it.  If no action is required, then the loops default to check their respective bus or DAQ.
    Currently, I am running 13 timed loops (whose periods I have extended signficantly during debug to no detrimental effect of my software, but to no improvement in the issue in question):
    RS-232/J1708 converter loop (50ms period)
    CAN loop (50ms)
    DMM loop (250ms)
    Oscilloscope loop (250ms)
    DAQ loop (50ms, includes 1 AI task, 4 DI tasks, and 6 CTR in tasks)
    Switch loop (50ms)
    RS-232 loops (50ms for the main, 1 additional loop at 1Hz)
    RS-485 loops (50ms for the main, 4 additional loops at 1Hz)
    Both cores appear to share the load, usually the aggregate load is under 15%.  When the popup appears telling me that the host is waiting for a reply from the target, the PXI controller monitor output still updates the CPU loads, which do not show anything unusual, such as a spike or a freeze in loading.  The target loading does spike up to about 30% total after the communication is reestablished, but that appears to be the software attempting to "catch up" with the events that occurred during the "black out". 
    The error reads like this:
    Shared Variable in Main Target Application.vi
    This error or warning occurred while reading the following Shared Variable:
    \\My Computer\Host-Target Interface\RS-485 Messages to Target    [<--insert other variables here]
    \\192.168.1.122\Host-Target Interface\RS-485 Messages to Target
    Unable to locate variable in the Shared Variable Engine.  Deployment of this variable may have failed.
    Are there any other drivers that would be starving the Shared Variable Engine?  For example, if a VISA or NI-DAQmx driver goes to sleep, could it hold up the SVE?  What execution system are they running under? 
    Thanks for your help!
    Dan M.

  • RT Shared Variable Engine stops publishing

    I have an RT system (PXI-8106) that hosts quite a few network published shared variables (NPSVs) for communicating to a Host PC. My Host and RT executables have been functioning fine on their respective systems for weeks, but just recently, I started running into problems with my NPSVs. My Host application has indicators to display DAQ data being acquired on the RT target and transferred via NPSV, and lately the application will update normally fine for several hours and then the displays will stop updating all of a sudden. If I reboot the RT target, the communication is restored...for a couple hours, anway, until we get another NPSV lockup. I can see no rhyme or reason as to why it stops updating the variables when it does; it seems to just randomly crap out.
    It just happened again, so I brought my development laptop down to run the Distributed System Manager. Sure enough, the NPSVs all stopped updating (latest timestamp was about 30 min previous to my check). I know, however, that the RT system is still running (I can open remote front panels), and none of the NPSV calls use their error input clusters, so an upstream error would not be causing the issue. Also of note, I have a couple NPSVs that are aliased to PSP URLs (NI_SystemState\CPULoad), which do continue to update while the remaining NPSVs do not. So that seems to indicate to me that it is not a networking issue, nor is it a Shared Variable Engine issue.
    I also programmatically deploy the NPSV library from the Host to the RT target on initialization, so I know they are deployed properly. Redeploying does not kickstart the RT SVE into updating. The only thing that seems to solve the problem (albeit temporarily) is a reboot of the RT target.
    Does anyone have any ideas as to what might be causing the RT to stop updating the NPSVs? I have already check the NPSV Troubleshooting KB (http://digital.ni.com/public.nsf/websearch/6E37AC5435E44F9F862570D2005FEF25?OpenDocument), and none of those suggestions appear applicable in this case (most address networking issues that result in never being able to read the NPSVs in the first place, whereas my problem is NPSV communication dropping out arbitrarily). Has anyone else run into such a problem?
    Thanks!

    I think I have an idea as to why my NPSV communication was freezing. One of my NPSVs is a 2D String Array of Alarm History Data, which just published infomation about alarms that have been triggered on the RT system; each new alarm appends a 10 element string array onto the 2D string array. For the most recent testing we were running, there was a recurring alarm condition that was not applicable (i.e. did not need to be handled--it just kept adding new elements onto the history array), and I am guessing that the array may have just gotten too big. When the RT target kept updating the NPSV (at 1 Hz) with more and more 2D String Data, it may have caused a buffer overflow for the shared variable.
    I will attempt to recreate the problem on another system to verify the cause.

  • Attempting to install a compiled 8.6.1 package fails with "NI Variable Engine (higher version already installed)

    This is long as there are a collection of details I thought would be useful.  Please bear with me.
    I have a VI compiled with LV 8.6.1 PDS.  The installer ran on the development machine and it works fine there (WinXP SP3).
    Was handed a laptop (another WinXP SP3) that already had LV 7.0 (academic) on it.  Someone was fiddling with an old version of LV.  OK.
    Wanted to uninstall 7.0 so there would be a clean field for the program compiled under LV 8.6.1.
    So: Start --> Control Panel --> Add/Remove Programs and uninstalled "National Instruments Software".  That went smoothly.  It wanted a reboot.  Fine.
    Ran the setup program in my package, the one I'd wanted to install.  No errors.  The following installers were included with the Build:
      * NI LabVIEW Run-Time Engine 8.6.1
      * NI Measurement & Automation Explorer 4.5
      * NI DAQmx 8.8
    By the way, this generated an installation package of "almost" 900 megabytes.
    Connected the hardware (one ethernet-based, another RS-232 based).  Started the program, "EDGAR2".
    First error:
      Unable to locate the LabVIEW Run-Time Engine.
      EDGAR2 requires a version 8.6.1 (or compatible) LabVIEW Run-Time Engine.  Please contact the vendor of EDGAR2 to correct this problem.
    (This is Error1.JPG, attached).
    A check of C:\National Instruments\Shared\LabView Run-Time\8.6 shows that there is only one item in that directory: a sub-directory named "errors".  That's it.  If the executable is looking for something in the 8.6 directory, well, there's nothing there.
    Uninstalled EDGAR2 using the Control Panel.  Reinstalled.  Same problem.
    Downloaded the standalone LabVIEW Run-Time 8.6.1 installer, Standard Edition, from NI's site, unpacked, and ran the setup.exe from that package.
    There is one box with a green checkmark in it:  NI Variable Engine .
    Click Next.  Up pops a pane and Error2.JPG is attached.  It won't continue because the "detected" version of Variable Engine is of a higher revision.
    The "Next>>" button is grayed out.
    Uninstalled EDGAR2 again.  But there was no entry in the Windows uninstall panel for uninstalling any National Instruments software.  This raised a flag in my mind and NI Support was telephoned.
    With the Support Guy running Google searches for relevent topics (I'd done some of that, too), a number of things were tried.. ending up with deleting everything in C:\Program Files\National Instruments while in Safe Mode, everything in C:\Documents and Settings\All Users\Application Data\National Instruments, going through the Windows Registry with REGEDIT, uninstalls and attempted reinstalls.  Nope, nothing worked.  That defective Variable Engine seems glued into the system
    The application can't find the 8.6.1 run-time because it doesn't exist.  It doesn't exist because both the standalone and built-in installers see a Variable Engine of a higher version installed and apparently won't install over it.  There is no uninstall for any NI software in the Windows Control Panel --> Add/Remove pane and so I can't seem to get rid of this Variable Engine.
    At this point, the Support guy says, "Time to reimage your computer.  Call us for anything else.. you know we're here for you."
    This is the first trouble I've had installing a compiled VI.  All other packages built with 8.6.1 PDS just slid right in.
    There's been a LOT of software installed on the target over the years and going on the proverbial "scavenger hunt" to locate all of the installation disks will be a time-consuming task (a week is a conservative estimate).  Is there a solution to this problem?  Where are the installers "looking" for the Variable Engine revision level?  Is there a specific Registry key that can be adjusted?
    Went looking through the WinXP Event log.  No errors are popping up there.
    Your time is appreciated.
    Mark
    Attachments:
    Error1.JPG ‏17 KB
    Error2.JPG ‏28 KB

    Hi Mark,
    I'm sorry to hear your having trouble installing the LabVIEW 8.6.1 Run-Time Engine.  It sounds like there could be a few problems going on here.  First, you should have more options when installing the Run-Time Engine than just the Variable Engine.  If you uncheck the Variable Engine, does it try to install anything?  Second, not being able to install the Variable Engine suggests that there may be something wrong with your registry.  If you removed all National Instruments keys when cleaning the registry, then this shouldn't be a problem.
    At this point, there are a couple things I would suggest.  Unfortunately, the best solution would probably be to reformat.  It sounds like some low level parts have been corrupted and this would be the quickest way to fix everything for sure.  Other than that, you can try installing the full 8.6.1 Development System on the computer.  This will install the Run-Time Engine on the computer.  You can simply not activate the software, which means you won't be able to edit anything.  You will be able to run the program, though.
    Jared S.
    Applications Engineering
    National Instruments

  • Front Panel binding of shared variables very slow initialization / start

    Hello @ all,
    I am using a server running Windows2000 and LV 8 DSC RTS for datalogging. All shared variables are deployed on that server.
    I am now facing the problem, that all front panels running on the clients using the network shared variables on the server take very long to sync on startup. First the flags on the controls bind to the shared variables turn red, after up to ten minutes they start to turn green. The panels use up to 40 controls bind to the shared variables.
    All firewalls are turned off. I tried to connect the client to the same switch the server is connected to. Same problem. Does anybody have a clue?
    Thx for your quick answers.
    Carsten 

    While I can't offer any solution to your problem, I am having a similar issue running LV8.0 and shared variables on my block diagram (no DSC installed).
    When using network published shared variables, it takes anywhere from 30 sec to 4 min from the vi start for any updates to be seen. Given enough time, they will all update normally, however this 4 minute time lag is somewhat troublesome.
    I have confirmed the issue to be present when running the shared variable engine on windows and RT platforms, with exactly the same results.
    In my case, the worst offenders are a couple of double precision arrays (4 elements each). They will normally exhibit similar "spurty" behavior on startup, and eventually work their way up to continuous and normal update rates. Interestingly enough there are no errors generated by the shared variables on the block diagram.

  • What causes the Shared Variable Engine to Crash?

    All,
    Some background info:
    I am using the SVE and DSC so that I can log my data to Citadel using Data Sets. I converted a previous DSC 7.1 project that used the tag engine over. That app ran for over 18 months. Need to upgrade app and add features at my customer requests so we migrated to LV 8.0.1.
    I have an app that crashes the Shared Variable Engine (SVE). I created a test app with a single SV and then created a control and bound it to the SV and it works every time until I launch the larger app. The main app only has 33 SV that are set when I receive TCP data from PXI RT system (not using SV on RT since the logged data is only a fraction of the total data streamed and I don't want to take apart the RT data and send the SV separately). I have bound front panels controls to the SV's. When I run, I get server connection has been closed. I verified that the SVE was running with the test app before launching the main app.
    I deploy the shared variables in the application and have verified they are deployed by the Monitor Variables utility ... but it always shows "No Value" for the data fields. I have set logging to enabled for data only, set Value Deaband (%) to 0 and Value resolution to 0, Update Deadband is Disabled as is Alarming, Scaling, Initial Value and Description. Security is set to default. All of the variables are set to Double, Network-Published, Single Writer with Buffering and Bind to Source disabled.
    I have verified that the SV deploy without error by clicking Deploy from the project. Autodeploy All is off but I get the same results with it On (checked).
    I undeploy and kill the process when I close the application.
    I have tried only using 1 or 2 of the SV in the main app but get the same results. Every once in a blue moon it will work after rebooting the PC (but not everytime). Once it dies I have tried running NI examples as well as the test app and they fail until I reboot.
    The error code indicates that the SVE engine has crashed. I have changed the service settings on Windows to relaunch on 1st, 2nd and all times after but nothing restarts the SVE. After it crashes it is impossible to exit LabVIEW without it hanging or reboot the PC without pressing the hard On/Off switch.
    Once it dies there is nothing that I can do to get it back alive without rebooting the PC (a real problem for a control and monitoring system).
    Any ideas would be greatly appreciated
    Thanks.
    Randy

    Randy
    Sorry for the delay, I've been researching your issue and juggling a few other issues. :-)  One thing we can check is the Windows Event Log which will give us some more details as to WHY the Shared Variable engine seems to be blowing up on us (Conttrol Panel -> Administrative Tools -> Event Viewer).  Any details in there along the lines of Variable Engine or Tagger crashing will help us narrow down what's going on.
    There's always a possibility of files not getting upgraded correctly; however there aren't many shared components between LV 7.1 and LV 8.0. The Shared Variable engine is entirely new and the installations of LabVIEW themselves don't share many files outside of the example finder and a few other small common components (things located in the appropriately named Shared folder)  I keep both on my machine (in addition to 5.1, 6.1, 7.0, and 8.2) without any hiccups.
    The SVE crashing I have seen in the past (and from internal bug reports) has been from buggered installs, so uninstalling and reinstalling DSC may be a good course of action. One good test to do in the middle is to see if the engine still crashes with DSC uninstalled. 
    Hope this helps.
    --Paul Mandeltort
    Automotive and Industrial Communications Product Marketing

Maybe you are looking for

  • ADVICE needed --- use  301 Redirect or revert to HTM   from  HTML  ?

    Due to ignorance, I now have two versions of the same website online, the only difference being one is all HTM while the newer one is HTML The original was built using DW MX2004  with all pages having an HTM extension while DW CS5.5 has all pages wit

  • Multiple Apple TV System Planning

    I am donating apple tv's to the Maine Children's Cancer Program to put in the kids treatment rooms. There will be 5 160GB apple TVs connecting to a mac mini with a 1TB WD hard drive. All of this connecting over a wireless network using an airport ext

  • Luck Up using XSLT Mapping

    Dear SDN, I have a interface SOAP(HTTP) -> XI -> R/3. In this interface, 3rd party sending 4 fields and are getting updated  in R/3. Now, I need to change in this interface. There are  4 fields in sender side and one field is like primary field. whil

  • 9i and 10g on same host + listeners

    Dear All, I have 2 simple questions: 1- Is it possible to have 2 database servers on one machine given that one is 10g (10.1.0.3) and the other is 9i (9.2.0.x) ? 2- Second, which of course is valied if answer to question 1 is YES, What about lsnrclt

  • Loss of Edits in a non cross-platform InDesign/InCopy Workflow

    I have read, and understand, the cross-platform issues related to loss of edits in InCopy. We are experiencing the same issue on an all Windows network.  Some authors have experienced the following issue: Author checks out a story and edits the conte