Update for Velocity 3.1 (KB600) Release Notes

   

 

Update for Velocity 3.1 (KB600) Released 03/18/2011 contains file changes to address the following knowledge base articles:

 

Download and install the update by executing the EXE file on the Velocity Server which will launch the update wizard. Once the update completes, as each client re-connects to the Velocity Server, updates will automatically be applied. You do not need take the update to each Velocity client and run it.

IMPORTANT:  If ANY of the Velocity Services or Processes fails to "STOP" automatically while applying the updates, use the "Task Manager" and select the "Processes" tab to manually end the process.

 

NOTE:  Applying (KB600) 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.

NOTE:  Update for Velocity 3.1 (KB600) includes compatibility with MS SQL Server 2008 R2 Express Edition.

Issues Fixed:

PRB:  An application error occurred when restricting access via Roles to only view an M64 Controller

SYMPTOM: 

When selecting the Relay folder to only view an M64 Controller with restricted access via Roles, the following error occurred:

Description: Item cannot be found in the collection corresponding to the requested name or ordinal.
Function: ADODB.Fields.FAdministration.Hardware_NodeClick(84)
Error Number: 3265

CAUSE:

This function failed due to an SQL error.

SOLUTION:

To resolve this problem, apply Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-473

PRB:  The Disable “Right Click” function via Roles in Graphics do not work

SYMPTOM:

While in Graphics, it does not allow you to disable the “Right Click” option even it is disabled via Roles.

SOLUTION:

To resolve this issue, apply Update for Velocity 3.1 (KB600)

APPLIES TO:  VEL-564

PRB:  Inconsistent date format appears in the print preview when defined in the User Defined Field (UDF)

SYMPTOM:

When a UDF is set to be a specific Date format such as MM/DD/YYYY and you attempt to preview the badge template, you will notice that the badge will display or print as YYYY/MM/DD.

CAUSE:

Due to a minor programming error, the UDF date field in the Enrollment Manager is not recognizing the localized date format consistently.

SOLUTION:

Badge Printing was modified to display the UDF date field in the localized date format. To resolve this problem, apply Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-579 

PRB:  Changing a Linked Credential Template does not download the associated credentials

SYMPTOM:

When changing a Linked Credential Template, the associated credential will not download and instead will send a message “Operator started download of all controller setups:" in the Event Viewer.

CAUSE:

Due to an internal software defect, the Linked Credential Template is not downloading the associated credential.

WORKAROUND:

Right click mouse the Controller and select Download Credential.

SOLUTION:

To resolve this problem, apply Update for Velocity 3.1 (KB600)

APPLIES TO:  VEL-584, VEL-692

PRB:  Adding or modifying a credential template is generating a download of all controller setups

SYMPTOM:

When adding or modifying the Credential Template, the associated credential will not download and instead will perform a “download of all controller setups".

CAUSE:

Due to an internal software defect, the Credential Template is not downloading the associated credential.

SOLUTION:

To resolve this problem, apply Update for Velocity 3.1 (KB600)

APPLIES TO:  VEL-584, VEL-692

PRB:  An unexpected application error may occur when you open Enrollment Manager if the Scanner, PIV or RUU is enabled

SYMPTOM: 

An unexpected application error occurred when opening the Enrollment Manger if the Scanner, PIV or RUU is enabled under Device Configuration, similar to the error listed below:

Function Name: ScannerSupport.InitRegionCombos
FunctionSubItem: 4
Number: -2147024770
Description: Automation error
The specified module could not be found.

CAUSE:

This behavior is caused by a defective .dll file.

SOLUTION:

To resolve this issue, apply ScanWex.dll version 9.3.13.4. This file is available in Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-715

PRB:  An unexpected application error may occur when opening Guest or Unassigned Credential in the Enrollment Manager

SYMPTOM: 

An unexpected application error occurred when opening the Guest or Unassigned Credential in the Enrollment Manager, as shown below:

Function Name: frmCredential.LoadBiometricData
FunctionSubItem: 51
Number: 94
Description: Invalid use of Null

SOLUTION:

To resolve this problem, apply Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-807

PRB:  Inputs report incorrect names

SYMPTOM:

When an alarm is generated, the alarm will display with a different name in the Event Viewer and Alarm Viewer as well in Graphics Maps. In addition, the Report will show the incorrect input name.

CAUSE:

The specific cause of this defect is unknown at this time.  This problem was ONLY reproducible with the customer’s database.

SOLUTION:

To resolve this issue, apply SDServer.exe version 3.1.600.4. This file is available in Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-814

PRB:  An exception error occurred in the Enrollment Manager when adding a Credential Template on a UK Region setting

SYMPTOM:

An exception error occurred in the Enrollment Manager when adding a Credential Template on a UK Region setting.

SOLUTION:

To resolve this problem, apply Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-815

PRB:  Function Groups are being deleted from a Credential

SYMPTOM:

When multiple Function Groups are assigned to a Credential, and a Velocity Operator deletes any one of them, they are all deleted from the Credential.

SOLUTION:

To resolve this issue, apply HirschFunctionGroup.dll version 3.1.600.1. This file is available in Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-847

PRB:  An application error occurred when restarting the Velocity Services following a Database Application Role Password change

SYMPTOM:

An application error may occur when restarting the Velocity Services after changing the Database Application Role Password.

SOLUTION:

To resolve this problem, apply Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-850

PRB:   Unable to use the Service Control Manage (SCM) to stop the Velocity Extension Service

SYMPTOM:

Unable to use the Service Control Manage (SCM) to stop the Velocity Extension Service when the DVR Reader Server Extension is Enabled.

SOLUTION:

To resolve this issue, apply HirschSensormaticExt version 3.1.600.1. This file is available in Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-857

PRB:  SDServer Log Files do not display the full version number

SYMPTOM:

Since the automating the build process with the new longer version numbers, the log files no longer display the accurate version string.

For Example:

DServer version 3.1.544.54 is only displaying 3.1.54 instead of 3.1.544.54 in the logs.

SOLUTION:

To resolve this issue, apply SDServer.exe version 3.1.600.4 and DTServer.exe version 3.1600.4. These files are available in Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-874

PRB:  An unexpected error occurred when attempting to print from a Zebra ZXP-8 Badge Printer

SYMPTOM: 

An unexpected error occurred when attempting to print from a Zebra ZXP-8 Badge Printer, as shown below:

Description: Invalid property value
Function: PrintEngine.FPPreview.PrintPicture(23)
Error Number: 380

SOLUTION:

To resolve this problem, apply Update for Velocity 3.1 (KB600).

APPLIES TO:  VEL-877

Enhancements:

ENH:  The “Show Last Door Name” for Credentials option will show the Door Name in the Enrollment Manager

DESCRIPTION:

Modified Enrollment Manager to add “Show Last Door Name” for Credential options to show the Door Name instead of the Door Address under the Last Door column.

To Enable or Disable the “Show Last Door Name” option:

1. Select View from the Enrollment Manager Main Menu.
2. Select to place a check mark on “Show Last Access for Credentials” and “Show Last Door Name”.

NOTE: NO check mark will show the Door Address

To verify this function, select a User with Credential and view the Last Door Column

INSTALLATION:

Apply Update for Velocity 3.1 (KB600)

APPLIES TO:  VEL-442

ENH:  Support for American Dynamics Intellex version 4.3

DESCRIPTION:

Support for American Dynamics Intellex version 4.3 has been added

INSTALLATION:

Apply Update for Velocity 3.1 (KB600)

APPLIES TO:  VEL-537

ENH:  Card Scanning Solutions (CSSN) SDK Update 9.42.0

DESCRIPTION:

The SDK version has been updated to support the new Nevada driver's license format.

INSTALLATION:

Apply Update for Velocity 3.1 (KB600)

APPLIES TO:  VEL-576

ENH:  Improve Velocity system performance when running large Archive Reports

DESCRIPTION:

Currently when a large archive file is being restored to the database for the purpose of generating a report, it runs at the same priority as everything else. Priority should be given to alarm reporting and event handling. Reports should run in the background.

This enhancement only affects the restoration of an archive table to the current database. It prevents that restoration from tying up the SQL server during the restoration period. The restoration will take place in the background allowing other processes to use the SQL server and preventing the archive process from starving the system of resources.

INSTALLATION:

Apply Update for Velocity 3.1 (KB600)

APPLIES TO:  VEL-584

Known Issues:

 

PRB:  Pelco DVR integration does not work in Windows Vista or Windows 7

SYMPTOM:  Pelco DVR integration with Velocity does not work in Windows Vista or Windows 7

CAUSE:  Pelco do not support Vista or Windows 7 at this time.

SOLUTION:  None at this time.

WORKAROUND:  None at this time.

STATUS:  This is a known issue that will be addressed in a future release.

APPLIES TO:  VEL-878

PRB: MATCH number generated by Batch Enroll Credentials does not match what is being displayed by Readers

SYMPTOM:  The MATCH number on cards being enrolled using the Batch Enroll Credentials Function are different than what is being reported by readers.  As a result, the card won't perform the assigned function.

CAUSE:  Unknown at this time.

SOLUTION:   None at this time.

WORKAROUND:  Use the standard Enrollment process instead of the Batch Enrollment process.

STATUS:  This is a known issue that will be addressed in a future release.

APPLIES TO: VEL-896

 

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

Last modified:  March 23, 2011 09:029:25

Copyright © 2011  Hirsch Electronics, LLC.  All rights reserved.