## Troubleshooting SAP Datasphere connectivity

URL: https://docs.atlan.com/apps/connectors/data-warehouses/sap-datasphere/troubleshooting/troubleshooting-sap-datasphere-connectivity

> Resolve common SAP Datasphere connection issues and errors.

# Troubleshooting SAP Datasphere connectivity 

## Datasphere authentication failed

**Error**: `Authentication failed` or `invalid client credentials`

**Cause**: The OAuth client ID, client secret, or token URL is incorrect, or the OAuth client isn't authorized for the client-credentials grant.

**Solution**: Verify the OAuth client ID, client secret, and token URL. Confirm the client is configured for API access using the client-credentials grant by following the [setup guide](https://docs.atlan.com/llms/connectors/sap-datasphere/set-up-sap-datasphere/llms.txt).

## No spaces returned

**Error**: `Spaces check failed` or no spaces available to select

**Cause**: The OAuth client authenticated successfully but isn't authorized to access the space catalog.

**Solution**: Grant the OAuth client access to the spaces you want to catalog, then run the [preflight checks](https://docs.atlan.com/llms/connectors/sap-datasphere/preflight-checks-for-sap-datasphere/llms.txt) again.

## SAP HANA connection refused

**Error**: `Connection refused` or `cannot connect`

**Cause**: The SAP HANA Cloud SQL endpoint isn't reachable from Atlan.

**Solution**:
- Verify the host and port are correct. SAP HANA Cloud uses port `443` by default.
- Make sure your firewall or security group rules permit inbound connections from Atlan's IP addresses on the specified port.
- For tenants behind a firewall, consider using [Self-Deployed Runtime](https://docs.atlan.com/llms/connectors/sap-datasphere/how-atlan-connects-to-sap-datasphere/llms.txt).

## SAP HANA authentication failed

**Error**: `Authentication failed` or `invalid username or password`

**Cause**: The database user or password is incorrect, or the user doesn't exist.

**Solution**: Verify the database user and password are correct. If the user doesn't exist, create it by following the [setup guide](https://docs.atlan.com/llms/connectors/sap-datasphere/set-up-sap-datasphere/llms.txt).

## Missing upstream lineage from replication flows

**Error**: Replication flows are cataloged, but no upstream lineage appears to source systems

**Cause**: The database user doesn't have cross-space read access, so Atlan can't resolve which source system each replication flow reads from.

**Solution**: Provide a database user with cross-space read access, as described in the [setup guide](https://docs.atlan.com/llms/connectors/sap-datasphere/set-up-sap-datasphere/llms.txt), then crawl again. Where a replicated table's source connection can't be resolved, Atlan catalogs the asset without an upstream lineage edge.

---