Quantcast
Viewing all articles
Browse latest Browse all 10045

SSRS 2016 GA: Server error in ReportServer Application for non-Admins.

We installed SQL Server 2016 this week, and migrating reports from older versions onto the new SSRS instance.

We segregate reports/datasets into folders and then assign certain users to access each folder. As an Administrator, I can use Report Manager to navigate the folders and execute any of the reports successfully. I can also navigate the reportserver URL successfully at http:<server>/ReportServer/Pages/ReportViewer.aspx?<report>.

I've assigned a non-admin user as a Browser on the Home directory. That user can log into Report Manager and navigate the folder structure, but when trying to run a report it gets an error in the reportserver application (shown below). The same user gets the same error in navigating to the reportserver URL (listed above).

Server Error in '/ReportServer' Application.


Access is denied.

Description: An error occurred while accessing the resources required to serve this request. The server may not be configured for access to the requested URL. 

Error message 401.2.: Unauthorized: Logon failed due to server configuration.  Verify that you have permission to view this directory or page based on the credentials you supplied and the authentication methods enabled on the Web server.  Contact the Web server's administrator for additional assistance.

I've set SSRS logging to level 4 in ReportingServicesService.exe, but haven't found anything helpful to me in the resulting logging:

rshost!rshost!18d4!06/29/2016-18:13:07:: v VERBOSE: AcceptCallback(): accepted new connection pipeline=0x000000E3180A1B90...
rshost!rshost!1a08!06/29/2016-18:13:07:: v VERBOSE: ThreadContinuePipeline: processing request on pipeline=0x000000E3180A1B90, state=0, IOError=0, node=0.
rshost!rshost!1a08!06/29/2016-18:13:07:: v VERBOSE: Processing request pipeline=0x000000E3180A1B90, callback=0x180a2620, callback->pipeline=0x000000E3180A1B90, id=18086456109962363304, connid=18086456109425492386 ...
webserver!ReportServer_0-1!1a08!06/29/2016-18:13:07:: v VERBOSE: Logging usage IP: 192.168.30.1, Username: {Domain}\scottlyons
runningrequests!ReportServer_0-1!1a08!06/29/2016-18:13:07:: v VERBOSE: User map'<Users><User><Name>{Domain}\scottlyons</Name><Paths><Path>http://{Server}/ReportServer/Pages/ReportViewer.aspx?{Report}&amp;rc:showbackbutton=true</Path><NrReq>1</NrReq></Paths></User></Users>'
library!ReportServer_0-1!1a08!06/29/2016-18:13:07:: i INFO: Call to GetItemTypeAction(/{Report}).
appdomainmanager!DefaultDomain!1bf4!06/29/2016-18:13:07:: v VERBOSE: GetAppDomainId for AppDomain type 'WindowsService' found AppDomain 2
servicecontroller!DefaultDomain!1bf4!06/29/2016-18:13:07:: v VERBOSE: ServiceAppDomainController::ServiceMaintenanceInternal - Mark the WindowsService (worker) AppDomain as active.
servicecontroller!DefaultDomain!1bf4!06/29/2016-18:13:07:: v VERBOSE: ServiceAppDomainController::MarkProcessAsActive - Mark the WindowsService (worker) AppDomain as active.
library!ReportServer_0-1!1a08!06/29/2016-18:13:07:: i INFO: Call to GetItemTypeAction completed. Returns 2.
rshost!rshost!1a08!06/29/2016-18:13:07:: v VERBOSE: HttpPipelineCallback::EndOfRequest(): continue pipeline=0x000000E3180A1B90.
rshost!rshost!18d4!06/29/2016-18:13:07:: v VERBOSE: ThreadContinuePipeline: processing request on pipeline=0x000000E3180A1B90, state=2, IOError=0, node=0.
appdomainmanager!DefaultDomain!1bf4!06/29/2016-18:13:08:: v VERBOSE: GetAppDomainId for AppDomain type 'WindowsService' found AppDomain 2
servicecontroller!DefaultDomain!1bf4!06/29/2016-18:13:08:: v VERBOSE: ServiceAppDomainController::ServiceMaintenanceInternal - Mark the WindowsService (worker) AppDomain as active.
servicecontroller!DefaultDomain!1bf4!06/29/2016-18:13:08:: v VERBOSE: ServiceAppDomainController::MarkProcessAsActive - Mark the WindowsService (worker) AppDomain as active.

My Reporting Services configuration is set to use the Virtual Service Account.

If I add the Browser user to the local Administrators group on the server, then the reports execute successfully. Remove it, they fail again.

I appreciate any and all help as I've gone in circles for a long time on this! Hoping there's a file system file with bad permissions or something simple to fix. Are there any suggestions?



Viewing all articles
Browse latest Browse all 10045

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>