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

 

 

Description

  • The main problem in this case is that Microsoft SQL Server 2005 is no longer supported in Automation Engine 16.1 and on the other hand Microsoft SQL Server 2008R2, which is the lowest version supported in Automation Engine 16.1 was not yet supported in Automation Engine 12.1.0 and older.
    • Automation Engine 12.0.0, 12.0.1 and 12.1.0 were shipped with an Microsoft SQL Server 2005.
    • Automation Engine 12.1.1, 12.2 and 14.0.x were shipped with a Microsoft SQL Server 2008R2.
    • Automation Engine 14.1.x and 16.0.x were shipped with a Microsoft SQL Server 2014.
    • If an Automation Engine is upgraded to a newer version, the Microsoft SQL Server is never upgraded, is kept at the current installed version, so the issue can occur with any upgrade of Automation Engine to 16.1.
  • When upgrading any Automation Engine which is currently configured to use Microsoft SQL Server 2005, after upgrading to Automation Engine 16.1, you will end up with a system which is no longer working. It is not just unsupported, but some servers in Automation Engine ( Elemserver, JDFServer, etc) will not be able to startup anymore. Please follow the steps given below to upgrade the Automation Engine Server and the Microsoft SQL Server software as well to ensure a good working configuration after the upgrade.

Procedure

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

  1. Check if used version of Microsoft SQL server is still compatible with Automation Engine 16.1 (Currently SQL 2008R2 or newer are supported)

    • If current installed version is version 14.1.x or 16.0.x, go Server Checks on the Automation Engine Master Server web pages and run the database check.
      • In the case, any of the databases are still running on an SQL Server 2005, you will get a warning that Microsoft SQL Server 2005 will soon be outdated.
      • When you get this warning proceed to step xxx to upgrade the SQL Server 2005 to SQL Server 2014.
      • If the installed version of SQL Server is 2005, proceed to step 2 to upgrade SQL Server 2005 to 2014.
      • If the installed version of SQL Server is 2008R2 or newer, you can upgrade as usual to Automation Engine 16.1.
    • If current installed version is a 14.0, you can upgrade to Automation Engine 16.1 directly, but a manual check of the used SQL Server is needed.
      • In the Automation Engine Pilot, go too 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 2008R2 or newer.
      • If the installed version of SQL Server is 2005, proceed to step 2 to upgrade SQL Server 2005 to 2014.
      • If the installed version of SQL Server is 2008R2 or newer, you can upgrade as usual to Automation Engine 16.1.
    • If current installed version is a version 12.x, first upgrade to Automation Engine 14.1.x or 16.0.x as described in the Automation Engine 14.1 or 16.0 manual.
      • After upgrading to Automation Engine 14.1 or 16.0, go to the Automation Engine Master Server web pages and run the database check.
      • In case any of the databases are still running on an SQL Server 2005, you will get a warning that Microsoft SQL Server 2005 will soon be outdated.
      • When you get this warning, proceed to step 2 to upgrade the SQL Server 2005 to SQL Server 2014.
      • If the installed version of SQL Server is 2008R2 or newer, you can upgrade as usual to Automation Engine 16.1.
  1. Upgrade Microsoft SQL Server 2005 to SQL Server 2014

    • Verify that the compatibility level is set to SQL 2005, please check the following KBA for instruction how to do so:
    • 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 to 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 Microsoft SQL Server 2005. Select the MSSQLSERVER (is 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 ( this is 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 are 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).
    • Using the Automation Engine DVD, go to Extra and click the link: Install the Microsoft SQL Server 2014 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.0.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 16.1 as usual.

  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 2008R2).
    • If so, we advice to upgrade to SQL 2014 in the near future as a new version of Automation Engine might not support SQL 2008 anymore.
  4. Check and update compatibility level of the Microsoft SQL Server databases

  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.
    • Put this backup in a safe place.
Article information
Applies to

Automation Engine 16.1 and newer

Created05-Oct-17
Last revised 
AuthorGDM
Case Number 
Contents