Error -1967390704 when trying to read historical data from CITADEL

[unclebump]

I am trying to read historical data for 8 tags in a 'for loop'. If I run the historical vi while my data collection vi is running, I get the error -1967390704 CIT_ReadTrace.vi error code 0x8abc010. I have installed the DSC6.1 fixes and also updated the logos version to 4.4. Is it generally a good practice to not access historical data while new data could still be written to CITADEL?? Is there a vi or anything that could check the versions of all the installed NI software to the latest versions that are available??

[unclebump]

I noticed another error while watching the READ HISTORICAL TREND vi. This vi showed 'socket has been disconnected by peer' in the error message window.

[Mike S. @NI]

The error means that LabVIEW has been disconnected from the database. There can be several causes, but the most common are that the database is corrupted or the Citadel Service has shut down or stopped. Please verify that you have the latest version of logos (4.4.0.15) by checking LKCITDL.EXE in the System32 directory. If you do have this, then please generate an email support request and send us your database.

Regards,
Michael Shasteen
Applications Engineering
National Instruments
www.ni.com/ask
1-866-ASK-MY-NI

[unclebump]

I don't think I could send the whole database. It has 92 traces and is almost 1Gb in size. I made a zip backup of the directory and then deleted everything in it. I'll try again with a smaller database size. It may help if I archived specific traces to another database file and worked with smaller chunks of data. When my data collection vi is running there are around 5000 tags active. I am running the most current version of logos.

[unclebump]

I deleted all of the files from the data directory and restarted the data collection. When I came back later, in MAX it showed that I had 4098 traces available in the historical database. I wrote a vi to check the number of tags in the scf file that had logging enabled and it was only 90 of them. I also checked the number of tags with history data and it showed 4098 were available. Why would the database show historical data available for tags that are not set to log data in the scf file??

[Mike S. @NI]

Be sure to create a new entry in MAX for your database instead of using the same old one. Also, there could be another SCF file logging to that directory. It sounds like you could have a corrupted database, though.

[unclebump]

I just went into my .scf file and moved the database for historical logging to another hard drive. After I restarted the tag engine, and before I ran any other vi's, I created a new database entry in MAX. The new file in max showed 4098 traces available and a file size of 17meg before I even tried to write any data. There are only 90 tags enabled to log historical data in the .scf file. Why would there be 4098 traces available??

[ICA]

My problem is the same as the one reported with the error code -1967390704, but besides it seems I loose all the data I stored in the database before this error occurred, and also the DSCEngine.exe falls down.I need to restart my computer to launch the engine again and also to start the citadell service, because otherwise it is impossible.

[unclebump]

I had some major problems when I installed the latest updates. I unzipped to the wrong directory and had multiple copies of some labview files. It really made for some strange operation. Right now I am running labview 6.1 with feb26,2003 updates from the web, logos version 4.4.0.17. It sounds like your database may be corrupted. They also sent me a file to workaround a read issue with the historical vi's.