March 9, 2016 at 8:27 am
We are running SQL Server 2012, SP1 on Windows Server 2008 R2 Standard O/S. Just configured SSRS 2012 for the first time. Have a few questions that I am researching:
1. What URL should I give the user, the Report Manager URL or the Report Server Web Service URL? The Report Manager URL displays the Report Manager with the main reports folder. I am able to run the reports located within this folder. The Web Service URL displays the main reports folder via links in a simple text format (as a Directory) but I still can click on the main folder and get to the reports and execute the reports. The Report Manager URL Web Interface (GUI) appears to more friendlier. I have read where the Web Service URL (web service interface) allows for the integration of reports with other applications.
Report Manager URL: http://ServerName:80/Reports
Report Server Web Service URL: http://ServerName:80/ReportServer
2. Does the port (80) needs to be kept in the URL? I notice when I copy/paste it into address bar, it appears the 80 (default port) is removed.
3. Should Internet Explorer be used as the preferred browser when using SSRS? Are there advantages using IE verses Google or other browsers?
Thanks in advance, Kevin
March 9, 2016 at 8:56 am
Two other items, I am researching:
I read that Report Manager has a quirk and you should run it in administrator mode for all the features to work. To do this , select Run as Administrator while opening Internet Explorer. Should the users/developers run IE in administrator mode also? What features does not work if you do not run in administrator mode?
In Report Manager, under Site Settings, under Security page, there is a BUILTIN\Administrators Group. How may I determine who is included in that group?
Thanks in advance, Kevin
March 9, 2016 at 9:15 am
Hi Kevin,
1. You should give the Users the Report Manager URL. It will enable them to use the report manager and associated features (e.g. subscriptions). The Report Server URL provides access to the underlying webservice and is actually used by the report manager.
For the devs, the Report Server URL is used when deploying reports or when connecting via Report Builder.
2. Since your service is using port 80 you can remove it from the URL as that is the default port.
3. IE should be used as the preferred browser and should be run in compatibility mode. At SSRS 2012 there are still rendering issues though other browsers (Chrome reports render blank etc). There are some javascript fixes you can do to get reports to render properly however the report manager can still look wrong.
I think SSRS still uses old quirks mode stuff so IE works best.
4. I don't think that's the case, SSRS security and features are managed via roles. The only time it makes a difference is if you are in the BUILTIN\Administrators group (see q5).
The are issues with ACS. If you are an admin on the server if you connect with IE it can say you aren't authorised. Running IE as admin fixes this.
SSRS itself uses Role based security, you can add people to the administrator role there if required.
5. BUILTIN\Administrators is the local administrator group on the server. It's most likely the Administrator user and maybe your domain admins. You can check under Local Users and Groups in the Server Manager.
If you are running as admin on the server you get admin access in SSRS, it's there for when you install.
I'd recommend creating an AD group for the report devs and assigning SSRS roles and access to that.
March 15, 2016 at 9:37 am
Spiff,
Thanks for the excellent responses.
Kevin
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply