Update for Velocity 3.0 (KB181) Release Notes
 

January 31, 2007

 

Update for Velocity 3.0 (KB181) Released 07/16/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.

 

 

KB180 - PRB: Database archiving is set up in the Velocity Scheduling Agent, but never runs

Symptom:  The user sets up a schedule in the Velocity Scheduling Agent to archive data at regular intervals but the archive may never happen.

A review of the technical support file for the Security domain server may have the following error:

     06/01/2007 09:10:00     EXCEPTION in Class::Scheduler.ScheduleCallback.250 [13] Type mismatch

Cause:  On new installations of Velocity 3.0 or upgraded systems that never have used archiving in the past, the database contains no entries for a last known archive point.  As a result, when the scheduling system attempts to calculate the start and end date, based on number of days to retain of data, an application error is generated when the start date is empty.  This causes the scheduled archive to never run.

Solution:  Apply DTServer.exe version 3.0.0.132 dated June 21, 2007.  This is available in Update for Velocity 3.0 (KB181) and will be automatically installed on each client machine once applied to the Security Domain.

 
Applies To:  DC 4230

KB184 - PRB: System transactions throughout the system with the phrase 'Watch dog' should be

Symptom:  Events 2816-2849 display with a typo.  The correct text should be "Watch log"

Cause:  Error in the SystemTransTypes table that builds the SystemTransactionEvents table

Solution:  To resolve this issue, apply Update for Velocity 3.0 (KB181) to the Velocity Domain Machine which contains an SQL script to correct this error.  The update will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 4234

KB 186 - PRB:  Controller timeout error may occur when creating a new controller on a large system

Symptom:  For very large installations adding a controller may generate a timeout error.

Causes:  The default controller timeout period may be insufficient for a very large system while performing database operation.  With a large system, it may take several minutes to manage the propagation of data as Roles are managed in the database. 

Solution:  The default timeout for a adding a new controller has been increased to 5 minutes.  In addition, a database entry in table MiscProperties may be made to customize the new controller timeout period.

For example:

set New controller timeout to 5 minutes (Note: timeout is specified in seconds)
MiscProperites.Name = 'NewControllerTimeout'
MiscProperites.Value = 300

Install and register HirschController.dll, version 3.0.0.31 dated Wednesday, June 6, 2007 which includes an SQL script that optimizes the indexes on the Boundaries table in the Velocity database.  This file is available in Update for Velocity 3.0 (KB181) and will be automatically installed on each client machine once applied to the Security Domain.

NOTE:   For a very large system, applying Update for Velocity 3.0 (KB181) may process longer than expected.

Applies To:  DC 4251

KB187 - PRB:  New version v3.0 database contains test data

Symptom:  After installing a new Velocity v3.0, the following two tables contain test data:
 
          dbo.personfolders
          dbo.personfolderstopersons
 
This data does not display in the Velocity Enrollment Manager.  However it can be seen by querying these tables using the Microsoft SQL Server Management Studio.
 
Cause:  The Velocity model database contained test data that should have been removed.
 
Solution:  To manually fix an existing system run the following script:

delete from personfolders where Groupid not in (select PersonGroupID from personGroups)
delete from PersonFoldersToPersons where HostUserId not in (select HostUSerId from users)
GO

This script will be automatically run as part of Update for Velocity 3.0 (KB181).  The update will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To: DC 4240

KB188 - PRB:  “ActiveX component can't create object” error message after restoring database in Velocity 3.0

Symptom:  After restoring a database in Velocity 3.0, you may get the following error message:

429: ActiveX component can't create object
Velocity will now shut down.
SubItem:10

Cause:  If the Application Role password is different from the original database to the restored database, Velocity will prompt you to enter the new Application Role password.  The error would happen as a result of following this code segment path.

Solution:  To resolve this issue, install Velocity.exe v3.0.0.303 that is available in Update for Velocity 3.0 (KB181).

Applies To:  DC 4252

KB189 - PRB:  Cannot add multiple IP ports with same IP Address

Symptom:  Velocity will not allow you to add an IP port using an IP address that's already assigned to another port.  This will become an issue where sites are using multi-port devices where the IP address is the same but the port number is different.
 
Cause:  This normally won’t happen because each hardware usually has its own IP Address.  But it will become a problem when a multi-port device is used where it is acceptable that the IP address is the same but the port number is different.  Therefore, checking only the uniqueness of IP Address will cause the problem.
 
Solution:  To resolve this issue, apply Update for Velocity 3.0 (KB181) which includes HirschPort.dll (version 1.0.0.304) dated 6/28/2007 4:25 PM.

Applies To:  DC 4244

KB193 - PRB:  In the Control Zone Editor Timezone names may be displayed as "?????"

Symptom:  In the Control Zone Editor Timezone names may be displayed as "?????". This may only happen with some TimeZones and not others.

Cause:  Due to an internal programming error, the internal cache of TimeZone names was not searched correctly resulting in the TimeZone name not being found.

Solution:  To resolve this issue, copy and register HirschControlZoneEditor.dll version 3.0.0.16 dated 06/07/2007 to the Velocity directory on both client and server machines.  This file is available in Update for Velocity 3.0 (KB181) and will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 4259

KB194 - PRB:  Velocity 3.0 Update do not run properly on client machines

Symptom:  After Server installation with updates from the installation CD,  Updates for Velocity 3.0 may not install correctly on Velocity clients.

Cause:  The problem was happening when Velocity checks for updates from the database and finds one.  It will then attempt to download the update from the database and execute it.  Sometimes, when more than one are done in rapid succession, the previous update is still in the process of cleaning up its temporary files as Velocity is trying to download and overwrite the new update over the old one, before the old one has had a chance to complete.

Solution:  To resolve this issue, apply Velocity.exe v3.0.0.303 to the Velocity directory.  This file is available in Update for Velocity 3.0 (KB181) and will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 4250

KB195 - PRB:  Using ( ' ) apostrophes in door names causes "Unhandled internal errors"

Symptom:   Some users may experience an error in the Event Viewer when a Credential is used at a Door that has special characters as part of the name in Velocity

“Unhandled internal error: -2147217900-Incorrect syntax near ‘s’.”

Cause:  The use of apostrophes in SQL Server requires special handling.  They must be double quoted on an insert/update.  A new feature of 3.0 that tracks passback zone information is attempting to write the names of Doors as they are used to the database and when the Door or Reader name contains an apostrophe will generate this error.

Solution:  To resolve this issue, install Update for Velocity 3.0 (KB 181) which contains DTServer.exe version 3.0.0.133.

Applies To: DC 4255