First Time Delay on Client Systems

I've just set up a SQL Reporting Services server.
All seems to be working fine, however I've noticed that when a report is
opened from a user system accessing the report server for the first time, the
report takes a very long time to open (a few minutes in some cases), and
sometimes I have to abort it and start again.
This is a report that should take a couple of seconds at most. Once the
report does finally open, it opens fine from then on, even when refreshed, or
run by different parameters. Also all other reports availale to the user also
run fine after that first one finally opens.
There are no errors, just the Report is being generated message. It's like
the server has to get aquainted with the machine accessing it the first
time...
Again, once the report has run, this problem goes away. I have tested this
on around 10 different user systems, with the same results on all of them,
some are Win2k, some are XP. The report server is running on a dual
processor, clean install Server 2003, SQL Server 2000 sp 3a.
Any assistance would be greatly appreciated. I'm holding off a full on roll
out of this until I get this solved, as it will certainly drive users crazy.
Thanks,
TomTIs this the first time *each* user runs the same report, or the first time
*any* user runs the same report?
If it's the first time each user runs the report (which your message seems
to say), it may be some overhead in setting up a user cache (just grasping
at straws here). It would be interesting to run a SQL performance monitor
and some other administrative performance tools when this happens. Perhaps
you could set logging to verbose for a moment.
If it's the first time any user runs the report, then it could be a source
database (back end) issue. Perhaps it's compiling the SQL statement for the
first time, and then the statement is in cache from then on. Or perhaps
it's setting up automatic indexes on the data the first time, and they're
there after that. Or, ...
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"TomT" <tomt@.tomt.com> wrote in message
news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> I've just set up a SQL Reporting Services server.
> All seems to be working fine, however I've noticed that when a report is
> opened from a user system accessing the report server for the first time,
> the
> report takes a very long time to open (a few minutes in some cases), and
> sometimes I have to abort it and start again.
> This is a report that should take a couple of seconds at most. Once the
> report does finally open, it opens fine from then on, even when refreshed,
> or
> run by different parameters. Also all other reports availale to the user
> also
> run fine after that first one finally opens.
> There are no errors, just the Report is being generated message. It's like
> the server has to get aquainted with the machine accessing it the first
> time...
> Again, once the report has run, this problem goes away. I have tested this
> on around 10 different user systems, with the same results on all of them,
> some are Win2k, some are XP. The report server is running on a dual
> processor, clean install Server 2003, SQL Server 2000 sp 3a.
> Any assistance would be greatly appreciated. I'm holding off a full on
> roll
> out of this until I get this solved, as it will certainly drive users
> crazy.
> Thanks,
> TomT|||Jeff,
Thanks for your reply. This is when each user runs any report from their
system for the first time. E.g., I could run it from my system and it runs
properly, however if a user who has never accessed the report server before
runs the same report, there is a significant delay. Once it finally opens,
things run properly for that user from then on (at least so far). However,
user B, who has never accessed the server, gets the delay.
A bit disappointing, really...
"Jeff A. Stucker" wrote:
> Is this the first time *each* user runs the same report, or the first time
> *any* user runs the same report?
> If it's the first time each user runs the report (which your message seems
> to say), it may be some overhead in setting up a user cache (just grasping
> at straws here). It would be interesting to run a SQL performance monitor
> and some other administrative performance tools when this happens. Perhaps
> you could set logging to verbose for a moment.
> If it's the first time any user runs the report, then it could be a source
> database (back end) issue. Perhaps it's compiling the SQL statement for the
> first time, and then the statement is in cache from then on. Or perhaps
> it's setting up automatic indexes on the data the first time, and they're
> there after that. Or, ...
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "TomT" <tomt@.tomt.com> wrote in message
> news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> > I've just set up a SQL Reporting Services server.
> >
> > All seems to be working fine, however I've noticed that when a report is
> > opened from a user system accessing the report server for the first time,
> > the
> > report takes a very long time to open (a few minutes in some cases), and
> > sometimes I have to abort it and start again.
> >
> > This is a report that should take a couple of seconds at most. Once the
> > report does finally open, it opens fine from then on, even when refreshed,
> > or
> > run by different parameters. Also all other reports availale to the user
> > also
> > run fine after that first one finally opens.
> >
> > There are no errors, just the Report is being generated message. It's like
> > the server has to get aquainted with the machine accessing it the first
> > time...
> >
> > Again, once the report has run, this problem goes away. I have tested this
> > on around 10 different user systems, with the same results on all of them,
> > some are Win2k, some are XP. The report server is running on a dual
> > processor, clean install Server 2003, SQL Server 2000 sp 3a.
> >
> > Any assistance would be greatly appreciated. I'm holding off a full on
> > roll
> > out of this until I get this solved, as it will certainly drive users
> > crazy.
> >
> > Thanks,
> >
> > TomT
>
>|||This is my experience. What I have seen is what matters is whether anyone
has hit the report server in awhile. It is not user or report specific. To
keep things predicatable I have a report open that is a very simple and
quick report that I set to autorefresh once a minute. This then prevents the
delay from happening.
You set autorefresh in the report properties. Try creating a report used
just by yourself to test this out.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"TomT" <tomt@.tomt.com> wrote in message
news:7FAEFC07-F89A-42BC-B095-28AD440314A5@.microsoft.com...
> Jeff,
> Thanks for your reply. This is when each user runs any report from their
> system for the first time. E.g., I could run it from my system and it runs
> properly, however if a user who has never accessed the report server
before
> runs the same report, there is a significant delay. Once it finally opens,
> things run properly for that user from then on (at least so far). However,
> user B, who has never accessed the server, gets the delay.
> A bit disappointing, really...
> "Jeff A. Stucker" wrote:
> > Is this the first time *each* user runs the same report, or the first
time
> > *any* user runs the same report?
> >
> > If it's the first time each user runs the report (which your message
seems
> > to say), it may be some overhead in setting up a user cache (just
grasping
> > at straws here). It would be interesting to run a SQL performance
monitor
> > and some other administrative performance tools when this happens.
Perhaps
> > you could set logging to verbose for a moment.
> >
> > If it's the first time any user runs the report, then it could be a
source
> > database (back end) issue. Perhaps it's compiling the SQL statement for
the
> > first time, and then the statement is in cache from then on. Or perhaps
> > it's setting up automatic indexes on the data the first time, and
they're
> > there after that. Or, ...
> >
> > Cheers,
> >
> > '(' Jeff A. Stucker
> > \
> >
> > Business Intelligence
> > www.criadvantage.com
> > ---
> > "TomT" <tomt@.tomt.com> wrote in message
> > news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> > > I've just set up a SQL Reporting Services server.
> > >
> > > All seems to be working fine, however I've noticed that when a report
is
> > > opened from a user system accessing the report server for the first
time,
> > > the
> > > report takes a very long time to open (a few minutes in some cases),
and
> > > sometimes I have to abort it and start again.
> > >
> > > This is a report that should take a couple of seconds at most. Once
the
> > > report does finally open, it opens fine from then on, even when
refreshed,
> > > or
> > > run by different parameters. Also all other reports availale to the
user
> > > also
> > > run fine after that first one finally opens.
> > >
> > > There are no errors, just the Report is being generated message. It's
like
> > > the server has to get aquainted with the machine accessing it the
first
> > > time...
> > >
> > > Again, once the report has run, this problem goes away. I have tested
this
> > > on around 10 different user systems, with the same results on all of
them,
> > > some are Win2k, some are XP. The report server is running on a dual
> > > processor, clean install Server 2003, SQL Server 2000 sp 3a.
> > >
> > > Any assistance would be greatly appreciated. I'm holding off a full on
> > > roll
> > > out of this until I get this solved, as it will certainly drive users
> > > crazy.
> > >
> > > Thanks,
> > >
> > > TomT
> >
> >
> >|||Ditto. I noticed it occurring more on the very first time RS was accessed
or after sufficient 'idle' time. I hadn't got around to working around the
issue just yet, but your work around seems good. In the back of my mind I
was thinking of writing a simple .rss script that does something like
ListChildren at the root folder and putting it on a schedule (once every n
minutes or so). My thinking was to just make a web service call and force
RS to re-cache whatever it had expired from its cached information.
Of course, I don't know if RS is expiring cached info or what...it would be
nice if MS would jump in an let us know exactly was happening here...
--
Adrian M.
MCP
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:uoFR3HdFFHA.3272@.TK2MSFTNGP10.phx.gbl...
> This is my experience. What I have seen is what matters is whether anyone
> has hit the report server in awhile. It is not user or report specific. To
> keep things predicatable I have a report open that is a very simple and
> quick report that I set to autorefresh once a minute. This then prevents
> the
> delay from happening.
> You set autorefresh in the report properties. Try creating a report used
> just by yourself to test this out.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "TomT" <tomt@.tomt.com> wrote in message
> news:7FAEFC07-F89A-42BC-B095-28AD440314A5@.microsoft.com...
>> Jeff,
>> Thanks for your reply. This is when each user runs any report from their
>> system for the first time. E.g., I could run it from my system and it
>> runs
>> properly, however if a user who has never accessed the report server
> before
>> runs the same report, there is a significant delay. Once it finally
>> opens,
>> things run properly for that user from then on (at least so far).
>> However,
>> user B, who has never accessed the server, gets the delay.
>> A bit disappointing, really...
>> "Jeff A. Stucker" wrote:
>> > Is this the first time *each* user runs the same report, or the first
> time
>> > *any* user runs the same report?
>> >
>> > If it's the first time each user runs the report (which your message
> seems
>> > to say), it may be some overhead in setting up a user cache (just
> grasping
>> > at straws here). It would be interesting to run a SQL performance
> monitor
>> > and some other administrative performance tools when this happens.
> Perhaps
>> > you could set logging to verbose for a moment.
>> >
>> > If it's the first time any user runs the report, then it could be a
> source
>> > database (back end) issue. Perhaps it's compiling the SQL statement
>> > for
> the
>> > first time, and then the statement is in cache from then on. Or
>> > perhaps
>> > it's setting up automatic indexes on the data the first time, and
> they're
>> > there after that. Or, ...
>> >
>> > Cheers,
>> >
>> > '(' Jeff A. Stucker
>> > \
>> >
>> > Business Intelligence
>> > www.criadvantage.com
>> > ---
>> > "TomT" <tomt@.tomt.com> wrote in message
>> > news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
>> > > I've just set up a SQL Reporting Services server.
>> > >
>> > > All seems to be working fine, however I've noticed that when a report
> is
>> > > opened from a user system accessing the report server for the first
> time,
>> > > the
>> > > report takes a very long time to open (a few minutes in some cases),
> and
>> > > sometimes I have to abort it and start again.
>> > >
>> > > This is a report that should take a couple of seconds at most. Once
> the
>> > > report does finally open, it opens fine from then on, even when
> refreshed,
>> > > or
>> > > run by different parameters. Also all other reports availale to the
> user
>> > > also
>> > > run fine after that first one finally opens.
>> > >
>> > > There are no errors, just the Report is being generated message. It's
> like
>> > > the server has to get aquainted with the machine accessing it the
> first
>> > > time...
>> > >
>> > > Again, once the report has run, this problem goes away. I have tested
> this
>> > > on around 10 different user systems, with the same results on all of
> them,
>> > > some are Win2k, some are XP. The report server is running on a dual
>> > > processor, clean install Server 2003, SQL Server 2000 sp 3a.
>> > >
>> > > Any assistance would be greatly appreciated. I'm holding off a full
>> > > on
>> > > roll
>> > > out of this until I get this solved, as it will certainly drive users
>> > > crazy.
>> > >
>> > > Thanks,
>> > >
>> > > TomT
>> >
>> >
>> >
>|||If you are running Windows 2003 server for your IIS reportserver, then this
is a simple issue - I'll explain what happens:
The report service engine, once it is idle for more than the default 20
minutes, the worker process is shutdown.
This is controlled by IIS.
Open up the Internet Information Services (IIS) Manager
Expand the server node then the application pools.
On my IIS machine, I created an application pool dedicated to the
reportserver & reportmanager virtual webs.
But anyways, for the application pool that the reportserver is pointing to
if you left everything to their defaults will be the DefaultAppPool.
Right click the default app pool and select properties.
There are two things that are checked by default - On the recycling tab
there is a checkbox for recycling worker processes - it is currently set to
1740 minutes (29 hours). Leave it.
The other one is on the performance tab - which is the one you are
interested in changing...
See the "Idle Timeout" section and increase the number of minutes to be 8
hours a typical working day - 8*60 = 480 minutes.
Next, to be sure the "morning person" that runs the first report doesn't get
the delay, set up a schedule for either a dummy or adhoc report to fire off
like at 6am so that the report component worker processes get loaded.
I hope this helps you.
There is no need to have a report fire off every minute to keep things
alive - it is just that the report service was "unloaded" and needed to load
back up.
=-Chris
"TomT" <tomt@.tomt.com> wrote in message
news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> I've just set up a SQL Reporting Services server.
> All seems to be working fine, however I've noticed that when a report is
> opened from a user system accessing the report server for the first time,
> the
> report takes a very long time to open (a few minutes in some cases), and
> sometimes I have to abort it and start again.
> This is a report that should take a couple of seconds at most. Once the
> report does finally open, it opens fine from then on, even when refreshed,
> or
> run by different parameters. Also all other reports availale to the user
> also
> run fine after that first one finally opens.
> There are no errors, just the Report is being generated message. It's like
> the server has to get aquainted with the machine accessing it the first
> time...
> Again, once the report has run, this problem goes away. I have tested this
> on around 10 different user systems, with the same results on all of them,
> some are Win2k, some are XP. The report server is running on a dual
> processor, clean install Server 2003, SQL Server 2000 sp 3a.
> Any assistance would be greatly appreciated. I'm holding off a full on
> roll
> out of this until I get this solved, as it will certainly drive users
> crazy.
> Thanks,
> TomT|||Very good. I figured something like that was happening. Of course I can also
just set the report to be refreshed every 15 minutes instead of every
minute.
Thanks for the info. Your solution is the correct way. Mine is a hack but
works.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Christopher Conner" <someone@.someplace.com> wrote in message
news:e9GOK2dFFHA.1084@.tk2msftngp13.phx.gbl...
> If you are running Windows 2003 server for your IIS reportserver, then
this
> is a simple issue - I'll explain what happens:
> The report service engine, once it is idle for more than the default 20
> minutes, the worker process is shutdown.
> This is controlled by IIS.
> Open up the Internet Information Services (IIS) Manager
> Expand the server node then the application pools.
> On my IIS machine, I created an application pool dedicated to the
> reportserver & reportmanager virtual webs.
> But anyways, for the application pool that the reportserver is pointing to
> if you left everything to their defaults will be the DefaultAppPool.
> Right click the default app pool and select properties.
> There are two things that are checked by default - On the recycling tab
> there is a checkbox for recycling worker processes - it is currently set
to
> 1740 minutes (29 hours). Leave it.
> The other one is on the performance tab - which is the one you are
> interested in changing...
> See the "Idle Timeout" section and increase the number of minutes to be 8
> hours a typical working day - 8*60 = 480 minutes.
> Next, to be sure the "morning person" that runs the first report doesn't
get
> the delay, set up a schedule for either a dummy or adhoc report to fire
off
> like at 6am so that the report component worker processes get loaded.
> I hope this helps you.
> There is no need to have a report fire off every minute to keep things
> alive - it is just that the report service was "unloaded" and needed to
load
> back up.
> =-Chris
>
>
>
> "TomT" <tomt@.tomt.com> wrote in message
> news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> > I've just set up a SQL Reporting Services server.
> >
> > All seems to be working fine, however I've noticed that when a report is
> > opened from a user system accessing the report server for the first
time,
> > the
> > report takes a very long time to open (a few minutes in some cases), and
> > sometimes I have to abort it and start again.
> >
> > This is a report that should take a couple of seconds at most. Once the
> > report does finally open, it opens fine from then on, even when
refreshed,
> > or
> > run by different parameters. Also all other reports availale to the user
> > also
> > run fine after that first one finally opens.
> >
> > There are no errors, just the Report is being generated message. It's
like
> > the server has to get aquainted with the machine accessing it the first
> > time...
> >
> > Again, once the report has run, this problem goes away. I have tested
this
> > on around 10 different user systems, with the same results on all of
them,
> > some are Win2k, some are XP. The report server is running on a dual
> > processor, clean install Server 2003, SQL Server 2000 sp 3a.
> >
> > Any assistance would be greatly appreciated. I'm holding off a full on
> > roll
> > out of this until I get this solved, as it will certainly drive users
> > crazy.
> >
> > Thanks,
> >
> > TomT
>|||thx Christopher...
--
Adrian M.
MCP
"Christopher Conner" <someone@.someplace.com> wrote in message
news:e9GOK2dFFHA.1084@.tk2msftngp13.phx.gbl...
> If you are running Windows 2003 server for your IIS reportserver, then
> this is a simple issue - I'll explain what happens:
> The report service engine, once it is idle for more than the default 20
> minutes, the worker process is shutdown.
> This is controlled by IIS.
> Open up the Internet Information Services (IIS) Manager
> Expand the server node then the application pools.
> On my IIS machine, I created an application pool dedicated to the
> reportserver & reportmanager virtual webs.
> But anyways, for the application pool that the reportserver is pointing to
> if you left everything to their defaults will be the DefaultAppPool.
> Right click the default app pool and select properties.
> There are two things that are checked by default - On the recycling tab
> there is a checkbox for recycling worker processes - it is currently set
> to 1740 minutes (29 hours). Leave it.
> The other one is on the performance tab - which is the one you are
> interested in changing...
> See the "Idle Timeout" section and increase the number of minutes to be 8
> hours a typical working day - 8*60 = 480 minutes.
> Next, to be sure the "morning person" that runs the first report doesn't
> get the delay, set up a schedule for either a dummy or adhoc report to
> fire off like at 6am so that the report component worker processes get
> loaded.
> I hope this helps you.
> There is no need to have a report fire off every minute to keep things
> alive - it is just that the report service was "unloaded" and needed to
> load back up.
> =-Chris
>
>
>
> "TomT" <tomt@.tomt.com> wrote in message
> news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
>> I've just set up a SQL Reporting Services server.
>> All seems to be working fine, however I've noticed that when a report is
>> opened from a user system accessing the report server for the first time,
>> the
>> report takes a very long time to open (a few minutes in some cases), and
>> sometimes I have to abort it and start again.
>> This is a report that should take a couple of seconds at most. Once the
>> report does finally open, it opens fine from then on, even when
>> refreshed, or
>> run by different parameters. Also all other reports availale to the user
>> also
>> run fine after that first one finally opens.
>> There are no errors, just the Report is being generated message. It's
>> like
>> the server has to get aquainted with the machine accessing it the first
>> time...
>> Again, once the report has run, this problem goes away. I have tested
>> this
>> on around 10 different user systems, with the same results on all of
>> them,
>> some are Win2k, some are XP. The report server is running on a dual
>> processor, clean install Server 2003, SQL Server 2000 sp 3a.
>> Any assistance would be greatly appreciated. I'm holding off a full on
>> roll
>> out of this until I get this solved, as it will certainly drive users
>> crazy.
>> Thanks,
>> TomT
>|||Christopher,
Thanks for your help on this. I wonder though, if this is what is going on
in my case. E.g., if I open the report from my system, it runs normally.
Then, if I were to go to a system that had never accessed the report server
before, (right after I had opened it on my system), there is a delay, with
the Report Processing message lasting for up to several minutes.
Since the report had just run on my system, unless I'm missing something, I
don't see how what you described causes the delay on the other system.
Any ideas?
Thanks again,
Tom
"Christopher Conner" wrote:
> If you are running Windows 2003 server for your IIS reportserver, then this
> is a simple issue - I'll explain what happens:
> The report service engine, once it is idle for more than the default 20
> minutes, the worker process is shutdown.
> This is controlled by IIS.
> Open up the Internet Information Services (IIS) Manager
> Expand the server node then the application pools.
> On my IIS machine, I created an application pool dedicated to the
> reportserver & reportmanager virtual webs.
> But anyways, for the application pool that the reportserver is pointing to
> if you left everything to their defaults will be the DefaultAppPool.
> Right click the default app pool and select properties.
> There are two things that are checked by default - On the recycling tab
> there is a checkbox for recycling worker processes - it is currently set to
> 1740 minutes (29 hours). Leave it.
> The other one is on the performance tab - which is the one you are
> interested in changing...
> See the "Idle Timeout" section and increase the number of minutes to be 8
> hours a typical working day - 8*60 = 480 minutes.
> Next, to be sure the "morning person" that runs the first report doesn't get
> the delay, set up a schedule for either a dummy or adhoc report to fire off
> like at 6am so that the report component worker processes get loaded.
> I hope this helps you.
> There is no need to have a report fire off every minute to keep things
> alive - it is just that the report service was "unloaded" and needed to load
> back up.
> =-Chris
>
>
>
> "TomT" <tomt@.tomt.com> wrote in message
> news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> > I've just set up a SQL Reporting Services server.
> >
> > All seems to be working fine, however I've noticed that when a report is
> > opened from a user system accessing the report server for the first time,
> > the
> > report takes a very long time to open (a few minutes in some cases), and
> > sometimes I have to abort it and start again.
> >
> > This is a report that should take a couple of seconds at most. Once the
> > report does finally open, it opens fine from then on, even when refreshed,
> > or
> > run by different parameters. Also all other reports availale to the user
> > also
> > run fine after that first one finally opens.
> >
> > There are no errors, just the Report is being generated message. It's like
> > the server has to get aquainted with the machine accessing it the first
> > time...
> >
> > Again, once the report has run, this problem goes away. I have tested this
> > on around 10 different user systems, with the same results on all of them,
> > some are Win2k, some are XP. The report server is running on a dual
> > processor, clean install Server 2003, SQL Server 2000 sp 3a.
> >
> > Any assistance would be greatly appreciated. I'm holding off a full on
> > roll
> > out of this until I get this solved, as it will certainly drive users
> > crazy.
> >
> > Thanks,
> >
> > TomT
>
>|||Bruce,
My case is not whether the server has been hit recently or not, it's whether
a particular client has hit it. I.e., if I open a report from my system, it's
fine. If I immediately go to a system which has never hit the server before,
it takes quite awhile for the same report, or any other for that matter, to
open...
Thanks for your help
"Bruce L-C [MVP]" wrote:
> This is my experience. What I have seen is what matters is whether anyone
> has hit the report server in awhile. It is not user or report specific. To
> keep things predicatable I have a report open that is a very simple and
> quick report that I set to autorefresh once a minute. This then prevents the
> delay from happening.
> You set autorefresh in the report properties. Try creating a report used
> just by yourself to test this out.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "TomT" <tomt@.tomt.com> wrote in message
> news:7FAEFC07-F89A-42BC-B095-28AD440314A5@.microsoft.com...
> > Jeff,
> >
> > Thanks for your reply. This is when each user runs any report from their
> > system for the first time. E.g., I could run it from my system and it runs
> > properly, however if a user who has never accessed the report server
> before
> > runs the same report, there is a significant delay. Once it finally opens,
> > things run properly for that user from then on (at least so far). However,
> > user B, who has never accessed the server, gets the delay.
> >
> > A bit disappointing, really...
> >
> > "Jeff A. Stucker" wrote:
> >
> > > Is this the first time *each* user runs the same report, or the first
> time
> > > *any* user runs the same report?
> > >
> > > If it's the first time each user runs the report (which your message
> seems
> > > to say), it may be some overhead in setting up a user cache (just
> grasping
> > > at straws here). It would be interesting to run a SQL performance
> monitor
> > > and some other administrative performance tools when this happens.
> Perhaps
> > > you could set logging to verbose for a moment.
> > >
> > > If it's the first time any user runs the report, then it could be a
> source
> > > database (back end) issue. Perhaps it's compiling the SQL statement for
> the
> > > first time, and then the statement is in cache from then on. Or perhaps
> > > it's setting up automatic indexes on the data the first time, and
> they're
> > > there after that. Or, ...
> > >
> > > Cheers,
> > >
> > > '(' Jeff A. Stucker
> > > \
> > >
> > > Business Intelligence
> > > www.criadvantage.com
> > > ---
> > > "TomT" <tomt@.tomt.com> wrote in message
> > > news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> > > > I've just set up a SQL Reporting Services server.
> > > >
> > > > All seems to be working fine, however I've noticed that when a report
> is
> > > > opened from a user system accessing the report server for the first
> time,
> > > > the
> > > > report takes a very long time to open (a few minutes in some cases),
> and
> > > > sometimes I have to abort it and start again.
> > > >
> > > > This is a report that should take a couple of seconds at most. Once
> the
> > > > report does finally open, it opens fine from then on, even when
> refreshed,
> > > > or
> > > > run by different parameters. Also all other reports availale to the
> user
> > > > also
> > > > run fine after that first one finally opens.
> > > >
> > > > There are no errors, just the Report is being generated message. It's
> like
> > > > the server has to get aquainted with the machine accessing it the
> first
> > > > time...
> > > >
> > > > Again, once the report has run, this problem goes away. I have tested
> this
> > > > on around 10 different user systems, with the same results on all of
> them,
> > > > some are Win2k, some are XP. The report server is running on a dual
> > > > processor, clean install Server 2003, SQL Server 2000 sp 3a.
> > > >
> > > > Any assistance would be greatly appreciated. I'm holding off a full on
> > > > roll
> > > > out of this until I get this solved, as it will certainly drive users
> > > > crazy.
> > > >
> > > > Thanks,
> > > >
> > > > TomT
> > >
> > >
> > >
>
>|||Anyone from Microsoft care to comment on this?
"TomT" wrote:
> Christopher,
> Thanks for your help on this. I wonder though, if this is what is going on
> in my case. E.g., if I open the report from my system, it runs normally.
> Then, if I were to go to a system that had never accessed the report server
> before, (right after I had opened it on my system), there is a delay, with
> the Report Processing message lasting for up to several minutes.
> Since the report had just run on my system, unless I'm missing something, I
> don't see how what you described causes the delay on the other system.
> Any ideas?
> Thanks again,
> Tom
> "Christopher Conner" wrote:
> > If you are running Windows 2003 server for your IIS reportserver, then this
> > is a simple issue - I'll explain what happens:
> >
> > The report service engine, once it is idle for more than the default 20
> > minutes, the worker process is shutdown.
> >
> > This is controlled by IIS.
> >
> > Open up the Internet Information Services (IIS) Manager
> > Expand the server node then the application pools.
> > On my IIS machine, I created an application pool dedicated to the
> > reportserver & reportmanager virtual webs.
> > But anyways, for the application pool that the reportserver is pointing to
> > if you left everything to their defaults will be the DefaultAppPool.
> > Right click the default app pool and select properties.
> > There are two things that are checked by default - On the recycling tab
> > there is a checkbox for recycling worker processes - it is currently set to
> > 1740 minutes (29 hours). Leave it.
> >
> > The other one is on the performance tab - which is the one you are
> > interested in changing...
> > See the "Idle Timeout" section and increase the number of minutes to be 8
> > hours a typical working day - 8*60 = 480 minutes.
> >
> > Next, to be sure the "morning person" that runs the first report doesn't get
> > the delay, set up a schedule for either a dummy or adhoc report to fire off
> > like at 6am so that the report component worker processes get loaded.
> >
> > I hope this helps you.
> >
> > There is no need to have a report fire off every minute to keep things
> > alive - it is just that the report service was "unloaded" and needed to load
> > back up.
> >
> > =-Chris
> >
> >
> >
> >
> >
> >
> >
> > "TomT" <tomt@.tomt.com> wrote in message
> > news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> > > I've just set up a SQL Reporting Services server.
> > >
> > > All seems to be working fine, however I've noticed that when a report is
> > > opened from a user system accessing the report server for the first time,
> > > the
> > > report takes a very long time to open (a few minutes in some cases), and
> > > sometimes I have to abort it and start again.
> > >
> > > This is a report that should take a couple of seconds at most. Once the
> > > report does finally open, it opens fine from then on, even when refreshed,
> > > or
> > > run by different parameters. Also all other reports availale to the user
> > > also
> > > run fine after that first one finally opens.
> > >
> > > There are no errors, just the Report is being generated message. It's like
> > > the server has to get aquainted with the machine accessing it the first
> > > time...
> > >
> > > Again, once the report has run, this problem goes away. I have tested this
> > > on around 10 different user systems, with the same results on all of them,
> > > some are Win2k, some are XP. The report server is running on a dual
> > > processor, clean install Server 2003, SQL Server 2000 sp 3a.
> > >
> > > Any assistance would be greatly appreciated. I'm holding off a full on
> > > roll
> > > out of this until I get this solved, as it will certainly drive users
> > > crazy.
> > >
> > > Thanks,
> > >
> > > TomT
> >
> >
> >|||Actually, this is a different issue - remember, the report manager uses NT
authentication - so it has to validate the user before allowing them access
to those resources - in this case - the report manager so you can view the
reports.
I have some customers who have domain controllers that take forever (i.e. a
few minutes "delay" on logon) when the user signs onto the domain.
On the web server that is running your report manager, find out what domain
controller is authenicating the users - you can do this by going to the
command prompt and typing "Set logonserver" and it will tell you the name of
the DC that is authenticating your users for the resources on the machine.
I use the "divide & conquer" method to troubleshooting. Lets try to
eliminate what the cause is. I would recommend, ONLY FOR A TEST, that you
access the report anonymously (allow anonymous) and bypass the
authentication. Of course, I do not know if this is possible. But at least
this would tell you whether the slow down is based on getting users
authenticated with the resources, or a different issue entirely.
I wish I could provide more information.
=-Chris
"TomT" <tomt@.tomt.com> wrote in message
news:EF3E6243-43D8-42A0-A027-84C58B638553@.microsoft.com...
> Christopher,
> Thanks for your help on this. I wonder though, if this is what is going on
> in my case. E.g., if I open the report from my system, it runs normally.
> Then, if I were to go to a system that had never accessed the report
> server
> before, (right after I had opened it on my system), there is a delay, with
> the Report Processing message lasting for up to several minutes.
> Since the report had just run on my system, unless I'm missing something,
> I
> don't see how what you described causes the delay on the other system.
> Any ideas?
> Thanks again,
> Tom
> "Christopher Conner" wrote:
>> If you are running Windows 2003 server for your IIS reportserver, then
>> this
>> is a simple issue - I'll explain what happens:
>> The report service engine, once it is idle for more than the default 20
>> minutes, the worker process is shutdown.
>> This is controlled by IIS.
>> Open up the Internet Information Services (IIS) Manager
>> Expand the server node then the application pools.
>> On my IIS machine, I created an application pool dedicated to the
>> reportserver & reportmanager virtual webs.
>> But anyways, for the application pool that the reportserver is pointing
>> to
>> if you left everything to their defaults will be the DefaultAppPool.
>> Right click the default app pool and select properties.
>> There are two things that are checked by default - On the recycling tab
>> there is a checkbox for recycling worker processes - it is currently set
>> to
>> 1740 minutes (29 hours). Leave it.
>> The other one is on the performance tab - which is the one you are
>> interested in changing...
>> See the "Idle Timeout" section and increase the number of minutes to be 8
>> hours a typical working day - 8*60 = 480 minutes.
>> Next, to be sure the "morning person" that runs the first report doesn't
>> get
>> the delay, set up a schedule for either a dummy or adhoc report to fire
>> off
>> like at 6am so that the report component worker processes get loaded.
>> I hope this helps you.
>> There is no need to have a report fire off every minute to keep things
>> alive - it is just that the report service was "unloaded" and needed to
>> load
>> back up.
>> =-Chris
>>
>>
>>
>> "TomT" <tomt@.tomt.com> wrote in message
>> news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
>> > I've just set up a SQL Reporting Services server.
>> >
>> > All seems to be working fine, however I've noticed that when a report
>> > is
>> > opened from a user system accessing the report server for the first
>> > time,
>> > the
>> > report takes a very long time to open (a few minutes in some cases),
>> > and
>> > sometimes I have to abort it and start again.
>> >
>> > This is a report that should take a couple of seconds at most. Once the
>> > report does finally open, it opens fine from then on, even when
>> > refreshed,
>> > or
>> > run by different parameters. Also all other reports availale to the
>> > user
>> > also
>> > run fine after that first one finally opens.
>> >
>> > There are no errors, just the Report is being generated message. It's
>> > like
>> > the server has to get aquainted with the machine accessing it the first
>> > time...
>> >
>> > Again, once the report has run, this problem goes away. I have tested
>> > this
>> > on around 10 different user systems, with the same results on all of
>> > them,
>> > some are Win2k, some are XP. The report server is running on a dual
>> > processor, clean install Server 2003, SQL Server 2000 sp 3a.
>> >
>> > Any assistance would be greatly appreciated. I'm holding off a full on
>> > roll
>> > out of this until I get this solved, as it will certainly drive users
>> > crazy.
>> >
>> > Thanks,
>> >
>> > TomT
>>|||Thanks Chris, I'll see if I can test that. According to our Domain guy tho,
we have a fast login validation. Also, so far it seems to be more machine
specific, as opposed to user accounts...
"Christopher Conner" wrote:
> Actually, this is a different issue - remember, the report manager uses NT
> authentication - so it has to validate the user before allowing them access
> to those resources - in this case - the report manager so you can view the
> reports.
> I have some customers who have domain controllers that take forever (i.e. a
> few minutes "delay" on logon) when the user signs onto the domain.
> On the web server that is running your report manager, find out what domain
> controller is authenicating the users - you can do this by going to the
> command prompt and typing "Set logonserver" and it will tell you the name of
> the DC that is authenticating your users for the resources on the machine.
> I use the "divide & conquer" method to troubleshooting. Lets try to
> eliminate what the cause is. I would recommend, ONLY FOR A TEST, that you
> access the report anonymously (allow anonymous) and bypass the
> authentication. Of course, I do not know if this is possible. But at least
> this would tell you whether the slow down is based on getting users
> authenticated with the resources, or a different issue entirely.
> I wish I could provide more information.
> =-Chris
>
> "TomT" <tomt@.tomt.com> wrote in message
> news:EF3E6243-43D8-42A0-A027-84C58B638553@.microsoft.com...
> > Christopher,
> >
> > Thanks for your help on this. I wonder though, if this is what is going on
> > in my case. E.g., if I open the report from my system, it runs normally.
> > Then, if I were to go to a system that had never accessed the report
> > server
> > before, (right after I had opened it on my system), there is a delay, with
> > the Report Processing message lasting for up to several minutes.
> >
> > Since the report had just run on my system, unless I'm missing something,
> > I
> > don't see how what you described causes the delay on the other system.
> >
> > Any ideas?
> >
> > Thanks again,
> >
> > Tom
> >
> > "Christopher Conner" wrote:
> >
> >> If you are running Windows 2003 server for your IIS reportserver, then
> >> this
> >> is a simple issue - I'll explain what happens:
> >>
> >> The report service engine, once it is idle for more than the default 20
> >> minutes, the worker process is shutdown.
> >>
> >> This is controlled by IIS.
> >>
> >> Open up the Internet Information Services (IIS) Manager
> >> Expand the server node then the application pools.
> >> On my IIS machine, I created an application pool dedicated to the
> >> reportserver & reportmanager virtual webs.
> >> But anyways, for the application pool that the reportserver is pointing
> >> to
> >> if you left everything to their defaults will be the DefaultAppPool.
> >> Right click the default app pool and select properties.
> >> There are two things that are checked by default - On the recycling tab
> >> there is a checkbox for recycling worker processes - it is currently set
> >> to
> >> 1740 minutes (29 hours). Leave it.
> >>
> >> The other one is on the performance tab - which is the one you are
> >> interested in changing...
> >> See the "Idle Timeout" section and increase the number of minutes to be 8
> >> hours a typical working day - 8*60 = 480 minutes.
> >>
> >> Next, to be sure the "morning person" that runs the first report doesn't
> >> get
> >> the delay, set up a schedule for either a dummy or adhoc report to fire
> >> off
> >> like at 6am so that the report component worker processes get loaded.
> >>
> >> I hope this helps you.
> >>
> >> There is no need to have a report fire off every minute to keep things
> >> alive - it is just that the report service was "unloaded" and needed to
> >> load
> >> back up.
> >>
> >> =-Chris
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> "TomT" <tomt@.tomt.com> wrote in message
> >> news:3031983D-75F9-466C-AD3A-3D76F0BEBDC5@.microsoft.com...
> >> > I've just set up a SQL Reporting Services server.
> >> >
> >> > All seems to be working fine, however I've noticed that when a report
> >> > is
> >> > opened from a user system accessing the report server for the first
> >> > time,
> >> > the
> >> > report takes a very long time to open (a few minutes in some cases),
> >> > and
> >> > sometimes I have to abort it and start again.
> >> >
> >> > This is a report that should take a couple of seconds at most. Once the
> >> > report does finally open, it opens fine from then on, even when
> >> > refreshed,
> >> > or
> >> > run by different parameters. Also all other reports availale to the
> >> > user
> >> > also
> >> > run fine after that first one finally opens.
> >> >
> >> > There are no errors, just the Report is being generated message. It's
> >> > like
> >> > the server has to get aquainted with the machine accessing it the first
> >> > time...
> >> >
> >> > Again, once the report has run, this problem goes away. I have tested
> >> > this
> >> > on around 10 different user systems, with the same results on all of
> >> > them,
> >> > some are Win2k, some are XP. The report server is running on a dual
> >> > processor, clean install Server 2003, SQL Server 2000 sp 3a.
> >> >
> >> > Any assistance would be greatly appreciated. I'm holding off a full on
> >> > roll
> >> > out of this until I get this solved, as it will certainly drive users
> >> > crazy.
> >> >
> >> > Thanks,
> >> >
> >> > TomT
> >>
> >>
> >>
>
>