Генератор зла » Пт июл 29, 2011 2:41 pm
1.
This issue is caused if there are alarms in the database that have been unacknowledged for over 24 days.
Resolution Details:
See Tech Alert 118
Use the following workaround.
But the side effect is that the Unack duration column won't be displayed:
In the AlarmDBViewControl, click the Selection Tab > Duration Column.
Click Unack Duration.
In the AlarmDBViewControl click the General Tab > Column Details.
Uncheck the Duration Column.
Alternatively, you can purge the database so that there are no alarms older than 24 days, let alone unack'd alarms.
2.
Problem:
SQL Server error caused by an overflow at run time due to difference of two Datetime columns. This error occurs when an alarm that has been in an alarm state for more than 24 days returns to normal.
Solution:
Notes: Known issue with this fix: If the database is created with the registry setting "DateDiffInSec = 1", the Alarm duration is calculated in seconds, but is shown in milliseconds in the Duration column in the Alarm DB View control. This issue will be resolved in the future release.
To use the fix in this CR, follow these following steps:
1. Apply the InTouch 9.5 Patch 02.
2. Create a DWORD value "DateDiffInSec" in the registry section HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\\AlarmLogger.
3. Set the value for DateDiffInSec to 1. This setting MUST be done before creating a new database.
4. Create a new alarm database with Alarm DB Logger Manager.
The new view v_AlarmEvenHistoryInternal2 is generated, which uses the second for Duration calculation.
To undo this, remove the "DateDiffInSec" or set the value to 0, and then create a new alarm database.
Vita est dolor.