Skip to main content

Common SSRS connection and crawl issues

Resolve common connection, authentication, and crawl issues when integrating SQL Server Reporting Services (SSRS) with Atlan.

Can't connect to Report Server​

Error

Connection timeout or connection refused when connecting to Report Server

Cause​

The Atlan workflow can't reach the SSRS Report Server. Common causes include an incorrect Web Service Endpoint URL, network or firewall blocking traffic, or the SSRS service not running.

Solution​

  1. Verify the Web Service Endpoint URL format is correct (for example, http://servername/ReportServer/ReportService2010.asmx or https://servername/ReportServer/ReportService2010.asmx for HTTPS).
  2. Verify the Windows Host hostname or IP address is correct and test connectivity from the Atlan environment (for example, using ping or telnet).
  3. Check that firewall rules permit traffic on the required ports (default: 80 for HTTP, 443 for HTTPS).
  4. Confirm the SSRS service is running in Windows Services (search for "SQL Server Reporting Services") and that the service status is "Running."
  5. Open the Simple Object Access Protocol (SOAP) endpoint URL in a web browser to confirm it responds; if using HTTPS, check for SSL certificate errors.

Authentication failures​

Error

401 Unauthorized or authentication test failures when connecting to SSRS

Cause​

Windows credentials are incorrect, the Windows domain is wrong, or the account doesn't have the required SSRS permissions.

Solution​

  1. Confirm Windows UserName and Windows Password are accurate and check for special characters that may need escaping.
  2. Verify Windows Domain matches your Windows domain (for example, CONTOSO) and that the domain controller is reachable from the Windows Host.
  3. Confirm the Windows account has Content Manager role in SSRS and check folder-level permissions in Report Manager.
  4. In Report Manager, go to Folder Settings → Security and confirm the user or group has the correct roles.
  5. Make sure Server Name matches your SSRS instance name; for multi-instance deployments, verify the named instance is correct.
  6. Confirm the SOAP Schema namespace matches your SSRS Server Version (for example, http://schemas.microsoft.com/sqlserver/reporting/2010/03/01/ReportServer).

Missing assets or incomplete metadata​

Error

Expected reports, datasets, models, entities, attributes, or roles not appearing after crawl

Cause​

Misconfigured folder filters, a Windows account that lacks read access to some folders, or assets that aren't published in Report Manager.

Solution​

  1. Check Top-level folder names in the workflow: verify paths use correct spelling, include the leading / and trailing * for wildcards, and that comma-separated values have no extra spaces; leave blank to crawl all folders.
  2. Confirm the Windows account has Content Manager role and read access to all folders you're crawling, including inherited permissions on subfolders.
  3. Review workflow execution logs for permission denied or timeout errors on specific folders.
  4. In Report Manager, confirm that the expected reports, datasets, and other assets exist and that Report Manager shows them as published (not in draft).

Performance issues during crawl​

Error

Slow workflow execution or timeouts during SSRS crawl

Cause​

Crawling the entire Report Server is too large in scope, the SSRS server or network is under load, or Report Server configuration limits are too low.

Solution​

  1. Reduce scope using Top-level folder names: specify only the folders you need, crawl high-priority folders first, or create separate workflows for different folder groups.
  2. Schedule workflow runs during off-peak hours and account for time zones if your team works across multiple regions.
  3. Monitor SSRS server CPU, memory, and disk I/O during the crawl and review SSRS execution logs for slow operations.
  4. Review rsreportserver.config for performance settings and consider increasing memory limits for the Report Server.
  5. Test network latency between Atlan and the Windows Host and check for congestion during the crawl.

Lineage not appearing​

Error

Lineage connections missing between SSRS assets and stored procedures or source columns

Cause​

Data source connection strings aren't captured, source database assets aren't cataloged in Atlan, or dataset or field metadata doesn't reference the expected stored procedures or columns.

Solution​

  1. Confirm data source connections are configured and that the connector captures ssrsDataSourceConnectionString; make sure data sources reference valid external databases.
  2. Catalog source databases (such as SQL Server, Oracle, and MySQL) in Atlan using their connectors and make sure you've run a crawl that discovers stored procedures before expecting lineage.
  3. Review workflow execution logs for errors during lineage extraction or connection issues to source databases.
  4. Verify datasets reference stored procedures in ssrsDataSetStoredProcedureName, that procedure names match the source database exactly, and that fields have source column references in ssrsFieldReferencedColumnNames.

See also​

Need help​

If you need assistance after trying the steps in this guide, contact Atlan support: Submit a request.