# Update guide

# Manual update of ELO Sync without the ELO Server Setup

To update ELO Sync manually, first the ELO Sync service has to be stopped.

After this, the files have to be extracted from the ELO Sync ZIP file to the ELO Sync installation directory. Existing files should be deleted to avoid inconsistencies. Only the appsettings.json file with the configuration data may be kept.

After it has been ensured that the data in the appsettings.json is correct and e.g. the specified certificate exists at the corresponding path, the service can be started again. The manual update is then completed.

Information

We recommend renaming the existing installation directory and copying the ELO Sync files into a new folder with the name of the old installation. As a result, both versions are retained temporarily, and configuration files such as the appsettings.json can easily be switched out. This is recommended especially for major version upgrades, as the structure of the configuration files may have changed or new properties may have been added. The old and new appsettings.json files can then easily be compared and populated accordingly.

# Update from 23.6 to 25.0

# High-impact changes

# Conflict types added

The conflict types have been simplified for use with the REST API.

The new properties 'FirstSystem' and 'SecondSystem' were added, which make it possible to identify the respective system of the items directly in a conflict. These fields may not be populated yet for older conflicts. Running the synchronization job again populates these additional conflict fields.

# Conflict resolutions simplified

Conflict resolution has been simplified. Now, only the item ID has to be entered without the system prefix.

# OracleDB no longer supported

OracleDB is no longer supported in 25.0 due to low demand.

# Update from 23.4 to 23.5

# High-impact changes

# Minimum database versions increased

The minimum required version of Microsoft SQL Server was increased to SQL Server 2016.

This is due to a change by Microsoft in a dependency used by ELO Sync. You will find more information under Microsoft Docs (opens new window).
The minimum required version of Oracle Database was increased to 19c

Oracle has discontinued support for older database versions with the introduction of support for .NET 8. You will find the detailed system requirements in the Oracle Developer Guide (opens new window) under ODP.NET Core.
The minimum required version of PostgreSQL was increased to 12.20

This is in line with the standard support policy for PostgreSQL. See the Versioning Policy (opens new window) for supported PostgreSQL versions.

# ConnectionString change required for SQL Server when using self-signed certificates

If ELO Sync is unable to connect to the SQL Server database, it may be necessary to update the ConnectionString in the appsettings.json file.

If the ELO Sync log file contains the following error (or a similar message), the trust settings for the server certificate have changed.

<details>
<summary>Microsoft.Data.SqlClient.SqlException</summary>
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
</details>

This error occurs due to a change in the default behavior when connecting to SQL Server. The server certificate now has to be signed by a trusted certificate authority.

Self-signed certificates as created by the standard SQL server setup are no longer accepted.

As a workaround, you can add TrustServerCertificate=true; to the ConnectionString to re-enable trust in self-signed certificates.

← Service registration