Update for Velocity 3.1 (KB438) Release Notes

 

Update for Velocity 3.1 (KB438) Released 11/12/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.

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

KB445 - PRB: Door Name not updating until the "SDServer" has been restarted

Symptom:  Door Name are not updating after renaming under "Door Properties" until after the Services has been restarted

Cause:  The internal caching mechanism in the SDServer service was not updated when the door name was changed.

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

Applies To:  DC 580

KB446 - PRB:  Velocity client may disconnect from SDServer when running Vista or Windows Server 2008

Symptom:   Running Velocity client on Vista or Windows Server 2008 may result in the client disconnecting from the Security Domain Service.

Cause:  The method used by Velocity to test the connection to the SDServer sometimes returned an erroneous result causing the client to report the connection as lost.

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

Applies To:  DC 321

KB447 - PRB:  Velocity E-mail and Message Queue Writers not delivering notifications for deleted users

Symptom:  When you configure E-mail and Message Queue Writers, you experience one of the following symptoms:

•  Message Queue notifications are not being sent out when users are deleted

•  E-mail writer notifications are not being sent out when users are deleted

Cause:  Most miscellaneous controller events are filtered from the E-mail Writers and Message Queue Writers. The User Deleted Event, a miscellaneous event, was mistakenly being filtered.

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

Applies To:  DC 534, DC 535

KB448 - PRB:  Pictures read from scanned PIV Cards are not being cleared when scanning the next New Person

Symptom:  When scanning the next New Person from scanned PIV Card, you experience one of the following symptoms:

• After the information and picture are read and saved from a PIV card, the picture remains in memory for the next "Verify Scanner Data" screen.  Simply clicking "Accept" on the Verify Scanner Data screen without reading a new card will put the previous picture into the new person file

• If a PIV card format that doesn't support pictures and is selected on the "Verify Scanner Data" screen, an application error will occur when the "Accept" button is clicked.

Cause:  Due to an internal software defect, the image was not being cleared from memory after the scanned data was accepted.

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

Applies To:  DC 548

KB449 - PRB:  TWIC mapping are not being saved after restarting Enrollment Manager

Symptom:  After enabling a PIV card reader and mapping the UDF fields for TWIC Contact, the mapped User Defined Field is not saved after restarting Enrollment Manager.

Cause:  The problem was caused by a duplicate UDF field index in the database.

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

Applies To:  DC 568

KB450 - PRB:  "TWIC Organizational Identifier" was misspelled

Symptom:  The Document Field "TWIC Organizational Identifier" is spelled incorrectly in the Map UDF Fields window.

Cause:  Misspelling in the default database

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

Applies To:  DC 586

KB451 - PRB:  Velocity PIV Reader conflicts with ActiveIdentity Client software

Symptom:  When you attempt to read a PIV card when ActiveIdentity Client is running on the same computer the card cannot be read due to  a PIV_CONNECTION_LOCKED message.  The following Error message is displayed.

• Unable to read PIV data

NOTE: The Output Window message:

Connect: PIV_CONNECTION_LOCKED

Cause:  The ActiveIdentity Client accesses the PIV card when it is inserted.  Velocity was then unable to gain exclusive access to the card.

Solution:  The PIV component has been updated to open the smart card in shared mode.  To resolve this issue, apply Update for Velocity 3.1 (KB438) which will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 596

KB452 - PRB:  Process transactionqueue is reporting "invalid column name 'xddr'" in DT Service Log

Description:  Process transactionqueue is reporting "invalid column name 'xddr" in DT Service Log.

Cause:  An internal query was malformed and caused the error

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

Applies To:  DC 598

KB453 - PRB:  Importing a controller from an XML file causes error

Symptom:  When importing a controller from an XML file the following error was encountered:

" Error # -2147467259 occurred in frmWizard: SaveDoors at line: 23 Key column information is insufficient or incorrect. Too many rows were affected by update."

Cause:  Using dynamic recordset to update the database table with two or more rows with the same data cause the above error but it doesn’t seem to always happen.

Solution:  Changed the code to use another more reliable ado object (commandset) to update the database in the SaveDoors function.  To resolve this issue, apply Update for Velocity 3.1 (KB438) which will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 595

KB455 - PRB:  None of the serial port defaults are filled in when the form is opened

Symptom:  When opening the Serial Port Writers, the default values would not be populated.

Cause:  A silent error was preventing the code from executing the default routines.

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

Applies To:  DC 551

KB456 - PRB:  Unable to clear alarms after truncating the AlarmActive table

Symptom:  Sometimes, it is not possible to clear alarms

Cause:  Not being able to clear alarms is a result of truncating the AlarmActive table.  There is an identity problem that can occur when this happens where two alarms share the same identity.  To do a back door clear (not recommended) you should do a delete instead of a truncate.  However, recent performance changes to the alarm viewer in (KB438) have made is so clearing and acknowledging alarms are now quicker than ever, thereby making the back door method of clearing not needed.

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

Applies To:  DC 558

KB457 - PRB:  Barcode flips upside down when typing in the position values

Symptom:  Sometimes it may appear that a barcode will flip upside down when manually setting values.

Cause:  Barcodes are special objects that only use the normal Top and Left properties for positioning them. The right and bottom properties are not used.  The height of the barcode is determined by the Barcode Height property and the width is determined by the actual data during printing.

Solution:  Do not use the Right and Bottom properties to specify barcode height and width

Status:  This behavior is by design

Applies To:  DC 571

KB458 - PRB:  Alarm icon in Status bar disappears when an alarm is active

Symptom:  As an alarm would come in, the status bar icon would cease to flash and disappear completely.

Cause:  There was a corrupted bitmap that represents the icons in the status bar. These icons have been fixed.

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

Applies To:  DC 581

KB459 - PRB:  A blinking alarm in graphics will cause the canvas to not refresh correctly when states are changed

Symptom:  The blinking of the alarm flash objects was interrupting the drawing of state change events. The Redraw property of the canvas was set to false while updating the blinking objects then set it to true afterwards.

Cause:  State change drawing functions were ignored until the next refresh occurred. The canvas redraws on everything that change now.

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

Applies To:  DC 582

KB460 - PRB:  Type Mismatch Error occurred while clearing Alarms in Graphics

Symptom:  The following error may occur while clearing Alarms in Graphics:

Description:  Type mismatch
Function:  Graphics.FMain.ClearAQ(88)
Error Number: 13
File Version:  Velocity Graphics – 3.2.201 

Cause: The process of looking up which alarm needed to be cleared was taking a while.

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

Applies To: DC 583

KB461 - PRB:  Virtual relays on graphics canvas may not update correctly

Symptom:  Sometimes virtual relays, or any other VIO would not refresh all the time.

Cause:  State change drawing functions were ignored until the next refresh occurred.

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

Applies To:  DC 584

KB462 - PRB:  Alarm Viewer routing not refreshing with expected Alarms until some are cleared on a different Velocity client's Alarm Viewer

Symptom:  Alarm viewer routing not refreshing with expected alarms until some are cleared on a different Velocity client's Alarm Viewer after receiving all alarms.  It would appear that some machines would not get alarms until routed alarms on another machine were cleared first.  This is will occur on a Server/Client configuration.

Cause:  This is a result of how the alarm viewer determined which alarms to display. The result set would grab the MAX_LINES count of possible alarms to display. If these alarms were not routed to the machine, they would not be displayed.

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

Applies To: DC 585

KB463 - PRB:  Escalated alarms disappears from Alarm Viewer on refresh

Symptom:   Escalated alarms were not refreshing in the Alarm Viewer

Cause:  The escalated alarm code was not properly being executed on refresh.

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

Applies To:  DC 587

KB464 - PRB:  Double-clicking an alarm in the Alarm Viewer causes an application error

Symptom:  When you double-clicked an alarm after recent performance enhancements, you may receive the following error:

Description:  Invalid Column Index
Function: HI65D9~1.sGrid.FAlarms.vGrid_MouseUp(17)
Error Number: 9
File Version:  Velocity Alarm Viewer – 3.2.38

Cause:  A double-click fires two mouse events. The second mouse event causes the error and is safely ignored.

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

Applies To:  DC 588

KB465 - PRB:  In Graphics, clicking a link to another drawing during an "Acknowledge All Alarms" is causing an application error

Symptom:  An Application Error may occur while performing a combination of the following functions:  Acknowledge or Clear a group of alarms and then switching canvas while the system is busy.

Description:  Invalid object handle in the "Current" property
Function: MDraw30.FMain.MDraw_HitObject(220)
Error Number: 23002
File Version:  Velocity Graphics – 3.2.241

Cause:  While alarms are being acknowledged and a canvas change request comes in, there may be invalid pointers left because the object has been acknowledged or cleared. The pointer has been cleaned up.

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

Applies To:  DC 591

KB466 - PRB:  Clicking the "Clear All Button" in Graphics a second time causes an Application Error

Symptom:  Similar errors may occur when clicking the Clear All or Acknowledge All buttons:

Description:  Subscript out of range
Function: cAlarmQueue.SecuredFlag(Get)(1):Graphics.cAlarmQueue.CanClear(7)
Error Number: 9
File Version:  Velocity Graphics – 3.2.244

Description:  Operation is not allowed when the object is open
Function: ADODB.Recordset.FMain.ClearAQ(690)
Error Number: 375
File Version:  Velocity Graphics – 3.2.243

Cause:  A double-click fires two mouse events. The second mouse event causes the error and is safely ignored.

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

Applies To:  DC 593

KB467 - PRB:  Access, Control Functions and Show Credential Information are missing on copied doors in Graphics

Symptom:  When copying a VIO, the software did not go through the same code path as plotting the VIO.

Cause:  Two different functions had different results. Both use the same code path now.

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

Applies To:  DC 594

KB468 - PRB:  Credential template “Link to:” combined with "Function Group" causes Function Group to be removed from credential in creation

Symptom:  A message "There are no functions defined for this credential.  Continue with save?" will appear when you click the "OK" button after creating a credential template using the "Function Group" and "Link to:" under Enrollment Manager.

Cause:  Due to an internal software defect, the Function Group was removed from the credential.

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

Applies To:  DC 566

KB470 - PRB:  Badge templates not sorted in Credential dropdown list

Symptom:  Badge templates are not sorted alphabetically in the "Credentials Badge Template" combo box.

Cause:  List was not sorted by name.

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

Applies To:  DC 577

KB471 - PRB:  Unnecessary Activation/Deactivation scheduled for Badge only (IDF 0) credentials

Symptom:  Credential Activation/Deactivation tasks were being scheduled when there when no non-IDF0 credentials required activation or deactivation.

Cause:  An internal software error caused activation/deactivation tasks to be scheduled when they were unnecessary.

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

Applies To:  DC 572

KB472 - PRB:  Open Diagnostic Window During Downloads Prevents Use of Other Velocity Modules

Symptom:  If the diagnostic window is opened while there are large downloads in progress the Velocity client begins to become more and more unresponsive and may appear frozen. The amount of slowdown is proportional to the number of messages being displayed by the Diagnostic Window

Cause:  The display processing overhead associated with large downloads prevented the Velocity Client from processing other request.

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

Applies To:  DC 563

KB473 - PRB:  With Customization enabled, modifying one screen tab will take affect on another screen tab

Symptom:  When you enter Design Mode in the Device Settings tab of the Enrollment Manager to customize the screen for one tab setting, it tends to also take affect another tab.  For example, if you go into Device Settings with Enrollment Manager and customize one of the settings tabs, it also tends to appear in the RUU tab.

Cause:  Due to an internal software error the customization settings for one tab were displayed on another tab.

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

Applies To:  DC 562

KB474 - PRB:  Signature Pad T-L-462-HSB will not work

Symptom:  Attempting to capture a signature using a Signature Pad T-L-462-HSB pad caused the following error:

Function name: CaptureSignature
FunctionSubItem: 55
Number:13
Description: Type mismatch

Cause:  There was a problem with Velocity’s internal interface to the SDK for the capture device.

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

Applies To:  DC 561

KB476 - PRB:  Web service doesn't send all command to Velocity

Symptom:  Some XML request to the Velocity web service were not being executed. For example, relay requests would not function.

Cause:  Due to an internal software error some XML requests were not being processed correctly.

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

Applies To:  DC 538

KB478 - PRB:  Unable to receive any alarms from Bosch D6600 Receiver version 01.03.01

Symptom:  The Velocity does not receive any alarm from Bosch D6600 Receiver version 01.03.01 dated 12/23/2008.

Cause:  The newer version expects different echo data format back.

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

Applies To:  DC 605

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