LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Alarm/event archiving does not complete correctly.

Hello.
I am using the Alarm & Event Archive VI in Labview DSC 7.1 and I have a problem. The archiving works correctly, but after archiving, if I try to copy the archive folder, Windows refuses (I am using Windows 2000). It seems that Labview is not releasing the references to the mssql.ldf and mssql.mdf files in the archive folder, hence I cannot copy because of a sharing violation.

I have tried all of the follwoing, but I cannot release the reference:

1. Stopping Tag Engine.
2. Exiting Tag Engine.
3. Exiting Labview.

I have even tried stopping the sql processes in Windows Task Manager, but the sharing violation still occurs. The only way to backup the archive folder is to restart Windows, then copy it
!

I have included the VI I am using to archive the alarms/events. Note that first it archives historical data (this is fine), then it archives alarms.
0 Kudos
Message 1 of 3
(2,701 Views)
In MAX you need to setup the database under the Historical Data section in order to accept Events only, Alarms only or both.

Has this been setup?

Kind Regards

Steven Bird
0 Kudos
Message 2 of 3
(2,701 Views)
I have worked a bit more on this problem today and I have (sort-of) fixed it: I needed to use the Detach Database VI to properly release the archived database. However the problem still occasionally occurs if I try to archive the alarm database BEFORE any Tags have gone into alarm (i.e. when the system starts-up).

Very strange.
0 Kudos
Message 3 of 3
(2,701 Views)