> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open-metadata.org/llms.txt
> Use this file to discover all available pages before exploring further.

# SSRS Troubleshooting | OpenMetadata Connector

> Troubleshoot common SSRS connector issues in OpenMetadata — connection failures, NTLM authentication errors, and ingestion problems.

## Troubleshooting

## Workflow Deployment Error

If there were any errors during the workflow deployment process, the
Ingestion Pipeline Entity will still be created, but no workflow will be
present in the Ingestion container.

* You can then Edit the Ingestion Pipeline and **Deploy** it again.
* From the Connection tab, you can also Edit the Service if needed.

## Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in OpenMetadata. Below are some of the most frequently observed troubleshooting scenarios.

## How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in OpenMetadata:

1. **Navigate to Services**
   Go to **Settings > Services > Service Type** (e.g., Database) in the OpenMetadata UI.

2. **Select a Service**
   Choose the specific service for which you want to enable debug logging.

3. **Access Ingestion Tab**
   Go to the **Ingestion tab** and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.

4. **Enable Debug Logging**
   In the configuration dialog, enable the **Debug Log** option and click **Next**.

5. **Schedule and Submit**
   Configure the schedule if needed and click **Submit** to apply the changes.

## Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

## SSRS-Specific Issues

### NTLM Authentication Failure

If the connector fails with a `401 Unauthorized` error, verify that:

* The username uses the correct format (`DOMAIN\username` for domain accounts)
* The account has at least the **Browser** role on the SSRS Report Server
* NTLM authentication is enabled on the Report Server (not only Kerberos)

### Cannot Connect to SSRS REST API

Ensure the SSRS REST API is enabled. The connector uses `/api/v2.0/` endpoints — this requires **SSRS 2017 or later**. Older versions using SOAP-based web services are not supported by this connector.

### SSL Certificate Errors

If you see SSL verification errors, either:

* Set `verifySSL: ignore` to skip validation (not recommended for production)
* Set `verifySSL: validate` and provide the correct CA certificate path in `sslConfig`

### Reports Not Appearing

If reports are missing after ingestion:

* Confirm the service account has **Browser** role access on the folder containing those reports
* Check whether `dashboardFilterPattern` or `projectFilterPattern` is inadvertently excluding them
* Hidden reports are automatically skipped by the connector