PostgreSQL: A call to SSPI failed, see internal exception

PostgreSQL: A call to SSPI failed, see internal exception

The error message "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 Skyvia connector. Additionally, please double-check that all other connection settings are configured correctly.

    • Related Articles

    • Freshdesk: The Limit of Freshdesk API Calls Per Hour Has Been Reached

      This error occurs on the Freshdesk side, indicating that the API call limit for the hour has been exceeded. For more details on Freshdesk's API limits, refer to their API documentation. Freshdesk enforces a limit on the number of API calls that can ...

    • 📊 Skyvia Data Flow Logs Explained: The Reason Errors and Successes Aren't Shown by Default

      In Data Flow, tracking execution success or failure can be challenging due to the nature of row processing. Rows that fail in one component may succeed in another, complicating error detection. By default, Skyvia logs do not provide detailed error or ...

    • Integration Failure Types in Skyvia Data Integration

      When using Skyvia Data Integration product, you may encounter two distinct types of integration failures: 1. Record-Level Errors These occur when one or more individual records fail to process during an integration task. For example, in operations ...

    • Replication creates extra tables in the database

      In some cases, as a result of Replication, in addition to the main tables (for example, dbo.Account ), empty additional tables are created in the database with names of the following types: dbo.Account_2ade4447_5e11_4308_9e81_5eab62d9ed52 ...

    • Automation: Task Limit Reached

      The "You have reached the limit of tasks" error in Automation indicates that you have exceeded the number of billed tasks allowed in your pricing plan for the current billing period. A billed task is any successful execution of an Action component ...