NI Variable Engine (tagsrv.exe) Runtime Error Dialog Upon Restart -- Resolved

[LabBEAN]

After installing LabVIEW 2009, I started getting an error dialog when I restarted, and shared variables stopped working.  So, I figured I'd post what I did to resolve it.

For forums searchability, here's the text:

Dialog Window Title:

Microsoft Visual C++ Runtime Library

Dialog Window Text:

Runtime Error!

Program: ...gram Files\National Instruments\Shared\Tagger\tagsrv.exe


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information

=======

Here's the dialog:

I also noticed that the NIVE (National Instruments Variable Engine) service timed out when I manually tried to stop it.

So, I:
    * Closed out of everything, opened Distributed System Manager 2009, and removed all processes (except for "System", of course)
    * Restarted the PC

Visual C++ Runtime error is gone! 😄

Message Edited by LabBEAN on 11-11-2009 10:02 AM

[Burt_S]

Hello LabBEAN,

Thank you for taking the time to submit this valuable feedback.  This was reported to R&D (#196095) for further investigation.  Thank you also for providing the detailed workaround. 

[FabiolaDelaCueva]

I am getting the exact same dialog every time I restart my computer. When I go to the Distributed System Manager there are no processes to remove.

I believe I started getting this error after I started working with projects that have a cRIO target.

It is getting annoying to get the same dialog box every time I reboot the computer.

Any idea how to get rid of this window?

Thanks,

Fab 

[LabBEAN]

Maybe install Distributed System Manager 2009 SP1?

[FabiolaDelaCueva]

This seems to have resolved the issue. Thanks!

[FabiolaDelaCueva]

Nevermind. That did not solved it. I am still getting the same error. It only went away from a couple of reboots, now it is back.

[LabBEAN]

Corruptions can happen.  At one point on one of many, many shared variable Service Requests I've had with NI, an R&D guy connected to my PC and used some tool to "clean out" my NIVE (NI Variable Engine).  So, you either have something REALLY corrupted and need to uninstall/reinstall LabVIEW...

...or you are causing this corruption repeatedly by something you're doing.  In this latter case, my instructions above should clear it up.  Then, you would need to explore why you're code is breaking the NIVE.

[FabiolaDelaCueva]

Thanks LabBEAN.

I did remove all the processes from the Distributed System Manager, then restarted the computer, but the message is still there. So, I guess I will have to try uninstall/reinstall LabVIEW... not fun 😞

Thanks again,

Fabiola 

[LabBEAN]

Sorry to hear that.  I've been there a few times myself.  While you're going through that process, consider uninstalling EVERYTHING NI through Control Panel » Add Remove Programs.  Running msiBlast (attached below) can clean out anything you missed.

As a last resort, you could call NI support (if you have support) and at least allow them to probe around.  At a minimum, they can document this internally so maybe it's fixed at some point.  If you go that route, request a CAR number and post it back here if they give you one.

Message Edited by LabBEAN on 04-23-2010 05:39 PM

[LabBEAN]

Actually, I just looked above and Burt provided this number:  196095

You could reference that CAR if you call them.