Update for Velocity 3

Update for Velocity 3.0 (KB274) Release Notes

Update for Velocity 3.0 (KB274) Released 04/28/2008 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.

KB276 - An "Application Error" may occur after disconnecting and reconnecting Client

Symptom: Graphics or Enrollment Manager fails to reconnect to the database and causes an error after a Velocity
Client has reconnected to the Velocity Server.

Cause: Due to an internal software defect, Graphics or Enrollment Manager was not reopening its database connection
and therefore encountered an error while accessing the database through the broken connection.

Solution: To resolve this issues, install HirschGraphics.exe (v3.0.0.66), HirshEnrollManagerV3.exe (v3.0.0.585),
HirschEnrollManagerTV3.exe (v3.0.0.588) and HirschEMSupport.dll (v3.1.0.9). These files are available in Update for
Velocity 3.0 (KB274) and will be automatically installed on the Security Domain Server.

Applies To: DC 4357

KB277 - PRB: Unable to set "Who's Inside" screen to desired view after minimizing the screen

Symptom: Upon restoring the Who's Inside window after it had been minimized, the splitter bar would be reset to the
default position.

Cause: The mechanism for persisting the splitter bar position was being overridden by code executing after it.

Solution: To resolve this issue, install HirschWhosInside.dll 3.0.0.53 or later. This file is available in Update
for Velocity 3.0 (KB274) and will be automatically installed on each client machine once applied to the Security
Domain.

Applies To: DC 4360

KB278 - PRB: Velocity Security Domain crashes intermittently. Most notably when closing the Velocity client

Symptom: T he Security Domain Service may crash intermittently, usually when the Velocity Client application is
closed on a workstation.

Cause: Improper handling of the socket close event on the server side results in an Access Violation that the
service cannot trap and the service will crash.

Solution: To resolve this issue, apply SDServer.exe version 3.0.0.185 or later. This file is available in Update for
Velocity 3.0 (KB274) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To: DC 4366

KB279 - PRB: The Status Viewer shows Controllers offline

Symptom: Disabling a Port in Velocity may result in Controller Status being removed from the Status Viewer

Cause: As a Port, Xbox, or Controller is disabled, removed, or goes offline, the status for the points at the same
level and below are erased. An error in the cleanup routine was taking the identity of the port taken offline and
erasing controller information for a controller with the same identity number in the database.

Solution: To resolve this issue, install DTServer.exe version 3.0.0.161 or higher. This file is available in Update
for Velocity 3.0 (KB274) and will be automatically installed on the Security Domain Server.

Applies To: DC 4365

KB280 - PRB: CCTV “Invalid response” events in the Event Viewer

Symptom: When CCTV integration is used, there will sometimes be “CCTV: Invalid Response” events in the Event Viewer.
This may occur intermittently. This symptom most often occurs when CCTV switcher is connected to the Velocity
Server via a Serial to TCP converter (E.G. Digi, Lantronix).

Cause: Due to an internal software error, CCTV switcher response packets were sometimes parsed incorrectly causing a
spurious “invalid response” event.

Solution: To resolve this issue, install HirschPortman.dll (3/26/2008) or later. This file is available in Update for
Velocity 3.0 (KB274) and will be automatically installed on the Security Domain Server.

Applies To: DC 4359, DC 3821

KB281 - PRB: CCTV Camera does not switch on Alarm

Symptom: CCTV camera does not switch in response to Velocity alarm. This occurs when there are CCTV Triggers to
switch a camera on an alarm and to switch a camera on an alarm acknowledgement.

Cause: Due to an internal software error CCTV camera switch may be canceled before it is sent.

Solution: To resovle this issue, install HirschCCTVServer.ocx (5/27/2007). This file is available in Update for
Velocity 3.0 (KB274) and will be automatically installed on the Security Domain Server.

Applies To: DC 4368

KB282 - PRB: Credentials are expired as per the US date format, not the international format

Symptom: Credentials are expired as per the US Date Format, not the International Format.

Example: Set the Windows date format is set to English (United Kingdom). If today is March 1st (1/3/2008 UK) and a
credential was set to expire on April 1st (1/4/2008 UK) it would expire immediately since the date is processed as a
US Date (1/4/2008 US) which would be January 4th.

Cause: Due to an internal software error, international dates were being saved incorrectly to the database. In
addition, the calculation to determine if a credential has expired was also incorrect.

Solution:

For V2.6SP2: Install HirschEnrollManager.exe (3/21/2008), HirschEnrollManagerT.exe (4/1/2008) and
HirschEMSupport.dll (3/21/2008). These files are available as a v2.6SP2 patch from Hirsch Technical Support.

For V3.0: Install HirschEnrollManager.exe, HirschEnrollManagerT.exe and HirschEMSupport.dll. These files are
available in Update for Velocity 3.0 (KB274) and will be automatically installed on the Security Domain Server.

Applies To: DC 4353, V2.6SP2, V3.0

KB283- PRB: Search Person do not show results when specifying two different UDF fields

Symptom: When you try to search for a person by specifying two different UDF fields using the "AND" or “OR" clause,
the search results show nothing.

Cause: Due to a software defect the query for multiple UDFs was incorrectly generated causing no results to be
returned.

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

Applies To: DC 4362

KB284 - Time Zone in-use warning dialog title bar misspelling

Symptom: In the Time Zone in-use warning dialog’s title bar, “Were” was misspelled as “Where”.

Cause: There was a typo in the resource string.

Solution: Fixed by updating the resource string in the database for resource ID 3357. To resolve this issue, apply
Update for Velocity 3.0 (KB274) and will be automatically installed on the Security Domain Server.

Applies To: DC 3493