Another quick one, as part of one of my standard deployments of SFB 2019 I went to deploy the Skype for Business Monitoring Reports and received the error message
Cannot get the ReportServerWebService URL. Verify that Reporting Services is deployed and configured properly on the target SQL instance:"sql.www.UcMadScientist.com\SSRS", and that WMI is included on the exception list of firewall setting on the server that is running Reporting Services.
And I did the usual things, Checked for WMI access, Checked the instance name and checked that the SSRS service was installed and running. Yep all good. But I still I couldn’t deploy the Monitoring Reports.
Luckily this SQL admin gave me access to the SQL boxes so I logged in to have a look. and in checking the SSRS config I note this little notification that the SQL admin hadn’t actually completed the SSRS setup for the Web Service URL
On the SQL Server open Start > Microsoft SQL Server Reporting Services > Report Server Configuration Manager and navigate to Web Service URL
Now you can just hit Apply here and SSRS will configure its backend site for HTTP, but you should really stick an SSL cert in there and configure HTTPS
It’s also pretty likely if the Web Service wasn’t configured, that the Web Portal and Database aren’t configured either.
So lets setup the backend database for SSRS. This is for the SSRS service itself and not our monitoring reports, on the database tab click Change Database
In the Change Database wizard, click Create new report server database then Next.
Specify which instance that SSRS can store its data in. Check with your SQL admin, but I typically stick it in the SkypeReporting instance as you should separate the backend and reporting to prevent SSRS causing load issues on the FrontEnd SQL.
Click Test Connection and check everything is okay, then click Next
Check the Database Name matches your requirements adjust as required and click Next
Again, check the Authentication Type matches your specific requirements and click Next
Check the summary page and click Next
Watch the pretty progress bars as SSRS configures its backend, once it’s done. Click Finish
Now that all that’s done, let’s check the Web Portal URL.
Click Web Portal URL on the left, check the URL is suitable for your deployment and click Apply (You can setup HTTPS afterward)
Now head back to your FrontEnd/Management Server and try to deploy the reports again. (Press Back then Next to keep your current settings)
Tada! We can deploy our reports.
If you need to setup HTTPS, you can find these settings in Web Service URL and Web Portal URL on the SSRS config tool. Just click on Advanced. (You will need to have a relevant cert installed in IIS already)
Hope this helped someone, till next time.