PostgreSQL: A call to SSPI failed, see internal exception

"A call to SSPI failed, see internal exception" indicates that the security protocol (SSL/TLS) used in your PostgreSQL connector does not match the version supported by your server. To resolve this, we recommend trying different SSL/TLS protocol versions in your connection settings in Skyvia.

You can also contact your database administrator to confirm the SSL/TLS version configured on your PostgreSQL server and ensure the same version is specified in the connector. Additionally, please double-check that all other connection settings are configured correctly.

• Related Articles

• MySQL: Resolving "Lost connection to MySQL server during query" Error

  To resolve the "Lost connection to MySQL server during query" error, please follow the steps below: Go to the Connections page and select your MySQL connection. Click Edit. In the Connection Editor, go to Advanced, then increase or set to 0 the ...

• SQL Server: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding

  The "Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding" error may occur when the command took too long to execute or the server stopped responding during the command. To resolve ...

• 🔒Skyvia IPs for Whitelist

  Skyvia will access your server from one of the following IP addresses: 40.118.246.204 13.86.253.112 52.190.252.0 To ensure proper functionality of your connections, all of these IP addresses must be whitelisted.

• Salesforce API errors: TotalRequests Limit Exceeded/ApiBatchItems Limit Exceeded

  The TotalRequests Limit Exceeded and ApiBatchItems Limit Exceeded errors are Salesforce-specific errors indicating that you have reached specific API limits on the Salesforce platform. Please find explanations of each error and relevant documentation ...

• QuickBooks Online: Could not start QuickBooks

  The "Could not start QuickBooks" error may occur if QuickBooks and the Skyvia Agent are running with different user permissions. To avoid this, make sure both applications are launched either as a regular user or as an administrator. If this does not ...