Data 360: Troubleshooting Connection Errors in DBeaver

Please ensure you are using the latest version of the JDBC driver if you are seeing any errors not resolved by the steps listed below. You can download this from the GitHub Repository here.

Update to the latest version as follows:

• Right-click on the connection in DBeaver.
• Under Connection settings, click Driver Settings.
• Click Libraries.
• Click the driver and then click Download/Update. If you still see that the version listed is not the latest version listed on GitHub then proceed to the next step to manually update.
• If that is not clickable or the driver does not update to the latest automatically, you can delete the existing driver file and click Add File to add the latest version of the driver download from the GitHub Repository here.
• Note: if manually updating the driver does not resolve the issue, you can click Reset to Defaults within Driver Settings to return to the default version.

Common Errors in DBeaver

Note: unless specified most of these errors are observed after creating a connection in DBeaver when click the Connect or Test Connection button.

"Error in driver initialization...  Reason: Can't create driver instance..."

This error indicates an issue with the driver files required to create a Salesforce Data 360 connection. Follow these steps to confirm that a driver file is present:

• Right-click on the connection and click Edit Connection.
• Click Driver Settings.
• On the Libraries tab check if a .jar file is listed. If no .jar file is listed or there is an error, click Reset to Defaults to restore the default driver settings. Then click Download/Update and then Download in the popup. If you do not want to use the default settings, click Add File to select a .jar file that is present on your local machine.
• Click OK to confirm the changes and then retry opening the connection.

"Client Id cannot be null"

This error indicates that you have not added a clientId to the connection settings, complete the following steps:

• Right-click on the connection and click Edit Connection.
• Under Connection settings, click Driver properties.
• Right-click and choose Add new property.
• Enter clientId and press OK.
• Click on the Value column for the clientId property and add the Consumer Key value from App Manager. See Set Up Connected App for DBeaver for full step to get Consumer Key value.

"Client Secret cannot be null"

This error indicates that you have not added a clientSecret to the connection settings, complete the following steps:

• Right-click on the connection and click Edit Connection.
• Under Connection settings, click Driver properties.
• Right-click and choose Add new property.
• Enter clientSecret and press OK.
• Click on the Value column for the clientSecret property and add the Consumer Secret value from App Manager. See Set Up Connected App for DBeaver for full step to get Consumer Secret value.

"Dataspace cannot be changed in the same connections"

As outlined in Use Data 360 APIs with Data Spaces, a dataspace parameter can be passed when connecting to Data 360 via API. This is also true with DBeaver. In the same way you configured the clientId and clientSecret in Connection settings > Driver properties, you can also create a dataspace property and set the name of the dataspace you wish to connect to as its value. If you have done this configuration you may notice this error "Dataspace cannot be changed in the same connections" when attempting to view the contents of another dataspace in the Database Navigator. Create a new connection and specify the name of the other dataspace in the connection settings in order to view the dataspace's objects.

"Expected URL scheme 'http' or 'https' but no colon was found"

• Right-click on connection and click Edit Connection
• Confirm that the JDBC URL field is set correctly.
  • When using the Salesforce Data 360 database driver this would be in one of the following formats:
    • jdbc:salesforce-datacloud://login.salesforce.com
    • jdbc:salesforce-datacloud:https://[insert your domain here].my.salesforce.com
  • If you chose the Salesforce Data 360 (Legacy) database driver this would be in one of the following formats:
    • jdbc:queryService-jdbc:https://[insert your domain here].my.salesforce.com
    • jdbc:queryService-jdbc:https://login.salesforce.com
• Confirm your Username and Password are entered correctly.

"Failed to get config from server"

Review the access of the user whose credentials are entered in the Username and Password settings of your connection. Ensure that the user is assigned a permission set that provides Data 360 access. See Data 360 Standard Permission Sets for details on available permission sets. Also confirm that the assigned permission set is associated with the data space being connected to. If you are passing a dataspace parameter in the Connection settings > Driver properties, then confirm that the Data 360 permission set assigned to your user is associated with that data space by following the steps in Associate a Permission Set with a Data Space. If no dataspace parameter is configured then ensure the permission set is associated with the default data space.

"authentication failure - Failed to login. Please check credentials"

This error indicates an issue during authentication. To get more information about what error is being returned during the login attempt follow these steps:

• Login to your Data 360 org.
• Go to Setup and search for Login History in Quick Find. Note: the Application column should contain the name given to your Connected App.
• Based on the details in the Status column, review the suggestion resolution in the table below: