SQL Server

To use SQL Server, an SQL-srv account has to be used as opposed to a Windows-authenticated (AD) account. Furthermore, the following is required:

1. Database host

2. (Optional) Database port

3. Database name

4. Database username

5. Database password

Leave the username and password empty to use the local user of the system. When you do this, make sure to change the logon user of the service when running the application as service in the background to match this user.

Using a host like machine01instance? Write it like this: machine01instance

Password cannot contain $ signs.

SQLSTATE[08001]: SSL Provider: The certificate chain was issued by an authority that is not trusted

Symptoms

During installation or configuration, the extension cannot establish a database connection. Error messages may mention SSL/TLS, certificate trust, or “the certificate chain was issued by an authority that is not trusted.”

• Error message example:

  SQLSTATE[08001]: [Microsoft][ODBC Driver 18 for SQL Server]SSL Provider: 
  The certificate chain was issued by an authority that is not trusted.

Cause The SQL Server requires SSL encryption, but the certificate presented cannot be validated. This usually happens when:

• A self-signed certificate is being used, and the authority certificate is not trusted on the machine running WBE.

• The full certificate chain (including intermediates) is not installed.

Solution

1. If possible, install a certificate signed by a trusted Certificate Authority (CA).

2. If using a self-signed certificate, import the authority certificate into the Trusted Root Certification Authorities store on the server where WBE runs.

3. If the issue persists during installation, try the following steps:

   • Stop the WriteBackExtreme service.

   • Delete the runtime and config folders to reset the installation.

   • Restart the installation and re-enter database details.

   • Tick Disable SSL certificate validation for the SQL Server database to bypass the validation check.