Troubleshooting SSRS collector issues
Collector runtime and troubleshooting
The catalog collector may run in several seconds to many minutes depending on the size and complexity of the system being crawled.
If the catalog collector runs without issues, you should see no output on the terminal, but a new file that matching *.dwec.ttl should be in the directory you specified for the output.
If there was an issue connecting or running the catalog collector, there will be either a stack trace or a *.log file. Both of those can be sent to support to investigate if the errors are not clear.
A list of common issues and problems encountered when running the collectors is available here.
Issue 1: Collector takes a long time to harvest metadata
Cause: The large size of an SSRS API results may take long time to harvest metadata. The collector paginates through the results which may lead to many API calls.
Solution: Increase the page size (--pagination-limit) to reduce the number of API calls.
Issue 2: Collector cannot connect to SSRS
Cause: Either the base URL of your SSRS instance is incorrect or your login credentials are incorrect.
Solution:
Verify user role: Review that the user used for running the collector has the Browser role assigned.
Check Base URL and Login: In a browser, navigate to the page specified by your base url. For instance, https://ssrs-server.mycompany.com/reports/api/v2.0. When prompted, input your username and password. If the base url is correct, you should see a result in json format