Link to home
Start Free TrialLog in
Avatar of Ryan McCauley
Ryan McCauleyFlag for United States of America

asked on

Unhandled exception (sometimes) in SSRS 2016 Native mode

We're currently using SSRS 2016 (the unpatched RTM) in Native mode and we've run into an issue that occurs rarely, but often enough to be a problem. When viewing a report, leaving it up on the screen for a while (more than a few minutes, but it doesn't always occur) and then coming back later and trying to expand a group or open a separate segment of the report results in an exception:

Sys.Webforms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500

Unfortunately that's pretty generic and not much help - I found an ASP.NET 4.0.30319.0 "Warning" (Event ID 1309) in the server's application event log that has a bit more detail (snipped a bit to show what seems like the relevant portions):

Event code: 3005
Event message: An unhandled exception has occurred.
(Snip)
Event detail code: 0
 
Application information:
    Application domain: ReportServer_MSSQLSERVER_0-34-131190290606090156
    Trust level: RosettaSrv
    Application Virtual Path: /ReportServer
    Application Path: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer\
    (Snip)
 
Process information:
    Process ID: 1600
    Process name: ReportingServicesService.exe
    (Snip)
 
Exception information:
   Exception type: ArgumentNullException
    Exception message: Value cannot be null.
Parameter name: exception
   at System.Web.UI.AsyncPostBackErrorEventArgs..ctor(Exception exception)
   at System.Web.UI.PageRequestManager.OnPageError(Object sender, EventArgs e)

Has anybody seen this before? It's occurring on all three of our servers (we have a scale-out deployment), but it only happens once every few days or so (about once/week per server). I don't think it's not a strict timeout, as I've let a report sit open on the site for hours and then browsed around with no issue at all.

There's a CU out for SQL 2016 that we're going to apply in our lab to see if that resolves it, but I wanted to see if anybody here had thoughts before we do that.
SOLUTION
Avatar of Megan Brooks
Megan Brooks
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Ryan McCauley

ASKER

This occurs on the native SSRS site when viewing a report - we're not embedding anything or doing any non-standard rendering. If there are other options for rendering, I'm happy to try those but I thought it was just the HTML renderer - it appears to be entirely handled by IIS.

I figured the CU is the best place to start - we'll be testing those next week and I'll post here if it resolves the issue (I'm not hopeful based on the released notes, but I'd love to be pleasantly surprised).
CU2 came out today. It seems to contain a number of additional SSRS fixes.
We're trying to reproduce this error in our UAT environment - once we're able to do that, we'll be applying CU2 to see if it resolves it and then I'll update the thread.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Final resolution wasn't suggested by any other participants.
Ouch, that would do it!