Search

Custom Security Extensions for SQL Server 2008 R2 Reporting (SSRS) - "Temporary User issue" by Har P

Active

1
0
Sign in
to vote
Type: Bug
ID: 774345
Opened: 12/14/2012 2:55:13 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
We are using Custom Security extension for user authentication (form based) for SSRS reporting access, we are getting an error

"The remote server returned an error: (500) Internal Server Error." for the first time click from web based application or even if access directly the report manager, for the second time click the report page gets loaded. When i tried to log the custom security extension code, on the first click we are getting "Temporary User" in GetUserInfo() method, so as its not a valid user to get the access we get http 500 error on the screen. This happens when we restart the Reporting Services and click on any of the reports in Report manager for the first time, but it works on the second click.

Have tested with many scenarios by tweaking the custom code and also logging the errors to trace the issue, but we get "Unknown" or "Temporary User" on the first click inside GetUserInfo() method. On the second click we get access to the reporting services which is strange.

How to handle temporary user in custom security extension code so that we can avoid the Http 500 error before it loads with proper sign on user. As per the analysis made, the issue is with Microsoft Product (SSRS), once the temporary user is created as per the CU3 release from Microsoft, but its not handled to check the proper user authentication until its found.

It seems Microsoft Product issue, any fix/resolution from Microsoft much appreciated.


Details (expand)

Product Language

English

Version

SQL Server 2008 R2 SP1

Category

Reporting Services

Operating System

Windows Server 2008 Enterprise

Operating System Language

English

Steps to Reproduce

Steps to Reproduce:
1. Restart the Reporting Services @ Services.msc manager or Open Reporting Services Configuration Manager connect to the server, Stop the services and restart it again
2. Try to access Reporting Manager link, we get "The remote server returned an error: (500) Internal Server Error."
3. Click again (or refresh the page) reporting manager gets loaded and we can access the reports

Actual Results

Once the reporting services restarted, we are getting "The remote server returned an error: (500) Internal Server Error." for the first time access and it works perfect for the second time click or reporting page refresh

Attached is the Log file for the error generated after the Reporting Services restarted and first time access to the Report Manager

Expected Results

As per the SSRS, once we restart the services there should not be any error message thrown for the report access via Report Manager. This needs to be handled in the product

Platform

X64

Virtualization

 
File Attachments
File Name Submitted By Submitted On File Size  
ReportServerService__12_14_2012_11_00_44.log (restricted) 12/14/2012 -
Sign in to post a comment.
Sign in to post a workaround.