Report request orphaned after 60 seconds?

I am trying to debug a problem where a report times out after 60 seconds; the
report is calling a stored procedure via ADO.Net. The stored procedure is
slow, but acceptable.
Iâ've set the report timeout settings to 300 in all the relevant config files
and the report itself but this had no effect.
The RunningJobs record for this request in the ReportServer database shows
the report having a timeout of 1800.
My questions are:
1. These time values consistently represent the time in seconds, right?
2. I realise orphaned and expired requests are cancelled after 60 seconds by
default, but why does is this request orphaned?
Section of the ReportServer log:
>>
aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to RenderFirst(
'/Reports/NumberOneReport' )
aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
SqlStreamingBufferSize to default value of '65536' Bytes because it was not
specified in Server system properties.
aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1 running
jobs to the database
aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., Error doing timer action for Running Requests Scavenger;
<<
Any help or suggestions appreciated.Roberto,
FYI: The ADO connection probably has its own Timeout setting. I know SQL
Server itself does. Have you checked these two properties yet? I'm not sure
where the ADO timeout setting is, but I know the SQL Server one is in the
Server Properties window.
Hope that helps.
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Roberto" wrote:
> I am trying to debug a problem where a report times out after 60 seconds; the
> report is calling a stored procedure via ADO.Net. The stored procedure is
> slow, but acceptable.
> Iâ've set the report timeout settings to 300 in all the relevant config files
> and the report itself but this had no effect.
> The RunningJobs record for this request in the ReportServer database shows
> the report having a timeout of 1800.
> My questions are:
> 1. These time values consistently represent the time in seconds, right?
> 2. I realise orphaned and expired requests are cancelled after 60 seconds by
> default, but why does is this request orphaned?
> Section of the ReportServer log:
> >>
> aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to RenderFirst(
> '/Reports/NumberOneReport' )
> aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
> SqlStreamingBufferSize to default value of '65536' Bytes because it was not
> specified in Server system properties.
> aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1 running
> jobs to the database
> aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details., Error doing timer action for Running Requests Scavenger;
> <<
> Any help or suggestions appreciated.|||The ADO timeout is set in my component.config to 300 (debugged this and the
call is using this value), the SQL server timeout to 600.
I hadn't thought of the SQL Server timeout so thanks for the post.
Still having the same problem though.
"Catadmin" wrote:
> Roberto,
> FYI: The ADO connection probably has its own Timeout setting. I know SQL
> Server itself does. Have you checked these two properties yet? I'm not sure
> where the ADO timeout setting is, but I know the SQL Server one is in the
> Server Properties window.
> Hope that helps.
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the back?
> @.=)
>
> "Roberto" wrote:
> > I am trying to debug a problem where a report times out after 60 seconds; the
> > report is calling a stored procedure via ADO.Net. The stored procedure is
> > slow, but acceptable.
> >
> > Iâ've set the report timeout settings to 300 in all the relevant config files
> > and the report itself but this had no effect.
> >
> > The RunningJobs record for this request in the ReportServer database shows
> > the report having a timeout of 1800.
> >
> > My questions are:
> >
> > 1. These time values consistently represent the time in seconds, right?
> >
> > 2. I realise orphaned and expired requests are cancelled after 60 seconds by
> > default, but why does is this request orphaned?
> >
> > Section of the ReportServer log:
> >
> > >>
> >
> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to RenderFirst(
> > '/Reports/NumberOneReport' )
> >
> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
> > SqlStreamingBufferSize to default value of '65536' Bytes because it was not
> > specified in Server system properties.
> >
> > aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1 running
> > jobs to the database
> >
> > aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
> > RunningJobContext.IsClientConnected; found orphaned request
> >
> > aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for more
> > details., Error doing timer action for Running Requests Scavenger;
> > <<
> >
> > Any help or suggestions appreciated.|||Is your report server running on Windows 2003 with IIS 6? Check if
increasing the IIS timeout (120 seconds on IIS6) on the default web site
helps.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roberto" <Roberto@.discussions.microsoft.com> wrote in message
news:C5C7D412-819E-46AD-86D6-53E782A09368@.microsoft.com...
> The ADO timeout is set in my component.config to 300 (debugged this and
> the
> call is using this value), the SQL server timeout to 600.
> I hadn't thought of the SQL Server timeout so thanks for the post.
> Still having the same problem though.
> "Catadmin" wrote:
>> Roberto,
>> FYI: The ADO connection probably has its own Timeout setting. I know SQL
>> Server itself does. Have you checked these two properties yet? I'm not
>> sure
>> where the ADO timeout setting is, but I know the SQL Server one is in the
>> Server Properties window.
>> Hope that helps.
>> Catadmin
>> --
>> MCDBA, MCSA
>> Random Thoughts: If a person is Microsoft Certified, does that mean that
>> Microsoft pays the bills for the funny white jackets that tie in the
>> back?
>> @.=)
>>
>> "Roberto" wrote:
>> > I am trying to debug a problem where a report times out after 60
>> > seconds; the
>> > report is calling a stored procedure via ADO.Net. The stored procedure
>> > is
>> > slow, but acceptable.
>> >
>> > I've set the report timeout settings to 300 in all the relevant config
>> > files
>> > and the report itself but this had no effect.
>> >
>> > The RunningJobs record for this request in the ReportServer database
>> > shows
>> > the report having a timeout of 1800.
>> >
>> > My questions are:
>> >
>> > 1. These time values consistently represent the time in seconds, right?
>> >
>> > 2. I realise orphaned and expired requests are cancelled after 60
>> > seconds by
>> > default, but why does is this request orphaned?
>> >
>> > Section of the ReportServer log:
>> >
>> > >>
>> >
>> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to
>> > RenderFirst(
>> > '/Reports/NumberOneReport' )
>> >
>> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
>> > SqlStreamingBufferSize to default value of '65536' Bytes because it was
>> > not
>> > specified in Server system properties.
>> >
>> > aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1
>> > running
>> > jobs to the database
>> >
>> > aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
>> > RunningJobContext.IsClientConnected; found orphaned request
>> >
>> > aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
>> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> > An internal error occurred on the report server. See the error log for
>> > more
>> > details., Error doing timer action for Running Requests Scavenger;
>> > <<
>> >
>> > Any help or suggestions appreciated.|||I'm running locally on XP Pro, IIS 5.1
The IIS connection timeout is set to 900 seconds.
The report is executed via a web service which uses ADO.Net to call a stored
proc. I'll keep working on this and post more information when I get it. Keep
the ideas coming!
"Robert Bruckner [MSFT]" wrote:
> Is your report server running on Windows 2003 with IIS 6? Check if
> increasing the IIS timeout (120 seconds on IIS6) on the default web site
> helps.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Roberto" <Roberto@.discussions.microsoft.com> wrote in message
> news:C5C7D412-819E-46AD-86D6-53E782A09368@.microsoft.com...|||The report is executed via a web service which uses ADO.Net to call a stored
proc.
Web services have a default timeout of 100 seconds; that was the problem,
not the report server.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwebservicesprotocolswebclientprotocolclasstimeouttopic.asp
The code to resolve this issue was:
this.Timeout = System.Threading.Timeout.Infinite;
Where â'thisâ' is my web service class, which is inheriting from
System.Web.Services.Protocols.SoapHttpClientProtocol