Compartir a través de

SSRS Reports timed out with '503' error | SharePoint 2013 |

  • Artículo

I was working with a customer who has issue with SSRS reports which keeps in spinning for around 2 minutes and end up with throwing following error in SharePoint 2013 farm environment. But the normal reports are generating successfully which takes less than a minute to load.

 

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

and you may see following time out exception in ULS Logs...

08/15/2014 10:59:49.66* w3wp.exe (0x1130) 0x2C78 SharePoint Foundation Service Connections ev2x Verbose ...om the socket did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. ---&amp;gt; System.Net.Sockets.SocketException: The I/O operation has been aborted because of either a thread exit or an application request at System.ServiceModel.Channels.SocketConnection.HandleReceiveAsyncCompleted() at System.ServiceModel.Channels.SocketConnection.OnReceiveAsync(Object sender, SocketAsyncEventArgs eventArgs) --- End of inner exception stack trace --- at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult.End(IAsyncResult result) at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)</ExceptionString>...

08/15/2014 10:59:49.66* w3wp.exe (0x1130) 0x2C78 SharePoint Foundation Service Connections ev2x Verbose ...<InnerException><ExceptionType>System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The I/O operation has been aborted because of either a thread exit or an application request</Message><StackTrace> at System.ServiceModel.Channels.SocketConnection.HandleReceiveAsyncCompleted() at System.ServiceModel.Channels.SocketConnection.OnReceiveAsync(Object sender, SocketAsyncEventArgs eventArgs)</StackTrace><ExceptionString>System.Net.Sockets.SocketException (0x80004005): The I/O operation has been aborted because of either a thread exit or an application request at System.ServiceModel.Channels.SocketConnection.HandleReceiveAsyncCompleted() at System.ServiceModel.Channels.SocketConnection.OnReceiveAsync(Ob...

I had a deep drive in to research on this issue by making use of articles and my energetic lab and found this may due to the default timeout value in Request Management Service..

Basically, If the Request Management service is enabled, it manages all incoming requests by evaluating logic rules against the user requests in order to determine what\which action to take and which machine or machines (targets) in the farm should handle the request.

By default the Request time out value for Request Management service are as follows,

RequestTimeout : 00:01:40
RequestExecutionTimeout : 01:00:00

So the error throws from RM service for those reports who take more than 1 minute to generate the report.

If you do not have any defined rules in Request management Service other than the by default value, you may keep stop the RM service in your farm. If you would like to keep the RM Service running, then go ahead and increase the time out value by making use of following PowerShell script.

 

$waUrl = "URLofWEbApp"

$wa = Get-SPWebApplication $waUrl

$rmSettings = $wa | Get-SPRequestManagementSettings

$req=$wa.RequestManagementSettings

$timeout2= New-TimeSpan -minutes 5

$req.Requesttimeout=$timeout2

$req.update()

Happy Troubleshooting..

Comments

  • Anonymous
    January 01, 2003
    Hello Manjunath,

    As you may already aware of Request management service is not available in SharePoint 2010. In your scenario, are you getting 503 service unavailable exception? also same same error mesage as mentioned in above article? You may have to look at the logs to see more information on the exception after increasing the logging level to Verbose, from SharePoint perspective. (Default log location: C:Program FilesCommon Filesmicrosoft sharedWeb Server Extensions14LOGS). As far as I know there are some default parameter values from SSRS perspective in the RSReportserver configuration file. Ref: https://msdn.microsoft.com/en-us/library/ms157273(v=sql.105).aspx which you may have to look at it.
  • Anonymous
    May 21, 2015
    HI Sjitha, I am getting this error in SharePoint 2010 while generating SSRS report.
  • Anonymous
    May 21, 2015
    HI Sjitha, I am getting this error in SharePoint 2010 while generating SSRS report.
    can you please suggest me how it can be resolved. for me if report takes more than 3 minutes, the error will be thrown, thanks
  • Anonymous
    June 25, 2015
    The solution is working. Thanks; There is a typo in the script

    Sreq.Requesttimeout=$timeout2

    the variable should be $req instead of Sreq.
  • Anonymous
    July 02, 2015
    Thank you Bhaskar. I updated the article.
  • Anonymous
    July 03, 2015
    It was very usefull information and keep updating with new topics
    http://staygreenacademy.com/sharepoint-training/