dgosbell
commented
2 years ago So ReportService2010.asmx was introduced in SQL Server 2008R2 and is valid in any version after that.
the examples use "reportserver_sql16", which so far as I can tell isn't standard either, and is confusing.
I think this is the main issue here as the default report service uri for a default instance is http://ssrsservernamehere/reportserver the reportserver_sql16 would be the default if you installed SSRS in a named instance called "sql16"
I think the documentation is what needs fixing here since people can set both the portal uri and the service uri to whatever they want in the Report Server Configuration Tool.
Do you want to request a feature or report a bug? Feature and Bug
What is the current behavior? When running code like Get-RsDataSource, the ReportServerUri assumes "ReportService2010.asmx" if it's not given, which isn't valid on SSRS 2012 or 2016, just to name two versions. (" Failed to establish proxy connection to http://ssrsservernamehere/ReportService2010.asmx : There was an error downloading 'http://ssrsservernamehere/ReportService2010.asmx")
Additionally, the examples use "reportserver_sql16", which so far as I can tell isn't standard either, and is confusing. Changing either the default or the document to reflect more typical use cases would be really helpful for people who only dabble in SSRS.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
What is the expected behavior? That I don't need to know why it's throwing an error about why "ReportService2010.asmx" isn't working.
Which versions of Powershell and which OS are affected by this issue? Did this work in previous versions of our scripts? platform/OS is irrelevant.