Issue | Request timed out logged in w3wp log after the User Interface pops up a Log Reference ID.
Performing a Lookup from a Cross-Reference field that searches through hundreds of thousands of records and takes longer than the default 3 min execution timeout as configured in the Web.config.
A sample w3wp error follows:
<ApplicationData> <TraceData> <DataItem> <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord"> <TraceIdentifier>Archer.Web</TraceIdentifier> <LogReferenceId>080316-163008-5926</LogReferenceId> <Description>Request timed out.</Description> <AppDomain>/LM/W3SVC/944038430/ROOT-1-131146731375176131</AppDomain> <ContextData> <BaseUrl>http://XXXX.com/SearchContent/Search.aspx</BaseUrl> <View>Default</View> <Module>ModuleId: 471, ModuleName: XXXXXXXXXX, ModuleStatus: ActiveInProduction, ModuleType: Application</Module> <frameWidthHeight>879,388</frameWidthHeight> </ContextData> <Exception> <ExceptionType>System.Web.HttpException, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a</ExceptionType> <Message>Request timed out.</Message> <Source /> <StackTrace /> </Exception> </TraceRecord> </DataItem> </TraceData> </ApplicationData>
|