Syniti Solutions Upgrade Manual 7.4.2


IMPORTANT: Clients running the Stewardship Tier in 32-bit mode are recommended to switch to 64-bit mode prior to upgrading to version 7.4.2 to allow sufficient testing before upgrading. If issues occur during the switch to 64-bit mode, it is easier to roll back the architecture switch than the entire upgrade.

The following steps assume a working Stewardship Tier instance is installed. It is never advisable to attempt to upgrade a broken or non-functional instance with the goal of fixing it.

NOTE: Version 7.1 introduced a new centralized security model and users of Data Quality, Master Data Management and Mass Maintenance must update security roles when upgrading to 7.1 and later. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.1 or later. Consult this manual BEFORE upgrading to 7.1 or later.

NOTE: Only upgrades from 6.0 and later are supported; there is no upgrade from version 5.x products available.

The upgrade process will upgrade all components of Stewardship Tier, including all delivered WebApps. The upgrade may fail if any of the delivered components have been customized.

A customization is a change to the underlying source code, which differs from configuration, a normal setup of the software, such as setting up workflows and defining parameters via the configuration pages.

The upgrade does not modify any existing Construct pages or menus.

Custom CTS Configurations

WARNING: Any additions or changes users have made to CTS configuration (Admin -> CTS ->Configuration) may be lost when upgrading from DSP 6.6.x or earlier.

Prior to any upgrade backups should be taken of all databases. Once the upgrade is complete, if any custom CTS configurations are found to be missing, then the backup of the CranSoft database should be restored to a new database (DO NOT restore it to the CranSoft database). The missing custom configurations can be merged into the CranSoft.dbo.CTSConfig% tables from the restored backup.

Please contact Syniti Product Support at if you would like assistance with this activity.

Preserve Customizations

WARNING: Customizations made to any component of the delivered Stewardship Tier will be overwritten in this upgrade. To preserve customizations, make a copy of the customizations prior to applying any upgrade.

Upgrading from a 6.0.x Version

If you are upgrading from a 6.0.x version,

  1. Enter a ticket at Syniti Support at to request the 61UpgradeTargetERPTableCheck.sql script. This script detects problems with targets, for example if the ERP table name is different between 6.0.x and 6.6.
  2. Run the 61UpgradeTargetERPTableCheck.sql prior to upgrading from 6.0.x to 6.6.

If the query detects problems, open a ticket with Syniti Support at

Stewardship Tier version 6.0 or later must be installed. Do not attempt to perform the upgrade process on any Syniti product prior to version 6.0.

NOTE: To identify the currently running version of the Stewardship Tier framework, log in and look at the footer.

Version 6.5 introduced the restriction that a license key is tied to a single server and cannot be used on any other server. In order to enforce this restriction, starting with version 6.5 a hardware ID must be generated on the application server where the Stewardship Tier is installed which must accompany the request for a new license for that instance. Obtaining a license file is therefore now a two-step process described in the Install a Permanent License section. Until the new licenses are applied, the upgraded site will not be functional.

How to Request a New Product License File

  1. Navigate to the location of the Hardware Identifier program called “HardwareIdentifier.exe” downloaded automatically with the SST<Version>FullPackage.exe installer.

  2. Right-click the program file and select Run as Administrator.
  3. Click Generate.

  4. The Hardware ID field populates.
  5. Click Copy to copy the automatically generated ID.
  6. Include the automatically generated ID along with the Windows computer name of the server and your Company name in an email to, with the subject “Product License Request”.

    NOTE: A license file will be sent as an attachment to an email you will receive in response within two business days.

NOTE: If the upgrade includes the addition of a Syniti Knowledge Platform subscription contact Syniti Support at

Align Column Encryption State for key Target Source column in Collect Before Upgrade

NOTE: Version 7.1.3 runs post-installation scripts that create a new Common Data Source Registry entry of type SAP Application Server and then assign this record to the associated Collect Target Source record. If the same SAP Application / Client is registered on multiple Target Source records, duplicate records will be created in the Data Source Registry. Users should be aware of this change and review the created data sources post installation to ensure that there are no duplicate entries in the Data Source Registry. Review this section BEFORE upgrading from 7.1.2 or earlier versions.

A new feature was introduced in SST 7.1.3 whereby the SAP connection settings on a Collect Target Source are moved to a dedicated Data Source Registry record. During upgrade, the following DataGarage dgTargetSource table columns are used to create the new DSPCommon Data Source Registry records.

Database Table Column Database Table Column
On upgrade, the data in these columns is copied from... ... to these columns
DataGarage dgTargetSource SAPPassword DSPCommon ttDataSourceRegistry SAPPassword
DataGarage dgTargetSource SAPUserID DSPCommon ttDataSourceRegistry SAPUserID
DataGarage dgTargetSource RfcNameSpaceOption DSPCommon ttDataSourceRegistry RfcNameSpaceOption
DataGarage dgTargetSource SAPServerHost DSPCommon ttDataSourceRegistry SAPApplicationServer
DataGarage dgTargetSource Language DSPCommon ttDataSourceRegistry SAPLanguage
DataGarage dgTargetSource SAPMsgServerHost DSPCommon ttDataSourceRegistry SAPMessageServer
DataGarage dgTargetSource SAPLogonGroup DSPCommon ttDataSourceRegistry SAPLogonGroup

As a result of these changes, BEFORE UPGRADING to version 7.1.3 and later, you must review and confirm that the encryption state of these two sets of columns matches. If you do not confirm that the encryption state is identical in these two sets of columns, mixed data could be saved in the column when the Stewardship Tier is upgraded. Access the Data Source Column Encryption page in System Administration. The Status field indicates issues with encryption that must be corrected before upgrade.