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 ...Skyvia IPs for Whitelist
Overview Skyvia is a cloud-based platform that connects to your data sources and targets over the internet. If your database, server, or cloud service restricts inbound connections by IP address (e.g., via firewall rules, security groups, or ...Replication: Table '...' Schema Validation Failed (Resolving 'Absent Columns' and 'Redundant Columns' Errors)
If you encounter the following errors in an integration, it means the schema of your data source no longer matches the schema Skyvia has cached: Error: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...Zoho CRM: Integration failed: inactive user cannot access the API error
This error message is returned by the Zoho CRM API. Skyvia connects to data sources through their APIs and therefore is subject to its features and limitations. Unfortunately, there are no additional details, as this is all the information received ...Google Sheets: Internal error encountered. Error code: 500
The error "Internal error encountered. Error code: 500" is returned by the Google Sheets API and is typically caused by processing a large volume of data. To resolve this issue, we recommend adjusting the Batch Size value in your integration. For ...