Update for Velocity 3.0 (KB197) Release Notes

 

Update for Velocity 3.0 (KB197) Released 09/10/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.

KB196 - PRB: Ports are erased from the system

Symptom:  After adding a Port, at some time in the future, it disappears from the Administration Window or the user encounters errors in Door Groups.

The following unexpected application error occurred
Function Name: LoadControllers
FunctionSubItem: 47
Number: 35601
Description: Element not found

Cause:  The Port component expects to be told what type of port it is when used in the product.  Initially this is for the purpose of telling the Port component if it is SNET or XNET.  Subsequent use of the Port component outside the Administration Window does not provide this information and when the OK button is clicked, two columns in the database are erased.  This results in the Port and all Xbox’s and/or controllers from appearing in both the Administration Windows and Door Groups.

 

Solution:  Copy into the Velocity folder the file HirschPort.dll version 3.0.x and register it.  If the problem has already been encountered, technical assistance will be required to repair the database.

             Applies To: DC 4261

 

KB198 - PRB: Importing Person/Credential data from an outside source fails on dialup systems

Symptom: When importing Person/Credential data from multiple files using the Velocity Data Import Wizard, they fail to download to the dialup panels. The user may also notice the downloads are hung up in the Download Monitor.

 

Cause: When the Import Wizard completes, it notifies the DIGI*TRAC Network Service that download should begin. It in turn schedules a dialup session. When concurrent files are imported, the second or possibly third import causes a state machine problem in the service. It thinks a session in already in progress after the first import completes and does not need to dial up the remote controller, therefore attempts to start downloading immediately. This causes the lower level polling driver to freeze up with download commands for invalid addresses and subsequent downloads fail.

 

Solution: Install Update for Velocity 3.0 (KB197) which contains DTServer.exe version 3.0.0.134 or newer. This updated service will resolve the issue by removing redundant dialup schedules for the same location and wait for the last import to complete before dialing the remote controller.

 

Applies To: DC 4243

KB199 - PRB: Unable to configure Photo Call-Up for each client workstation

Symptom:  Photo Call-Up will appear on all workstations regardless of what workstation the photo call-up was meant to be shown.

 

Cause:  Initially, photo call-up in 3.0 was meant to use routing to determine what workstations it would be shown.  However, because of the performance hit routing incurs, it was decided to revert photo call-up to the 2.6 method so the user would not have to use routing if this was the only feature needed.

 

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

 

Applies To:  DC 4265

KB200 - PRB: Enrollment Manager Search all Groups for a specific ID number fails

Function Name: QuerySupport.PerformSearch
FunctionSubItem: 11
Number: -2147217900
Description:  Cannot find either column "dbo" or the user-defined function or aggregate "dbo.fn_kek_IntConvert", or the name is ambiguous

Cause:  The SQL function kek_fn_InConvert is missing from the V3.0 schema

 

Solution:  To resolve this issue, apply Update for Velocity 3.0 (KB197) that includes the missing SQL function which will be automatically installed on each client machine once applied to the Velocity Security Domain.

 

Applies To: DC 4271

KB201 - PRB: Selecting UDF Field Summary generates an error in Enrollment Manager

Symptom:  In the Enrollment Manager under some circumstances if UDF Field Summary is selected and then the user clicks on "Search Results" in the person tree the following error message will appear:

The following unexpected application error occurred...
Function Name:  EMQuery.GetQueryPartsEX
FunctionSubItem:22
Number: 5
Description:  Invalid procedure call or argument

Cause:  Due to an internal error there are some instances where the query parsing engine fails.

 

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

 

Applies To: DC 4277

KB202 - PRB: Enrollment Manager Date Search produces incorrect queries

Symptom:  When searching on UDF fields designated as dates, the Search function treating the dates as strings instead of dates.  Therefore, “11/3/2006” comes before “2/3/2006” which is incorrect.

 

Cause:  Internally all UDF data is stored as character strings and all queries are performed as such.

 

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

This update modifies the query engine to treat UDF defined to be dates or numbers as such.  However, if existing data in the database is not compatible with the specified UDF format then an query error can occur.

 

Therefore, whenever a UDF type is changed all existing date in the database is scanned for compatibility with the currently specified UDF types.  Data not compatible with the specified UDF types will be displayed.  The operator may then manually go back and correct the malformed data by editing individual person records or may have the system automatically clear all malformed data.

IMPORTANT:  To avoid query errors, after applying this update the operator should open the User Defined Setup Dialog in the Enrollment Manager to check for any existing data that is not compatible with the current UDF types.

 

Applies To: DC 4276

KB203 - Role Modification to Enrollment Manager and Function Groups

Symptom:  A Role is able to view Credential or Function Group data even though that particular Role does not have permission to see the data.

 

For example, if Role1 has permission to Badge 1 and Door Group 1, and Role 2 does not.  Then an operator logged in as Role 2 should not be able to select Badge 1 or Door Group 1 when defining a credential.  This also applies to Function Groups when defining access or control functions.

 

Cause:  Velocity v3.0 did not apply Role permission checking to Badge Templates, Door Groups or Controllers when defining Credentials and Function Groups.

 

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

This update adds Role checking to Credentials and Functions Groups.  Therefore, an operator will now only be able to select those data objects that they were granted permission for.

 

Likewise, if a Credential or Function Group is edited by an operator whose role does not have permission for data objects that have already been defined for a Credential or Function Group, then they will not be able to delete these objects (I.e., an access function that has a door group that the current operator does not have permission for).

Status:This behavior is by design

Applies To: DC 4263

KB204 - PRB: Topaz Signature Pad Model # T-L462-HSB fails to connect

Symptom:  Velocity v3.0 fails to connect to newer Topaz Signature Pad Model # T-L462-HSB.

 

Cause:  The newer model Topaz Signature Pad Model # T-L462-HSB is incompatible with the SigPlus Control Module (SigPlus.ocx) distributed in Role Modification to Enrollment Manager and Function Groups in Velocity.

 

Solution: Install and register SigPlus.ocx, version 3.74.0.0. This file is available in Update for Velocity 3.0 (KB197) and will be automatically installed on each client machine once applied to the Velocity Security Domain.

 

Applies To:  DC 4256

KB206 - PRB: Software Errors, after enabling Customization Manager on Windows XP with Chinese Regional Settings

Symptom:   After installing Velocity 3.0, setup Windows XP with Chinese Regional Language settings.  Select Chinese PRC for languages and all other settings that is possible. Open Console->Preferences and check “'Access and Enable Customized Values for Components in Customization Manager”, shut down Velocity and open Velocity again, if Event viewer is not open by default, open either Event Viewer, Alarm Viewer or Status viewer causes a series of errors which eventually requires an “End Task”.

 

Cause:  This is caused by the failure to set the font property of the new Grid control (HirschGrid2.ocx) used by Event Viewer, Alarm Viewer and Status Viewer to a double byte font.

 

Solution:  Fixed by changing the SetFont procedure of HirschGrid2 control.  To resolve this issue, apply Update for Velocity 3.0 (KB197) which includes HirschGrid2.ocx, HirschAlarmViewer.dll, HirschEventViewer.dll and HirschStatusViewer.dll.

 

Applies To:  DC 4235

KB207 - PRB: Velocity Data Export Crashes Velocity

Symptom:  Selecting IDF in the criteria selection screen and click “equal to” in the Function combo box causes Data Export Wizard to generate a series of errors which eventually requires an “End Task”.

 

Cause:  For performance purpose, we limit the criteria selection to only include UDF 1-14, which causes confusion in the internal backtracking to the actual database field.

 

Solution:  Replace and register HirschDataExport.dll (3.0.0.27).  This file is available in Update for Velocity 3.0 (KB197) and will be automatically installed on each client machine once applied to the Velocity Security Domain.

 

Applies To:  DC 4269

KB208 - PRB: If you have a controller with all doors unbundled you will get an error when trying to add a new standard door group or edit an existing one

Symptom:  Unbundle all the doors for one controller and try to edit or create a standard door group will get an error.

 

Cause:  This is caused by the line of code that tries to close the recordset again after it is already closed.

 

Solution:  Fixed by adding a conditional statement to see if the recordset has already been closed before closing it.  Install Update for Velocity 3.0 (KB197) with HirschDoorGroup.exe (3.0.0.41) dated 7/25/2007, 14:46:58.

 

Applies To:  DC 4273

KB209 - PRB: Expansion inputs 1 - 16 were not being displayed in Roles for an M16 Controller

Symptom:  Open roles and look at the expansion inputs for a controller type M16. The Expansion Inputs 1 through 16 would not show, but 17 through 32 would.  This would cause the role permissions to be unsettable for these points.

 

Cause:  The logic in the code was reveresed for the expansion points associated with an M16 controller.

 

Solution:  Install VelocityRole.dll v3.0.0.96 or later and database scripts.  These files are available in Update for Velocity 3.0 (KB197).

 

Applies To:  DC 4242

KB210 - PRB: First 16 Xinputs for M16 not visible for Non Administration Window