Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Large report timing out after 10 mins or 600 seconds

The same report works if I reduce the timeframe so it has to be a timeout issue.

Orion Web log:

WARN SolarWinds.InformationService.Contract2.InfoServiceProxy - (null) Support! -- LONG RUNNING QUERY

Followed by:

ERROR SolarWinds.Orion.Web.InformationService.InformationServiceProxy - (null) Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Changed the following in web.config:

To:

SWNetPerfMon does not reference any 600 second timeout:

! Connection timeout in seconds
Timeout=20

!
! Database Command timeout in seconds
CommandTimeout=90


!
! SqlCommand.CommandTimeout in seconds
SqlCommandTimeout=0

however tried the following:

! Connection timeout in seconds
Timeout=20

!
! Database Command timeout in seconds
CommandTimeout=3600


!
! SqlCommand.CommandTimeout in seconds
SqlCommandTimeout=0

SQL Connection was set to 600 secs, increased to 3600 and even tried 0.

Still after 10 mins I get the following error:

"Report resource failed to properly initialize" and the same error in Orion Web log.

This is the error report:

URL: http://localhost:80/Orion/Reports/Preview.aspx?ReportID=232&amp;ReturnTo=aHR0cDovL2xvY2FsaG9zdC9vcmlvbi9yZXBvcnRzL3ZpZXdyZXBvcnRzLmFzcHg=&amp;waitid=2f380967b2f14088ad15b58bef1907a6
Referrer: http://localhost:80/Orion/Reports/Preview.aspx?ReportID=232&amp;ReturnTo=aHR0cDovL2xvY2FsaG9zdC9vcmlvbi9yZXBvcnRzL3ZpZXdyZXBvcnRzLmFzcHg=&amp;waitid=2f380967b2f14088ad15b58bef1907a6
Message: Error: A query to the SolarWinds Information Service failed.
ErrorSite: OrionWeb.InformationServiceProxy.PropagateException
ErrorType: SolarWinds.Orion.Web.InformationService.SwisQueryException
Stack: 
at SolarWinds.Orion.Web.InformationService.InformationServiceProxy.PropagateException(Exception e)
at SolarWinds.Orion.Web.InformationService.InformationServiceProxy.Query(String query, IDictionary`2 parameters, Boolean useSeparateExecutionContext, Nullable`1 dataProviderTimeout)
at SolarWinds.Orion.Web.InformationService.InformationServiceProxy.Query(String query, IDictionary`2 parameters)
at SolarWinds.Orion.Core.Reporting.DataTableQueryDynamic.Query(IQueryResult result)
at SolarWinds.Orion.Core.Reporting.DataTableQueryBase.QueryInternal()
at SolarWinds.Orion.Core.Reporting.DataTableQueryBase.Query()
at SolarWinds.Reporting.Impl.Tables.DataTableRequester.DoQuery()
at SolarWinds.Reporting.Impl.Tables.DataTablePresenterProcessor.PrepareForRendering(DataTableRequester requester)
at SolarWinds.Reporting.Impl.Rendering.TableRenderer.Render(IRenderCellContext host, HtmlTextWriter control)
at SolarWinds.Orion.Web.Reporting.ReportCellWrapper.<>c__DisplayClass9_0.b__1()
at SolarWinds.Orion.Web.Reporting.ReportCellWrapper.WithinExceptionCatcher(Func`1 errorMessage, Action fnCode)
-- Inner Exception
  Message: RunQuery failed, check fault information.
           Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
  Type: System.ServiceModel.FaultException`1[[SolarWinds.InformationService.Contract2.InfoServiceFaultContract, SolarWinds.InformationService.Contract2, Version=2020.2.1.4312, Culture=neutral, PublicKeyToken=null]]
  Stack: 
at SolarWinds.InformationService.InformationServiceClient.InformationServiceCommand.CreateFaultException(Message message)
  at SolarWinds.InformationService.InformationServiceClient.InformationServiceCommand.HandleQueryResponse(Message message)
  at SolarWinds.InformationService.InformationServiceClient.InformationServiceCommand.ExecuteReader(CommandBehavior behavior)
  at SolarWinds.InformationService.InformationServiceClient.InformationServiceCommand.ExecuteDbDataReader(CommandBehavior behavior)
  at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
  at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
  at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
  at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
  at SolarWinds.Orion.Web.InformationService.InformationServiceProxy.<>c__DisplayClass26_0.b__0(InfoServiceProxy n)
  at SolarWinds.Orion.Core.Common.ChannelProxy`1.CallMethodWithPool[TResult](Func`2 fnc, Boolean retryCall)
  at SolarWinds.Orion.Core.Common.ChannelProxy`1.Invoke[TResult](Func`2 fnc, ChannelProxyBehavior behavior, String methodName)
  at SolarWinds.Orion.Core.Common.ChannelProxy`1.Invoke[TResult](Func`2 fnc, ChannelProxyBehavior behavior)
  at SolarWinds.Orion.Web.InformationService.InformationServiceProxy.Query(String query, IDictionary`2 parameters, Boolean useSeparateExecutionContext, Nullable`1 dataProviderTimeout)

IIS timeout is 120 seconds

Any other ideas where the timeout of 600s could be set that is causing our reports to fail?

Find more posts tagged with

Reports

timeout

Accepted answers

All comments

KMSigma.SWI

Is it possible for you to export the report and attach it? This might prove helpful in understanding the cause of the timeout.

Have you reviewed Large report error: Unexpected Website Error "Request timed out." (solarwinds.com) to see if it offers any troubleshooting help?

dman4cloud

I tried the suggestion in the large report error article, changed to 3600 as shown above but makes no difference, I even made sure there was no time set to 600 in the web.config but the error still appears after 600 seconds. I am not sure how to attach the report but this is the export:

AvailabilityNode Availability - This Yeard8cfe23f-12b3-4203-ad64-d51fa48f4dd400000000-0000-0000-0000-000000000000LeftDateSystem.DateTimeDateTimeNotSpecifiedfalsefalsefalsetruefalsetruefalseTimestampResponseTimeHistoryResponse Time HistoryOrion.ResponseTime|ObservationTimestamp|ResponseTimeHistory00000000-0000-0000-0000-000000000000Leftfalsefalse12.121orion.core.text.datetimeformatDateTimeFormatDateFormatListMonthDateTimeFormatFormatStringMM/dd/yy h:mm:ss ttResponse Time History/Timestampbe2ca3ba-f818-75e5-8cf1-a8ede340c629NotSpecifiedNotSpecified00000000-0000-0000-0000-000000000000LeftNode IDSystem.Int32IntegerNotSpecifiedfalsetruefalsefalsetruefalsefalseNode IDNodeOrion.Nodes|NodeID00000000-0000-0000-0000-000000000000LeftfalsetrueNode/Node ID5d953348-3dcb-3f25-4474-a30bd558c5c9NotSpecifiedNotSpecified00000000-0000-0000-0000-000000000000LeftNodeSystem.StringTextNotSpecifiedfalsefalsefalsefalsetruefalsefalseNode NameNodeOrion.Nodes|NodeName00000000-0000-0000-0000-000000000000Leftfalsefalse61.915orion.core.link.entityEnabledTooltipsonorion.core.image.vendor.watermarkimageformat/netperfmon/images/vendors/{0}Node/Node Namefe97e8f3-c3cf-3189-62d3-c4fad483c60fNotSpecifiedNotSpecified00000000-0000-0000-0000-000000000000LeftIP AddressCore.IPAddressSystem.StringTextNotSpecifiedfalsetruetruefalsetruefalsefalseIP AddressNodeOrion.Nodes|IPAddress00000000-0000-0000-0000-000000000000Leftfalsefalse18.106Node/IP Addressa68cee51-2672-f933-1e3d-0a9e1ba01d0dNotSpecifiedNotSpecified00000000-0000-0000-0000-000000000000CenterAvailabilityCore.PercentSystem.DoubleFloatAveragefalsefalsefalsefalsefalsetruefalseAvailabilityResponseTimeHistoryResponse Time HistoryOrion.ResponseTime|Availability|ResponseTimeHistory00000000-0000-0000-0000-000000000000Centerfalsefalse16.233orion.core.text.numericformatNumericFormat{0:0.00} %Response Time History/Availability280b432b-7881-5400-4dc9-252bf1f612acAverageNotSpecifiedShowAllbe2ca3ba-f818-75e5-8cf1-a8ede340c629falseAscendingbe2ca3ba-f818-75e5-8cf1-a8ede340c629Ascendingfe97e8f3-c3cf-3189-62d3-c4fad483c60fByMonthOrion.ResponseTime|ObservationTimestamp|ResponseTimeHistorySimpleorion.nodesAll Nodese4b00557-9328-4cb8-95bf-86000f373041DynamicDisplays the Availability for each Node for this year© SolarWinds Worldwide, LLC. All Rights Reserved.truetruetruetruestandardAvailability - This YeartrueDefault FolderNode Availability - This Year0web960e3ab8911-d56e-4dea-949c-35ddada67d69d8cfe23f-12b3-4203-ad64-d51fa48f4dd4e4b00557-9328-4cb8-95bf-86000f373041Custom Tablecc2734b4-1101-47ad-952c-f4e18c3e444dSolarWinds.Reporting,Table2b2ffd41-eddd-4486-8058-a7b06e9d850410058f69f41-b574-4890-983f-c8b269014be2c42744f7-20ad-4666-8904-25c58a8f50c8This Yearfalse2b2ffd41-eddd-4486-8058-a7b06e9d8504ThisYearYear1

KMSigma.SWI

Is that the Out of the Box report Node Availability - This Year?

dman4cloud

Yes it is