INFO: Reporting Web Server stopped

I see an this message at the end of the the
ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
Server stopped
Then in the most recent log file I see this at the beginning:
w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web Server
started
I assume this is because I have some how set up reporting to services to
automatically shutdown after a period of non-activity.
It seems that everytime the first person tries reporting services when it is
stopped. It takes a long time to render the report. Then after it is
running it gets rendered much quicker. Once again I'm guessing this happens
be cause reporting services needs to start (slow rendering), or is all ready
running (fast rendering).
Is ther way to always keep the Reporting Web Server running and not having
is shut down periodically Are there drawbacks to doing this?
--
If you are looking for SQL Server examples or a free SQL Server DBA
Dashboard tool check out my Website at http://www.sqlserverexamples.comThis is an IIS issue.
Go to IIS Manager, under Applocation Pools node, right click
"DefaultAppPool" in which the Reporting Server work process is running,
select properties. On "Performace" tag, you will see, by default, the app
pool will shut down if > being idle for 20 min. You can extend this time to
8x60min 480min, so that the app pool will not shut down for a regular
working day. However, the first report reader of the day, will hit the
delay. You may schedule a dummy report at beginning of a work day for this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
news:F30BE481-A090-4988-B5B4-8D3A44B64627@.microsoft.com...
>I see an this message at the end of the the
> ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
> w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
> Server stopped
> Then in the most recent log file I see this at the beginning:
> w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web
> Server
> started
> I assume this is because I have some how set up reporting to services to
> automatically shutdown after a period of non-activity.
> It seems that everytime the first person tries reporting services when it
> is
> stopped. It takes a long time to render the report. Then after it is
> running it gets rendered much quicker. Once again I'm guessing this
> happens
> be cause reporting services needs to start (slow rendering), or is all
> ready
> running (fast rendering).
> Is ther way to always keep the Reporting Web Server running and not having
> is shut down periodically Are there drawbacks to doing this?
>
> --
> If you are looking for SQL Server examples or a free SQL Server DBA
> Dashboard tool check out my Website at http://www.sqlserverexamples.com|||I just unchecked the box. Doesn't unchecking the box in the performance tab
disable the non-activity shutdown all together?
--
If you are looking for SQL Server examples or a free SQL Server DBA
Dashboard tool check out my Website at http://www.sqlserverexamples.com
"Bruce L-C [MVP]" wrote:
> This is an IIS issue.
> Go to IIS Manager, under Applocation Pools node, right click
> "DefaultAppPool" in which the Reporting Server work process is running,
> select properties. On "Performace" tag, you will see, by default, the app
> pool will shut down if > being idle for 20 min. You can extend this time to
> 8x60min 480min, so that the app pool will not shut down for a regular
> working day. However, the first report reader of the day, will hit the
> delay. You may schedule a dummy report at beginning of a work day for this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
> news:F30BE481-A090-4988-B5B4-8D3A44B64627@.microsoft.com...
> >I see an this message at the end of the the
> > ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
> >
> > w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
> > Server stopped
> >
> > Then in the most recent log file I see this at the beginning:
> >
> > w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web
> > Server
> > started
> >
> > I assume this is because I have some how set up reporting to services to
> > automatically shutdown after a period of non-activity.
> >
> > It seems that everytime the first person tries reporting services when it
> > is
> > stopped. It takes a long time to render the report. Then after it is
> > running it gets rendered much quicker. Once again I'm guessing this
> > happens
> > be cause reporting services needs to start (slow rendering), or is all
> > ready
> > running (fast rendering).
> >
> > Is ther way to always keep the Reporting Web Server running and not having
> > is shut down periodically Are there drawbacks to doing this?
> >
> >
> > --
> > If you are looking for SQL Server examples or a free SQL Server DBA
> > Dashboard tool check out my Website at http://www.sqlserverexamples.com
>
>|||I don't think so. I think it just does the default.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
news:8A7FABB3-0295-4C42-BBF5-889A53B63AFB@.microsoft.com...
>I just unchecked the box. Doesn't unchecking the box in the performance
>tab
> disable the non-activity shutdown all together?
> --
> If you are looking for SQL Server examples or a free SQL Server DBA
> Dashboard tool check out my Website at http://www.sqlserverexamples.com
>
> "Bruce L-C [MVP]" wrote:
>> This is an IIS issue.
>> Go to IIS Manager, under Applocation Pools node, right click
>> "DefaultAppPool" in which the Reporting Server work process is running,
>> select properties. On "Performace" tag, you will see, by default, the
>> app
>> pool will shut down if > being idle for 20 min. You can extend this time
>> to
>> 8x60min 480min, so that the app pool will not shut down for a regular
>> working day. However, the first report reader of the day, will hit the
>> delay. You may schedule a dummy report at beginning of a work day for
>> this.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
>> news:F30BE481-A090-4988-B5B4-8D3A44B64627@.microsoft.com...
>> >I see an this message at the end of the the
>> > ReportServer__mm_dd_yy_hh_mm_ss.log file the second oldest log file.
>> >
>> > w3wp!webserver!1!11/28/2007-09:17:57:: i INFO: Reporting Web
>> > Server stopped
>> >
>> > Then in the most recent log file I see this at the beginning:
>> >
>> > w3wp!webserver!9!11/28/2007-10:37:19:: i INFO: Reporting Web
>> > Server
>> > started
>> >
>> > I assume this is because I have some how set up reporting to services
>> > to
>> > automatically shutdown after a period of non-activity.
>> >
>> > It seems that everytime the first person tries reporting services when
>> > it
>> > is
>> > stopped. It takes a long time to render the report. Then after it is
>> > running it gets rendered much quicker. Once again I'm guessing this
>> > happens
>> > be cause reporting services needs to start (slow rendering), or is all
>> > ready
>> > running (fast rendering).
>> >
>> > Is ther way to always keep the Reporting Web Server running and not
>> > having
>> > is shut down periodically Are there drawbacks to doing this?
>> >
>> >
>> > --
>> > If you are looking for SQL Server examples or a free SQL Server DBA
>> > Dashboard tool check out my Website at http://www.sqlserverexamples.com
>>sql