Update for Velocity 3.1 (KB480) Release Notes

 

Update for Velocity 3.1 (KB480) Released 03/09/2010 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.

IMPORTANT:  If the Extension Services fails to "STOP" automatically while applying the updates, use the "Task Manager" and select the "Processes" tab to end the process “HirschSensormaticExt.exe”.  See article KB479 under Known Issue for more details.

 

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 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 be logged in as Administrator or be a member of Domain Admin. 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.

New Minimum Hardware Requirements

•  Pentium 4 with 2 GHz or higher for Velocity with DVR
•  2 GB or higher of RAM (Client, Standalone and Server)
•  10 GB Hard Drive (SCSI or IDE): 1 GB + 40 MB per client

In addition, the host PC should have these components:

•  4X or better CD-ROM Drive
•  SVGA monitor (XGA recommended)
•  1 serial port for each:
    • hardwired channel of controllers
    • enrollment station for cards (optional)
    • dial-in modem (optional for remote support, updates, etc.)
    • CCTV matrix switcher controls (optional)
•  1 parallel port for each:
    • report printer (optional)
    • badge printer (optional)
    • alarm/logging printer (optional)
    • parallel multi-port adapter (for multiple printers, available through Hirsch)
•  NIC (Network Interface Card) for TCP/IP connections between server and workstations
•  Video Card (256 MB video RAM minimum) when using graphics or badging, or any system running Vista
•  Switch or Hub for server installations
•  Microsoft-compatible PS2 or USB mouse
•  Sound Card (optional, recommended for tutorials & alarms)
•  Modem (recommended for tech support)
•  Tape, CD-RW, Zip Drive, or other mass storage back up (optional)
•  Video Capture Card (optional for photos or CCTV matrix switcher)

Issue Fixed:

KB501 - PRB: Out of Stack Space Error occurs if all items in the ColumnHeaders (Acknowledged Pane and/or Unacknowledged Pane) are unchecked

Symptom:  An "Out of Stack Space Error" occurs when all items in the ColumnHeaders for Acknowledged Pane and/or Unacknowledged Pane are unchecked in the Alarm Viewer Properties

Cause:  The Hirsch Grid has a problem when only showing one Column Header

Solution:  Modified the Column Headers to require two items be visible.  To resolve this issue, install HirschAlarmView.dll version 3.2.59 or later. This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To:  VEL-147, DC 633

KB502 - PRB:  Error in access database" message received when activating Video Explorer

Symptom:   An "Error in access database" message occurred when activating Video Explorer if logged in as Non-Administrator in Windows and Velocity

Cause:  The Video Explorer did not setup the right privilege to access the database on the client machine

Solution:  To resolve this issue, install VideoExplorerExe.exe version 3.5.0.11 or later.  This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server.

Applies To:  VEL-142

KB503 - PRB:  Moving controller from SNET to XNET doesn’t change address after upgrading from Velocity v2.6SP2 to v3.1

Symptom:  After an upgrade from Velocity 2.6SP2 to Velocity 3.1, moving a controller from SNET to XNET the address for that controller remains listed as an SNET address when it should have been converted to XNET

NOTE:  This issue ONLY applies to systems that have been upgraded from Velocity 2.6SP2 and is not an issue on new Velocity 3.1 installs

Cause:   Due to an internal software defect, a stored procedure in the database was not upgraded properly

Solution:  To resolve this issue, apply Update for Velocity 3.1 (KB480) which will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  VEL-143, DC 640

KB504 - PRB:  Application error occurred when setting Database Application Role Password in Service Control Manager (SCM)

Symptom:  An application error occurred when setting the database "Application Role" password in Service Control Manager similar to the error below:

Unhandled exception in class WinMain.OnSetPassword.19 Exception: ADODB property has not been set

Cause:  Due to an internal software defect, the Service Control Manager did not create the database connection correctly

Solution:  To resolve this issue, install VelocitySCM.exe version 3.2.0.15 or later.  This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server.

Applies To:  VEL-144

KB505 - PRB:  Velocity Help does not include reference to NVR

Symptom:  No reference to NVR available when viewing Velocity Help

Cause:  Due to documentation error, the Velocity Help file was not updated to reflect the NVR features

Solution:  To resolve this issue, apply Update for Velocity 3.1 (KB480) which will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  VEL-145

KB506 - PRB:  Video Explorer Help page is hidden behind the Video Explorer main window when viewed

Symptom:  When opening the Help for Video Explorer, the Help page which usually appears on top will launch behind the Video Explorer page when viewed

Cause:  Due to an internal software defect, the Help file did not have the Active window privilege

Solution:  To resolve this issue, install VideoExplorerExe.exe version 3.5.0.11 or later.  This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server.

Applies To:  VEL-148

KB507 - PRB:  Enrollment Manager - Mapping UDF Fields does not include reference to RUU in the Velocity Help file

Symptom:  When viewing Enrollment Manager - Mapping UDF Fields in Velocity Help, notice that there are no references to RUU

Cause:  Due to documentation error, the Velocity Help file was not updated to reflect the RUU features

Solution:  To resolve this Issue, install Update for Velocity 3.1 (KB480) and will be automatically installed on each client machine once applied to the Security Domain

Applies To:  VEL-149

KB508 - PRB:  Imported Users with future Activation/Expiration Date are not having their Credentials downloaded to the Controllers

Symptom:   When importing Users with future Activation/Expiration Date, their Credentials do not get downloaded to the Controllers according to schedule

Cause:  The “Activation/Expiration” flags of the newly created credential is updated before applying relative date to the credential in the database

Solution:  To resolve this issue, install HirschEMSupport.dll version 3.5.0.11 or later.  This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To:  VEL-151

KB509 - PRB:  COM ports do not show on a Velocity Client computer

Symptom:  No available COM ports appears in the "Serial Port" drop-down list when selected from a Velocity Client machine on a Server/Client configuration.

Cause:  Due to programming error, the routine did not enumerate the COM ports on the client machine correctly

Solution:  To resolve this issue, install RS232Witer.exe version 3.2.0.36 or later. This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To:  VEL-152

KB510 - PRB:   Computer with more than 2 COM ports may see "Phantom" ports in Velocity Serial Port Writers

Symptom:  Phantom ports may appear under "Serial Port" drop-down list when configuring Serial Port Writers on computers with multiple COM ports

Cause:  Due to an internal software defect, the serial port that the modem uses is being listed in the available COM ports under Velocity Serial Port Writers

Solution:  To resolve this issue, install RS232Writer.exe version 3.2.0.36 or later.  This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To:  VEL-153

KB511 - PRB:  Velocity 3.1 (KB438) broke Credential Downloads via IDK

Symptom:  When downloading Credential using the "Wrapper" via IDK, the credential is not being processed at the top of the minute as expected. Instead it is being put in a queue to be downloaded when a function is assigned to or deleted from a credential that was created on the same day

Cause:  Due to an internal software defect, the current routine only worked for credential created on the current day

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

Applies To:  VEL-154

KB512 - PRB:  Who's Inside windows locks up or freezes in the event of a high number of transactions

Symptom:  The Velocity Who's Inside window locks up or freezes the Velocity Client UI, when it is used on larger sites

Cause:  The Who's Inside Information pane keeps updating too rapid that causes Velocity Client UI to be busy and locks up or freezes

Solution:  Modified Who's Inside to display listed items every two (2) seconds.  To resolve this issue, install HirschWhosINside.dll version 3.1.0.059 or later.  This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To:  VEL-156

KB513 - PRB:  Velocity not recognizing COM ports created via Realport Driver

Symptom:  Velocity does not recognize any ports except COM1 and COM2 when creating COM ports via RealPort Driver

Cause:  The current routine in Velocity did not recognize the COM port being created by Digi

Solution:  To resolve this issue, install DTServer.exe version 3.2.0.160 or later, HirschDotNetRoutines.dll version 3.5.1.0 or later and HirschDotNetRoutines.tlb. These files are available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To:  VEL-164

KB514 - PRB:  Application error occurred in Enrollment Manager when searching for Person ID with the value of "is" and "equal to" under Function Field

Symptom:  When searching for Person ID with the value of "is" and "equal to" under Function Field in Enrollment Manager, the following error occurred:

Function Name:frmQueryBuilder.cmbOp_Click
FunctionSubItem: 155
Number:6
Description: Overflow

Cause:  Due to an internal software defect, the queries are not being processed correctly resulting the error

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

Applies To:  VEL-169

KB515 - PRB:  Graphics usage causes system wide slow down

Symptom:   Significant performance decrease in Velocity When a great number of "State Changes" are triggered on a very large map in Graphics

Cause:  On large maps, the amount of data that each message needs to wade through in order to update the map.  A map with few objects on it has very little data it needs to go through in order to update the VIO that message belongs to.

Solution:  An option to "Ignore State Changes" has been added to increase performance.  This feature is found in the "View|Options" menu and does exactly what it says, ignores all state changes in Graphics.  To apply this option, install HirschGraphics.exe version 3.2.257 or later. This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To: VEL-170

KB516 - PRB:  A message received "Can't make a connection with "NVR"" when viewing camera from Velocity Client

Symptom:  When viewing cameras from a Velocity Client machine, a message "Can't make a connection with "NVR"" will appear on the screen making it unable to view cameras

Cause:  Due to an internal software defect, the update program did not register the .NET dlls correctly on the client machine causing the error when viewing NVR cameras from Velocity Client machine

Solution:  To resolve this issue, apply Update for Velocity 3.1 (KB480) which will be automatically installed on each client machine once applied to the Velocity Security Domain

Applies To:  VEL-178

KB517 - PRB:  An application error occurred when Bundling/Unbundling Doors

Symptom:  Bundling/Unbundling doors causes an application error as shown below:

Description: Argument not optional
Function: Velocity.FAdministration.lstRightPane_ItemCheck(142)
Error Number: 449

Cause:  When a door is bundled/unbundled, a message is sent to Graphics stating as much. The message to Graphics was missing a parameter

Solution:  To resolve this issue, install Velocity.exe version 3.1.0.465 or later.  This file is available in Update for Velocity 3.1 (KB480) and will be automatically installed on the Security Domain Server

Applies To:  VEL-209

Known Issues:

KB479 - PRB:  Extension service may not stop automatically when applying Velocity Updates.

Symptom:  Extension service failed to stop automatically while applying Velocity Updates and may stop responding (hang) for excessive periods of time.   When this happens, the following message appears on your screen:

The service 'EXServer' is currently running and must be stopped in order for the update to
continue.

You may stop the service yourself and then press 'Retry' to continue with this update or
press 'Cancel' to exit without installing this update.

Please consult the KB Release Notes for additional Installation Instructions which may
pertain to the error condition.

Cause:  If the "DVR Reader" Server Extension is checked under "Velocity Server Extensions Manager" and there is no DVR configured in Velocity, the DVR Extension Service fails to stop.

Workaround:   The workaround is to "Stop" the DVR Extension Service manually.  Use the "Task Manager" and select the "Processes" tab to end the process "Hirsch “HirschSensormaticExt.exe” before installing Update.

Status:  This is a known issue that will be addressed in a future release and is resolved by following the above steps.

Applies To:  DC 607

KB497 - PRB:  Pelco DVR cameras could not view all 16 cameras at the same time

Symptom:   Unable to view all 16 cameras at the same time

Cause:  There are only five concurrent connections available for this model.  Each connection needs a different user to log in

Solution:  None at this time.  This is a Known Limitation.  For more details, see Update for Velocity 3.1 (KB289) Release Notes

Applies To:  DC 610