Update for Velocity 3.1 (KB541) Release Notes

 

Update for Velocity 3.1 (KB541) Released 06/22/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 (KB541) 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.

Issue Fixed:

KB543 - PRB:  Velocity Data are lost when Events/Alarms are in the queue

Symptom

Velocity Data are lost when Events/Alarms are in the queue and the Security Domain Service get's restarted intermittently

Cause

The specific cause is unknown at this time. However, after conducting several test it was discovered that by using the Security Control Manager (SCM); the services are shutting down at the same time and by the time SDServer is ready to shut down, the DIGI*TRAC connection is already severed

Solution

Modified the SDService to check the event queue if empty before shutting down. If the DIGI*TRAC service isn't already shut down, it sends a message asking the DIGI*TRAC service to stop sending new messages to it. It then sets a timer that periodically checks to see when the event queue is empty and then allows for an orderly shutdown.  To resolve this issue, install SDserver.exe version 3.01.487 or later.  This file is available in Update for Velocity 3.1 (KB541) and will be automatically installed on the Security Domain Server

Applies To:  VEL-165

KB544 - PRB:  Unable to clear alarms from Velocity Alarm Manager

Symptom

Unable to clear alarms from Velocity Alarm Manager

Cause

Truncating table AlarmActive will reset the primary key.  This will cause the duplicate primary key in AlarmLog table

Solution

Removed primary key from Alarm_ID and added new column Alarm_ID2 with primary key in AlarmLog and AlarmLog_archive table .  To resolve this issue, apply Update for Velocity 3.1 (KB541) which will be automatically installed on the Security Domain Server

Applies To:  VEL-166                       

KB545 - PRB:  Acknowledging alarm with video clip then closing and re-opening Velocity will cause the icon to disappear

Symptom

Video clip icon in the Alarm Viewer disappears when closing and re-opening Velocity after acknowledging alarms with video clip

Cause

Due to an internal software defect, the entries in the table that the icon is referenced to is being removed after acknowledgedging an alarm with video clip

Solution

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

Applies To:  VEL-212

KB546 - PRB:  NVR Video Explorer windows flickers before displaying cameras causing a delay

Symptom

When launching the NVR Video Explorer, the NVR Video Explorer window will flicker two (2) to three (3) times before it displays the cameras causing a delay

Cause

Due to an internal software defect, the NVR makes the connection every time when there is a connection request

Solution

To resolve this issue, apply Update for Velocity 3.1 (KB541) which will be automatically installed on the Security Domain Server

Applies To:  VEL-217

KB547 - PRB:  Creating an Archive interrupts Velocity Client operation

Symptom

When the scheduled task to archive Alarms/Events runs, velocity clients do not receive Alarms/Events until the archive is complete

Cause

Cause of this defect is currently Unknown

Solution

Modified the Archive Log server so that it uses its own database connection to communicate with the SQL Server.  This allows greater independence from the DIGI*TRAC Service and allow events to continue to be streamed to Velocity clients even when an archive is running.  To resolve this issue, install ArchiveLogServer.exe version 3.1.0.520 or later.  This file is available in Update for Velocity 3.1 (KB541) and will be automatically installed on the Security Domain Server

Applies To:  VEL-277

KB548 - PRB:  Running an Archive Report Interrupts Velocity Client Operation

Symptom

When a report is run, and it requires data from an archive database, the Velocity Clients stop displaying Alarms/Events until the report is complete

Cause

Cause of this defect is currently Unknown

Solution

Modified Report to run inside its own process, freeing up the Velocity client while it's running. To resolve this issue, install Report.exe version 3.1.0.36 or later. This file is available in Update for Velocity 3.1 (KB541) and will be automatically installed on the Security Domain Server

Applies To:  VEL-278

KB549 - PRB:   Alarm Secure and Return to Normal (RTN) are not being reported on time

Symptom

In Velocity, Alarms are reported very quickly.  However, Alarm Secure and Return to Normal (RTN) messages are delayed

Cause

Due to an internal software defect, Alarm Secure and Return to Normal (RTN) messages are not being reported on time

Solution

Modified Return to Normal (RTN) messages to identify at the DIGI*TRAC service level be routed through the Alarm socket giving them the same priority as Alarms. To resolve this issue, install DTServer.exe version 3.01.0525 or later.  This file is available in Update for Velocity 3.1 (KB541) and will be automatically installed on the Security Domain Server

Applies To:  VEL-302

KB550 - PRB:  Stopping all Velocity Services does not end the SQLTransactions.exe process

Symptom

When stopping all Velocity Services from the Security Control Manager (SCM), you will notice that the SQLTransactions.exe process still shows under Processes of the Windows Task Manager

Cause

Due to an internal software defect, the SQLTransactions.exe do not end the process in Windows Task Manager

Solution

Modified SD Service which is now responsible for ensuring that the SQL Transactions process is shut down when it shuts down.  This will prevent future updates from complaining about that program being active when an update occurs.  To resolve this issue, install SDserver.exe version 3.1.0.492 or later. This file is available in Update for Velocity 3.1 (KB541) and will be automatically installed on the Security Domain Server

Applies To:  VEL-381

KB551 - PRB:  EXCEPTION in Class message when Restarting Services

Symptom

An EXCEPTION in Class message is appearing in the Velocity Security Domain Service log when SDService is restarted. It appears before the DIGI*TRAC Network service is started

Cause

Due to a custom message being used that had no accompanying description with it when restarting the DIGI*TRAC service

Solution

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

Applies To:  VEL-419

KB552 - PRB:  Unable to apply Update for Velocity 3.1

Symptom

In some cases when installing Update for Velocity 3.1, the Install Wizard may not start.  The files are extracted to the designated temporary directory and once extracted they immediately disappear

Cause

In the Installation Wizard, there are two (2) Administrator checks. Normally the first one will work, but in certain circumstances it would cause a fatal error to the wizard

Solution

Modified Install Wizard so that all test must pass before installation may proceed.  To resolve this issue, apply Update for Velocity 3.1 (KB541) which will be automatically installed on the Security Domain Server

Applies To:  VEL-421

KB556 - PRB:  Applying Velocity Update may fail on certain Velocity Clients

Symptom

While applying Update for Velocity 3.1 on certain Clients, the VelocityUpdate.exe may encounter an error while extracting files similar to following message:

Error signature

szAppName: VelocityUpdate.exe         szAppVer: 3.1.0.61         szModName: ntdll.dll
szModVer: 5.2.3790.4455         offset: 0001bf37

Cause

The cause of this error is unknown.  it is most likely an internal failure in the Install Wizard

Solution

Modified Install Wizard.  To resolve this issue, apply Update for Velocity 3.1 (KB541) which will be automatically installed on the Security Domain Server

Applies To:  VEL-441

KB558 - PRB:  An application error occurred when running reports

Symptom

When logged in as a different operator in windows and Velocity, the following unexpected application error may occur when running a report:

Function Name: PopulateTree
FunctionSubItem:5
Number:-2147217911
Description: The SELECT permission was denied on the object 'ReportGroups', database 'Velocity', schema 'dbo'.

Cause

Report Manager did not have permission to obtain reports if a regular domain user was logged into the client computer

Solution

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

Applies To:  VEL-446

KB559 - PRB:  Events written to the database are delayed versus Events sent to Velocity Clients

Symptom

When an event appears in the Event Viewer, it may not be written into the database immediately until after a few events has passed

Cause

Due to an internal software defect, the background .NET Thread is not responding in a timely manner

Solution

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

Applies To:  VEL-440

KB560 - PRB:  Update for Velocity 3.1 (KB500) caused the DVR Trigger Actions to stop working

Symptom

In some cases, after applying Update for Velocity 3.1 (KB500), the DVR Trigger Actions stopped working

Cause

Due to a side-effect of a recent defect where Video clip icon in the Alarm Viewer disappears when acknowledging alarms with video clip

Solution

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

Applies To:  VEL-431

KB561 - PRB:  Archive database error occurred during Scheduled Task

Symptom

The following error occurred when scheduling an Archive to take place:

Archive database error: ERROR:ArchiveAllLogs.19: (-2147217900) CREATE DATABASE permission denied in database `master`

Cause

This is a side effect of an earlier fix where the permissions for ArchiveLogServer no longer depended on
the calling process

Solution

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

Applies To:  VEL-450

Enhancements:

KB553 - ENH: Added "Active" or "Frozen" option in Who's Inside

Description

Sites with large number of credentials may experience difficulties selecting people in Who's Inside while it is updating.  The "Red" button when it appears halts the screen refresh which enables the operator to focus on investigation of specific lines and problems.  This is particularly useful when screen is very busy and lines keep jumping around as new information flows in and the screen is refreshed. The "Green" button when it appears resumes the refresh and polling

Installation

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

Applies To:  VEL-213

KB555 - ENH:  Move Download Configuration code from DTServer to VelocityThreads

Description

Consolidated some code involved in downloading configuration data to controllers into the VelocityThreads process.  There is no change in functionality, this just keeps the code more localized

Installation

Apply VelocityThreads.exel version 3.02.0018 or later and VelocityThreadsQueue.exe version 3.01.0030 or later. This file is available in Update for Velocity 3.1 (KB541) and will be automatically installed on the Security Domain Server

Applies To:  VEL-299

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

NOTE:  After you apply the Velocity 3.1 Update, verify that the update successfully installed.  In Velocity, go to Help and select About Velocity and click the scroll bar to verify the current version number of the Update