Esko Logo Back to Esko Support
Choose your language for a machine translation:
Skip to end of metadata
Go to start of metadata



Description

Microsoft SQL Server versions 2005, 2008 and 2008R2 are no longer supported in Automation Engine 18.0. Automation Engine has moved to SQL Server 2017 Express for its onboard SQL Server. This upgrade also required an update of the Microsoft SQL driver, and that driver no longer supports SQL Server 2008R2 (and older).

Warning


For local database servers (i.e. SQL Server and Automation Engine are on the same computer), the installer will detect an unsupported database and block the upgrade from continuing.

In case of a remote database server (SQL Server and Automation Engine are on a different computer), the installer is not able to detect an unsupported database, which may leave your system unsupported and broken (some components are known to be broken).


Overview

These unsupported databases are still quite common, because we shipped 2008R2 until version 14.0.1 (released in October 2014).

  • Automation Engine 12.0.0, 12.0.1 and 12.1.0 were shipped with Microsoft SQL Server 2005 Express.
  • Automation Engine 12.1.1, 12.2 and 14.0.x were shipped with Microsoft SQL Server 2008R2 Express.
  • Automation Engine 14.1.x, 16.0.x and 16.1.x were shipped with Microsoft SQL Server 2014 Express.

Note that this limitation also applies to so-called 'External Databases' (Tools, Configure, External Database) where the DBMS type is "Microsoft SQL Server". For these external databases, a workaround to still use an older version of SQL Server is described in KB194843345.

Procedure

Follow the steps given below to upgrade to Automation Engine 18.0:

  1. Check if the version of Microsoft SQL server is still compatible with Automation Engine 18.0 (SQL 2012 or newer are supported)

    • In the Automation Engine Pilot, go to Tools > Configure > Automation Engine Databases and check the hostname and instance of the configured SQL Server.
    • Then either with Microsoft SQL Studio Management Express or using Server Admin, SQL Server, check the version of SQL Server is at least SQL Server 2012 or newer.
    • If the installed version of SQL Server is 2005/2008/2008R2, proceed to step 2 to upgrade SQL Server 2005 to 2014 or 2017.
    • If the installed version of SQL Server is 2012 or newer, you can upgrade without problems to Automation Engine 18.0.

  1. Upgrade Microsoft SQL Server 2005/2008 to SQL Server 2014 or 2017

    • Verify that the compatibility level is set to SQL 2005 (see KB105514234).
    • Stop the Automation Engine Server software on the Master.
    • Using Server Admin, make a full Backup, including the databases, make sure no errors occur when creating the backup.
    • Go to the Windows Services and stop the services: SQL Server (MSSQLSERVER) and if exists SQL Server (EG_APPSRV_JBOSS) too.
    • On the Automation Engine Master server, Go to Control panel and double click Program and Features.
      • Double click either Microsoft SQL Server 2005 or SQL Server 2008 (64bit) or SQL Server 2008 R2 (64 bit ). Select the MSSQLSERVER (the unnamed instance) and check the Workstation Components options and click Next to uninstall.
      • If there is a Microsoft SQL Server instance with the name EG_APPSRV_JBOSS (instance used by the EG Application Server), repeat the previous step but now select the instance EG_APPSRV_JBOSS and click Next to uninstall the named instance.
      • Check if there are other entries referring to Microsoft SQL Server 2005 in the Program and Features. If so, uninstall these as well.
      • If you get an error while uninstalling SQL Server 2005, you need to uninstall it manually, please check https://support.microsoft.com/en-us/help/909967/how-to-manually-uninstall-an-instance-of-sql-server-2005.
    • Once Microsoft SQL Server is completely uninstalled, reboot the Automation Engine Server.
    • After the reboot, stop the Automation Engine Server software again.
    • Go the the folder bg_data_fastserver_dbase and delete the Microsoft SQL Server database files (*.mdf, *.ldf).
    • If the operating system of your Automation Engine Database server is running Windows 2008R2 :
      • Using the Automation Engine 16.x DVD, go to Extra and click the link: Install the Microsoft SQL Server 2014 for the Automation Engine component and follow the onscreen instructions.
      • During installation, you may need to install .NET Framework 3.5 (see KB168068482)

    • If the operating system of your Automation Engine Database server is running Windows 2012 or higher
      • Using the Automation Engine 18.0.x DVD, go to Extra and click the link: Install the Microsoft SQL Server 2017 for the Automation Engine component and follow the onscreen instructions.
    • In Server Admin, stop the Automation Engine Server.
    • Go to Restore and from the backup you have taken, restore database only, select all the Microsoft SQL databases.
    • In case previously, there was a named instance EG_APPSRV_JBOSS, this database will not be restored. This has to be done manually.
      • Stop the Automation Engine Server.
      • In Server Admin, go to Database, unlock so you can make changes.
      • Create a new database.
      • When asked, choose to create a database from a backup file.
      • Go to: \Esko\AEBackup\timestamp\AppServer\Database and select the file Fastlane_JBoss.
      • Make sure settings are filled in as:
        • Database name: Fastlane_JBoss
        • Database master file: \Esko\bg_data_fastserver_dbase\Fastlane_JBoss.mdf
        • Database transaction log file: \Esko\bg_data_fastserver_dbase\Fastlane_JBoss.ldf
    • Start up Automation Engine, verify if all databases are working properly (via server checks, databases).
    • In case of problem, go to Configure > Automation Engine Databases and adapt setting to the SQL Database Server.
  2. Upgrade Automation Engine 14.x/16.x to Automation Engine 16.1

    • After either upgrading to SQL Server 2014 or remaining with an older SQL 2008 or 2012, you can upgrade from version 14.0 onwards to Automation Engine 18.0.

  3. After the upgrade, execute a database check and optional upgrade soon outdated versions to a newer version of SQL Server.

    • Go the the Server Checks on the Automation Engine Master Server web pages and run the database check.
    • Check if you have warnings for a soon outdated version (f.e.: SQL 2012).
    • If so, we advice to upgrade to SQL 2014 or 2017, depending on your operating system. In the near future as a new version of Automation Engine might not support SQL 2012 anymore.
  4. Check and update compatibility level of the Microsoft SQL Server databases

    • We do advice to set the SQL compatibility level to one of these versions of SQL Server (highest possible level) (principles explained in KB105514234 apply here as well)

      • For SQL Server 2014, put the compatibility level to SQL 2014.
      • For SQL Server 2017, put the compatibility level to SQL 2017.
  5. Verify your upgrade Automation Engine Server is working OK

    • Verify that the Automation Engine Server is working as expected.
    • Once all done, stop the Automation Engine Server software.
    • Create a full backup, including the databases.
    • Store this backup in a safe place.
Article information
Applies to

 Automation Engine 18.0 and newer

Created

  

Last revised 
Author
Case Number 
Contents