|
Update for Velocity 3.0 (KB80) Release Notes |
|
|
|
|
Update for Velocity 3.0 (KB80) Released 03
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.
KB82
-
PRB: External
integration processes may result in lost logged system transactions (events)
Symptom: System activity such as credential access
events are not recorded in the database. The events are seen in the event
viewer but do not show on reports.
Cause: If a third party tool or integration with the Velocity
database is used and frequently queries Velocity’s log tables (history of
events), those queries may take too long to complete and generate a “lock’ on
the tables(s) at the same time Velocity’s sub system is attempting to write new
events. The lock may result in new events getting lost if the lock is not
released and a successful SQL write is not performed.
Solution: While integration with the Velocity database
is not recommended, changes have been made to the file ‘SQLTransactions.exe’
that takes additional measures to provide fault tolerance under heavy locking
conditions. For Velocity 3.0, the revised file is available in Update
for Velocity 3.0 (KB80). For Velocity 2.6 SP2,
contact Technical Support for instructions on how to install the individual
file manually.
KB83 - PRB: Using PIN on some PIV cards may result in
an application error
Symptom: On certain PIV cards entering a PIN code to
access the Printed Information buffer may cause the following the following
error:
Velocity Client Application
An error has occurred.
Description: The remote server machine does not exist or is unavailable
Function: Velocity.FConsole.mnuConsoleArray_Click(37)
Error Number: 462
Causes: The
problem occurs if the data stored on the card is larger than the maximum values
listed in NIST SP800-73-1 Appendix A. These values are “suggested” maximum
lengths and may be changed by the card issuer.
Solution: Install and
register HirschPIV.dll version 1.0.0.25 dated
Applies To: DC4143
KB84 - PRB: If a camera, with
an index greater than 255, is programmed to use a preset, the index is set to
255 on the OK click.
Symptom: The Camera index value for a preset will be
reset to 255 if the camera index is greater than 255.
Causes: The camera index is being reset by a incorrect range checking function.
Solution: Install and register HirschCCTV.dll
version 3.0.0.5 dated
Applies To: DC4140
KB85 - PRB: Selecting cardformat for a UDF mapped MATCH code with no data causes
EM to disappear hanging Velocity
Symptom: When a MATCH code has been mapped to an UDF
that has no data and the cardformat is changed, the
Enrollment Manager may disappear and hang Velocity. At this point Velocity must
be terminated via the Windows Task Manager.
Note that this error only occurs if the UDF for the person
contains no data.
Causes: The program is trying to generate a MATCH code
on a zero length data field causing an unhandled internal error.
Solution: Install and register
HirschEnrollmentManagerV3.exe version 3.0.0.536 dated
Applies To: DC4139
KB86 - PRB: Multiple rows are
high-lighted in Standard Control Zone editor
Symptom: If the Control Zone editor is opened and
multiple points are clicked on different rows, all the rows stay highlighted.
Note: This only occurs if the point columns are clicked before
clicking on either the control zone name or time zone columns.
Causes: The problem is caused by a software defect in
the HirschControlZoneObject.dll.
Solution: Install and register
HirschControlZoneObject.dll version 3.0.0.10 dated
Applies To: DC4133
KB87 - PRB: Closing User
Defined Setups dialog causes application error
Symptom: Closing the User Defined Setups dialog will
cause an application error under the following circumstances:
1) Search Results group is
selected and there are no search results displayed and
2) There is no person record displayed.
The following error is produced:
Velocity EM
Run-time error '91':
Object variable or with block variable not set
Causes: This was caused by a software error in
HirschEnrollmentManagerV3.exe that was referencing the currently selected
person record, which in this case, was nothing
Solution: Install and register
HirschEnrollmentManagerV3.exe version 3.0.0.536 dated
Applies To: DC3999
KB88 - PRB: Error Importing customizations from V2.6Sp2 to V3.0 fails
Symptom: Importing older Customization files into
Velocity 3.0 will produce an incompatible issue
Cause: The older customization file did not contain
all elements that the new format was expecting. As a result the following error
would occur:
Error: frmStep_wizard.InsertValues
Line 240
Descr: file not found: ~ctinteg.tmp
Solution: Install CustImportExport.exe version 3.0.0.9
Applies To: DC4142
KB89 - PRB: Application error
when renaming VSO
Symptom: Trying to save a VSO that is currently being edited may cause in an application error
The following cascading error messages may be presented to the user:
Description: Subscript out of range
Function: Graphics.cCanvases.MDIndex(Get)(1)
Error Number: 9
Description: Subscript out of range
Function: Graphics.cCanvases.DBID(Get)(1)
Error Number: 9
Description: Subscript out of range
Function: Graphics.cCanvases.DisplayName(Get)(1)
Error Number: 9
Description: Subscript out of range
Function: Graphics.cCanvases.CanvasType(Get)(1)
Error Number: 9
Description: Subscript out of range
Function: Graphics.cCanvases.ScaleFactor(Get)(1)
Error Number: 9
Description: Subscript out of range
Function: Graphics.cCanvases.DBID(Get)(1)
Error Number: 9
Description: Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
Function: ADODB.Field.cDatabaseAccess.InputBLOB(5)
Error Number: 3021
Description: Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
Function: cDatabaseAccess.InputCanvas(5):ADODB.Field.cDatabaseAccess.SaveCanvas(24)
Error Number: 3021
Description: Subscript out of range
Function: Graphics.cCanvases.bDirty(Let)(1)
Error Number: 9
Description: Subscript out of range
Function: Graphics.cCanvases.bNewDrawing(Let)(1)
Error Number: 9Solution: Install HirschGraphics.exe version 3.0.0.58 January 18, 2007 and register the file in Windows. This file is available in Update for Velocity 3.0 (KB80) and will automatically be install on each client once applied to the Security Domain.
Applies To: DC4180
KB91 - PRB: Minimizing the
Photo Callup window exits Velocity client unexpectantly
Symptom: When Photo Callup
window is minimized, Velocity will close.
Cause: This was a result of trying to
"show" the form while it was minimized
Solution: Install PhotoCallupBT.dll version 3.0.0.18
Applies To: DC4135
KB92 - PRB: Door Access by
person Report displays inactive credentials
Symptom: Run the “Door Access by person” Report and
notice that the report displays inactive credentials as well as active
credentials. Inactive credentials should be excluded from this report.
Cause: The database view on which this report is
based (view_rpt_DoorAccessByUser ) does not exclude the inactive credentials. Add more
restricting criteria to prevent showing inactive credentials.
Solution: Install Update for Velocity 3.0 (KB80) which includes a script
to update view_rpt_DoorAccessByUser.
Applies To: DC4146
KB93 - PRB: Person Summary
reports do not show persons without credentials
Symptom: Run “Person Summary (with UDF
Cause: The database views on which the reports are
based (view_rpt_FAAUsersByUDF123 and
view_rpt_FAAUsersByUDF123withCodesAndCards) fail to include persons without
credentials.
Solution: Install Update for Velocity 3.0 (KB80) which includes a script
to update those views.
Applies To: DC4148
KB94 - PRB: Misspelling
February as “Febuary” in Scheduling Agent
Symptom: If a task is scheduled to run on a monthly
basis including February, the description says: Every xx day in January, Febuary.... “Febuary” should be
spelled as "February".
Cause: A typo in the ResourceStrings
table for resource id 1972.
Solution: Install Update for Velocity 3.0 (KB80) which includes a script
to update this record in the database.
Applies To: DC4150
KB95 - PRB: There is no
default auto-archive schedule in Velocity
Symptom: If users do not set up an archive schedule,
the log tables may keep growing to reach the 2GB or 4 GB limit and requires
major repair cost.
Cause: Insert an automatic archive schedule to run at
the 1st of each month at
Solution: Install Update for Velocity 3.0 (KB80) which includes a script
to insert this task.
KB97 - PRB: Application error
when closing Velocity while door group Edit Time Zone dialog is open.
Symptom: If users try to close Velocity while door
group and the Edit Time Zone dialog are open, they will get a runtime error.
Cause: In internal source code flag was not
being properly set that determines if the time zone window is open and should
prevent the shutdown of the Velocity client.
Solution: Install and register HirschDoorGroup.exe
version 3.0.0.32 dated
Applies To: DC4153
KB98 - PRB: Badge Print
Confirmation Dialog remains open after closing Enrollment Manager
Symptom: When printing a badge from EM, a print
confirmation form is displayed. If the Enrollment Manager or the Velocity
client is closed while the confirmation form will remain open. Trying to close
the orphaned form will then generate an application error.
In addition the confirmation dialog could lose focus and disappear behind
another window.
Cause: A defect in the software allowed the Print
Confirmation dialog to lose focus and allowed the Enrollment Manager and the
Velocity Client to close. The Print Confirmation dialog should be
dismissed before any other user input can be processed.
Solution: Install and register
HirschEnrollmentManagerV3.exe version 3.0.0.544 dated
Applies To: DC4151
KB99 - PRB: Changing a
credential’s IDF does not download credential to controllers
Symptom: If a credential is edited and only the IDF is
changed, no download will occur when the credential is saved and an event “No
download required” will be displayed in the Event Viewer.
Cause: A defect in the software failed to recognize
that changing the IDF requires a download.
Solution: Install and register
HirschEnrollmentManagerV3.exe version 3.0.0.544 dated
Applies To: DC4154