Update for Velocity 3

Update for Velocity 3.0 (KB254) Release Notes

Update for Velocity 3.0 (KB254) Released 02/01/2008 contains file changes to address the following knowledge base articles:

Download and install the update by executing the EXE file on the Velocity Security Domain server which will launch the update wizard. Once the update completes, as each client re-connects to the Velocity Security Domain, updates will automatically be applied. You do not need take the update to each Velocity client and run it.

Note: Requirements & planning for a system update

Before applying an update to the Velocity server, you must plan for independent client down time until the the update has been applied to each client respectively, in order for each client to stay in sync with the server system to prevent application errors and possible database corruption.

Before you install Velocity updates, the following requirements must be met:

Applying updates to the Velocity Server:

You must be logged into the Velocity server computer with a Windows account that has local Administrative privileges in order to install updates. Velocity Update may install new files and register them with the local Windows environment. On a Windows member server, you must be a member of the local Administrators group. On a domain or backup controller, you must logged in as Administrator or be a member of Domain Admins.

You must also be logged into the Velocity server computer with a Windows account that has 'sysadmin' privileges in the Velocity SQL Server. Updates may include schema changes to the Velocity database or modifications to SQL Server system databases. In order to make those changes, 'sysadmin' privileges is required. If the SQL Server used by Velocity is located on another computer on the network, your Windows account must have local Administrative privileges as well as 'sysadmin' privileges on the remote SQL Server.

Applying updates to the Velocity Client:

When updates are applied to the Velocity server, you will be advised that all Velocity clients will be updated the next time they are launched. In order for the updates to be applied to the client computer, the person logged into Windows at the time Velocity is launched must have local Administrative privileges. This is required in order for Velocity Update to apply file and folder and possibly Windows Registry changes to the Windows environment. If a non Administrator launches the Velocity client after an update has been applied to the Velocity server, they will be advised that the update cannot be run without local Administrative privileges and Velocity will exit.

KB255 - PRB: After installing Update for Velocity 3.0 (KB238) and (KB241), when Routing is enabled, Role members do not receive alarms or events that are granted to them in the DIGI*TRAC section of Roles

Symptom: After applying Update for Velocity 3.0 (KB238) and (KB241), and enabling Routing, members of Roles that should receive alarms & events do not get them in the Event Viewer or the Alarm Viewer until they are refreshed or in the alarm viewer until a RTN (Return to Normal) condition occurs.

Cause: An incorrect stored procedure in the Velocity database doe not properly identify when to deny an event.

Solution: To resolve this issue, apply Update for Velocity 3.0 (KB254) which contains a database script to correct the behavior.

Applies To: DC 4261

KB256 - PRB: When adding a person from template, credentials disappear

Symptom: When adding a person from a person template credentials added to the person may disappear when the person is re-opened. The credentials may re-appear under another person that is subsequently added to the system.

Cause: When adding a person from a person template the system should not allow the operator to add credentials until the new person record is saved by pressing the Apply button.

Solution: To resolve this issue, install HirschEnrollmentManagerV3.dll (version 3.0.0.581) and HirschEnrollmentManagerTV3.dll (version 3.0.0.580). These files are available in Update for Velocity 3.0 (KB254) and will be automatically installed on the Security Domain Server.

WORKAROUND: To work around this problem without applying the above mentioned solution, simply press the Apply button on the person form before adding any credentials.

Applies To: DC 4329

KB257 - PRB: "unrecognized by the localizer: vbalTreeView" message when activating Graphics for the first time after "Customization" is turned ON

Symptom: When you turn Customization ON, then activate Graphics for the first time, a message "unrecognized by the localizer: vbalTreeView" will appear on the screen. However, when you click "OK" to continue, the Graphic window screen will open.

Cause: This is caused the Localizer control not handling the new control type - vbalTreeView.

Solution: To resolve this issue, apply Update for Velocity 3.0 (KB254) which includes HirschLocalizer.ocx version (3.0.0.18) or later.

Applies To: DC 43231

KB258 - PRB: IP Port missing intermittently in the Search SNIB2

Symptom: Create or open an existing Port. Select TCP/IP, XNET 2 protocol, Click Search button. Notice that when the window comes up, the Port column will be randomly missing for some addresses.

Cause: The cause is suspected to be lost packet in UDP transport protocol.

Solution: We added a timer that fire every half second to see if the Port number is filled in, if not, send out a query to ask for the configuration again. To resolve this issue, apply Update for Velocity 3.0 (KB254) which includes HirschPort.dll version (1.0.0.314) or later.

Applies To: DC 4332

KB259 - PRB: CCTV Triggers do not work

Symptom: For Velocity v3.0 systems, CCTV Triggers at some locations do not work while other triggers at other locations work as expected.

Cause: Due to an internal software defect, the address field of the CCTV Trigger is truncated to 25 characters. Therefore any CCTV Trigger at a location that has an address exceeding 25 characters will fail to trigger.

Solution: To resolve this issue, install Update for Velocity 3.0 (KB254) on the Security Domain Server to prevent the trigger address from being truncated. After installing (KB254), new CCTV Triggers will work as expected.

NOTE: CCTV Triggers that were defined before installing Update for Velocity 3.0 (KB254) will still not work. Therefore pre-existing triggers must be deleted and re-added after applying (KB254).

Applies To: DC 4326