www.InTouch.su

Добрый день.
При открытии журнала сообщений появилась надпись: "Функция datediff вызвала переполнение" (используется AlmDbViewCtrl).
Конфигурация:
- InTouch 10.5
- Microsoft SQL Server 2008 SP1
на 3 рабочих станциях.

В log SMC Console след. сообщение: "Функция datediff вызвала переполнение. Слишком большое количество частей даты, разделяющих два экземпляра даты-времени. Попробуйте использовать функцию datediff с частью даты меньшей точности. Process ID 6196. Component almdbview"

За предыдущие дни сообщения открываются. А за сегодняшний - нет.
Данная ситуация на всех 3 рабочих станциях.
Заранее благодарен!!!

Tech Alert 118

Important Issue/Solution to Consider Prior to Creating the Alarm Database

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Topic#: 002305
Created: October 2008

Introduction
This Tech Alert describes an issue with the InTouch® Alarm Database, which is resolved in versions 9.5 P3 (and later).
However, Wonderware has identified a further adjustment to the Registry that is necessary to fully resolve the issue. The adjustment must be done prior to creating the Alarm database.

Application Versions
InTouch 9.5 P3 and later

Problem/Issue
The following SQL Server error is caused by an overflow at Runtime due to a difference between two DateTime columns:
Difference of two Datetime columns caused overflow at runtime.
This error occurs when an alarm that has been in an alarm state for more than 24 days returns to normal.

Solution
Complete the following steps to adjust the Registry. As always, use caution when modifying the Windows Registry. Only apply the following steps to InTouch version 9.5 Patch 03 or higher.
Create a DWORD value DateDiffInSec in the registry section HKEY_LOCAL_MACHINE\SOFTWARE\\Wonderware\\AlarmLogger.
Set the DateDiffInSec value to 1. This setting MUST be modified before creating a new database.
Create a new alarm database with Alarm DB Logger Manager.
A new view v_AlarmEvenHistoryInternal2 is generated, which uses the "second" for the Duration calculation and thus, resolves the issue.
To undo this, remove the DateDiffInSec item, or set the value to 0, and then create a new alarm database.

Note: Although the issue is fixed in current released products, the adjustment to the Registry must still be done.

Known Issue with This Fix
When the database is created with the registry setting DateDiffInSec = 1, the Alarm duration is calculated in seconds, but displayed in milliseconds in the Duration column of the Alarm DB View control. This issue will be resolved in the future release.

С помощью Alarm DB Logger Manager удалили старую базу данных и создали новую.
Журнал сообщений и Purge/Archive начал работать.

Как часто это может происходить с datediff???

На всё воля Аллаха.
Сам не сталкивался.