Velocity 3.1 R2 Release Notes

 

Velocity 3.1 (Build 3.1.17) R2

Velocity 3.1 R2, released 09/24/2010

This DVD contains Velocity 3.1 R2 for NEW installations (Part number: VEL).  If Velocity 2.6 SP2 or 3.0 is already installed, this DVD will upgrade it to Velocity 3.1 R2.  If you are currently running a Velocity system older than 2.6 SP2 you must contact your local Hirsch Dealer or Hirsch Sales representative to purchase the appropriate update CD’s.

To order a CD Set for an existing Velocity customer running an older version (1.0.9.60, 2.5.0.28, 2.5.0.35, 2.5.0.37, 2.6.0.15) who wants to update to Velocity 2.6 Service Pack 2 you will need to use part number (s) VEL-UPD25 and VEL-UPD26 and VEL-UPD26sp1 and VEL-UPDsp2.  Please contact your dealer or Hirsch Electronics representative for the part numbers for your specific needs.  Alternately, customers may order pat number VEL-UPDSUITE if they are running any version 2.0 or older.   It contains all upgrades from 2.0 to 3.1 R2.

  Note: September 2010

This installation DVD supports:

  • 32/64-Bit Windows Vista SP1, 32/64-Bit Windows XP with SP3 and 32/64-Bit Windows Server 2003 with Service Pack 2 Standard and Enterprise Edition, Windows Server 2008 R2 Standard Edition.
  • 32/64-Bit Microsoft SQL Server 2005 with Service Pack 2 Standard and Enterprise Edition, Microsoft SQL Server 2008 with Service Pack 1
  • Microsoft SQL Express 2005 Service Pack 2 edition.  It does not apply Service Pack 2 to existing systems if SQL Server 2005 is pre-installed.  Microsoft SQL Express 2008 is NOT supported in this version.

Installation Prerequisites:

Product Packaging for Hirsch Electronics part number VEL

Velocity 3.1 R2 Operating System and Service Pack Requirements

  • Windows 2000 Pro and Windows 2000 Server are no longer supported.  If you are running Windows 2000 Pro for either Single Workstation Edition or Windows 2000 Server for Server Edition, migration to Windows XP or Windows 2003 Server is required.

  • Windows Server 2003 with Service Pack 2 or Windows Server 2003 R2 for Velocity Server Edition installations.

  • Windows Server 2008 R2 Standard Edition and Microsoft SQL Server 2008 Standard with SP1 installations.

  • Windows XP Professional with Service Pack 3 or Windows Vista SP1 for Velocity Client or Workstation Edition installations.

Velocity 3.1 R2 Database Platform

The following are the supported Operating System and Database Configurations for Velocity 3.1 R2 Standalone Workstations and Servers only:

Velocity Configuration

SQL Server 2005 Express

SQL Server 2005

SQL Server 2008 Express

SQL Server 2008 SP1

Single-User System running Windows XP Professional SP3 or Windows Vista SP1

ž
Included

Optional

 

Not Supported

 

Not Supported

Windows Server 2003 SP1 & SP2 (including R2)

ž
Included (previously not supported using MSDE 1.0)

Optional

 

Not Supported

Not Supported

Windows Server 2008 R2 Standard Edition

 

 

Not Supported

 

Not Supported

 

 

Not Supported

ž
Not Included

  • Velocity 3.1 R2 supports Microsoft SQL Server 2008 SP1 on Windows Server 2008 R2 Standard Edition and Microsoft SQL Server 2005 on Windows Server 2003.  

  • Microsoft SQL Server 2008 Express Edition is currently NOT supported with the Velocity 3.1 R2 release.

  • Microsoft SQL Server 2005 Express SP2 Edition is installed when other versions are not detected on Windows Server 2003, Windows XP and Vista.

  • If you already have SQL Server 7.0 or SQL Server 2000 (non MSDE engine) installed, you must upgrade to or install SQL 2005 before running the installation of Velocity 3.1 R2.  The installer cannot upgrade a non MSDE engine to SQL Server 2005 Express Edition.

  • Velocity 3.1 R2 supports and uses “Named Instances”.  This allows Velocity to have an independent database engine separate from another application that may coexist on the same machine.

  • If SQL Server 2005 or Express is pre-installed, you may choose to create a named instance for Velocity to use and select it during the install process or you may elect to use the default instance if you do not want a named instance.

  • Installations of SQL Server 2005 Express Edition performed by the Velocity installer will enable server side "Forced Encryption" for protection between the server and clients.  It will only do this with a HIRSCH named instance of SQL Server 2005 Express.

Velocity 3.1 R2 CCM Firmware Requirements

The Velocity 3.1 R2 release requires that you be running DIGI*TRAC CCM Firmware 7.4.31 or higher.  At the time this version was packaged the current shipping CCM version is 7.4.31.  Failure to perform this update will result in unpredictable product behavior.  The most recent firmware can be found in the \Velocity\Firmware\DIGI-TRAC directory on this Velocity 3.1 R2 DVD.

IMPORTANT CCM 7.3.0 or HIGHER FLASH UPDATE INFORMATION

Before you can flash your current 7.2.x version CCM to 7.3.0 or higher you must first check the BIOS level of the CCM.  In order for the 7.3.0 flash update to work properly you must be running a CCM with a BIOS level of 7.1.20 or higher.  If you are running a BIOS Level less than 7.1.20 you will need to replace your CCM (DO NOT ATTEMPT TO FLASH IT THROUGH VELOCITY). The current shipping CCM BIOS Level at the time of this release is 7.3.17. To determine the BIOS level of a CCM you will need to use the Velocity Diagnostic Window found under the Help Menu.

How to determine your CCM BIOS Level

1. Go to the Help menu on the tool bar and click on the Diagnostic Window option. 

2. From within the Diagnostic Window use the Controller list box and select the appropriate controller.  Now go over to the Diagnostic Command list box and select option 1 - Date, Time, Version Number and click the button next to this list box.  The controller will display system information in the bottom pane of this window.  Please look for the following information below and determine the BIOS level of your CCM.  In this example we were running CCM BIOS 7.2.19.  The Firmware version number may be very different than the BIOS number.  Please remember to only determine the BIOS Level.

1:24:40 PM 001:001:001 SNET Message 139 Device Info Device Type 3 M2
1:24:40 PM . ROM Sig. ffffffffffffffffx BIOS=7.2.19 Firmware Date=20041027 Vn. 7.3.01

3. If you are running BIOS Level 7.1.20 or higher you can use Velocity to flash your CCM to 7.3.0 or higher.

Velocity 3.1 R2 SNIB2 Firmware Requirements

1. Velocity 3.1 R2 requires that you be running SNIB2 Firmware 5.98 or higher.  At the time this version was packaged the current shipping SNIB2 Firmware version is 5.98.

IMPORTANT SNIB2 INFORMATION

If you plan on deploying the SNIB2 high-security communication board you must update your controllers with DIGI*TRAC Firmware 7.3.0 or higher prior to installation of this board in your controller.  Please refer to the DIGI*TRAC section on in the Velocity Browser's Velocity Learning Center and review the Configuration Guide prior to updating your controllers with the SNIB2.

Velocity 3.1 R2 XBox Firmware Requirements

1. Velocity 3.1 R2 requires that you be running XBOX Firmware 2.45/3.15 or higher.  At the time this version was packaged the currently shipping XBox Firmware version is 3.15.

Installation Notes

CCM Firmware must be 7.4.31 or higher
SNIB2 Firmware must be 5.98 or higher
XBOX Firmware must be at 2.45/3.15 or higher

  Note:

When upgrading from Velocity 2.6 SP2 or 3.0, these upgrades should be performed before starting the upgrade process.

The password does not meet the password policy requirements.  Check the minimum password length, password complexity and password history requirements.

Upgrading Velocity 2.6 Service Pack 2 System to Velocity 3.1 R2

This DVD only updates Velocity 2.6 SP2 or 3.0 to Velocity 3.1 R2

 

Important Notes:  Before updating Velocity, you must be logged into the Server with an "account" that has Administrator rights.  If you attempt to install without such rights, the Installer will not continue.

 

You must upgrade the Server machine first.  You will upgrade the client machine after the server completes its upgrade.  Both server and client machines must be upgraded in order to use this version. 

 

The Server upgrade could take from 20-45 minutes or more depending on the size of your database.  Please do this upgrade off hours, and understand client users will not be able to connect during the upgrade process.

 

For more detail Information regarding Upgrade, refer to Velocity Quick Install Guide.

  Note:

Velocity 3.1 R2 is NOT backwardly compatible and does NOT work with older SQL Server editions:  neither SQL Server 7.0 nor SQL 2000 Server.  The previous version of run-time SQL Server, MSDE is no longer supported.

Update Steps:

  • Backup your Velocity 2.6 SP2 database using the Velocity SQL Manager or Microsoft Enterprise Manager if running SQL Server 7 or 2000.

  • Verify that all Controllers are running CCM Firmware 7.4.31 or higher.

  • Verify that all SNIB2’s are running Firmware 5.98 or higher.

  • Verify that all XBoxes are running Firmware 2.45/3.15 or higher.

  • Stop all Velocity services using the Velocity Service Control Manager found on your system tray.

  • Exit the Velocity Service Control Manager.

  • Do not stop the SQL services using the MS SQL Server Service Manager found on your system tray.  The Velocity Update program needs this service running for the update process to complete successfully.

  • Start the upgrade on the server by inserting the Velocity 3.1 R2 DVD in the CD/DVD drive and select the Upgrade to Velocity 3.1 R2 option from the installation wizard.

  • Run the upgrade on all client computers currently running Velocity 2.6 Service Pack 2 or 3.0 software.

What's New

The following are new features in Velocity 3.1 R2

Installation

  • Combine Software & Tutorial CD's into a single install on DVD

  • Support for Windows Server 2008 R2 Standard Edition

  • Support for Microsoft SQL Server 2008 SP1

Installation Notes

  • Fresh installations of 3.1 R2 will be described on the “Help About” tab as 3.1.17 R2.  Older versions of Velocity upgraded to (KB542) will be described as 3.1.17.  This will also be true of systems upgraded then migrated to a Windows 2008 Server platform.  There is no functional difference between the two.  The R2 only designates a system that was installed as 3.1 R2 initially.

What's Fixed

 

The following are problems and defects fixed in Velocity 3.1 R2

 

VEL-202 - PRB:  Scheduled e-mails may stop functioning after a few days

Symptom:  E-mails scheduled to be sent out of Velocity via the Scheduling Agent may fail to send after a few days and requires the Velocity Services to be restarted to regain functionality.

Cause:  Due to an internal software defect, the old .NET components sometimes will not startup and will receive an Invalid Procedure Call.

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

VEL-221 - PRB:  Selecting the Database option during the Velocity installer may cause the install wizard to disappear on a x64Bit Split Server Configuration

Symptom:  During installation of Velocity on a x64Bit Split Server configuration when you select the "Database Only" option, the installation wizard disappears.

Cause:  This behavior is caused by an internal software defect, the code that checks the instance from a x64Bit system was failing.

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

VEL-422 - PRB:  Every time you try to run the setup.exe to install Velocity, nothing happens.

Symptom:  On some systems, nothing appears to happen every time you try to run the setup.exe to install Velocity.


Cause:  Can Not Reproduce (CNR). The root cause of this issue is unknown at this time.

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

VEL-458 - PRB: Export Restriction in paragraph 7 of the EULA requires changes.

Symptom:  Export Restriction in paragraph 7 of the EULA requires changes in order to avoid conflict.

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

Known Issues

The following are known issues in Velocity 3.1 R2 release that will be addressed in later release:

VEL-197 - PRB:  Missing SCM icon when logged in as a "User" with rights to use Service Control Manager

Symptom:  Service Control Manager icon does not appear in the "Task Tray" when logged in as a User on a Velocity Client machine. In addition, the User may not have rights to launch SCM from the Menu.

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.

VEL-488 - PRB:  Unable to open SQL Server Manager from a Velocity Client and on a Split Server Configuration

Symptom:  After installing Velocity 3.1 R2 into a Velocity Client or on a Split Server Configuration, you are unable to open or access SQL
Server Manager.


Cause:  SQL Server 2008 Express Edition is NOT supported in this release version.

Solution:  None at this time.

Workaround:  None at this time.

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

VEL-604 - PRB:  On a Virtual Environment, the upgrade from 2.6SP2 to 3.1R2 may stop responding.

Symptom:  On a Virtual Environment, the Velocity 2.6SP2 to 3.1 R2 upgrade may not continue to install SQL 2005 Express and may stop
responding.

Cause:  The specific cause is unknown at this time.

Solution:  None at this time.

Workaround:  At this point the workaround for this issue is to install Windows Installer 4.5 before your Upgrade to Velocity 3.1 R2.

Status:  This is a known issue that will be addressed in a future release and is resolved by following the above steps.

VEL-608 - PRB:  An error may occur when accessing Archives created from a Windows Server 2003 system

Symptom:  An error may occur when accessing Archives created from a Windows Server 2003 system and then restored into a Split Server 2008 Configuration.

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

Solution:  None at this time.

Workaround:  At this point the workaround for this issue is to delete the .ldf files after moving the Archives into the new system
or you may also rename the .ldf files.

Status:  This is a known issue that will be addressed in a future release and is resolved by following the above steps.

 

Last modified:  September 24, 2010 08:43:45

Copyright © 2010  Hirsch Electronics, LLC.  All rights reserved.