Update for Velocity 3.1 (KB500) Release Notes

 

Update for Velocity 3.1 (KB500) Released 05/07/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:  Applying (KB500) may take much longer than normal depending on the size of the database.  Please wait for the process to complete and DO NOT "End Task" while the Update is being applied.

 

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:

KB523 - ENH: Enhanced performance in Velocity when "Routing" is enabled

Description

When routing is enabled, adding clients slows down the message handling of the SDServer to the point where it falls behind very easily with a lot of clients connected

Cause

Each client requires a database lookup which the SDServer was doing one after another for each message.  So if there are 30 clients connected it was doing a database lookup 30 times in a row before moving on to the next message

Solution

The Velocity client will execute the query on the client instead of in the SDServer.  This will allow for near simultaneous lookups and the SDServer won’t have to wait until they are all complete before moving on to the next message

Installation

Apply SDServer.exe version 3.2.0.127 or later and Velocity.exe version 3.1.477 or later.  These files are available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-285

KB524 - PRB:  Alarm priority in message handling by the SDServer was showing delayed alarm processing

Symptom

"Alarm Priority" over regular events was not working in most cases

Cause:

The solution using dual queues did not work because of the nature of network buffers

Solution

A secondary socket for alarms was added which allows for a separate network buffer just for alarms.  This gives alarms priority over regular events since they must all share the same socket and network buffer.  To resolve this issue, apply SDServer.exe version 3.2.0.127 or later and DTServer.exe version 3.2.0.170 or later. These files are available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-192

KB525 - PRB:  Velocity "Default Beep" stay active on top of multimedia alarm

Symptom

The Velocity "Default Beep" stay active on top of multimedia alarm

Cause

There was a refresh issue.  Changing Console|Preferences or Customization Manager did not immediately refresh the audio settings in Alarm Viewer

Solution

To resolve this issue, install HirschAlarmView.dll version 3.2.0.70 or later.  This file is available in Update for Velocity 3.1 (KB500) which will be automatically installed on each client machine once applied to the Velocity Security Domain

Applies To:  VEL-179

KB526 - PRB:  An "Application error occurred" while Adding/Downloading Credential when controller has been disabled

Symptom

In Graphics, when mapping the point on the canvas at the same time Adding/Downloading Credential while the controller has been disabled, the following unexpected application error may occurred:

Function Name: SendToGraphics
FunctionSubItem:1
Number:91
Description: Object variable or With block variable not set

Cause

Graphics was telling Velocity that it was shutting down, then aborting the shutdown. Velocity did not know about the abort

Solution:

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

Applies To:  VEL-204

KB527 - ENH:  Alarm Viewer Refresh Performance

Description

The Alarm Viewer was refreshing the grids for each alarm that was cleared or acknowledged.  This amount of refresh was unnecessary

Solution

A timer was added to only refresh the grids no sooner than 40 millisecond intervals

Installation

Apply HirschAlarmView.dll version 3.2.0.70 or later. This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server.

Applies To:  VEL-274

KB528 - ENH:  Event Viewer Refresh Performance and Queuing

Description

The Event Viewer was using a Queue to store events if the system was handing them out at a fast rate.  This caused a perceived slowdown of events showing up in the event viewer

Solution

The Queue was removed and a refresh timer was added.  Events will now show up as soon as they get to the client from the services.   The timer will only allow the Event Viewer to refresh its display once every 40ms

Installation

Apply HirschEventView.dll version 3.2.0.65 or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server.

Applies To:  VEL-273

KB529 - PRB:  DIGI*TRAC Service was deadlocked in SQL and SQL rejected the connection

Symptom

DIGI*TRAC Service was deadlocked in SQL and causes SQL to reject the connection.  The DTService never recovered and had to be restarted manually to regain communication

Cause

Graphics was querying the database and caused a deadlock with another process

Solution

The query was changed so that it would not lock the database.  To resolve this issue, apply HirschGraphics.exe version 3.2.261 or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-224

KB530 - PRB:  Occasional delay occurs in Graphics preventing functionality to unlock a door when Video Call-Up is taking place

Symptom

Delay occurs in Graphics preventing functionality to unlock a door when Video Call-Up is taking place

Cause

Video Explorer waits for the camera connection to be completed before responding causing delays

Solution

Modified Video Explorer to show all the time until it is closed.  To resolve this issue, apply the following files:

VideoExplorerExe.exe version 3.5.0.111 or later
VideoSensormatic.dll version 3.5.0.49 or later
VideoNVR_AD.dll version 3.5.0.46 or later
HiddenDeviceAdmin.dll version 3.5.0.32 or later

These files are available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-195

KB531 - PRB:  Dual Monitor configuration causes video image to appear on one monitor and the Video Explorer component to appear on the other

Symptom

Dual Monitor configuration causes image to appear on one monitor and the Video Explorer component to appear on the other

Cause

When the second monitor is on the left side, the X coordinate is negative

Solution

Modify the routine to handle negative coordinate correctly.  To resolve this issue, apply VideoExplorerExe.exe version 3.5.0.111 or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-189

KB532 - PRB:   Delay occurs in Video Explorer when displaying video on an alarm trigger

Symptom

There is a 10 to 15 seconds delay when displaying video upon an alarm condition

Cause

Root cause of the delay is unknown at this time

Solution

Modified Video Explorer to display video sooner upon alarm condition.  To resolve this issue, apply the following files:

VideoExplorerExe.exe version 3.5.0.111 or later
VideoSensormatic.dll version 3.5.0.49 or later
VideoNVR_AD.dll version 3.5.0.46 or later
HiddenDeviceAdmin.dll version 3.5.0.32 or later

These files are available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-188

KB533 - PRB:  Help button does not work under E-Mail Writer Properties when viewed

Symptom

When you tried to activate the Help in E-Mail Writer Properties, nothing happens

Cause

Due to internal programming error, the Help file was not available in E-Mail Writer Properties

Solution

To resolve this issue, install Velocity.chm dated 03/30/2010  or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-223

KB534 - PRB:  "Add-Ins" Help button in Server Extension Properties does not work

Symptom

When you click the "Add-Ins" Help button in Server Extension Properties, nothing happens

Cause

Due to internal programming error, the Help file was not available in Server Extension Properties

Solution

To resolve this issue, install Velocity.chm dated 03/30/2010  or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-216

KB535 - PRB:  Unable to display Help from Who's Inside

Symptom

When you click the Help "(?)" icon from Who's Inside window, nothing happens

Cause

Due to internal programming error, the Help file was not available in Who's Inside

Solution

To resolve this issue, install Velocity.chm dated 03/30/2010  or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-215

KB536 - PRB:  Clicking Help on RUU tab brings up help for Central Stations

Symptom

When you click the Help on RUU tab, the Help opens the wrong topic/reference

Cause

Due to internal programming error, the Help file was linked incorrectly

Solution

To resolve this issue, install Velocity.chm dated 03/30/2010 or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server

Applies To:  VEL-150

KB537 - ENH:  Return To Normal (RTN) alerts will now be audible

Description

Return To Normal (RTN) alerts will now be audible if they are present in the "Unacknowledged" pane of the Alarm Viewer

Installation

Apply HirschAlarmView.dll version 3.2.0.70 or later.  This file is available in Update for Velocity 3.1 (KB500) and will be automatically installed on the Security Domain Server.

Applies To:  VEL-348

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