Update for Velocity 3

Update for Velocity 3.1 (KB419.1) Release Notes

Update for Velocity 3.1 (KB419.1) Released 09/29/2009 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.

KB434 - ENH: Optimized the processing time on the Client to prevent latency

Description: Enhanced the performance especially when in receipt of alarms with a high volume of transactions to reduce latency period usually occurs when modifying a credential or a Door Group on a large system with a large number of Controllers.

Installation: Apply Update for Velocity 3.1 (KB419.1) which will be automatically installed on each client machine once applied to the Security Domain

KB441 - PRB: OperatorLog report not pulling archived data after upgrading to Velocity v3.1

Symptom: Report will run but you won't see archived data. After looking in ArchiveServer.log file will show errors similar to below:

"8/14/2009 10:35:50 AM: RestoreArchivedTables.16: ERROR: -2147217900 Insert Error: Column name or number of supplied values does not match table definition."

Cause: Due to an internal software error, a field in OperatorLog table is not present in version 3.0.

Solution: To resolve this issue, apply Update for Velocity 3.1 (KB419.1) and will be automatically installed on the Security Domain Server.

Applies To: DC 560