January 15, 2019 at 1:32 pm
I have a SSRS 2017 installation that is working fine using the default URL (eg http://<servername>/Reports). There are no problems using the portal to run reports either local or remote.
I have added a second URL (eg http://TestURL/Reports) for both the web service URL and web portal URL using the SSRS Configuration Manager. No errors were reported but when I try to open the second URL, Edge, IE and Chrome report the page cannot be found.
There are no obvious errors in any of the logs (SSRS, SQL, IE, etc) and everything seems to be set up correctly.
Any thoughts or suggestions would be appreciated.
January 15, 2019 at 1:38 pm
dlander525 - Tuesday, January 15, 2019 1:32 PMI have a SSRS 2017 installation that is working fine using the default URL (eg http://<servername>/Reports). There are no problems using the portal to run reports either local or remote.
I have added a second URL (eg http://TestURL/Reports) for both the web service URL and web portal URL using the SSRS Configuration Manager. No errors were reported but when I try to open the second URL, Edge, IE and Chrome report the page cannot be found.
There are no obvious errors in any of the logs (SSRS, SQL, IE, etc) and everything seems to be set up correctly.
Any thoughts or suggestions would be appreciated.
Did you restart the service after the changes? The service starting/restarting is what starts the process for the URL registrations.
Sue
January 15, 2019 at 1:55 pm
The service restarts inside the config manager when the URLs are created but have also restarted outside the config manager.
The original URL (eg http://<servername>/Reports) works fine but the new one (eg http://TestURL/Reports) still get the cannot find page error.
January 15, 2019 at 2:52 pm
dlander525 - Tuesday, January 15, 2019 1:55 PMThe service restarts inside the config manager when the URLs are created but have also restarted outside the config manager.
The original URL (eg http://<servername>/Reports) works fine but the new one (eg http://TestURL/Reports) still get the cannot find page error.
Then it sounds like the added one really didn't get added. Not sure if you see it in Reporting Services Configuration Manager...on the Advanced page for the reservations but you can run the following from the command line on the report server to see all of the reserved URLs: netsh http show urlacl
Sue
January 16, 2019 at 8:19 am
Sue_H - Tuesday, January 15, 2019 2:52 PMdlander525 - Tuesday, January 15, 2019 1:55 PMThe service restarts inside the config manager when the URLs are created but have also restarted outside the config manager.
The original URL (eg http://<servername>/Reports) works fine but the new one (eg http://TestURL/Reports) still get the cannot find page error.Then it sounds like the added one really didn't get added. Not sure if you see it in Reporting Services Configuration Manager...on the Advanced page for the reservations but you can run the following from the command line on the report server to see all of the reserved URLs: netsh http show urlacl
Sue
Had run netsh already and confirmed URL as well as checking rsreportserver.config
Everything I can check says the second URL is good and cannot open it.
January 16, 2019 at 10:35 am
dlander525 - Wednesday, January 16, 2019 8:19 AMSue_H - Tuesday, January 15, 2019 2:52 PMdlander525 - Tuesday, January 15, 2019 1:55 PMThe service restarts inside the config manager when the URLs are created but have also restarted outside the config manager.
The original URL (eg http://<servername>/Reports) works fine but the new one (eg http://TestURL/Reports) still get the cannot find page error.Then it sounds like the added one really didn't get added. Not sure if you see it in Reporting Services Configuration Manager...on the Advanced page for the reservations but you can run the following from the command line on the report server to see all of the reserved URLs: netsh http show urlacl
Sue
Had run netsh already and confirmed URL as well as checking rsreportserver.config
Everything I can check says the second URL is good and cannot open it.
As long as it's all configured correctly, you are using a different port and the port is not being used by anything else and the same for the url, it works.
Make sure the port or url is not being used by something else.
Sue
January 16, 2019 at 11:28 am
Can the default URL and the test one use the same port - 80 in this case?
January 16, 2019 at 2:00 pm
dlander525 - Wednesday, January 16, 2019 11:28 AMCan the default URL and the test one use the same port - 80 in this case?
They can. I just re-read your original post - TestURL needs to resolve to something. Did you just add this Host Header Name when you got to the advanced page?
Sue
January 16, 2019 at 2:54 pm
Yes - clicked on Advanced button for both Web Service URL and Web Portal URL. In the Advanced Multiple Web Site Configuration dialog, clicked Add, selected Host Header Name, entered TestURL then OK
January 16, 2019 at 4:02 pm
dlander525 - Wednesday, January 16, 2019 2:54 PMYes - clicked on Advanced button for both Web Service URL and Web Portal URL. In the Advanced Multiple Web Site Configuration dialog, clicked Add, selected Host Header Name, entered TestURL then OK
And if that's all that was done, it won't work. TestURL has to resolve to the IP of the report server. You need a DNS entry as well.
Sue
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply