Update for Velocity 3.1 (KB554.1) Release Notes

 

Update for Velocity 3.1 (KB554.1) Released 01/05/2011 contains file changes to address the following knowledge base articles:

 

Download and install the update by executing the EXE file on the Velocity Server which will launch the update wizard. Once the update completes, as each client re-connects to the Velocity Server, updates will automatically be applied. You do not need take the update to each Velocity client and run it.

IMPORTANT:  If ANY of the Velocity Services or Processes fails to "STOP" automatically while applying the updates, use the "Task Manager" and select the "Processes" tab to manually end the process.   NOTE:  Applying (KB554.1) may take much longer than normal depending on the size of the database.  Please wait for the process to complete and DO NOT "End Task" while the Update is being applied.

 

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 be logged in as Administrator or be a member of Domain Admin. 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.

IMPORTANT:  Update for Velocity 3.1 (KB542) contains fixes for compatibility issues with Windows Server 2008 and SQL Server 2008.   You MUST first apply Update for Velocity 3.1 (KB542) before migrating from Windows Server 2003, Windows XP or Vista to Windows Server 2008.   NOTE:  Update for Velocity 3.1 (KB554) includes compatibility with Windows 7 (Velocity Client ONLY).   This version currently DOES NOT support Single-User Workstation installation for Windows 7.   NOTE:  SQL Server 2008 Express is NOT currently supported.  Full version of SQL Server 2008 must first be installed prior to migrating to Windows Server 2008.  This is a known issue that will be addressed in a future release.

Issue Fixed:

VEL-814 - PRB:  Inputs reporting incorrect names

Symptom:

When an alarm is generated, the alarm may show the incorrect input name or description in the "Event Viewer" as well as in the "Alarm Viewer"

Cause:

Due to an internal software defect, the Event Description Strings causes the point names to report incorrect

Solution:

Modified the Event Description Strings (point names in particular).  To resolve this issue, install SDServer.exe version 3.1.554.54 or later.  This file is available in Update for Velocity 3.1 (KB554.1).

Known Issues:

VEL-629 - TT-607 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, an error message similar to the following appears on 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

VEL-787 - PRB:  Unable to open SQL Manager from Velocity Client

Symptom:  Unable to open the SQL Manager from the Client machine. When you click the SQL Manager icon from a Velocity Client machine, nothing happens.

Cause:  This is a pre-existing defect. The specific cause is unknown at this time.

Solution:  None at this time.

Workaround:  None at this time.

Status:  This is a known issue that will be addressed in a future release.

NOTE:  After you apply the Velocity 3.1 Update, verify that the update successfully installed.  In Velocity, go to Help and select About Velocity and click the scroll bar to verify the current version number of the Update