Jitterbit · Database connector (SQL Server MS JDBC)
SQL Server: PKIX path building failed
This Jitterbit SQL Server error means the JDBC driver requested encryption and could not trace the server certificate to a certificate authority the agent trusts. In the Database connection's Optional Settings, add encrypt=false; to the Additional Connection String Parameters field, or include it in a manual connection string.
VerifiedLast verified
01Error text
PKIX path building failed: unable to find valid certification path to requested target.02Likely causes
- Current SQL Server MS JDBC drivers request encryption by default and validate the server certificate. The connection fails when the certificate is self-signed, internally issued or otherwise not trusted by the agent.
- Agent 12.8 updated the bundled driver to request encryption by default, so a connection that worked before the upgrade can fail after it.
03How to fix it
- In the Database connection's Optional Settings, add
encrypt=false;to the Additional Connection String Parameters field, or include it in a manual connection string.
iNotes
With encrypt=false, data travels unencrypted between the agent and the database, so use it only where that is acceptable.
04Official documentation
→Related errors
- Base64 decoding failedThis Jitterbit error in DBLookup or DBExecute means an agent earlier than 12.9 tried to Base64-decode a JDBC result that only looks like Base64, such as a JWT. For private agents, upgrade to version 12.9 or later.
- Database connection could not be established due to a security policy violationThis Jitterbit error means agent 12.10 or later blocked a database connection to a loopback address or one that uses a restricted connection string parameter. On the private agent, configure the [JdbcSecurity] section of jitterbit.conf to allow the specific connection or parameter.
- Field value too long / values were truncatedThis Jitterbit database error means a mapped source value is longer than the target column, and by default the value is rejected. In the activity configuration, enable Allow truncation of character fields.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries