Troubleshoot Partner Connect

This section provides information to help address common issues with Partner Connect.

Troubleshoot general errors

You might see the following general errors when you try to connect using Partner Connect.

When trying to connect to a partner, an error message is displayed

Issue: When you try to connect your Databricks workspace to a partner solution by using Partner Connect, an error displays, and you cannot create the connection.

Causes:

There are multiple reasons why this issue may occur:

  • If multiple individuals within an organization try to create an account with a partner, only the first individual succeeds. This is because the partner may offer some accounts at only the organizational level, and the first individual who creates such an account also establishes the account for the organization.

  • If you already have an account with the partner, the connection may still fail. This is because the partner may mistakenly try to create a duplicate account.

Solutions:

Do one of the following:

  • Ask the first individual who created the organizational account with the partner to add your email address to that account. Then bypass Partner Connect and sign in to the partner account directly to begin using the partner’s solution.

  • Try making the connection again through Partner Connect, but this time, specify an email address that is not associated with your organization’s domain, such as a personal email address. This may require you to also add that email address as a user to your Databricks workspace.

  • Bypass Partner Connect and sign in to the partner directly with your existing account, and begin using the partner solution.

If your workspace is not already connected after you sign in to the partner, complete the connection by following the instructions in the appropriate partner connection guide.

When trying to sign in to a partner’s account or website, a pop-up blocker is displayed

Issue: For a partner solution that uses Partner Connect to sign in to the partner’s account or website, when you click Sign in, Partner Connect opens a new tab in your web browser and a pop-up blocker is displayed. This pop-up blocker prevents you from signing in to the partner’s account or website.

Cause: Your web browser is blocking pop-ups.

Solution: Allow pop-ups for the partner’s website in your web browser. Specific instructions vary by web browser. For example, for Google Chrome, see Block or allow popups in Chrome on the Google Chrome Help website. For other web browsers, search the Internet with a phrase such as “how do I allow pop-ups for a specific website?”

Insufficient permissions to create a partner connection

Issue: When you try to create the partner connection, a permissions error displays and you can’t create the connection.

Cause: This issue might occur because you aren’t a workspace admin.

Solution: An account admin or a workspace admin must add your user to the admins group. See Manage groups.

Insufficient permissions to create a partner connection to data managed by Unity Catalog

Issue: When you try to create the partner connection, the following missing permissions error displays and you can’t create the connection:

You do not have permission to grant <read|write> access to the workspace default catalog. To enable granting <read|write> access to the default catalog or other catalogs, contact an account admin

Cause: This issue might occur because you don’t own the workspace default catalog. If a partner solution isn’t enabled for Unity Catalog with Partner Connect, you can only connect to the default catalog, and the default catalog must be hive_metastore or another catalog that you explicitly own.

Solution: Do one of the following:

  • Ask an owner of the default catalog to create the connection.

  • Ask an owner of the default catalog to add you to the group that owns the default catalog. See Manage groups.

  • Ask an account admin to change the default catalog by running databricks metastores assign. In the following command example, replace these placeholders:

    • Replace <workspace-id> with the ID of the workspace.

    • Replace <metastore-id> with the ID of the metastore.

    • Replace <catalog-name> with the name of the default catalog.

    databricks metastores assign <workspace-id> <metastore-id> <catalog-name>

    Warning

    Changing the default catalog can break existing data operations that depend on it. In particular, data operations that don’t specify the catalog assume the default catalog. Changing the default causes those operations to be unable to find the data objects that they reference.

    For more information about the databricks metastores command, see Databricks CLI commands.

Existing partner connection can no longer access Databricks data

Issue: When you sign in to an existing partner account that connects to your workspace using Partner Connect, and the partner tries to access Databricks data, an error displays, stating that you don’t have permissions to access the workspace default catalog.

Cause: If your workspace is Unity Catalog-enabled, this issue might occur because the default catalog isn’t hive_metastore. If the partner solution doesn’t support connections to data managed by Unity Catalog using Partner Connect, this breaks your existing connection.

Solution: Do one of the following:

  • Disconnect from the partner and then reconnect, specifying the default catalog. See Disconnect from a partner. This solution requires that you own the default catalog.

  • Ask an account admin to change the default catalog to hive_metastore by running databricks metastores assign. In the following command example, replace these placeholders:

    • Replace <workspace-id> with the ID of the workspace.

    • Replace <metastore-id> with the ID of the metastore.

    databricks metastores assign <workspace-id> <metastore-id> hive_metastore

    Warning

    Changing the default catalog can break existing data operations that depend on it. In particular, data operations that don’t specify the catalog assume the default catalog. Changing the default causes those operations to be unable to find the data objects that they reference.

    For more information about the databricks metastores command, see Databricks CLI commands.

Troubleshoot security errors

The security configurations mentioned in this section might cause Partner Connect integrations to fail.

IP access lists

Issue: The following warning appears in the Connect to partner dialog box, and you’re unable to create a connection to a partner:

Partner Connect might not work because IP access list is enabled.

Cause: If the IP access list feature is enabled on your workspace, you might have to add the partner integration to the allowlist.

Solution: For steps to add partner integrations to the allowlist, see the partner documentation or contact the partner’s support team.

For more information about IP access lists, see Configure IP access lists for workspaces.

Personal access tokens

Issue: When you try to create a connection, the following Missing permissions error displays:

Partner Connect requires personal access tokens to be enabled.

Cause: If token-based authentication is disabled on your workspace, you can’t use Partner Connect to integrate with partner solutions.

For more information about personal access tokens, see Monitor and manage access to personal access tokens.