Update for Velocity 3.1 (KB443) Release Notes

 

Update for Velocity 3.1 (KB443) Released 01/04/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 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 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.

Issue Fixed:

KB481 - PRB: Dial-Up will not connect when you right click "Download Configuration"

Symptom:  Dial-Up will not connect when you right-click on Controller "Download Configuration.

Cause:  Due to an internal software defect the "Service" was not initiating a dial-up for the controller.

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

Applies To:  DC 603

KB482 - PRB:  Command failure on Date/Time Download when set to Arizona Time Zone

Symptom:   Command Failure 457 on Date/Time Download when set to Arizona Time Zone

Cause:  The Velocity service was generating an invalid DIGI*TRAC command for time zones that do not observe Daylight Savings Time

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

Applies To:  DC 602

KB483 - PRB:  Dial-Up is causing issues with updating and defining credentials

Symptom:  As a credential is being added or updated:

1. The Event Viewer will show an “Execution failed port disabled at host” message.  
2. The Download Monitor will queue the credential, but never show the download taking place

Cause:   Due to the way DTServer was checking if port was a dial-up.

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

Applies To:  DC 523

KB484 - PRB:  Apostrophes (') in hardware names causes exceptions in the SDServer log file

Symptom:  Inspecting the Velocity Security Domain Service-Technical Support File.txt log file has lines similar to the following:

10/26/2009 22:02:38 EXCEPTION in Class::FService.OnHardwareMessage.134 [-2147217900] Incorrect syntax near 's'

Cause:  Due to an internal software error, apostrophes were not being processed correctly in a database update statement

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

Applies To:  DC 597

KB486 - PRB:  Extension Service error message - EXCEPTION in Class::WinMain.DispatchMessage.5097.14 [9] Subscript out of range

Symptom:  An error is logged in the “Velocity Extension Service-Technical Support File.txt” log file when event 5097 occurs.  The error logged is:

Extension Service - EXCEPTION in Class::WinMain.DispatchMessage.5097.14 [9] Subscript out of range

Cause:  The problem was that the code was trying to parse data that does not exist for 5097 event

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

Applies To:  DC 601

KB487 - PRB:  SDServer error message - EXCEPTION in Class::FService.OnXBoxMessage.69 [9] Subscript out of range

Symptom:  An error is logged in the “Velocity Security Domain Service-Technical Support File.txt” file while decorating an Xbox message error message pertaining to the network connection.  The error logged is:

SDServer - EXCEPTION in Class::FService.OnXBoxMessage.69 [9] Subscript out of range

The exception also causes this Xbox message not to be logged or dispatched to client viewers.

Cause:  Velocity did not know how to decorate an error value returned by the SNIB2

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

Applies To:  DC 600

KB488 - PRB:  Help button on "Verify Scanner Data" form does not work

Symptom:  When you press the "Help" button on the Verify Scanner Data form in the Enrollment Manager, no help is displayed for Card Scanning, PIV, and RUU readers

Cause:  The Help file did not include help for these items

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

Applies To:  DC 622

KB489 - PRB:  Run-Time Error occurred in Enrollment Manager when moving the screen's dividing line

Symptom:   A run-time error occurs if you move the line that divides the two halves of the Enrollment Manager screen all the way to the left

Cause:  Due to an internal software defect in the resize handler, an invalid value was being generated which caused a fatal application error in the Enrollment Manager

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

Applies To:  DC 608

KB490 - PRB:  Customized RUU tab replaces Credential Enrollment tab when updating to (KB438)

Symptom:  If you have a customized RUU tab, it will replace the Credential Enrollment tab with the RUU contents when you apply Update for Velocity 3.1 (KB438)

Cause:  Due to the way Velocity implements customization some design-time changes require resetting previous customizations

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

Applies To:  DC 614

KB491 - PRB:  First time use of SCM SDI010 Card Reader causes application error in Enrollment Manager

Symptom:  The first time using a SCM SDI010 contact/contactless reader will produce an application error:

Function Name: Form1GetSCReaderSelection

FunctionSubItem: 16

Number: 380
Description: Invalid property value

Cause:  The SCM SDI010 card reader is actually two card readers in one housing: a contactless and contact reader.  Due to an internal software defect, the Scanner component of the Enrollment Manager encountered an error while preparing the display the two card readers for operator selection

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

Applies To:  DC 604

KB492 - PRB:  When "Customization" is enabled, the Event Viewer Properties window will display the Filter Tab content on the General Tab

Symptom:  If "Customization" is enabled and the General Tab is customized under Event Viewer Properties, you will notice that the Filter Tab content is displayed in General Tab

Cause:  Upgrading from version to version produces an incompatibility

Solution:  A script has been added to re-register the Event Viewer customizations.  To resolve this Issue, install Update for Velocity 3.1 (KB443) and will be automatically installed on each client machine once applied to the Security Domain

Applies To:  DC 623

KB493 - PRB:  Unable to Register Velocity due to incorrect version information

Symptom:  Using the Registration Form to register Velocity will not pull up the right information

Cause:  Due to an older version of the registration wizard was being used

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

Applies To:  DC 615

KB494 - PRB:  Application Error occurred in Graphics after applying Update for Velocity 3.1 (KB438)

Symptom:  A similar application error may occur in Graphics after applying Update for Velocity 3.1 (KB438):

Function Name:  Velocity1_OnCLR

FunctionSubItem: 6
 
Number: -2147418107
Description:  Automation error
It is illegal to call out while inside message filter.

Cause: Numerous places were trying to callback to Velocity while Graphics was in a process intensive loop

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

Applies To: DC 625

KB495 - PRB:  Unable to add the Bosch Alarm Receiver

Symptom:  Unable to add Bosch Alarm Receiver into Velocity

Cause:  Due to no conventional COM name entry in the table PhysicalPorts

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

Applies To:  DC 579

KB496 - PRB:  Deleting then re-adding DVR Server Extension does not keep the same generic "DVR Reader" entry

Symptom:   Deleting then re-adding DVR server extension changes it from generic DVR to specific American Dynamics

Cause:  Due to the Display Name entry is not a generic name

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

Applies To: DC 609

KB498 - PRB:  Display problems occur when moving or dragging Video Explorer window while Graphics is open

Symptom:  With Graphics and Video Explorer open at the same time, moving or dragging the Video Explorer window has a tendency to cause display problems

Cause:  Moving the Video Explorer uses too much CPU resources.  The Windows can’t repaint it in a timely manner

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

Workaround:  If this happen again, you can right click the Video Explorer from task bar and choose “Close” (Alt+F4) to close the Video Explorer. And reopen Video Explorer again.  If the Windows can’t repaint it correctly, you can right click the Windows desk top and choose “Refresh” from the menu.

Applies To:  DC 616

KB499 - PRB:  16 cameras are not being recognized under Pelco DVR Properties settings

Symptom:  When adding Pelco DVR and then closing and reopening DVR Properties when set to 16 cameras, the settings will change from 16 to 8

Cause:  Due to an internal software defect, the information in the DVR Properties are not being saved in the table

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

Applies To:  DC 569, 624

Enhancements:

KB500 - ENH:  American Dynamics NVR (VideoEdge) integration

Description:   A new feature has been added to Update for Velocity 3.1 (KB443) to integrate American Dynamics NVR (VideoEdge) into Velocity System

Installation:   Apply Update for Velocity 3.1 (KB443) which will be automatically installed on each client machine once applied to the Security Domain

System Requirements:

     This is the minimum recommended Velocity workstation system requirements when the Velocity Client will be used for viewing and controlling cameras from an American Dynamics VideoEdge Server.  A larger hard drive is recommend if you will be storing local video clips.  A faster processor, additional RAM and additional video RAM will improve performance.

1.  2.0GHz Dual-core Intel processor or faster.
2.  2 GB DDR2 RAM or more.
3.  250 GB hard drive space or more.
4.  Gigabit Ethernet 1000 Mbit NIC.
5.  256 MB PCI Express x16 graphics card.
6.  1280 x 1024 (SXGA) with 32-bit color.

Known Integration Limitations:

1. Exporting Recorded Video is not supported from the Velocity Client.  This feature is supported with the American Dynamics Vx Client and Browser interface.

2. Retrieving Alarm History List is not supported.  Alarms generated when the Velocity Extension Service is not up and running will not be available in Velocity

3. For proper operation, the Velocity Server and the American Dynamics Video Edge Server must be synchronized to the same network time source

Known Issues:

1. When playing back the recorded video, the end time shown on the screen may not be the correct end time.  American Dynamics API support team is aware of this issue

NOTE:  This ONLY happens when recording ACC and is not seen in recording mpeg 4 or mjpeg.  In addition, this s seen when using Velocity or VX Client but no Web Client.

2. The Play Video window may not show any recorded video the first time after you install Update for Velocity 3.1 (KB443)

Workaround:  Close the Play Video window and re-do it again. The Play Video window will function correctly after this

3. In Video Explorer, the icon sometimes changes to contain “+” sign but nothing happens after that, when you drag a camera from left pane to the right pane. The drag and drop action is not complete at this moment. Please re-do it again

NOTE:  If you want to administrate the server from the Windows browser, you need to install Java from http://www.java.com/en/download/index.jsp

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 appear in 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