I get the following error on- and off in an app. The message is

[Ben]

Error -2147467259 occurred at CIT_ReadStringTrace.vi.

This error is being returned by the read string history VI.

If I put this VI in another dummy VI I can predict when it will occur (mostly). If repeatedly run my dummy VI until I stop getting this error (just hit run button) the main app never sees a problem. If I do not do this repeated run thing, my main app sees the error.

The code value almost makes it look like the tag history is being accessed via a serial port!
Go figure.

Ben

[Ben]

The next day I started working with NI.
I was able to develop a VI that duplicates error I was seeing in my app.
NI was able to duplicate error.
See service request # 395330.

The same error by the "N" version of the same VI.

A serious memory leak was also noticed while using the continuous run button.

I will try to remember to update this question when NI (or I) come up with a fix or work-around.

Ben

(So hows that for an answer?)

[bryce]

Ben,
Update Logos to Logos 4.4.
ftp://ftp.ni.com/support/lookout/logos/logos.zip
Check out the updates to LabVIEW 6.0.2.
ftp://ftp.ni.com/support/labview/labviewdsc/fixes/6.0.2/
Read the README.TXT files to see if the fixes apply.
This does not happen within LabVIEW 6.1. I have noticed memory usage rising when using this VI and am having R&D verify and fix it if it is a legitimate problem.

Thanks,
Bryce