When deploying a recent Skype for Business Server 2019 deployment, I came across an issue when installing monitoring reports on a server. In previous editions of SQL Server, SQL Server Reporting Services (SSRS) was installed and configured by default. With the release of SQL Server 2017, this is now a seperate download that only installs the service. After installing SSRS, the Report Server Web Service/Report Manager in Reporting Services Configuration Manager needed to be configured.
This was fairly simple to configure, however, the error “Cannot Get the ReportServerWebService URL. Verify that Reporting Services is deployed and configured properly on the target SQL Instance” kept appearing when attempting to deploy monitoring reports. Since this was a single server, the Windows Defender Firewall should not have been an issue.
In this scenario, SQL was installed as the Default Instance so there should not have had to been anything after the SQL Server FQDN. Looking back at the initial “Specify Monitoring Database” section of the Monitoring Reports Wizard, everything looked normal and was to the specification stated. This can be seen in the below image:
After a bit of trial and error, I found that SSRS is its own instance (regardless that its databases are installed in the default sql instance (MSSQLSERVER)) and will need to be defined. The following format should be used <SQL Server FQDN>\SSRS. In this case, the following instance was used:
After making this change in the deployment wizard, everything installed successfully and was confirmed to be fully working.
