April 15, 2016 at 11:25 am
We recently installed SSRS on new servers. Everything went fine in our DEV area.
We followed the steps on our production server. We can access the reports while on the production server via: http://localhost/Reports but when we try to access the reports from our desktops via http://[servername]/Reports, the reports are not accessible. Even on the server itself, if we try http://[servername]/Reports, the reports are not accessible.
First thought was firewall was blocking port 80, but I can telnet to the server over port 80 with no issues.
What are we missing that is causing this? Our "server management teams" claim they are configured the same, but something is not right. Anyone have any ideas or know what could be causing this?
April 15, 2016 at 12:33 pm
is there a specific error? what if you try https?
Lowell
April 15, 2016 at 1:04 pm
https:// does not work. Says "can't be redirected".
When trying to access the reports with normal http://, we get a prompt for "Windows Security" asking for Username / Password. No account we try grants us access and after the third attempt, the page goes blank. No specific error, just a blank page.
April 15, 2016 at 1:18 pm
i think it's related to permissions; a lot of the time someone might get a permissions error that says
"User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed."
i've fixed that issue before like this, maybe this will help?
connect to local host from the SSRS server itself.
add some users in both places as seen in this screenshot,and then try to connect as one of those users.
Lowell
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply