Update for Velocity 3.0 (KB102) Release Notes
 

January 31, 2007

 

Update for Velocity 3.0 (KB102) Released 03/08/2007 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.

 

KB106 - HowTo: Enabling UDF tab level security

Update for Velocity 3.0 (KB102) includes an enhancement to Velocity Roles that enables Tab level security in the Enrollment Manager Person screen. Roles now support setting View and Edit permission on each individual tab. This allows the system to restrict Role members from seeing and/or editing sensitive information belonging to Persons in the Velocity system. After the update is applied, existing Roles will automatically have View and Edit allowed for all tabs in order to preserve existing functionality. New Roles created after the update applied will not have View and Edit tabs allowed by default.

KB104 - PRB: Error assigning and unassigned credential when "Show UDF Field Summary" is selected

Symptom:  If the Show UDF Field Summary option is enabled, trying to assign an unassigned credential will generate the following error:

The following unexpected application error occurred...
Function Name: mPublic.SetPersonRow
FunctionSubItem: 11
Number: 3265
Description: Item cannot be found in the collection corresponding to the requested name or ordinal. 

Cause:  An internal software defect produced an invalid database query which causes the above described error.

Solution: Install and register HirschEnrollmentManagerV3.exe version 3.0.0553.  This file is available in Update for Velocity 3.0 (KB102) and will be automatically installed on each client once applied to the Velocity Security Domain.

Applies To: DC4165


KB105 - PRB: Credential Template Properties may display incorrectly if Customization is enabled

Symptom:  When customization is enabled, the Credential Template Properties may not display correctly.

 

Cause:  An internal software error caused Saved Searched dialog and Credential Template dialog customization data to be mixed.

 

Solution:  Apply Update for Velocity 3.0 (KB102) to the Velocity Domain Machine.  The update will be automatically installed on each client once applied to the Velocity Security Domain.

 

Applies To: DC4161

KB107 - PRB: Adding or Removing doors from Door Group causes Time Out

Symptom: In a system which has a lot of user credentials defined, sometimes when you change a door group to add or remove a door from a controller and when that door group is referenced by many credentials, the conflict checking (check if adding or removing a door will cause an existing credential to have more than one function defined in one controller - invalid) step takes a long time and eventually will time out giving the error message of either "server cursor cannot be open on this statement" or  "Query time out".

Cause: The stored procedure kek_FetchConflictingCredentialsControllerforDG takes too long to run.  Use with (nolock) clause and cut down unnecessary table joins to significantly reduce the query time so it won't be an issue.

Solution: Install Update for Velocity 3.0 (KB102) which includes a script to update kek_FetchConflictingCredentialsControllersforDG and HirschDoorGroup.exe version 3.0.0.3

 

Applies To: DC4164

KB111 - PRB: User selected WAVE file does not play for RTN (Return to Normal) events

Symptom: The user selects a WAVE file but no sound is made for RTN (Return to Normal ) events
 
Cause: The RTN code was commented out and using an earlier version of the sound source playback routine. It has been modified to use the new sound source routines.
 
Solution: Install Velocity.exe version 3.0.0.237 and HirschAlarmView.dll version 3.0.0.57 and register the latter file in Windows.  This file is available in Update for Velocity 3.0 (KB102) and will automatically be install on each client once applied to the Security Domain.
 
Applies To: DC4159