We have just upgraded to SQL Server Reporting Service 2005 and our reports
were consistently generating 'rsExecutionNotFound' errors, like the one
shown below. The errors happen when a report was refreshed or a drilldown
'+' was clicked 90 seconds after the report was initially delivered.
We found the value for SessionTimeout was set to 60 instead of the default
value of 600. We had changed the value to 60 while attempting to decrease
the startup time for delivering a report. I'm not really sure how a 60
second setting got translated to a 90 second timeout but it was very
consistent.
When we changed the value to back to 600, the 90 second timeout ceased.
However, we have several users who like to keep the report up all day and
periodically hit 'Refresh' to see any updates. I suspect the current
SessionTimeout setting of 10 minutes will not be satisfactory.
How high can we set the value for SessionTimeout before causing problems
with Reporting Services or IIS?
Thanks,
TomHi Tom,
Welcome to MSDN newsgroup.
From your description, I learned that you're upgrading your SQLServer
Reporting services reports from 2000 to 2005 version. And you found that
since the default session timeout setting is changed to 60 in the report
server application, there will occur 'rsExecutionNotFound' error. Currently
you're wondering whether there is any means to enlarge the session timeout
to a large enough value to avoid such issue, correct?
Based on my understanding, SQL Server reporting service use ASP.NET web
application as its report server application, therefore the session timeout
you mentioned should be ASP.NET web application's session timeout setting.
And this timeout setting controls how long data stored in ASP.NET session
state can be persisted. Generally, we don't recommend that we set the
timeout to a too large value because session state consumes server's memory
resource and will hit server application's performance.
In addition, for the 90 seconds you mentioned, I'm thinking it could be the
ASP.NET http request's execution timeout setting since executionTimeout's
default value is 90 seconds(set in server's machine.config in .net
framework config dir). This timeout controls how long each ASP.NET request
can run on the server. For example, if our web page or web report page will
need to run a long task, we need to enlarge this timeout setting:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
ml/gngrfhttpruntimesection.asp
<system.web>
<httpRuntime
executionTimeout="45"
/>
Hope this helps.
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Tom Bean" <tbean@.newsgroup.nospam>
| Subject: rsExecutionNotFound
| Date: Wed, 25 Jan 2006 14:33:47 -0600
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67516
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| We have just upgraded to SQL Server Reporting Service 2005 and our
reports
| were consistently generating 'rsExecutionNotFound' errors, like the one
| shown below. The errors happen when a report was refreshed or a
drilldown
| '+' was clicked 90 seconds after the report was initially delivered.
|
| We found the value for SessionTimeout was set to 60 instead of the
default
| value of 600. We had changed the value to 60 while attempting to
decrease
| the startup time for delivering a report. I'm not really sure how a 60
| second setting got translated to a 90 second timeout but it was very
| consistent.
|
| When we changed the value to back to 600, the 90 second timeout ceased.
| However, we have several users who like to keep the report up all day and
| periodically hit 'Refresh' to see any updates. I suspect the current
| SessionTimeout setting of 10 minutes will not be satisfactory.
|
| How high can we set the value for SessionTimeout before causing problems
| with Reporting Services or IIS?
|
| Thanks,
| Tom
|
|
||||Steven,
We changed 'Idle Timeout', 'Execution Timeout', and anything else in IIS
that could possibly cause the reports to timeout but the reports continued
to throw 'rsExecutionNotFound' after 90 seconds. The only change that
eliminated the error was increasing 'SessionTimeout' in the
ConfigurationInfo table.
Since sending my original message, I have recalled why we had lowered the
'SessionTimeout' setting to 60. We lowered the value to see new results in
a refreshed report sooner and under RS2000 there were no timeout problems.
We are noticing other problems with reports that worked perfectly in RS2000.
These problems appear to be the result of timeouts. Some of the problems we
have encountered are?
1) The 'rsExecutionNotFound' error when trying to refresh a report, as in
the original post.
2) Our users get the message "This report requires a default or
user-defined value for the report parameter 'Id'. To run or subscribe to
this report, you must provide a parameter value.
(rsReportParameterValueNotSet)" when they click a drilldown '+' after a
report has been sitting in the browser for about 5-10 minutes.
3) 'rsInternalError' generated when using the &rc:Toolbar=false with some
reports that contain subreports. This error says "See the error log for
more details" but where is the error log?
What has changed in RS2005 to cause these problems? And, what do I need to
do to resolve them?
Thanks,
Tom
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl...
> Hi Tom,
> Welcome to MSDN newsgroup.
> From your description, I learned that you're upgrading your SQLServer
> Reporting services reports from 2000 to 2005 version. And you found that
> since the default session timeout setting is changed to 60 in the report
> server application, there will occur 'rsExecutionNotFound' error.
> Currently
> you're wondering whether there is any means to enlarge the session timeout
> to a large enough value to avoid such issue, correct?
> Based on my understanding, SQL Server reporting service use ASP.NET web
> application as its report server application, therefore the session
> timeout
> you mentioned should be ASP.NET web application's session timeout setting.
> And this timeout setting controls how long data stored in ASP.NET session
> state can be persisted. Generally, we don't recommend that we set the
> timeout to a too large value because session state consumes server's
> memory
> resource and will hit server application's performance.
> In addition, for the 90 seconds you mentioned, I'm thinking it could be
> the
> ASP.NET http request's execution timeout setting since executionTimeout's
> default value is 90 seconds(set in server's machine.config in .net
> framework config dir). This timeout controls how long each ASP.NET
> request
> can run on the server. For example, if our web page or web report page
> will
> need to run a long task, we need to enlarge this timeout setting:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
> ml/gngrfhttpruntimesection.asp
> <system.web>
> <httpRuntime
> executionTimeout="45"
> />
> Hope this helps.
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
> --
> | From: "Tom Bean" <tbean@.newsgroup.nospam>
> | Subject: rsExecutionNotFound
> | Date: Wed, 25 Jan 2006 14:33:47 -0600
> | Lines: 23
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:67516
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | We have just upgraded to SQL Server Reporting Service 2005 and our
> reports
> | were consistently generating 'rsExecutionNotFound' errors, like the one
> | shown below. The errors happen when a report was refreshed or a
> drilldown
> | '+' was clicked 90 seconds after the report was initially delivered.
> |
> | We found the value for SessionTimeout was set to 60 instead of the
> default
> | value of 600. We had changed the value to 60 while attempting to
> decrease
> | the startup time for delivering a report. I'm not really sure how a 60
> | second setting got translated to a 90 second timeout but it was very
> | consistent.
> |
> | When we changed the value to back to 600, the 90 second timeout ceased.
> | However, we have several users who like to keep the report up all day
> and
> | periodically hit 'Refresh' to see any updates. I suspect the current
> | SessionTimeout setting of 10 minutes will not be satisfactory.
> |
> | How high can we set the value for SessionTimeout before causing problems
> | with Reporting Services or IIS?
> |
> | Thanks,
> | Tom
> |
> |
> |
>|||Thanks for your response Tom,
Em, as far as I known, there hasn't any particular changes regarding on the
timeout setting you mentioned, such setting is ususally adjusted by some
peformance tuning consideration compared to previous version.
Does the problem specific to machine or just concerned with those
particular reports?
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--
| From: "Tom Bean" <tbean@.newsgroup.nospam>
| References: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
<JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl>
| Subject: Re: rsExecutionNotFound
| Date: Thu, 26 Jan 2006 11:20:14 -0600
| Lines: 138
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <urYRNzpIGHA.3936@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67581
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Steven,
|
| We changed 'Idle Timeout', 'Execution Timeout', and anything else in IIS
| that could possibly cause the reports to timeout but the reports
continued
| to throw 'rsExecutionNotFound' after 90 seconds. The only change that
| eliminated the error was increasing 'SessionTimeout' in the
| ConfigurationInfo table.
|
| Since sending my original message, I have recalled why we had lowered the
| 'SessionTimeout' setting to 60. We lowered the value to see new results
in
| a refreshed report sooner and under RS2000 there were no timeout problems.
|
| We are noticing other problems with reports that worked perfectly in
RS2000.
| These problems appear to be the result of timeouts. Some of the problems
we
| have encountered are?
|
| 1) The 'rsExecutionNotFound' error when trying to refresh a report, as
in
| the original post.
|
| 2) Our users get the message "This report requires a default or
| user-defined value for the report parameter 'Id'. To run or subscribe to
| this report, you must provide a parameter value.
| (rsReportParameterValueNotSet)" when they click a drilldown '+' after a
| report has been sitting in the browser for about 5-10 minutes.
|
| 3) 'rsInternalError' generated when using the &rc:Toolbar=false with
some
| reports that contain subreports. This error says "See the error log for
| more details" but where is the error log?
|
| What has changed in RS2005 to cause these problems? And, what do I need
to
| do to resolve them?
|
| Thanks,
| Tom
|
| "Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
| news:JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl...
| > Hi Tom,
| >
| > Welcome to MSDN newsgroup.
| >
| > From your description, I learned that you're upgrading your SQLServer
| > Reporting services reports from 2000 to 2005 version. And you found that
| > since the default session timeout setting is changed to 60 in the report
| > server application, there will occur 'rsExecutionNotFound' error.
| > Currently
| > you're wondering whether there is any means to enlarge the session
timeout
| > to a large enough value to avoid such issue, correct?
| >
| > Based on my understanding, SQL Server reporting service use ASP.NET web
| > application as its report server application, therefore the session
| > timeout
| > you mentioned should be ASP.NET web application's session timeout
setting.
| > And this timeout setting controls how long data stored in ASP.NET
session
| > state can be persisted. Generally, we don't recommend that we set the
| > timeout to a too large value because session state consumes server's
| > memory
| > resource and will hit server application's performance.
| >
| > In addition, for the 90 seconds you mentioned, I'm thinking it could be
| > the
| > ASP.NET http request's execution timeout setting since
executionTimeout's
| > default value is 90 seconds(set in server's machine.config in .net
| > framework config dir). This timeout controls how long each ASP.NET
| > request
| > can run on the server. For example, if our web page or web report page
| > will
| > need to run a long task, we need to enlarge this timeout setting:
| >
| >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
| > ml/gngrfhttpruntimesection.asp
| >
| > <system.web>
| > <httpRuntime
| > executionTimeout="45"
| > />
| >
| > Hope this helps.
| >
| > Steven Cheng
| > Microsoft Online Support
| >
| > Get Secure! www.microsoft.com/security
| > (This posting is provided "AS IS", with no warranties, and confers no
| > rights.)
| >
| >
| >
| > --
| > | From: "Tom Bean" <tbean@.newsgroup.nospam>
| > | Subject: rsExecutionNotFound
| > | Date: Wed, 25 Jan 2006 14:33:47 -0600
| > | Lines: 23
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| > | X-RFC2646: Format=Flowed; Original
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| > | Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.reportingsvcs
| > | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
| > | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl
| > microsoft.public.sqlserver.reportingsvcs:67516
| > | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
| > |
| > | We have just upgraded to SQL Server Reporting Service 2005 and our
| > reports
| > | were consistently generating 'rsExecutionNotFound' errors, like the
one
| > | shown below. The errors happen when a report was refreshed or a
| > drilldown
| > | '+' was clicked 90 seconds after the report was initially delivered.
| > |
| > | We found the value for SessionTimeout was set to 60 instead of the
| > default
| > | value of 600. We had changed the value to 60 while attempting to
| > decrease
| > | the startup time for delivering a report. I'm not really sure how a
60
| > | second setting got translated to a 90 second timeout but it was very
| > | consistent.
| > |
| > | When we changed the value to back to 600, the 90 second timeout
ceased.
| > | However, we have several users who like to keep the report up all day
| > and
| > | periodically hit 'Refresh' to see any updates. I suspect the current
| > | SessionTimeout setting of 10 minutes will not be satisfactory.
| > |
| > | How high can we set the value for SessionTimeout before causing
problems
| > | with Reporting Services or IIS?
| > |
| > | Thanks,
| > | Tom
| > |
| > |
| > |
| >
|
|
||||Steven,
The problem outlined in 1) occurred with every report until we increased
'SessionTimeout'. The problem in 2) still occurs with every report. In
RS2000, if the report sat too long, the '+' didn't expand the subreport but
they didn't produce the error message which makes us look bad to our users.
We would prefer the stale reports just quit working rather than exposing an
error message to our users.
After working more with the report that caused problem 3), I discovered the
'rsInternalError' only happened when the report returned an empty dataset.
I have no idea why removing the &rc:Toolbar=false parameter would make the
problem to go away. As I said, the report ran fine in RS2000. It also ran
fine in designer. However, when put into production the error occurred, so
there is a definite disconnect between running reports in designer and in a
browser. Do you know of any changes in the way RS2005 handles empty
datasets?
Another irritation we have noticed is that the field names in RS2005 seem to
be case sensitive which wasn't the case with RS2000. This has caused
problems with parameters in the URL also.
As far as changes to performance tuning settings, we upgraded our
installation of RS2000 to RS2005 with no changes to the settings of IIS.
Any changes made to any settings must have been made by RS2005 but we don't
know what they are. Can you give us any more information?
Thanks,
Tom
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:Z6Utq%23XJGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Thanks for your response Tom,
> Em, as far as I known, there hasn't any particular changes regarding on
> the
> timeout setting you mentioned, such setting is ususally adjusted by some
> peformance tuning consideration compared to previous version.
> Does the problem specific to machine or just concerned with those
> particular reports?
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> --
> | From: "Tom Bean" <tbean@.newsgroup.nospam>
> | References: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
> <JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl>
> | Subject: Re: rsExecutionNotFound
> | Date: Thu, 26 Jan 2006 11:20:14 -0600
> | Lines: 138
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | Message-ID: <urYRNzpIGHA.3936@.TK2MSFTNGP12.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:67581
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Steven,
> |
> | We changed 'Idle Timeout', 'Execution Timeout', and anything else in IIS
> | that could possibly cause the reports to timeout but the reports
> continued
> | to throw 'rsExecutionNotFound' after 90 seconds. The only change that
> | eliminated the error was increasing 'SessionTimeout' in the
> | ConfigurationInfo table.
> |
> | Since sending my original message, I have recalled why we had lowered
> the
> | 'SessionTimeout' setting to 60. We lowered the value to see new results
> in
> | a refreshed report sooner and under RS2000 there were no timeout
> problems.
> |
> | We are noticing other problems with reports that worked perfectly in
> RS2000.
> | These problems appear to be the result of timeouts. Some of the
> problems
> we
> | have encountered are?
> |
> | 1) The 'rsExecutionNotFound' error when trying to refresh a report, as
> in
> | the original post.
> |
> | 2) Our users get the message "This report requires a default or
> | user-defined value for the report parameter 'Id'. To run or subscribe to
> | this report, you must provide a parameter value.
> | (rsReportParameterValueNotSet)" when they click a drilldown '+' after a
> | report has been sitting in the browser for about 5-10 minutes.
> |
> | 3) 'rsInternalError' generated when using the &rc:Toolbar=false with
> some
> | reports that contain subreports. This error says "See the error log for
> | more details" but where is the error log?
> |
> | What has changed in RS2005 to cause these problems? And, what do I need
> to
> | do to resolve them?
> |
> | Thanks,
> | Tom
> |
> | "Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
> | news:JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl...
> | > Hi Tom,
> | >
> | > Welcome to MSDN newsgroup.
> | >
> | > From your description, I learned that you're upgrading your SQLServer
> | > Reporting services reports from 2000 to 2005 version. And you found
> that
> | > since the default session timeout setting is changed to 60 in the
> report
> | > server application, there will occur 'rsExecutionNotFound' error.
> | > Currently
> | > you're wondering whether there is any means to enlarge the session
> timeout
> | > to a large enough value to avoid such issue, correct?
> | >
> | > Based on my understanding, SQL Server reporting service use ASP.NET
> web
> | > application as its report server application, therefore the session
> | > timeout
> | > you mentioned should be ASP.NET web application's session timeout
> setting.
> | > And this timeout setting controls how long data stored in ASP.NET
> session
> | > state can be persisted. Generally, we don't recommend that we set the
> | > timeout to a too large value because session state consumes server's
> | > memory
> | > resource and will hit server application's performance.
> | >
> | > In addition, for the 90 seconds you mentioned, I'm thinking it could
> be
> | > the
> | > ASP.NET http request's execution timeout setting since
> executionTimeout's
> | > default value is 90 seconds(set in server's machine.config in .net
> | > framework config dir). This timeout controls how long each ASP.NET
> | > request
> | > can run on the server. For example, if our web page or web report page
> | > will
> | > need to run a long task, we need to enlarge this timeout setting:
> | >
> | >
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
> | > ml/gngrfhttpruntimesection.asp
> | >
> | > <system.web>
> | > <httpRuntime
> | > executionTimeout="45"
> | > />
> | >
> | > Hope this helps.
> | >
> | > Steven Cheng
> | > Microsoft Online Support
> | >
> | > Get Secure! www.microsoft.com/security
> | > (This posting is provided "AS IS", with no warranties, and confers no
> | > rights.)
> | >
> | >
> | >
> | > --
> | > | From: "Tom Bean" <tbean@.newsgroup.nospam>
> | > | Subject: rsExecutionNotFound
> | > | Date: Wed, 25 Jan 2006 14:33:47 -0600
> | > | Lines: 23
> | > | X-Priority: 3
> | > | X-MSMail-Priority: Normal
> | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | > | X-RFC2646: Format=Flowed; Original
> | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | > | Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
> | > | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | > | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
> | > | Path:
> TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> | > | Xref: TK2MSFTNGXA02.phx.gbl
> | > microsoft.public.sqlserver.reportingsvcs:67516
> | > | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> | > |
> | > | We have just upgraded to SQL Server Reporting Service 2005 and our
> | > reports
> | > | were consistently generating 'rsExecutionNotFound' errors, like the
> one
> | > | shown below. The errors happen when a report was refreshed or a
> | > drilldown
> | > | '+' was clicked 90 seconds after the report was initially
> delivered.
> | > |
> | > | We found the value for SessionTimeout was set to 60 instead of the
> | > default
> | > | value of 600. We had changed the value to 60 while attempting to
> | > decrease
> | > | the startup time for delivering a report. I'm not really sure how a
> 60
> | > | second setting got translated to a 90 second timeout but it was very
> | > | consistent.
> | > |
> | > | When we changed the value to back to 600, the 90 second timeout
> ceased.
> | > | However, we have several users who like to keep the report up all
> day
> | > and
> | > | periodically hit 'Refresh' to see any updates. I suspect the
> current
> | > | SessionTimeout setting of 10 minutes will not be satisfactory.
> | > |
> | > | How high can we set the value for SessionTimeout before causing
> problems
> | > | with Reporting Services or IIS?
> | > |
> | > | Thanks,
> | > | Tom
> | > |
> | > |
> | > |
> | >
> |
> |
> |
>|||Thanks for your further followup Tom,
Since the reports used to work without any problem in Reporting Service
2000 but suffering the problem when upgraded to 2005, I think there may
have some certain issues according to your scenario. So far I haven't heard
any known issue on this, however, I don't think manually enlarge session
timeout is the formal means since there is not document on this also and
session state is a raw setting which more related to ASP.NET rather than
reporting service from SQL Server standpoint. So if this is an urgent
issue for you, I suggest you try contacting PSS for thorough
throubleshooting, it'll be better if you can provide a simplified version
of your report and application to them. Also, you can also submit this to
the MSDN feedback center to report the issue in case that this might be an
hidden issue.
http://lab.msdn.microsoft.com/productfeedback/default.aspx
Thanks & Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
) eventhough that was not the base of the problem.