Symptoms

Consider the following scenario:

  • You have User Account Control (UAC) enabled on a domain-joined computer.

  • You install SQL Server 2016 Reporting Services on this computer.

  • You disconnect the computer from the domain.

  • You use a web browser¬†to access the SSRS web portal.

In this scenario, the portal does not open. Instead, you receive a "The service is not available" error message. Additionally, error messages that resemble the following are logged in the log file for the SSRS web portal:

Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!a4!<Time stamp>:: i INFO: [kmu6t20u]: ::1: GET /api/v1.0/me - Response 200 - 0:00:00.6646669
Microsoft.ReportingServices.Portal.WebHost!library!a4!<Time stamp>:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 1355, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!a4!<Time stamp>:: e ERROR: [m4amitl6]: OData exception occurred: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. .
Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!a4!<Time stamp>:: i INFO: [m4amitl6]: ::1: GET /api/v1.0/ServiceState - Response 500 - 0:00:00.1205496


Note This issue does not occur if you have elevated permissions on the web browser.

Resolution

The issue was first fixed in the following cumulative update of SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:


More Information

SQL Server 2016 Reporting Services has introduced a new log file for the new portal. Those logs start with "Microsoft.ReportingServices.Portal." For example, Microsoft.ReportingServices.Portal.WebHost_06_19_2016_15_59_43.log.

The old logs still exist for any operation that interacts with the Report Server, including calls to the SOAP endpoint, report execution, and background operations.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×