Troubleshooting and Support

⌘K
  2. Home
  4. Docs
  6. Troubleshooting and Suppo...
  8. Self-Troubleshooting
  10. Failed to Connect to Database

Failed to Connect to Database

It is recommended to test the connection to a DBMS during the connection settings. Even though the connection was tested during the setup phase, you may still encounter errors related to connection settings during operation. This can depend on the specific DBMS you are using and any changes that may have occurred in your settings over time. Depending on the DBMS you are using, errors may vary, and we will describe the most common cases.

SQL Server

The most common issue encountered when using a local connection to SQL Server is incorrectly specified usernames or passwords. If you encounter this, you’ll receive an error explicitly stating:

[Error] Job execution error: #[SRV:8007#1326]} Authorization failed. Server name: "MSI". Username: "Dr-Co1". Domain: "MSI" > The user name or password is incorrect Server name: "MSI".

As a rule, to ensure you use the correct credentials, please make sure you can manually connect to your database, for example, via SQL Server Management Studio. Once the connection is set successfully via SSMS, you’ll be able to connect to your databases via SQLBackupAndFTP using the same credentials.

If TrustServerCertificate is set to true on your server, you may face the following error message:

[Error] Failed to backup "AdventureWorks" database with "Full" backup type: Could not connect to database server. > 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.) > The certificate chain was issued by an authority that is not trusted

To resolve the issue, simply go to the connection settings in SQLBackupAndFTP and enable the Trust Server Certificate option in the advanced connection settings.

If you encounter any other connection-related errors, you can always try to find a solution online. The majority of connection errors are generated by the user’s system or SQL Server and are unlikely to be resolved through SQLBackupAndFTP.

MySQL Server and PostgreSQL Server

To establish a connection to MySQL Server and PostgreSQL, SQLBackupAndFTP uses mysql.exe and psql.exe, respectively.

We always strive to update the application to utilize the latest binary files for MySQL Server and PostgreSQL Server. However, there are instances where users may be employing older versions of MySQL Server or PostgreSQL Server, in which case, they can manually specify the path. If different binary files are being used, a corresponding error will be displayed:

[Error] Failed to backup "MyDB" database with "Full" backup type: C:\Program Files (x86)\SQLBackupAndFTP\DBMS\PostgreSql\pg_dump.exe process has finished with "1" code. The error message: "pg_dump: error: server version: 15.1; pg_dump version: 14.2
pg_dump: error: aborting because of server version mismatch".

The path to the bin folder can be specified in the advanced backup job connection settings.

If you encounter any other issues during the connection, you can always try to check the connection manually. You can do this by clicking the info button and examining the command that SQLBackupAndFTP uses to connect to the database. To test the connection, please copy the command from the opened window and try to execute it via the command line. Please ensure that you set the correct password.