Update for Velocity 3

Update for Velocity 3.0 (KB261) Release Notes

Update for Velocity 3.0 (KB261) Released 03/26/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.

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

Symptom: Assigning Point Customized sound files to alarms and Return to Normal alarms would not play the correct file.

Cause: The query to determine what sound file to play was wrong, for both New Alarms and Return to Normal alarms. The embedded SQL statements have been modified.

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

Applies To: DC 4261, DC 4308, DC 4343

KB265 - PRB: Switch "Operator" may leave some windows open

Symptom: When switching "Operator" while in Administrator mode, and the following: Enrollment Manager, Who's Inside and Scheduler are currently open, you will notice that some windows may be left open when the roles says they shouldn't

Cause: Velocity did not handle the closing of these two components on a User Switch function

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

Applies To: DC 4347, DC 4344

KB266 - PRB: Unable to Plot Door, Input and Camera into Graphics during Design Mode

Symptom: You may receive this message "Your Role Permission do not allow you to plot this device" in Graphics during design mode

Cause: This behavior is caused by an internal software defect

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

Applies To: DC 4335

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

Symptom: The above error message would show when the user was prompted to enter a new Application Role password to match what was in the database.

Cause: The CommonVMO.dll was out of sync and the referenced object in Velocity.exe has been changed.

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

Applies To: DC 4252

KB268 - PRB: Unable to configure Photo Call-Up for each client workstation after applying (KB238)

Symptom: The above error message would show when the user was prompted to enter a new Application Role password to match what was in the database.

Cause: The CommonVMO.dll was out of sync and the referenced object in Velocity.exe has been changed.

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

Applies To: DC 4348

KB269 - PRB: Application Error occurred under Badge Design when you select "UDF Property Definitions" under "Tools"

Symptom: You would get an Invalid Column Name error sometimes when trying to open UDF Property Definitions.

Cause: The method for fixing string values with an apostrophe ( ' ) in the name was failing. This method has been changed.

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

Applies To: DC 4345

KB270 - PRB: Time Zone names are not correctly displayed for events that are related to time zones

Symptom: When events related to time zone activity such as Start/End of time zone or actuate relay during time zone, the time zone name may be incorrect

Cause: The DIGI*TRAC Network Service was sending the Security Domain Service the wrong parameter from the controller firmware which prevented it from being able to read the correct time zone name from the Velocity database.

Solution: To resolve this issue, apply Update for Velocity 3.0 (KB261) which contains updated services SDServer.exe version 3.0.166 and DTServer.exe version 3.0.154.

Applies To: DC 4336

KB273 - PRB: XML RPC calls over HTTP result in "Access Denied" XML exception after applying (KB142)

Symptom: When using the HTTP interface to execute an RPC such as execute a Command Set, unless the Workstation is ID=1 an XML Exception is returned with "Access Denied".

Cause: The 3.0 Interop routine had not been updated after Roles was changed to remove Workstations and still contained WHERE WorkstationID=n and the SQL check for permission failed on and workstation other than 1.

Solution: To resolve this issue, apply Update for Velocity 3.0 (KB261) which contains updated services SDServer.exe version 3.0.166 and DTServer.exe version 3.0.154.

Applies To: DC 4354

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~~. Install Update Velocity 3.0 (KB261) which includes DTServer.exe version 3.0.154 dated 03/26/08. 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, DC 4356

NOTE: Previously addressed in Update for Velocity 3.0 (KB157)