I am trying to access a report on a new install of ReportServer via a url and cannot get past error 404.
The url I am trying is (assuming the ID is the number that appears on the top of the report edit screen in ReportServer but could not find any documentation on this):
I have tried using key= and get the same response. I can access the login screen with the same link just using:
http:///reportserver
The Admin documentation says there should be a “reportserverbasedir” before /reportserver, but does not show anything in the examples as to what that path might be, so I have no idea what I am missing or what “reportserverbasedir” should be if it is needed.
I have entered that, applied it, and it still asks for a login on running from a url. Do I have to restart the server to get that picked up or is there something else I am missing?
2nd question, is there a way to allow all reports to be exported without login? It would be pretty annoying to have to add every report to that list for sites that have hundreds of reports available to users, we plan to call the reports from our app in browser windows for each report.
First question is easy: For the new configuration to take effect, you have to reload the config cache. For this open the ReportServer Terminal: In your browser press ctrl+alt+t, then type “config reload”. The config as well as the admin guide should have some more info on the terminal.
Second question: As far as I know there is currently no alternative to listing all reports seperately, but maybe there is a workaround. I’ll see what we can come up with and let you know.
Hey Thorsten,
Thanks for the quick response, but it still asks for the login is required after doing the config reload. I do get a confirmation that the reload happened in the terminal window, but after doing the reload it still prompts for the user login if using the ID or KEY values as the parameter on the url.
Thoughts on what to check?
Another item that just happened in playing around, I set up a scheduled job that I wanted to run in just a couple minutes so set the “All 1 days” value to “0” and now the scheduler throws a division by zero error when ever that job is clicked on, so it won’t run and I can’t get rid of it. How can I kill that job to re move it from the server?
wow .. that is a bumpy start you are having. Sorry for this.
For the first one. Which URL are you using? For the httpauthexecute to take any effect you need to use the “httpauthexport” servlet instead of the “reportexport” servlet. That is,
sorry, I forgot to mention this. The user and password in the configuration need to be added to the url (and do not have to match the user’s id with which the report is actually run). That is, if you defined username: user and password: pwd then the URL needs to be
The idea is that in the file you specify a “bogus” user and password that can be used within the URL but does not give away an actual username and password which may allow someone to login. Since a report always needs to be run with a specific user (for example, if a report uses a user variable) you additionally need to specify the ID of the user with which the report is to be run.