Update for Velocity 3.0 (KB185) Release Notes
	January 31, 2007

 

Update for Velocity 3.0 (KB185) Released 07/16/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.

 

KB185 - PRB: Following an upgrade to Velocity 3.0, archived databases may not attach to the SQL Server when running reports on legacy data

Symptom:  While attempting to run a report that requires archived data a message dialog similar to the following may appear:

Error: attachingVelocityArchives6212007100002AM

Do you wish to continue without archived data?

And looking at ArchiveLogServer.log has an error similar to the following:

"6/21/2007 3:43:41 PM: AttachArchiveDatabase.8 : ERROR(-2147217900): Unable to open the physical file ""c:\PROGRA~1\MICROS~2\MSSQL.1\MSSQL\Data\VelocityArchive6212007100002AM.mdf"". Operating system error 5: ""5(Access is denied.)"".

Cause:  During the upgrade process from Velocity 2.6 SP2 to Velocity 3.0, archived database files that are automatically migrated from the previous version of SQL Server to the new SQL 2005 \Data directory.  The archived database(s) mdf and LDF files do not have sufficient file permission to allow the Velocity Archive Log Server component to attach the archive database.
 
Solution:  Manually edit the Security file Properties for the archived data base files (*.mdf, *.ldf) and add the "VelocityServices" Windows account with Full permission to the files or apply Update for Velocity 3.0 (KB185).  This update will detect the location of the archive database files and apply the appropriate NTFS permissions to allow them to be attached.

NOTE:  This process must be ran ONLY once after performing an upgrade from Velocity 2.6 SP2 to Velocity 3.0.  It is highly recommended to create a backup of your original data prior to upgrading or applying any updates for recovery purposes.

Applies To:  DC 4237