Update for Velocity 3.0 (KB110) Release Notes
 

January 31, 2007

 

Update for Velocity 3.0 (KB110) Released 04/26/2007 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.

 

KB121 - PRB: Run time error when closing Velocity while New Door Group dialog is open

Symptom:  If an operator is defining a new Door Group for a Credential function and exits Velocity while the Door Group dialog is still open, the following error will occur:

Run-time error '462'

The remote server machine does not exist or is unavailable

Cause:  The Velocity client should not be allowed to close while a new Door Group is being defined for a credential function

Solution:  Install and register HirschEnrollmentManagerV3.exe version 3.0.0.556 and HirschEnrollmentManagerTV3.exe version 3.0.0.554 dated Friday, March 16, 2007. These files are available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4178

KB125 - PRB: Person added from person template generate incorrect event

Symptom:  Adding a person from template generates Event 1042 indicating the person was changed instead of event 1040 indicating the person was added.

Cause:  Due to an internal logic error the wrong event ID was generated.

Solution:  Install and register HirschEnrollmentManagerV3.exe version 3.0.0.556 dated Friday, March 16, 2007.  These files are available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4184

KB126 - PRB: Application error running history report

Symptom:  While running a history report the following error is displayed:

Error (5) occurred in LoadReportRDC_V3 at line: 210
Invalid procedure call or argument

Cause:  This problem occurs when SQLDMO is not properly registered on the computer running the report.  The error message is misleading because the module that actually encountered the error failed to report it correctly.

Solution: 

1)  Verify the following files exist in the Windows System32 folder on the computer having the
     problem:

sqldmo.dll version 2000.85.1054.0
sqldmo.rll version 2000.85.1054.0
ntwdblib.dll version 1999.4.12.0

2)  Register the file sqldmo.dll using REGSVR32.EXE which can be found in the Velocity folder.

3)  Install and register ArchiveLogServer.exe version 3.0.0.97 and HirschEnrollmentManagerTV3.exe dated Thursday, March 22, 2007.  This file is available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4197

KB130 - PRB: DIGI*TRAC Network Service may fail to start on systems with a computer date format that is not MM/DD/YYYY

Symptom:  Starting the DIGI*TRAC Network system does not connect to hardware.  No alarms or events are displayed. If the Technical Support file is reviewed (Velocity DIGI-TRAC Network Service-Technical Support File.Txt) there may be error messages logged:

EXCEPTION.PollingEngineInterface.ProcessMessage.88 [-2147217913] Error converting data type varchar to datetime

Cause:  The SQL Server platform requires a specific date format be selected at the time of installation.  The Velocity Installer set the date format to MM/DD/YYYY for consistency across all Velocity systems.  A defect in the source code may not properly convert the local date format from a different regional setting to the expected format and can result in an error returned from the SQL Server when it tries to manage messages coming back from a controller and logging them in the database.

Solution:  The source code for the file DTServer.exe has been updated to ensure that date handling properly formats all incoming data according to MM/DD/YYYY regardless of the server computer’s regional settings, which may have a different date format.  Install DTServer.exe version 3.0.0.120 or higher dated March 06, 2007. This file is available in Update for Velocity 3.0 (KB110)

Applies To:  DC 4176, DC 4207

KB131 -PRB: Velocity runs very slow after creating about 255 trigger action for the Intellex 4.0 DVR

Symptom:  Alarm Viewer may take a VERY long time to load, or refresh, when there are DVR Alarms.

Cause:  The date/time field in the table DVR_AlarmVideo2 was being misinterpreted.  The Value in that field is the Digi*Trac date/time, but the trigger that deletes the row was looking at the host date/time for comparisons.  Ultimately, the table would never get cleared of it's rows for doing these comparisons, making each successive compare longer and longer over time.

Solution:  This can be fixed by modifying the AlarmActive’s trDeleteActiveAlarm trigger to use the correct date/time field.  This file is available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

 Applies to: DC 4149

KB132 - PRB: Cosmetic flaws in various places in Velocity

Symptoms:  Cosmetic issues related to using Velocity application

Cause: 

a) Title bar for Critical Error is misspelled
b) The "OK" and "Cancel" button on Operator Note page
    displayed too far apart
c) "Add-In Manager" in the Add-Ins Menu should
     be followed by ellipsis points ( ... )  
d) "Exit..." in the File Menu should be "Exit" only,
    without ellipsis points ( ... ) 
e) Option to "Clear" and "Clear All" alarms are in Bold

Solution:  Install the latest Velocity.exe to fix the various cosmetic issues.  This file is available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain. 

Applies To:  DC 4206, DC 3498, DC 3702, DC 3562, DC 4114

KB135 - PRB: Integration Builder - 4 Basic Device state

Symptom:  When in the integration builder, click on the Cause | Basic Device State property, you would get an Undefined choice and nothing else.

Cause:  This behavior is by design.

Solution:  There is now a message box that will pop up and warn the user if they are trying to open the Integration Builder on a VIO that is not defined.  It will tell there where to go to define it first, or they can continue without defining it.  To resolve this issue, install Update for Velocity 3.0, this file is available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4127

KB136 - PRB: Able to assign duplicate IP address for a CCTV switcher even if the same port is already being used

Symptom:  You are able to assign an IP address for a CCTV switcher that is currently assigned to another device in Velocity (I.e., CSR, XNET/SNET Port, etc.).

Cause:  Velocity 3.0 did not check for duplicate IP addresses.

Solution:  Install and register HirschCCTVPort.dll version 3.0.0.5 dated Monday, March 16, 2007.  This file is available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4191

KB137 - PRB: An apostrophe ( ' ) in a UDF description causes error in Graphics

Symptom:  When opening the UDF Property Definitions form in Badge Designer, an error may occur if there is an apostrophe ( ' ) in one of the field values.

Cause:  When looking up the SQL query to find the value, the apostrophe would produce and invalid SQL syntax.

Solution:  The SQL statement has been modified to allow apostrophes.  To resolve this issue, install Update for Velocity 3.0, this file is available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4141

KB138 - PRB: Run Time error when closing Velocity while New Time Zone dialogue is open from Door Group

Symptom:  When user opens a Door Group configuration, then click on the time zones combo box and select <New> to open the time zone dialog.  When you shut down Velocity while the Time Zone dialog is still open, you may receive a runtime error message that is similar to the following:

Run-time error '462'

The remote server machine does not exist or is unavailable

Cause:  This issue may occur because the user shuts down the Velocity application while Time Zone component is still open.

Solution:  Set the busy flag in the Door Group component when user clicks <New> time zone to bring up the time zone component so that Velocity cannot be shut down while users are in the middle of creating a new time zone from the door group component.  To resolve this issue, apply Update for Velocity 3.0, this file is available in Update for Velocity 3.0 (KB110) which includes HirschDoorGroup.exe version 3.0.0.40 and will be automatically installed on each client machine once applied to the Security Domain.

Applies To: DC 4177

KB139 - PRB: Unable to Access Input Tab under Door Properties dialog box

Symptom: When Customization Manager is activated under Preferences, user is unable to select and expand Input Tab option under Door Properties dialog box.

Cause: This is caused by compiling the HirschDoor.dll while leaving the default tab at the Input tab.

Solution: To resolve this issue, install Update for Velocity 3.0.  This file is available in Update for Velocity 3.0 (KB110) which includes HirschDoor.dll version 3.0.0.26 and a script to reset the position of controls in the Door components.

 UPDATE Components SET ResetPosNextRun = 1 WHERE ComponentItemID = 13

Applies To: DC 4186

KB140 - PRB: Able to assign duplicate IP address when configuring XNET/SNET and do not show warning message if the same address is already being used by another component

Symptom:  When creating a new port (XNET/SNET), user is able to enter duplicate IP Address that is already being used by another component and do not show warning message "address already in use".

Cause:  No duplicate IP address checking in place.

Solution:  To resolve this issue, install Update for Velocity 3.0, this file is available in Update for Velocity 3.0 (KB110) which includes HirschPort.dll version 1.0.0.303 and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4189

KB141 - PRB: Time Zone icon disappears when using the "Enter" key under Door Properties and generate error message

Symptom:  Under Door Properties dialog box in the Input tab, click Logic tab and select a Time Zone.  While the time zone is selected, press Enter key and notice that the icon for time zone disappears and the form does not dismiss as expected.  If OK is clicked after this point, an error occurs:

Function Name:  SendToDtabase
FunctionSubItem:  156
Number:  91
Description:  Object variable or With block variable not set

Cause:  This is caused by not having the OK button as the default button on the Door Properties dialog box.

Solution:  To resolve this issue, install Update for Velocity 3.0, this file is available in Update for Velocity 3.0 (KB110) which includes HirschDoor.dll version 3.0.0.26 and will be automatically installed on each client machine once applied to the Security Domain.


Applies To:  DC 4199

KB142 - PRB: Expansion Input Properties Hot Key "Alt + _" does not function as expected

Symptom:  Not all controls on the expansion input properties dialog box have Hot Keys and some of those that have Hot Keys do not function correctly.

Cause:  This is caused by not properly assigning the Hot Keys and the Tab Index of the controls.

Solution:  To resolve this issue, install Update for Velocity 3.0 (KB110).  This file is available in Update for Velocity 3.0 (KB110) which includes HirschExpInput.dll version 3.0.0.7 and a script to un-register the Expansion Input component so that the new fix will take place.

UPDATE Components SET ResetPosNextRun = 1 WHERE ComponentItemID = 19

Applies To: DC 4203

KB143 - PRB: Reader Properties Hot Key "Alt + _" does not function as expected

Symptom:  Not all controls on the Reader Properties dialog box have Hot Keys and some of those that have Hot Keys do not function correctly.

Cause:  This is caused by not properly assigning the Hot Keys and the Tab Index of the controls.

Solution:  To resolve this issue, install Update for Velocity 3.0 (KB110).  This file is available in Update for Velocity 3.0 (KB110) which includes HirschReader.dll version 3.0.0.9 and a script to un-register the Expansion Input component so that the new fix will take place.

UPDATE Components SET ResetPosNextRun = 1 WHERE ComponentItemID = 33


Applies To: DC 4204

KB144 - PRB: Docked windows in the console will prevent DVR window from regaining focus

Symptom:  Docked windows in the console will prevent DVR window from regaining focus.  The viewer shows behind the graphics window and is not in primary focus.

Cause:  This behavior is caused by DVR window not being a child-window of Velocity main window.

Solution:  We added frmDisplayTemple as the child form of Velocity in the source code.  To resolve this issue, apply Update for Velocity 3.0 (KB110) to the Velocity Domain Machine.  The update will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 2635, DC 4115

KB145 - PRB: No connection failure message if DVR Service extension is not installed

Symptom:  If DVR service extension is not installed, there is no connection failure message to inform the user.

Cause:  This behavior is by design.

Solution:  A new message box "DVR server extension is not enabled.  Please select Add-Ins menu and click Server Extensions..." has been added.  To resolve this issue, apply Update for Velocity 3.0 (KB110) to the Velocity Domain Machine.  The update will be automatically installed on each client machine once applied to the Velocity Security Domain.

 Applies To:  DC 3709

KB148 - PRB: Able to assign duplicate IP address in the Central Station Receiver (CSR) Properties even if the same address is already being used

Symptom:  Able to assign duplicate IP address in the Central Station Receiver (CSR) Properties even if the address is currently assigned to another device in Velocity (I.e., CSR, XNET/SNET Port, etc.)

Cause:  There is a bug in Velocity 3.0 that it does not detect for duplicate IP Addresses

Solution:  A new message box "The IP Address" "0.0.0.0" has already been used, please assign another IP address" has been added.  To resolve this issue, apply Update for Velocity 3.0 (KB110) to the Velocity Domain Machine.  The update will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 4190

KB150 - PRB: Closing DVR Connection Status window with "X" (Close) button causes the connection to fail

Symptom:  When you view a camera, noticed that closing the DVR Connection Status window with "X" (Close) button causes the connection to fail

Cause:  There is a bug in Velocity 3.0 that the status window should NOT be closed manually.

Solution:  We removed the "X" (Close) window button from the DVR connection status window.  To resolve this issue, apply Update for Velocity 3.0 (KB110) to the Velocity Domain Machine.  The update will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 3710

KB151 - PRB: DVR Event History Viewer shows query result on both the Result pane and Crystal Report

Symptom:  No separate button to "Print" on DVR Event History Viewer to generate Crystal Report

Cause:  This behavior is by design 

Solution:  We added context menu, so that a user can have a choice to show result on the Result pane, or on both Result pane and Crystal Report.  To resolve this issue, install Update for Velocity 3.0, this file is available in Update for Velocity 3.0 (KB110) which and will be automatically installed on each client machine once applied to the Security Domain.

Applies to:  DC 3713

KB152 - PRB: The user interface on the DVR Alarm list should be disabled or hidden while in the process of retrieving video

Symptom:  When the form is displayed for a long time it seems like you're supposed to do something but if you do make a changes to the form (i.e., check off cameras, etc.) it has no effect on the results that are already in progress.

Cause:  This behavior is by design

Solution:  We disabled the components that are not used in the frmDateTimefile of the DVRAdminClinet module during download process.  To resolve this issue, apply Update for Velocity 3.0 (KB110) to the Velocity Domain Machine.  The update will be automatically installed on each client machine once applied to the Velocity Security Domain.

Applies To:  DC 3714

KB155 - PRB: Some PIV II End Point cards cannot be read

Symptom:  Attempting to read some PIV II cards will fail while attempting to select the card application.  The Output Window will show one of the two following error messages depending on whether you are using a contact or contact less reader respectively:

PIV_CARD_APPLICATION_NOT_FOUND
Select Application (<AID>) FAILED!

Cause:  An internal error caused the card select application command to fail on some cards.

Solution:  Install and register HirschPIVISO7816Reader.dll dated Friday, April 27, 2007. This file is available in Update for Velocity 3.0 (KB110) and will be automatically installed on each client machine once applied to the Security Domain.

Applies To:  DC 4210