I am not able to log alarms in DSC (LabVIEW 8.01). Please help

[RichiP]

In the DSC settings, I have enabled Data Logging and Alarms & Events logging (and use the same database foralarms and events).

I have also enabled Alarming and Logging (Log alarms & Events) on the selected TAG (shared variable).

I am reading this value from an OPC server.

I have received multiple alarms, but they will not be stored. WHY???

When I run the Alarm & Event Query, I receive this message:

Error -1967386611 occurred at HIST_RunAlarmQueryCORE.vi, Citadel:  (Hex 0x8ABC100D) The given Citadel database is not currently configured to log alarms to a relational database.

MSDE2000 are installed.

Sometimes the mssql.mdf and the mssql.ldf appear, but they disappear again after a few seconds.

Please help me solve this problem

regards

Richard

[Snamprogetti]

I have the same problem (but with 8.2, and no OPC).

If i try to read alarm history with MAX there is no error message, but no alarms are found.

How do we configure Citadel??

[VRspace4]

I'm running LabVIEw 8.20 and am getting the same error message when I use the Alarm and Event Query vi. It has been a year and no one have resolve this problem?

[CharlieM]

Hi Everyone,

I have not been able to find the source of these issues because it has not occurred on my computer and thus, I have not filed a CAR with R&D. However, the best actions to take in this situation are: 1) Make sure that your shared variables are configured to alarm and log the way you want. 2) Delete/Archive the database that is causing the issue and replace it with a fresh database. 3) Repair/reinstall LabVIEW DSC.

[Lloyd_obotomy]

Charlie:

Curiously, National Instruments engineers hardly ever experience the problems of NI software clients. What computer make and model does NI provide for you guys? What antivirus and firewall software do you use at NI? Do NI engineers use dual processor PCs to test their software?

Lloyd

[VRspace4]

I may have found the problem. When you first deploy a library with a totally new database, LabView fail to create all the necessary database files initially to make it become fully accessible. In other words, you will encounter that error message when you attempt to query any kind data using such subVIs as 'Alarm & Event Query.vi' for a new database. From your Windows Explorer, manually access the folder that your database resides in; you'll notice that there are two important database files that are not yet created.

1. mysql.ldf
2. mssql.mdf

To get around this, simply create a user defined event or alarm using the 'Set User Defined Event.vi' or 'Set User Defined Alarm.vi'. Only after this will your database be fully created and you'll see that the two files mentioned above will appear in the database folder.

So to sum it up, remember to create a user defined alarm and/or event either after you create a new database or when you delete or archive the database events and alarms.