08-07-2006 01:12 PM
08-07-2006 03:18 PM
Do you think it's because of the "filter input"?!
If I take it off, it looks like I don't have the error when I close the window. But I need this filter because I want to show only a period of time (last 24 hours).
I'll do other tests tomorrow..
Stephanie
08-08-2006 11:55 AM
Hi again lol
I did some tests today and I can see that the error is intermittent. So I don't know exactly when the error happens.
I guess if nobody answers me yet it's because you can't reproduce the error... I'm desperate! ![]()
I don't know if this error (lvrt.dll) is the reason why I have an error in my project (nids.dll). Maybe I forget to download something? Maybe I forget to enable something?....
Sorry if I'm annoying,
Thank you
Stephanie
08-09-2006 05:15 PM
Hi Stephanie,
We've been trying to get it to fail over on our end, so far without success. (This is also NIWeek, our annual user conference, so most of us are out teaching classes and running demonstrations this week) One wrinkle that we may be hitting is that our test machine has both LabVIEW and the LabVIEW run-time engine installed on it, so it may be a problem with the installation of the DSC run-time system. First thing I'd check is that you have the 8.0.1 version of both the run-time system for DSC (RTS) as well as the LabVIEW Run-Time Engine (RTE). We've seen intermittent run-time issues like this when the RTE is 8.0.1 and the RTS is still 8.0, and the easiest way to verify and fix this is to install the 8.0.1 maintenance release for DSC on your target machine as well as the development machine.
The latest version of DataSocket, which is controlled by the nids.dll file that is showing the problems with your full application, is installed with the LabVIEW Run-Time Engine. Incidentally, the run-time engine is controlled by a DLL called lvrt.dll. This leads me to believe the installation of the RTE, RTS, or both, has been corrupted and needs to be reinstalled on the machine.
The "Enable Enhanced DSC Run-Time Support" option when building an executable should be chosen when you access any of the DSC features in your application, such as logging to the Citadel database, using alarming and scaling on shared variables, etc. They will not function properly in your application if this support has not been enabled.
To recap, I haven't been able to reproduce the issue on my machine or my test machine, but given the type of error that you're experiencing, a reinstallation of the 8.0.1 versions of the RTE and RTS may solve the problem. First, rebuild your application with Enhanced Run-Time Support enabled, then if this fails, perform the reinstalls. This will likely clean out the problem for you.
08-10-2006 10:40 AM
@Peachy wrote:
-- snip --Also, I would like to know when we have to check the Enable Enhanced DSC Runtime Support in the Advanced tab when we build an executable?-- snip --
Hello Stephanie,
While it won't hurt to enable the enhanced DSC runtime support whenever you are using DSC features in your project, the only time you MUST enable it is when you are programmatically modifying library files using a refnum (the green one) or programmatically deploying/undeploying libraries. The rest of the DSC features will work without the enhanced support.
08-10-2006 10:52 AM
08-10-2006 11:43 AM
-- snip --I tried to enable this feature using only the Alarm and Event query.vi in my code but I had this "LABVIEW.LIB was not called from a LV process" error...-- snip --
Are you saying that you built an exectuable using this VI, but not using the enhanced support, and got that error message?
And I suspect that the support engineer who replied to your email just replied to the latest one.
08-10-2006
11:53 AM
- last edited on
06-30-2025
09:50 AM
by
Content Cleaner
08-10-2006 02:09 PM
I'll try and take a look into this. Is this the message where you initially talk about the error (http://forums.ni.com/ni/board/message?board.id=170&message.id=197777#M197777)?
It may be a day or so before I can get set up to test this. Hopefully then I will be able to reproduce it.
08-10-2006 02:26 PM