Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1007
  • Last Modified:

Sharepoint 2013/SSRS error long reports

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
vzorn
Asked:
vzorn
  • 5
  • 4
1 Solution
 
Melih SARICAIT ManagerCommented:
Which web.config ?

error 503 is service not avaiable
0
 
DcpKingCommented:
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
 
vzornAuthor Commented:
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
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
DcpKingCommented:
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
 
vzornAuthor Commented:
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
 
DcpKingCommented:
"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
 
vzornAuthor Commented:
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
 
DcpKingCommented:
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
 
DcpKingCommented:
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
 
vzornAuthor Commented:
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

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now