Report Manager - Timeout on searches

Question

Hi,

Whenever I perform a search using the search function in Native mode  on report manager I get the error (PFA).  can someone help me on this..

Thanks!

Jayakumar.J

Answer 1

Hi Jayakumar,

According to your description, when using the search function, you will get the error above. Right?

In Reporting Services, the default number of seconds after which a connection to the report server database times out is 120. While rendering a report, the reporting services need to store the exection information back to the report server database. The will cause the connection to be active. Once the connection is active more than 120 seconds, we will get the Timeout expired error.

In this scenario, when you use search in Report Manager, it will query the database again, it may exceed the default timeout value. To solve the issue, we can limit the returned data or increase the value for timeout. 
Please follow steps below:

1. Open the rsreportserver.config with Text Editior(e.g. Visual Studio, NotePad). By default, it is hosted in C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
2. Change the value for 'DatabaseQueryTimeout'. Valid values range from 0 to 2147483647.  A value of 0 specifies an unlimited wait time and therefore is not recommended.
3. Save the file, and then restart the Reporting Services to apply the changing.

For more information, please see: RSReportServer Configuration File

Also we suggest to go to see the Log files in

C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles

It will provide detail information about the error. Here are some similar threads below, please refer to the links below:

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/b80d7f29-b271-4845-b7be-df5a9b591ed2/ssrs-2008-connection-failure-timeout-or-low-disk-condition-within-the-database?forum=sqlreportingservices

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c35768b7-4fa7-4b63-acde-f9848673fe92/ssrs-reports-not-running-when-there-is-more-than-one-request?forum=sqlreportingservices

If you have any question, please feel free to ask.

Best Regards,
Simon Hou

Answer 2

Simon,

      Thanks for your reply. I have also  increased the Database Query Timeout earlier for around 30 minutes , but that doesnt helped me. Is there any other specific reasons for the Search error. And increasing the Datatimeout for infinite time will not solve our problem as we have only 5 reports in the specific folder and we are searching only those five RDL.Also as per the execution time it should not take much time right? Awaiting for your reply.

Thanks!

Jayakumar.J

Answer 3

You can find the specific reason by looking at the SSRS logs (i.e., C:\Program Files\.....).  Alternatively you can enable remote errors and have the reason displayed to the screen when i happens.  Feel free to post the error message.

Answer 4

JJordheim\Simon,

   Please find the below error message from the Log folder FYR.

Scenario: Assume that there are around 50 rdls in an folder. if i give the exact name of the Rdl in the search button, it gets filtered out. but if we give by using the first three letters of the RDL Name, it takes more time assume 10 minutes. FYI we have made the Database Query Timeout to 10 minutes. finally it errored out.

 ERROR: HTTP status code --> 200
-------Details--------
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors
   at Microsoft.ReportingServices.WebServer.ReportingService2010Impl.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, Property[] SearchOptions, SearchCondition[] SearchConditions, CatalogItem[]& Items)
   at Microsoft.ReportingServices.WebServer.ReportingService2010.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, Property[] SearchOptions, SearchCondition[] SearchConditions, CatalogItem[]& Items)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at Microsoft.SqlServer.ReportingServices2010.ReportingService2010.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, Property[] SearchOptions, SearchCondition[] SearchConditions)

   at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.<>c__DisplayClass2b.<FindItems>b__2a()

   at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)

   at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod()

   at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.FindItems(String folder, BooleanOperatorEnum booleanOperator, Property[] searchOptions, SearchCondition[] conditions)

   at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.FindItems(String folder, BooleanOperatorEnum booleanOperator, Property[] searchOptions, SearchCondition[] conditions)

   at Microsoft.ReportingServices.UI.SearchBox.GetSearchResults()

   at Microsoft.ReportingServices.UI.DetailedSearchResults.LoadItems()

   at Microsoft.ReportingServices.UI.SortableItems.Control_Init(Object sender, EventArgs args)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Web.UI.Control.OnInit(EventArgs e)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.AddedControl(Control control, Int32 index)

   at Microsoft.ReportingServices.UI.SharedArea.Control_Init(Object sender, EventArgs args)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Web.UI.Control.OnInit(EventArgs e)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.AddedControl(Control control, Int32 index)

   at Microsoft.ReportingServices.UI.SearchResultsPage.Page_Init(Object sender, EventArgs e)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Web.UI.Control.OnInit(EventArgs e)

   at System.Web.UI.Page.OnInit(EventArgs e)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
library!ReportServer_0-4!2384!09/16/2014-06:23:58:: Call to GetSystemPropertiesAction()

Awaiting For your reply.

Thanks!

Jayakumar.J

Answer 5

JJordheim\Simon,

        I have found an update on the search for button in the reporting manager Native mode. Basically the search for button works if we give the exact Report name or if we give the search character above 12 characters. Eg.,

01000 Reporting Change Configuration consider this as an report name. if we give the full character the search for works or atleast 01000 Report (12) characters the search for button works.

Can you please sort it  out if there is any setting that we can change that is limiting the search to twelve characters?

Thanks!

Jayakumar.J

Answer 6

Jayakumar,

Is there any more details in the log before or after that error message?  One thing to also consider is if this isn't a known issue that has been addressed in a cumulative update or service pack.  I recommend looking at the website below for the edition you have and reviewing the appropriate links.

http://sqlserverbuilds.blogspot.com/

Another thing to consider it maybe being related to your indexes or statistics.  You could try rebuilding the indexes on your database (which would rebuild trigger your statistics to be updated) and see its not related to the query not getting a good plan or something.

Lastly, you could try interacting with the method being used when searching. As indicated in the error message it is FindItems.  You might be able to get a better understanding of what is failing by interacting with it directly.

http://msdn.microsoft.com/en-us/library/reportservice2010.reportingservice2010.finditems.aspx

Answer 7

JJordheim,

     Thanks for the above links, i have checked the same for the SQL Server 2008 R2. I cant able to get any clue.Actually search is working only if we give @least 12 characters. is there any setting to change the same.

Also i have two  Folder in the native mode each folder comprises of more than 150 rdls. my Question is one folder responding time is quicker whereas another one takes atleast 3 minutes to open. FYI both folder resides in the same server.

Thanks!

Jayakumar.J