Update for Velocity 3.1 (KB417) Release Notes

 

Update for Velocity 3.1 (KB417) Released 08/07/2009 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.

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 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 Admins. 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.

KB421 - PRB: Inconsistent "Lock Down Workstation" operation

Symptom:  "Lock Down Workstation" ONLY worked properly once after the operation has been performed.  A "reboot" was required on both Server and Client in order for the operation to work correctly again.

Cause:  The collection of connection objects was not properly being removed when the socket was closed.  This caused the already closed socket to be closed again.

Solution:  To resolve this issue, install the file SDServer.exe version 3.2.0.83 or later.  This file is available in Update for Velocity 3.1 (KB417) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 529

KB422 - PRB:  Incorrect on board relay activates when logged-in as "Operator"

Symptom:   When an operator is logging in the non-admin view of the administration window, go to the relays tab and fire Expansion relay 1.  When this is done, base relay will 1 activate instead.  Expansion relay 1 will activate when you trigger Expansion relay 9.

Cause:  This happens in the Non-Admin view only.  If a relay or input was expansion, it was not properly setting the index to activate.

Solution:  To resolve this issue, install the file Velocity.exe version 3.1.0.446 or later.  This file is available in Update for Velocity 3.1 (KB417) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 524

KB423 - PRB:  Return to Normal events are duplicated in “All Event” report

Symptom:  Return to Normal events being duplicated in “All Events” report.

Cause:  Some RTN events (ie., port offline, port online) are logged in both the AlarmLog and Log_External tables.  When running the "All Events Log" report, data is pulled from all these log tables resulting in these RTN events to appear twice.

Solution:  Filtered the AlarmLog table to only show those non-RTN events since those will be pulled from Log_external table. To resolve this issue, install Update for Velocity 3.1 (KB417) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 530

KB424 - PRB:  Reports generated on non-US date format machines using date as a criteria display an incorrect date format at the top of report in the criteria

Symptom:  In an UK machine, if the date you want the report for is may 1st, at the top of the report will say 05/01/2009 which is correct for US but not for UK.

Cause:  The criteria just show the compiled SQL statement where clause as is.  In SQL, date format uses either US date format or YYYY-MM-DD.  It is not locale specific.

Solution:  Changed the criteria display at the top of report to be in the format of YYYY-MM-DD.  For example may 1st, 2009 will say 2009-05-01 which is independent of any locale setting.  It will always be in this format no matter what locale the customer's machine is set to.  To resolve this issue, install Update for Velocity 3.1 (KB417) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 531

KB425 - PRB:  Perform Database Maintenance in Velocity Scheduling Agent not working on a Split Server Configuration

Symptom:  Perform Database Maintenance schedule does not work on a split server configuration.  Error message in Velocity Scheduler_DB Maintenance.txt says “path not found”.

Cause:  The process to see if the SQL server backup directory exists is not valid if the sql server is on a different machine than the service.

Solution:  Omit the directory checking.  If the directory does not exist, the backup process will fail and the error will be logged in the log file.  To resolve this issue, install Update for Velocity 3.1 (KB417) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 545

KB426 - PRB:  Screen for PIV reader is not displaying properly if RUU is also configured

Symptom:  When both the RUU and PIV reader are configured, the tab for the PIV reader will display the contents of the RUU tab.

Workaround:  Show only the last credential’s zone status for any given person.  If a person uses one credential to get in and later another one to get out, the report only shows the person is out since that’s the last credential used. 

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

Applies To:  DC 526

KB427 - PRB:  Incorrect Import/Export Task Schedule Properties description

Symptom:  Import Properties description "Only configurable from the server since import files locate on the server.".  Should be replaced with “Only configurable from the server since import files are located on the server.".  Export Properties description "Only configurable from the server since export file destination locate on the server.".  Should be replaced with “Only configurable from the server since export file destination is located on the server.".

Cause:  Description error in the form.

Solution:  Corrected the Import/Export Task Schedule Properties form.  To resolve this Issue, install Update for Velocity 3.1 (KB417) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 522

KB428 - PRB:  UDF validation does not work as expected

Description:  Change a UDF type in the UI in such a way to invalidate existing UDF data and press OK you may not get any UDF validation errors.  However if you then reopen the UDF setup screen and press OK without changing anything you would get UDF validation errors.

Cause:  UDF checking criteria was obtained from the database instead of from the newly defined criteria specified in the UDF Setup screen.

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

Applies To:  DC 528, 543

KB429 - PRB:  Application error opening Controller component

Symptom:  The following error occurs when opening controller component.

GETTZInfo() Error (line:59): Invalid procedure call or argument

Cause:  If the Daylight Savings Time name entry for a Time Zone in the Windows registry has is empty this will cause the above error to occur.  Refer to the DLT entry for a specific time zone under the following registry key: HKLM\Software\Microsoft\Windows NT\CurrentVersion\TimeZones.

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

Applies To:  DC 544

KB430 - PRB:  Error opening component generated “Hirsch Localizer” error message

Symptom:  When opening a component you see the following error message.

Error #19 occured in LoadResStringEx at line 72
Object variable or With block variable not set
Control Type:
Contral Name:

Cause:  When customization is turned on the each component tries to load customization data from the database.  If this data has become corrupted the above error message may result.

Alternate Solution:  To eliminate the error message follow the steps below. Note that this will reset part or all of the customization done to the component.

1. Turn off customization. If not practical then
2. In Customization Manager, right-click on component that generated the error message and select "reset control positions".  If that doesn’t work try
3. In customization Manager, right click on component that generated the error message and select "Unregister"

Applies To:  DC 537

KB431 - ENH:  Additional Government smart card support

Description:  The following enhancements were made in Update for Velocity 3.1 (KB417):

•  Added support for CAC v2 (version 2) 144K smart cards.
•  Changed card processing for CAC cards to always try to read PIV applet no matter the ATR of the card.
•  Added support for multiple smart cards readers attached to system. If more than one smart card reader is attached to the computer the user must select which reader to use

Installation:  Apply Update for Velocity 3.1 (KB417) on the Velocity Server and will be automatically installed on each client machine once applied to the Security Domain.

KB432 - PRB:  Incorrect processing of Apostrophes in UDF fields

Description:  Apostrophe ( ' ) when used in any User Defined Field under Enrollment Manager are being replaced by a Quotation mark ( " ).  In addition, every time you enter a text with an apostrophe, it will duplicate the quotation mark.

Cause:  Due to an internal software defect apostrophe marks were being processed incorrectly.

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

Applies To:  DC 525