Solved

Sharepoint 2013/SSRS error long reports

Posted on 2014-03-11
11
483 Views
Last Modified: 2016-06-04
We are upgrading our Sharepoint to 2013.  I have several reports that take about 3minutes to run because of a slow ODBC connection used by a linked server.
They ran fine in Sharepoint 2007.  They run fine in Visual Studio 2013.  However they return this error after about 1.5 minutes.

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

Some reports run fine, it is only the ones that take longer than 1.5 minutes.  I have tried adjusting every timeout option I can find.  I have tried adding a connection timeout to the dataset.  I have updated the report processing options to not timeout.  I have added this to the web config file.
<httpRuntime maxRequestLength="51200" requestValidationMode="2.0" executionTimeout="1000"/>
 
No luck.  Please help!!
0
Comment
Question by:vzorn
  • 5
  • 4
11 Comments
 
LVL 19

Expert Comment

by:Melih SARICA
Comment Utility
Which web.config ?

error 503 is service not avaiable
0
 
LVL 16

Expert Comment

by:DcpKing
Comment Utility
Have you considered re-designing the reports so that they actually run automatically in advance and it's only the presentation that happens on-demand?
0
 

Author Comment

by:vzorn
Comment Utility
That is not an option, we go live on Saturday.  
I have figured out the reports run as subscriptions and email just fine.  They just don't come up on the screen in the report viewer.
0
 
LVL 16

Expert Comment

by:DcpKing
Comment Utility
How big are the reports? i.e. how much information to they move. Don't forget that there are limits to how much data SSRS can pivot and render. If you're viewing them on relatively small machines they may be just running out of space for rendering, and, in my experience, SSRS just "doesn't" - no warnings, nothing. Just a blank screen!
0
 

Author Comment

by:vzorn
Comment Utility
This is the error:
Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 503

We have a brand new VM with Windows Server 2012, it is only using 25% of the capacity while the report runs.
0
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 
LVL 16

Expert Comment

by:DcpKing
Comment Utility
"We have a brand new VM with Windows Server 2012, it is only using 25% of the capacity while the report runs."

And, as you observe, reports run there and turned into (presumably) pdf files and emailed out work fine.

OTOH, reports running on workstations fail.

This points to a problem with the workstations. So far as I am aware, SSRS renders on the local machine. Therefore, if you are sending a lot of information to the SSRS rendering engine it can just fail, giving you nothing to look at! Personally, I managed to achieve that by sending about 30,000 rows to a tablix!

hth

Mike
0
 

Author Comment

by:vzorn
Comment Utility
I have been testing on the server itself not on a workstation.
Are there any settings I can change to allow SSRS to render for a longer period?
I am pretty sure it is timing out.  It always times out at 2 minutes.
0
 
LVL 16

Expert Comment

by:DcpKing
Comment Utility
What's taking the time? Is it the query or the data transfer? Can you tell, maybe, by running a failing report's query on the database into a table and then re-running a version of the report with the report just doing a straight select from the new table?

If it's the transport then you're pretty much screwed unless you can speed it up or change the timeout in either SSRS or Sharepoint (I'd imagine that it would be a Sharepoint poblem, as SSRS was running them ok in 2007. If the query then look to ways of speeding it up.

Mike
0
 
LVL 16

Expert Comment

by:DcpKing
Comment Utility
This may help for SSRS timeouts:

http://technet.microsoft.com/en-us/library/ms155782.aspx

There are also some suggestions here (I'm not a Sharepoint developer, but some are relevant to this problem:

http://blogs.msdn.com/b/mariae/archive/2009/09/24/troubleshooting-timeout-errors-in-reporting-services.aspx

Good luck!


Mike
0
 

Accepted Solution

by:
vzorn earned 0 total points
Comment Utility
Turns out we needed to turn of the Request Manager service since there was only one server in the farm.  Had to get Microsoft to help on this one.
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
It is helpful to note: This is a cosmetic update and is not required, but should help your reports look better for your boss.  This issue has manifested itself in SSRS version 3.0 is where I have seen this behavior in.  And this behavior is only see…
Viewers will learn how the fundamental information of how to create a table.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now