Patch Reverting Process (version 13.0)

When applying a patch to your site, providing that you take the steps below, it is possible to revert a patch.

 Why you may wish to revert the patch?

  • Issues with applying patch
  • Noticed changes in behavior
  • You do not have a test site to try the patch out first before applying it to your production
  • You do not have a Virtual server that had a previous snapshot prior to the patch being applied

Taking backups

It is only possible to revert a patch if you have taken the proper precautions.

Step 1) Backup the SQL Database – this stores all of your content and site settings. Click here for the process to backup your SQL Database using SQL Server Management Studio.

Step 2) Backup the Intranet folder – on your web server that hosts the intranet, you will have an Intranet folder that contains all of the code files, as well as any files that have been uploaded to your intranet.

  • Open IIS (Internet Information Services Manager)
  • Select your web site from the list on the left
  • Click ‘Basic Settings’ from the right nav
  • Locate the physical path as shown in the image below:

Now that you have the location, navigate to the folder level above your Intranet folder.

  • Backup the entire Intranet folder

Note: Both of these backups should be of the same version of the software as restoring 2 different versions can lead to data discrepancies, or issues with restoring your site.


Reverting the patch

  1. Restore your SQL Database from the backup
  2. Right-click on the database within SQL Server Management Studios > select New Query
  3. Paste the following query into the box provided:
    • exec sp_change_users_login 'auto_fix','intranetconnections';
  4. Stop the Railo Server service and the IIS Server
  5. Rename the Intranet folder
  6. Restore the backup copy of the Intranet folder (in the example above, you would restore this to the wwwroot folder).
  7. Start the Railo Server service and IIS server
  8. Re-launch your intranet
Have more questions? Submit a request


Article is closed for comments.