Valid for Sitecore 6.x
31.  Sitecore CMS 6.3.0 Update rev.100716 (6.3 Initial Release)
Prev Next

Instructions for downloading and installing Sitecore CMS 6.3.0 Initial Rel.(rev. 100716).

This is an old CMS 6.3.0 update.
You should only use this update as an interim update when upgrading from Sitecore CMS 6.2 to CMS 6.3.1 or later.

Important: If you are upgrading from Sitecore CMS 6.2.0, you should continue upgrading to version 6.3.1 or later and not stop the upgrade process at version 6.3.0.

Choose the appropriate link to download Sitecore CMS 6.3.0 Initial Rel.(rev. 100716):

You may also want to consider downloading additional tools:

To upgrade a previous Sitecore CMS 6 version to this release:

Prerequisites:

  • Sitecore CMS 6.2.0 rev. 091012.
    SQLite is no longer supported. If you are running on SQLite, you must upgrade your 6.2 databases to SQL Server Server or Oracle before upgrading to 6.3. This can be done using the Database Vendor Change Tool.
  • If your Sitecore solution is based on an earlier version, then you must update to Sitecore 6.2.0 rev. 091012 before you install this update.

This update requires the following files:

Important: Sitecore 6.3.0 rev. 100716 and 6.3.0 Update-1 (rev. 100830) do not include the fixes that are included in 6.2 Update-4 (rev. 100831). If you are upgrading from 6.2 Update-4 (or later), you should install this update only if the target version you are upgrading to is 6.3 Update-2 or later 6.3 versions.

Important: A number of 3rd party DLLs have been updated to newer versions in CMS 6.3 (ComponentArt.Web.UI.dll, Newtonsoft.Json.dll, and the Stimulsoft DLLs). You might have to update and recompile your code if you are referencing these DLLs from your code. Also, CMS 6.3 itself contains a small number of breaking API changes that could require you to change and recompile your code if you are using these specific parts of the API.

Important: If you are using Staging module for Sitecore CMS, it should be uninstalled when upgrading to Sitecore CMS 6.3. Refer to these instructions to uninstall the Staging module. Refer to this article for information about new features in Sitecore CMS that make the Staging module obsolete.

Important
: If the Configuring Production Environments document was applied to your multi-instance environment, it is recommended to revert the changes. Instead, updated instructions from the Scaling Guide document should be used.

Follow the steps below to upgrade an existing Sitecore CMS 6.2.0 rev.091012 or later installation to Sitecore CMS 6.3.0 rev. 100716 (also known as 6.3.0 Initial Rel.):

  1. Important: If you are upgrading from Sitecore CMS 6.2.0, you should continue upgrading to version 6.3.1 or later after installing this update. The system will not work as expected if you stop the upgrade process at version 6.3.0.
  2. Back up the site.
  3. If you are updating from 6.2.0 rev. 091012, update the web.config file with the changes between rev. 091012 and rev. 100104 before you continue.
  4. Open the Update Installation Wizard by entering the following URL in your browser: http://<hostname>/sitecore/admin/UpdateInstallationWizard.aspx
    See the Update Installation Wizard Guide for more information about how to use the Wizard.
  5. Install the Sitecore CMS 6.3.0 rev. 100716 update package using the Wizard. Some expected collisions may occur, see the Note about expected collisions below for details. 
    1. Upload the update package using the Wizard.
    2. Analyze the package.
    3. Install the package.
  6. Update your web.config document to the current version step-by-step:
    1. Web.config changes in CMS 6.2.0 rev. 100104 (if you did not already apply them before installing the CMS 6.3 update package).
    2. Web.config changes in CMS 6.2.0 rev. 100507
    3. Web.config changes in CMS 6.2.0 rev. 100701
    4. Web.config changes in CMS 6.3.0 rev. 100716
  7. Upgrade the database schema:
    • SQL Server: Execute the SitecoreCMS630.sql script on each of your Sitecore databases (core, master, web and any custom Sitecore databases, but excluding the Analytics database and any Sitecore module databases you have installed). This will update the database schema to Sitecore CMS 6.3.0.
    • Oracle: Please refer to the Oracle-specific instructions at the bottom of this page.
  8. The /bin/Interop.Shell32.dll file is no longer used by Sitecore. It is recommended to remove this file (unless any of your custom code depends on it).
  9. Clear your browser's cache. For instance, in Internet Explorer this is done via the menu Tools » Internet Options » Browsing History » Delete » Delete Temporary Internet Files.
  10. Rebuild search indexes and the link database in the master and the core databases. You can do this using the wizards available via the Sitecore desktop link Sitecore » Control Panel » Database.
  11. If you are updating from 6.2.0 rev. 091012: Check if any of the Sitecore log files contain warnings that one or more Sitecore performance counters do not exist (hint: search for "Using temporary internal counter") or that one or more Sitecore counters cannot be instantiated because the category is marked as single-instance (hint: search for "single-instance"). To resolve this problem:
    1. Download sitecorecounters.zip.
    2. Unzip the archive.
    3. Run the SitecoreCounters.exe program to re-register the Sitecore performance counters.
  12. Reiterate the update procedure for every Sitecore instance in your Sitecore environment.

Optional steps:

  1. It is recommended to install updated translations to the Sitecore client languages:
    • Translation updates are available on the CMS 6.3 Client Translations page.
    • Notice that the CMS 6.3 update package automatically updates the English, Danish and Japanese client languages with new and changed phrases, but it is a good idea to check if a more up-to-date translation is available.
  2. If you already had a Japanese language node in the 6.2 core database, you will now have two Japanese language nodes. It is recommended to delete the old one by following these steps:
    1. Set the "Languages.AutoRemoveItemData" setting in the web.config file to "false".
    2. Remove the old Japanese language item in the core database (the new one has ID: {F3AE1386-24EF-45F1-9389-755FDFA9C4C8}).
    3. Change the "Languages.AutoRemoveItemData" setting back to its previous value.
  3. It is recommended to delete following files, since SQLite is no longer supported:
    • /App_Config/ConnectionStringsSQLite.config
    • /web.config.SQLite

Note about expected collisions:

If you are upgrading from a release later than Sitecore CMS 6.2.0 rev. 091012, you will see warnings that a number of files have been modified and will be overwritten. This is expected behavior for the following files (you might only see some of the warnings, depending on which release you are upgrading from).

Files:

  • \bin\Sitecore.Analytics.dll
  • \bin\Sitecore.Client.dll
  • \bin\Sitecore.Client.XML
  • \bin\Sitecore.Kernel.dll
  • \bin\Sitecore.Kernel.xml
  • \bin\Sitecore.Logging.dll
  • \bin\sitecore.nexus.dll
  • \bin\Sitecore.NVelocity.dll
  • \bin\Sitecore.Oracle.dll
  • \bin\Sitecore.SQLite.dll
  • \bin\Sitecore.Update.dll
  • \bin\Sitecore.Zip.dll
  • \sitecore\shell\Applications\Globalization\SitecoreClientTranslation\SitecoreClientTranslation.aspx
  • \sitecore\shell\Controls\Rich Text Editor\Preview.aspx
  • \sitecore\shell\Controls\Rich Text Editor\RichText Commands.js
  • \sitecore\shell\Schemas\sitecore.xsd
  • \sitecore\shell\sitecore.version.xml

Items:

  • /sitecore/templates/System/Validation/Validation Rule/Data/Text

Instructions for upgrading the database schema of Oracle databases

You will need the following files:

The zip files contains two files:

  • UpgradeScriptOracleCMS630.sql – an SQL*Plus script to upgrade the Sitecore database schema to 6.3.0
  • UpgradeCMS630.bat – a Windows batch file that invokes UpgradeScriptOracleCMS630.sql for the following Sitecore schemas: core, master, and web

Upgrade steps:

  1. Extract the SQL script and the batch file from the zip archive.
  2. Copy the SQL script and the batch file to the Database Server (or to the PC where the administration tools for the Oracle database are installed and set up).
  3. By default, the upgrade scripts will process three user schemas: sccore, scmaster, and scweb (the actual names depend on the value of the PREFIX environment variable).
    • If your user schema names are different or if you have additional Sitecore user schemas, modify the batch file as necessary (but do not add the Analytics schema – it uses a different database schema and should not be upgraded).
  4. Shut down Sitecore.
  5. Back up your Sitecore schemas.
  6. Upgrade your database schema.
    • In System Properties/Advanced/Environment Variables set up user-level variables as follows:
      • DATABASE = The name of the database instance that hosts the Sitecore data.
      • PASSWORD = Password for the system user of the Oracle instance.
      • PREFIX = Prefix for the Sitecore user schemas and their passwords (default value: 'sc').
        • Notice that user passwords are expected to be the same as the user names.
        • Launch UpgradeCMS630.bat.
        • Review the output of the script for errors.
        • Remove the DATABASE, PASSWORD and PREFIX variables from the environment.
  7. Start Sitecore.
  8. Continue with the CMS 6.2 to 6.3 upgrade procedure as described above.

Prev Next