Upgrading FocusOPEN 3.4.6.x to 3.4.7


The upgrade from FocusOPEN 3.4.6.x to 3.4.7 should be tested first on a development server (and having made full backups).Windows system administration and SQL Server knowledge are required.

Note 1: This upgrade procedure is for 3.4.6.x users only, do not attempt a direct upgrade from an older version to 3.4.7.

To check your current version, enable engineer user mode for your account and view the utilities/settings page in the admin area. The FocusOPEN version will be at the bottom of the page.

Backups & Preparation

A backup of the whole FocusOPEN application folder is recommended with at least the webroot folder being the minimum. It is especially important you make a copy of your configuration settings and original database.


Open the upgrade.cmd batch file and check the connection parameters to your FocusOPEN database and then run the upgrade.cmd script. You need to change three different areas:


Swap (LOCAL) for the instance of your local SQL Server.

echo osql -n -E -d FocusOPEN -S %FocusOPENDB_SQLSERVER% -i "347_updates.sql"
osql -n -E -d FocusOPEN -S %FocusOPENDB_SQLSERVER% -i "347_updates.sql"

Swap 'FocusOPEN' for the name of the FocusOPEN database.

If you installed FocusOPEN previously without changing the database name you may only need to change the database connection instance (at the top of the script).

Using SSMS To Upgrade The Database

Alternatively, you can use SQL Server Management Studio to execute the “347_updates.sql” updater script in the the DatabaseSetup\UpgradeScripts folder of the deployment package.

Upgrade Application Webroot and Change Config Settings

  1. Make a backup copy of your App_Data folder
  2. Make a backup copy of your AuthPlugins folder
  3. Make a backup copy of your Config folder
  4. Make a backup of your web.config file
  5. Make a backup copy of your Brands folder
  6. Copy the webroot folder from the 3.4.7 deployment package over the top of your existing webroot to replace and update your files.
  7. Delete the App_Data and Brands folders
  8. Move the Config, AuthPlugins and web.config folders/files over to a location away from the Webroot - you will need these later
  9. Copy your Config folder back to to the webroot to replace the one from the deployment package.
  10. Copy your Brands folder back to to the webroot to replace the one from the deployment package.
  11. Copy your App_Data folder back to to the webroot to replace the one from the deployment package.
  12. Copy your AuthPlugins folder back to to the webroot to replace the one from the deployment package.
  13. Copy your web.config file back and make the changes described below.

Use a comparison application such as Beyond Compare or WinMerge to identify the sections of the config files to be amended.


Add the following keys if not already present

<add key="EnableMetadataObjects" value="false"/>
<add key="MaximumAssetFormSearchObjectsToDisplay" value="0"/>
<add key="DisableAddingOfNewMetadataObjects" value="false"/>
<add key="DisableEditingOfMetadataObjects" value="false"/>
<add key="HideGroupMetadataDropDownViewSelector" value="false"/>
<add key="MaximumImportAutoGenerateMetadataThreshold" value="4"/>
<add key="ImportCarriageReturnCharacter" value=""/>
<add key="ImportParserHasFieldsEnclosedInQuotes" value="false"/>
<add key="VerboseImportLogging" value="false"/>
<add key="AutoSwapUnderscoresForSpacesInTitle" value="true"/>
<add key="UseAPSForImageTransformations" value="true"/>
<add key="UseAdvancedMetadataManager" value="true"/>
<add key="SkipRecordsWithInconsistentNumOfFields" value="false"/>
<add key="AppUnavailableIPAddressExclusionList" value=",::1"/>
<add key="DoNotProcessUploadsOrImports" value="false"/>
<add key="CopyFailedImportsToFailedFolder" value="false"/>
<add key="EnableRoleIDToDownloadUnpublishedAssetsAssetsOutsidePrimaryGroup=" value=""/>
<add key="EnforceNativeBlankPasswords" value="false"/>
<add key="DefaultShortDescription" value="No description available"/>
<add key="AllowDuplicateAssetsAcrossBrands" value="false"/>

Add the following to the Callbacks area of the httpHandlers section

<add verb="*" path="CustomRequestCallback.ashx" type="FocusOPEN.Website.Components.Handlers.CustomRequestCallbackHandler, FocusOPEN.Website" validate="false" />

Add this config key to the httpModules section

<add name="IPRestrictedAppOfflineModule" type="FocusOPEN.Website.Components.IPRestrictedAppOfflineModule, FocusOPEN.Website" />


The AdminNavigation.config file hass been updated with new features to allow the batch modification of users and some other adjustments. Unless you have changed this on an existing installation, you can usually copy the files wholesale from the deployment package over the top.

Bitmap Groups

The bitmap groups feature is intended to be used by those implementing custom preview plug-ins. The previous settings on 3.4.6 and earlier can be modified as follows to reduce the load on the APS:


Finishing Up and Testing

Once you have completed the upgrade procedure, you are recommended to restart IIS and ensure basic functions still work like logging in, uploading and cataloguing.

If you have difficulties with the upgrade, try a fresh deployment of 3.4.7.

upgrading-focusopen-3.4.6.x-to-3.4.7/start.txt · Last modified: 2015/05/20 10:30 by admin