Update for Velocity 3.0 (KB157) Release Notes
 

January 31, 2007

 

Update for Velocity 3.0 (KB157) Released 05/22/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.

 

 

KB156 - PRB: Adding/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 also belongs to a master door group, the conflict checking (check if adding or removing a door will cause any existing credentials 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 “Query timeout expired" or other error messages after that during the conflict checking step when saving a door group after adding or deleting doors to/from it.

Cause:  The stored procedure kek_FetchConflictingCredentialsControllersforMDGDueToDGChange and kek_FetchConflictingCredentialsControllersforMDG took 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.  This is a similar problem addressed in KB102 for DC4164.

Solution:  Install Update for Velocity 3.0 (KB157) which includes two SQL scripts to update kek_FetchConflictingCredentialsControllersforMDGDueToDGChange, kek_FetchConflictingCredentialsControllersforMDG and new EXE HirschMasterDoorGroup.exe (version 3.0.0.20) dated 5/16/2007 12:44 PM.

 
Applies To:  DC 4211

KB158 - PRB: Passback results in incorrect event viewer display for Entry/Exit readers passage

Symptom:  When passback occurs and the same Entry reader is used twice, the event viewer in Velocity displays the event as Internal Access Granted.  Expected behavior is that it display Entry Access each time the entry reader is used.

Cause:  Firmware changes made 7.4.x to support the Who's Inside feature of Velocity 3.0 changed the way passback zones are reported from the firmware.  The Security Domain Service was not updated to handle the passage text decoration for the events to the new reporting method.

Solution:  Install Update for Velocity 3.0 (KB157) which contains the file SDServer.exe version # 3.0.0.150 dated 05/17/2007


Applies To: DC 4213

KB159 - PRB: Frequent changing of time zones results in the controller getting time zones downloaded to it that are no longer assigned to other settings.

Symptom:  When standard time zones are frequently created and assigned/re-assigned, the controller will receive time zones downloads that are no longer being used by other setups within the controller and can result in not being able to create new master time zones.

Cause:  The CCM nor Velocity have support for automatic deletion of un-used time zones.  The CCM logically does not auto-delete them since in many commissioning situations, time zones may be created first, then later assigned.  Velocity does not prompt to auto-delete a time zone if once assigned then set back to <Never>.  Each time a new distinct time zone is used, a new index is allocated for each controller it is used in, and over time, this results in no further indexes being available.

Solution:  Install Update for Velocity 3.0 (KB157) which includes DTServer.exe version # 3.0.0.130 dated 05/17/2007.  This update includes changes to the Velocity Service that detects when a setup is downloaded and then automatically determines if there are orphaned time zones in the system that can be deleted from the controller.  If it finds an orphaned time zone, it issues the proper DIGI*TRAC commands to delete it from the system and updates the Velocity host database.  This does not increase the number of time zones available but does extend functionality as long as possible by clearing those that are no longer assigned to another setup such as a reader or relay.


Applies To: DC 4212

KB160 - PRB: Enrollment Manager UDF Search criteria is off by one

Symptom:  This defect was introduced in KB102 The UDF field in the Enrollment Manager Search dialog is off by one.  For example, If UDF 59 was selected for searching and the Function was set to “is equal to” the data results shown would be for UDF 60.

Another symptom of this problem is if the last UDF is selected for searching.  In this case the following error message will be displayed:

Function Name: frmQueryBuilder.cmbOp_Click

FunctionSubItem: 120

Number: -2147217900
Description: An object or column name missing or empty.  For SELECT INTO statement, verify each column has a name.  For other statements, look for empty alias names.  Aliases defined as "" or [] are not allowed.  Ad a name or single space as the alias name.

Cause:  Due to an internal error the UDF indexing was off by one.

Solution:  Install and register HirschEMQueryBuilder.dll, version 3.0.0.79 dated Friday, May 16, 2007 and HirschEnrollmentManagerV3.exe, version 3.0.0.560 dated May 16, 2007.  These files are available in Update for Velocity 3.0 (KB157) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4200

KB161 - PRB: Multimedia Set does not repeat after Velocity Update KB102 has been applied

Symptom:  Multimedia does not repeat when the option is set and an alarm comes is generated

Cause:  Initial multimedia is played by the Console Application when the alarm first comes in.  The repeating behavior is taken care of by the Alarm Viewer while it is active.  The repeating code was only executing when the refresh button was pressed, but not when the alarm first comes in.

Solution:  Install HirschAlarmView.dll version 3.0.0.65 May 18, 2007.  This file is available in Update for Velocity 3.0 (KB157) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To: DC 4216

KB162 - PRB: "Restart Operating System {Restart}" and "Log On as Different Windows User" generates error on Vista and Windows 2003 Server

Symptom:  Selecting "Restart Operating System {Restart}" or "Log On as Different Windows User" option may produce the following error:

"The remote server machine does not exist or is unavailable"
Function: Velocity.Console.CallBack(85)
Error Number: 462

Cause: The error was due to the Event Viewer trying to un-register itself with the Event Queue when the Event Queue was already unloaded.

In Vista, the Event Queue is getting terminated before the Event Viewer has a chance to un-register with it and raises the error.  A check is done to see if the Event Queue is active before attempting to un-register now.

Solution:  Install HirschEventView.dll v3.0.0.56 and Velocity.exe v3.0.0.271.  This file is available in Update for Velocity 3.0 (KB157) and will be automatically installed on each client machine once applied to the Security Domain.

 Applies To: DC 4192

KB163 - PRB: Updates folder get copied to C: drive even if other drive is specified for installation

Symptom:  If you have Velocity installed on a drive other than C:, the files from the update will still be extracted to the C:

Cause:  The archiving mechanism was using the "Program Files" folder which was on the C: drive and not the "Velocity" folder.  The update package has been modified to use the user's temp directory, wherever that may be. The files are then cleaned up after install.

Solution:  This file is available in Update for Velocity 3.0 (KB157) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To: DC 4205

KB164 - PRB: Files in the "Updates" folder in Velocity directory failed to be removed completely after the Updates have been applied

Symptom:  After and update, sometimes the remnants of files would be left in the Updates folder.

Cause:  After the update starts the Security Control Manager at the end of the update, the SCM would contain a lock on the updates folder and prevent deletion.  The update package has been modified to use the user's temp directory, wherever that may be.  The files are then cleaned up after install.

Solution:  This fix is available in Update for Velocity 3.0 (KB157) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To: DC 4201

KB165 - PRB: Service Control Manager may not correctly list Domains and Organizational Units following installation of KB108

Symptom: Update for Velocity 3.0 (KB108) added a new selection to the Service Control Manager for changing the location of the Velocity Users group from a Windows domain root, to an OU (Organizational Unit). The drop down list may display a DOMAIN entry more than once.

Cause: The routines that query for a list of OU's also returns the Domain root. The routine explicitly added the domain root first and attempted to detect when the OU collection was returned and filter out the domain controller entry. This intermittently fails.

Solution: Apply Update for Velocity 3.0 (KB157) which contains VelocitySCM.exe version 2.5.0.110 dated 5/22/2007 or newer.

Applies To: DC4227

KB166 - PRB: Velocity Operators that are not local Administrators for Single Workstation Edition or Domain Admins for Server installations cannot add new Velocity Operators when an Administrator has already created the Windows account and added that account to Velocity Users ahead of time.

Symptom: If a Domain Admin or Local Administrator has already created a Windows account and added them to Velocity Users for the Velocity system, a Velocity Administrator that is not a system administrator cannot add them to Velocity.

Cause: The Operator component was attempting to modify (save) the Windows account and then add them to Velocity Users even though it is not necessary. If they conditions are already met, it should simply create the Velocity account and link to the existing Windows account.

Solution: Apply Update for Velocity 3.0 (KB157) containing HirschOperator.dll version 3.0.0.50 dated 5/22/2007

Applies To: DC4225