Jitterbit · Database connector (JDBC)
Base64 decoding failed
Short answer
This 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.
VerifiedLast verified
01Error text
Base64 decoding failed. Reason: error:00000000:lib(0)::reason(0)02Likely causes
- Agent versions earlier than 12.9 may try to Base64-decode a JDBC result that only looks Base64-like, such as a JWT or other access token.
03How to fix it
- For private agents, upgrade to version 12.9 or later.
- If you cannot upgrade, convert the value to hexadecimal in the SQL query, then decode it in a script step with HexToString.
04Official documentation
→Related errors
- 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.
- Could not initialize class com.microsoft.sqlserver.jdbc.KerbAuthenticationThis Jitterbit error means the Kerberos configuration files on the agent host do not have the correct file permissions. On the private agent host, set permissions to 644 on jaas.conf, krb5.conf and the Kerberos ticket cache file.
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