Update for Velocity 3.0 (KB216) Release Notes
 

 

 

Update for Velocity 3.0 (KB216) Released 10/04/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.

KB218 - PRB: Stopping the DIGI*TRAC Network Service takes an unusually long time, possibly up to 30 minutes

Symptom:  When the user selects 'Stop Velocity DIGI*TRAC Network Service' from the Service Control Manager or stops the service from Windows, the service may take a very long time to stop and report 'DIGI*TRAC Network Service Offline' in the Velocity client

 

Cause:  Source code added to Velocity 3.0 to manage the new address scheme used an enumeration (a variable representing a number) for SNET communications with a different value than the correct and original enumeration from previous versions.  As a result, during the shutdown sequence, the service 'thinks' all controllers are running XNET and when it finds no XNET controllers, brute force shuts them down. This then cascades to the hardware interface (PollingEngine.DLL) and disrupts its shutdown mechanism.

 

Solution:  Apply Update for Velocity (KB216).  This contains DTServer.exe version 3.0.0.139 or newer that resolves the enumeration mismatch.  The service should shut down within several seconds.

             Applies To: DC 4289

 

KB224 - Archiving Task does not archive log data older than the date the archive task was created.

Symptom: After creating an Archive schedule task when it runs, it does not remove log data older than the date the archive schedule was created by the user.

 

Cause: The Archive schedule subsystem was using the start date (date to archive starting from) as the date the schedule was created in the absence of a existing archive (last run).

 

Solution: The syb-system has been modified to use "01/01/1900" so that the first archive that takes place will retain the number of days specified but from the earliest possible time. This will archive off all legacy data regardless of when the schedule was created.  The Ugraded from Velocity 3.0 to 3.1 will automate this process to clean up 3.0 systems.  For 3.0 systems, install Update for Velocity 3.0 (KB216) which contains DTServer.exe version 3.0.0.140 or newer.

 

Applies To: DC 4295

KB225 - PRB: Run a History Log report with more than one Date and Time criteria selected, Velocity will search the entire archived log files even if the time period does not fall within an archived time period

Symptom:  For history log reports which may or may not require restoring archive files, report manager tries to figure out the minimum date/time range that covers the criteria specified.  When multiple date/time criteria are specified and joined together by at least one “OR” operator, report manager will try to restore every archived file even though not all are needed.

 

Cause:  This is caused by the lack of complexity in the parsing algorithm.  It automatically restored everything once an “OR” is encountered.

 

Solution:  Fixed by changing the way report manager parse the criteria to get the more accurate date/time range.  To resolve this issue, install Update for Velocity 3.0 (KB216) which includes HirschReport.dll (3.0.0.107)

 

Applies To:  DC 4272

KB226 - PRB: Who's inside doesn't update everyone when new users go through, need to manual refresh

Symptom:  When adding a new user, then making that user go through a door that has passback set.  The Everyone folder in the Who's Inside window will not update the count property.

Cause:  Only the Zone in which the user was going to and leaving from would be updated.  Now the Everyone folder gets updated as well.

 

Solution:    To resolve this issue, install HirschWhosInside.dll v3.0.0.54 or later.  This file is available in Update for Velocity 3.0 (KB216).

 

Applies To: DC 4214

KB227 - PRB: If alarm has an RTN in clear window when an alarm comes in the alarm in not audible

Symptom:  The audible sound would only play when an alarm entered the lower pain or the window was refreshed.

 

Cause:  There was no code to start the audible beeping on new alarm.  The code has been added.

 

Solution:  To resolve this issue, install HirschAlarmView.dll v3.0.0.68 or later.  This file is available in Update for Velocity 3.0 (KB216).

 

Applies To:  DC 4217, DC 4280

KB228 - PRB: Download All Credentials to Controller fails on ports where port address greater than 99

Symptom:  When right-clicking Controller component select Download | Credentials the resulting download fails when the controller’s port address is greater than 99.

Note:  This defect only effects controller’s whose port address is greater than 99.

Cause:  The credential download is cached to a temporary file before it is queued for download.  Due a software defect the port address is incorrectly truncated to two digits when this intermediate file is read.

For example, port address 104 will be truncated to port address 10.

Solution:  To resolve this issue, install HECSpooler.dll.  This file is available in Update for Velocity 3.0 (KB216) and will be automatically installed on the Security Domain Server.

 

Applies To:  DC 4294

KB230 - PRB: Audio Response problem with Point Level Customization

Symptom:  Audio Response work incorrectly on RTN events when Point Level Customization is enabled

Cause:  There was an incorrect SQL statement that looks up which .WAV file to play and would return the same one for all.

Solution: To resolve this issue, install HirschAlarmView.dll v3.0.0.68 or later.  This file is available in Update for Velocity 3.0 (KB216) and will be automatically installed on the Security Domain Server.


Applies To:  DC 4297

KB232 - PRB: Multimedia set to repeat doesn't work after KB102 have been applied

Symptom:  When customizing the options for an Alarm to the point level, notice that it does not repeat like the general customized alarms do.

Cause:  The initial Alarm Sound is handled by the Velocity Console and will play regardless if the Alarm Viewer is open.  It does this for both point level and normal customizations for alarms.  The Alarm Viewer handles the repeating aspect of all alarms.  The Alarm Viewer was not handling the repeating of a point level customized alarm sound.

Solution:  To resolve this issue, install HirschAlarmView.dll v3.0.0.70 or later. This file is available in Update for Velocity 3.0 (KB216) and will be automatically installed on the Security Domain Server.


Applies To:  DC 4216

KB233 - PRB: If RTN is at the top of the Alarm List in the Alarm Viewer when an alarm comes in, no sound is audible

Symptom:  When an alarm is acknowledge but the Return To Normal (RTN) remains in the unacknowledged pane, a second alarm coming in will not sound.

NOTE: Auto Acknowledge is set to "OFF" in the Preference under Alarm Options.

 

Cause:  An error was present in the loop for detecting if an alarm was present in the unacknowledged pane.

Solution:  To resolve this issue, install HirschAlarmView.dll v3.0.0.71 or later.  This file is available in Update for Velocity 3.0 (KB216) and will be automatically installed on the Security Domain Server.


Applies To: DC 4301

KB234 - PRB: Unable to "Delete or "Edit" an existing Master Door Group from Credential or Function Group Function

Symptom:  Unable to delete or edit existing Master Door Group from a Credential Function or Function Group Function.

NOTE: The above behavior was introduced in Update for Velocity 3.0 KB197 and described in KB203 - Role Modification to Enrollment Manager and Function Groups.

 

Cause:  Due to an internal software defect the permission check for Master Door Groups was performed incorrectly which resulted in access being denied when attempting to edit or delete a function containing a Master Door Group.

Solution: To resolve this issue, apply Update for Velocity 3.0 (KB216) which will be automatically installed on each client machine once applied to the Velocity Security Domain. Files affected HirschEnrollManagerTV3.exe, HirschEnrollManagerV3.exe and HirschFunctionGroup.dll.


Applies To: DC 4303