Timeout from WijeJAspNetHost.aspx when running a report in SSRS

Answered
0
0

I have a WiseJ app that includes the SSRS Report Viewer wrapper class.  One of my customers is encountering an error when trying to render a certain report.  What they see is that ReportViewer displays its “Loading…” message for a while, and then a blank screen.   When I run the same report on my system after about 90 seconds I’m presented with a 39,000 page report.   On the customer system, they find this (redacted) in the Windows Event Log:

Event code: 3001
Event message: The request has been aborted.
Event time: 8/23/2023 3:40:16 PM
Event time (UTC): 8/23/2023 7:40:16 PM
Event ID: a10163d07c4c4be29d5b7c50c9e4c97c
Event sequence: 1379
Event occurrence: 11
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/ROOT/_____________-1-133372826026097997
Trust level: Full
Application Virtual Path: /_____________
Application Path: D:\_____________\_____________\code\Server.WebUI\
Machine name: _____________

Process information:
Process ID: 11700
Process name: w3wp.exe
Account name: _____________

Exception information:
Exception type: HttpException
Exception message: Request timed out.

Request information:
Request URL: https://_____________:443/_____________/Wisej.AspNetHost.aspx?sid=84f47017-3d96-d503-22a6-901dc25253f2&_cid=id_513&_sc=2
Request path: /_____________/Wisej.AspNetHost.aspx
User host address: —

What is logging this event – is this coming from WiseJ?  From IIS itself?  Any idea what timeout has expired?  How to increase that timeout?

  • You must to post comments
Best Answer
1
0

Hi Carl,

Since the report is very large, the request is what is timing out.

The error is coming from IIS, I would suggest that you increase the “Connection time out” value of your IIS Site.

Best,
Alaa

  • Carl Daniel
    That’s what we concluded as well – in 20+ years of working with ASP.NET on IIS I’ve never seen that timeout before! In this case, it turned out that the database server was vastly under-provisioned for memory, making the query take considerably longer than it should. Good to have discovered that timeout setting though. -Tnx.
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.