hi,
after changing the order of my report parameters (in this example test)
in the menue via the up and down arrow I get the following error
message:
an error occured during local processing. an error occured during
report processing. the value expression for the query parameter 'date'
contains an error: the expression referenced a non-existing parameter
in the report parameters collection.
anybody knows how to do this?
thanksIt sounds like you have either:
A) deleted a parameter which was there before, or more likely
B) changed the sequence required for cascading parameters, i.e. parameters
where one value depends on another one previously entered. It is probably
something to do with one of your report parameters' 'available values' or
'default values' definitions.
HTH,
Magendo_man
"florian" wrote:
> hi,
> after changing the order of my report parameters (in this example test)
> in the menue via the up and down arrow I get the following error
> message:
> an error occured during local processing. an error occured during
> report processing. the value expression for the query parameter 'date'
> contains an error: the expression referenced a non-existing parameter
> in the report parameters collection.
> anybody knows how to do this?
> thanks
>|||You're right I got this error msg. with cascading parameters. The
hierachie goes like this: A-->B-->C Originally I only included A and C
in my parameters but B was missing. So I added B but I didn't like it
to occure as the last report parameter so I wanted to change the
position and then I got the error msg. I get the same error when I
modifie the rdl file and swith the Report Parameters.
Any ideas instead of writing the whole report once again?
magendo_man schrieb:
> It sounds like you have either:
> A) deleted a parameter which was there before, or more likely
> B) changed the sequence required for cascading parameters, i.e. parameters
> where one value depends on another one previously entered. It is probably
> something to do with one of your report parameters' 'available values' or
> 'default values' definitions.
> HTH,
> Magendo_man
> "florian" wrote:
> > hi,
> >
> > after changing the order of my report parameters (in this example test)
> > in the menue via the up and down arrow I get the following error
> > message:
> >
> > an error occured during local processing. an error occured during
> > report processing. the value expression for the query parameter 'date'
> > contains an error: the expression referenced a non-existing parameter
> > in the report parameters collection.
> >
> > anybody knows how to do this?
> >
> > thanks
> >
> >|||Just add parameter B back in to Report Parameters in 2nd position.
"florian" wrote:
> You're right I got this error msg. with cascading parameters. The
> hierachie goes like this: A-->B-->C Originally I only included A and C
> in my parameters but B was missing. So I added B but I didn't like it
> to occure as the last report parameter so I wanted to change the
> position and then I got the error msg. I get the same error when I
> modifie the rdl file and swith the Report Parameters.
> Any ideas instead of writing the whole report once again?
>
> magendo_man schrieb:
> > It sounds like you have either:
> > A) deleted a parameter which was there before, or more likely
> > B) changed the sequence required for cascading parameters, i.e. parameters
> > where one value depends on another one previously entered. It is probably
> > something to do with one of your report parameters' 'available values' or
> > 'default values' definitions.
> >
> > HTH,
> > Magendo_man
> >
> > "florian" wrote:
> >
> > > hi,
> > >
> > > after changing the order of my report parameters (in this example test)
> > > in the menue via the up and down arrow I get the following error
> > > message:
> > >
> > > an error occured during local processing. an error occured during
> > > report processing. the value expression for the query parameter 'date'
> > > contains an error: the expression referenced a non-existing parameter
> > > in the report parameters collection.
> > >
> > > anybody knows how to do this?
> > >
> > > thanks
> > >
> > >
>|||do mean at the data view or where?
magendo_man schrieb:
> Just add parameter B back in to Report Parameters in 2nd position.
> "florian" wrote:
> > You're right I got this error msg. with cascading parameters. The
> > hierachie goes like this: A-->B-->C Originally I only included A and C
> > in my parameters but B was missing. So I added B but I didn't like it
> > to occure as the last report parameter so I wanted to change the
> > position and then I got the error msg. I get the same error when I
> > modifie the rdl file and swith the Report Parameters.
> >
> > Any ideas instead of writing the whole report once again?
> >
> >
> > magendo_man schrieb:
> >
> > > It sounds like you have either:
> > > A) deleted a parameter which was there before, or more likely
> > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > where one value depends on another one previously entered. It is probably
> > > something to do with one of your report parameters' 'available values' or
> > > 'default values' definitions.
> > >
> > > HTH,
> > > Magendo_man
> > >
> > > "florian" wrote:
> > >
> > > > hi,
> > > >
> > > > after changing the order of my report parameters (in this example test)
> > > > in the menue via the up and down arrow I get the following error
> > > > message:
> > > >
> > > > an error occured during local processing. an error occured during
> > > > report processing. the value expression for the query parameter 'date'
> > > > contains an error: the expression referenced a non-existing parameter
> > > > in the report parameters collection.
> > > >
> > > > anybody knows how to do this?
> > > >
> > > > thanks
> > > >
> > > >
> >
> >|||In Layout view select from the menu Report> Report Parameters..
You should then be able to add back in your deleted parameter and move it in
to the correct position.
~ Magendo_man
"florian" wrote:
> do mean at the data view or where?
>
> magendo_man schrieb:
> > Just add parameter B back in to Report Parameters in 2nd position.
> >
> > "florian" wrote:
> >
> > > You're right I got this error msg. with cascading parameters. The
> > > hierachie goes like this: A-->B-->C Originally I only included A and C
> > > in my parameters but B was missing. So I added B but I didn't like it
> > > to occure as the last report parameter so I wanted to change the
> > > position and then I got the error msg. I get the same error when I
> > > modifie the rdl file and swith the Report Parameters.
> > >
> > > Any ideas instead of writing the whole report once again?
> > >
> > >
> > > magendo_man schrieb:
> > >
> > > > It sounds like you have either:
> > > > A) deleted a parameter which was there before, or more likely
> > > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > > where one value depends on another one previously entered. It is probably
> > > > something to do with one of your report parameters' 'available values' or
> > > > 'default values' definitions.
> > > >
> > > > HTH,
> > > > Magendo_man
> > > >
> > > > "florian" wrote:
> > > >
> > > > > hi,
> > > > >
> > > > > after changing the order of my report parameters (in this example test)
> > > > > in the menue via the up and down arrow I get the following error
> > > > > message:
> > > > >
> > > > > an error occured during local processing. an error occured during
> > > > > report processing. the value expression for the query parameter 'date'
> > > > > contains an error: the expression referenced a non-existing parameter
> > > > > in the report parameters collection.
> > > > >
> > > > > anybody knows how to do this?
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > >
> > >
>sql
Showing posts with label order. Show all posts
Showing posts with label order. Show all posts
Friday, March 30, 2012
Tuesday, March 20, 2012
Report Manager-Tab Order
I have a mystery. I have a series of reports. Each report has the same
basic parameters all of which except for dates have default values. The
first two are From Date and Through Date. I have couple dozen of these
reports. When I select a report via Report Manager I click my mouse in the
first parameter box. I type date desired and hit tab key. Cursor goes to
Through Date. I type that in and then pressing the enter key activates "view
report". On a small handful of these reports the behavior is different. I
select these from repot manager and put the cursor inthe first parameter box
just like before. Enter the value and then press tab. The cursor does move
to the from date box BUT it doesn't stay there. It immediately leaves.
After this pressing enter does nothing. Using mouse I can put cursor back in
From Date box, but pressing enter still does nothing. I have to actually
click on view report to get it to generate. I'm using Internet Explorer 7.0
and SQL RS 2005. Another strange thing is that these reports are just clones
of each other with some tweaking of the query that returns the data sets.
The same layouts, xml (except query), and properties on all of them. Anyone
have any ideas? Thanks.
--
Thanks, JimOn Aug 9, 2:14 pm, Jim B <J...@.lightning.com> wrote:
> I have a mystery. I have a series of reports. Each report has the same
> basic parameters all of which except for dates have default values. The
> first two are From Date and Through Date. I have couple dozen of these
> reports. When I select a report via Report Manager I click my mouse in the
> first parameter box. I type date desired and hit tab key. Cursor goes to
> Through Date. I type that in and then pressing the enter key activates "view
> report". On a small handful of these reports the behavior is different. I
> select these from repot manager and put the cursor inthe first parameter box
> just like before. Enter the value and then press tab. The cursor does move
> to the from date box BUT it doesn't stay there. It immediately leaves.
> After this pressing enter does nothing. Using mouse I can put cursor back in
> From Date box, but pressing enter still does nothing. I have to actually
> click on view report to get it to generate. I'm using Internet Explorer 7.0
> and SQL RS 2005. Another strange thing is that these reports are just clones
> of each other with some tweaking of the query that returns the data sets.
> The same layouts, xml (except query), and properties on all of them. Anyone
> have any ideas? Thanks.
> --
> Thanks, Jim
>From what I can understand, some of the reports seem to have defaults
for the second parameter and some don't. You may want to check the
default properties of the report parameters to make sure that they are
consistent. Also, you may want to make sure that you have the latest
Microsoft updates (for IE7, SQL Server 2005 SP2, etc). If this does
not resolve the problem, you may want to re-upload the reports. Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Aug 9, 2:14 pm, Jim B <J...@.lightning.com> wrote:
> I have a mystery. I have a series of reports. Each report has the same
> basic parameters all of which except for dates have default values. The
> first two are From Date and Through Date. I have couple dozen of these
> reports. When I select a report via Report Manager I click my mouse in the
> first parameter box. I type date desired and hit tab key. Cursor goes to
> Through Date. I type that in and then pressing the enter key activates "view
> report". On a small handful of these reports the behavior is different. I
> select these from repot manager and put the cursor inthe first parameter box
> just like before. Enter the value and then press tab. The cursor does move
> to the from date box BUT it doesn't stay there. It immediately leaves.
> After this pressing enter does nothing. Using mouse I can put cursor back in
> From Date box, but pressing enter still does nothing. I have to actually
> click on view report to get it to generate. I'm using Internet Explorer 7.0
> and SQL RS 2005. Another strange thing is that these reports are just clones
> of each other with some tweaking of the query that returns the data sets.
> The same layouts, xml (except query), and properties on all of them. Anyone
> have any ideas? Thanks.
> --
> Thanks, Jim
>From what I can understand, some of the reports seem to have defaults
for the second parameter and some don't. You may want to check the
default properties of the report parameters to make sure that they are
consistent. Also, you may want to make sure that you have the latest
Microsoft updates (for IE7, SQL Server 2005 SP2, etc). If this does
not resolve the problem, you may want to re-upload the reports. Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
basic parameters all of which except for dates have default values. The
first two are From Date and Through Date. I have couple dozen of these
reports. When I select a report via Report Manager I click my mouse in the
first parameter box. I type date desired and hit tab key. Cursor goes to
Through Date. I type that in and then pressing the enter key activates "view
report". On a small handful of these reports the behavior is different. I
select these from repot manager and put the cursor inthe first parameter box
just like before. Enter the value and then press tab. The cursor does move
to the from date box BUT it doesn't stay there. It immediately leaves.
After this pressing enter does nothing. Using mouse I can put cursor back in
From Date box, but pressing enter still does nothing. I have to actually
click on view report to get it to generate. I'm using Internet Explorer 7.0
and SQL RS 2005. Another strange thing is that these reports are just clones
of each other with some tweaking of the query that returns the data sets.
The same layouts, xml (except query), and properties on all of them. Anyone
have any ideas? Thanks.
--
Thanks, JimOn Aug 9, 2:14 pm, Jim B <J...@.lightning.com> wrote:
> I have a mystery. I have a series of reports. Each report has the same
> basic parameters all of which except for dates have default values. The
> first two are From Date and Through Date. I have couple dozen of these
> reports. When I select a report via Report Manager I click my mouse in the
> first parameter box. I type date desired and hit tab key. Cursor goes to
> Through Date. I type that in and then pressing the enter key activates "view
> report". On a small handful of these reports the behavior is different. I
> select these from repot manager and put the cursor inthe first parameter box
> just like before. Enter the value and then press tab. The cursor does move
> to the from date box BUT it doesn't stay there. It immediately leaves.
> After this pressing enter does nothing. Using mouse I can put cursor back in
> From Date box, but pressing enter still does nothing. I have to actually
> click on view report to get it to generate. I'm using Internet Explorer 7.0
> and SQL RS 2005. Another strange thing is that these reports are just clones
> of each other with some tweaking of the query that returns the data sets.
> The same layouts, xml (except query), and properties on all of them. Anyone
> have any ideas? Thanks.
> --
> Thanks, Jim
>From what I can understand, some of the reports seem to have defaults
for the second parameter and some don't. You may want to check the
default properties of the report parameters to make sure that they are
consistent. Also, you may want to make sure that you have the latest
Microsoft updates (for IE7, SQL Server 2005 SP2, etc). If this does
not resolve the problem, you may want to re-upload the reports. Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Aug 9, 2:14 pm, Jim B <J...@.lightning.com> wrote:
> I have a mystery. I have a series of reports. Each report has the same
> basic parameters all of which except for dates have default values. The
> first two are From Date and Through Date. I have couple dozen of these
> reports. When I select a report via Report Manager I click my mouse in the
> first parameter box. I type date desired and hit tab key. Cursor goes to
> Through Date. I type that in and then pressing the enter key activates "view
> report". On a small handful of these reports the behavior is different. I
> select these from repot manager and put the cursor inthe first parameter box
> just like before. Enter the value and then press tab. The cursor does move
> to the from date box BUT it doesn't stay there. It immediately leaves.
> After this pressing enter does nothing. Using mouse I can put cursor back in
> From Date box, but pressing enter still does nothing. I have to actually
> click on view report to get it to generate. I'm using Internet Explorer 7.0
> and SQL RS 2005. Another strange thing is that these reports are just clones
> of each other with some tweaking of the query that returns the data sets.
> The same layouts, xml (except query), and properties on all of them. Anyone
> have any ideas? Thanks.
> --
> Thanks, Jim
>From what I can understand, some of the reports seem to have defaults
for the second parameter and some don't. You may want to check the
default properties of the report parameters to make sure that they are
consistent. Also, you may want to make sure that you have the latest
Microsoft updates (for IE7, SQL Server 2005 SP2, etc). If this does
not resolve the problem, you may want to re-upload the reports. Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
Report Manager Start Up
I believe that I read somewhere in the past that there was a setting in IIS
that you could change in order to have the Report Manager not recompile on
first request. As we all know it takes an unusually long time for Report
Manager to start up the first time you call the application. I would like to
know if there is a setting or change that I can make in order to have Report
Manager Load faster.
Thanks,
--
Andrew
MCSA,MCDBAHi,
I believe the setting you are looking for is the "Shutdown worker processes
after being idle for..." on the Performance tab of the application pool that
the Reports virtual directory is assigned to.
See old post below for details:
>>>>>>>>>>
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
>>>>>>>>>>
"Andrew" wrote:
> I believe that I read somewhere in the past that there was a setting in IIS
> that you could change in order to have the Report Manager not recompile on
> first request. As we all know it takes an unusually long time for Report
> Manager to start up the first time you call the application. I would like to
> know if there is a setting or change that I can make in order to have Report
> Manager Load faster.
> Thanks,
> --
> Andrew
> MCSA,MCDBA|||Chris,
Thanks, that is exactly what I was looking for.
--
Andrew
MCSA,MCDBA
"Oweste" wrote:
> Hi,
> I believe the setting you are looking for is the "Shutdown worker processes
> after being idle for..." on the Performance tab of the application pool that
> the Reports virtual directory is assigned to.
> See old post below for details:
> >>>>>>>>>>
> 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
> >>>>>>>>>>
>
> "Andrew" wrote:
> > I believe that I read somewhere in the past that there was a setting in IIS
> > that you could change in order to have the Report Manager not recompile on
> > first request. As we all know it takes an unusually long time for Report
> > Manager to start up the first time you call the application. I would like to
> > know if there is a setting or change that I can make in order to have Report
> > Manager Load faster.
> >
> > Thanks,
> >
> > --
> > Andrew
> > MCSA,MCDBA
that you could change in order to have the Report Manager not recompile on
first request. As we all know it takes an unusually long time for Report
Manager to start up the first time you call the application. I would like to
know if there is a setting or change that I can make in order to have Report
Manager Load faster.
Thanks,
--
Andrew
MCSA,MCDBAHi,
I believe the setting you are looking for is the "Shutdown worker processes
after being idle for..." on the Performance tab of the application pool that
the Reports virtual directory is assigned to.
See old post below for details:
>>>>>>>>>>
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
>>>>>>>>>>
"Andrew" wrote:
> I believe that I read somewhere in the past that there was a setting in IIS
> that you could change in order to have the Report Manager not recompile on
> first request. As we all know it takes an unusually long time for Report
> Manager to start up the first time you call the application. I would like to
> know if there is a setting or change that I can make in order to have Report
> Manager Load faster.
> Thanks,
> --
> Andrew
> MCSA,MCDBA|||Chris,
Thanks, that is exactly what I was looking for.
--
Andrew
MCSA,MCDBA
"Oweste" wrote:
> Hi,
> I believe the setting you are looking for is the "Shutdown worker processes
> after being idle for..." on the Performance tab of the application pool that
> the Reports virtual directory is assigned to.
> See old post below for details:
> >>>>>>>>>>
> 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
> >>>>>>>>>>
>
> "Andrew" wrote:
> > I believe that I read somewhere in the past that there was a setting in IIS
> > that you could change in order to have the Report Manager not recompile on
> > first request. As we all know it takes an unusually long time for Report
> > Manager to start up the first time you call the application. I would like to
> > know if there is a setting or change that I can make in order to have Report
> > Manager Load faster.
> >
> > Thanks,
> >
> > --
> > Andrew
> > MCSA,MCDBA
Report Manager slow to open
I have been trying various things I have read about in order to solve
the problem of Report Manager being very slow to open for the first
user. I have set the Idle Timeout section in IIS to 480 minutes. I have
created a scheduled report to run every 8 hours. (My client is a 24/7
organization.) I read somewhere that a fix was to refresh a report
every five minutes. I'm not sure how to refresh a report, but I did set
a snapshot to run every hour.
Setting the Idle Timeout to 480 minutes means that within an 8 hour
period the problem is solved. But there is still the problem of the
very slow open for the first user of the shift.
Creating the scheduled report and setting the snapshot have not solved
the problem. I am using Reporting Services 2000 and the scheduled
report and snapshot both contain no data because this client is
connecting to Access databases rather than SQL Server and the Access
database causes problems with both the schedule and the snapshot. Any
suggestions of what I can do to not cause the first user of the shift
to wait a minute or longer for Report Manager to open?
Thanks very much.
LisI would have thought that running a scheduled report every hour would work.
However, I guess because it returns nothing then it isn't doing what it
needs to do to wake up. Before I knew about the IIS configuration (which you
have done) I had a report open on my desktop and I set it to refresh. I did
it every 5 minutes because it was data I wanted to see. You obviously do not
have to have it do that. In layout, Report Menu-> Report Properties.
AutoRefresh
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<info@.techknowsolve.com> wrote in message
news:1168387368.490665.23570@.77g2000hsv.googlegroups.com...
>I have been trying various things I have read about in order to solve
> the problem of Report Manager being very slow to open for the first
> user. I have set the Idle Timeout section in IIS to 480 minutes. I have
> created a scheduled report to run every 8 hours. (My client is a 24/7
> organization.) I read somewhere that a fix was to refresh a report
> every five minutes. I'm not sure how to refresh a report, but I did set
> a snapshot to run every hour.
> Setting the Idle Timeout to 480 minutes means that within an 8 hour
> period the problem is solved. But there is still the problem of the
> very slow open for the first user of the shift.
> Creating the scheduled report and setting the snapshot have not solved
> the problem. I am using Reporting Services 2000 and the scheduled
> report and snapshot both contain no data because this client is
> connecting to Access databases rather than SQL Server and the Access
> database causes problems with both the schedule and the snapshot. Any
> suggestions of what I can do to not cause the first user of the shift
> to wait a minute or longer for Report Manager to open?
> Thanks very much.
> Lis
>|||Hi Bruce - Thanks for the quick reply. I tried scheduling a report
that actually pulls from a SQL Server database and though the
subscription ran just 30 minutes ago, Report Manager still took over a
minute to open... Thanks for the info on refreshing the report.
Unfortunately, that's not really a viable option because I'm trying to
get this to work for a remote client. I don't want anyone there to
have to have anything open on their desktop all day.
Any other suggestions?
Lis|||Other than to tell you that it shouldn't take so long to open Report
Manager. I assume that if you open report manager, close IE, open up IE and
Report Manager the second time it is fast?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<info@.techknowsolve.com> wrote in message
news:1168555000.446295.230260@.o58g2000hsb.googlegroups.com...
> Hi Bruce - Thanks for the quick reply. I tried scheduling a report
> that actually pulls from a SQL Server database and though the
> subscription ran just 30 minutes ago, Report Manager still took over a
> minute to open... Thanks for the info on refreshing the report.
> Unfortunately, that's not really a viable option because I'm trying to
> get this to work for a remote client. I don't want anyone there to
> have to have anything open on their desktop all day.
> Any other suggestions?
> Lis
>|||Yes, it is fast the second time. Here's another thing: yesterday I
read that I could change the idle timeout setting so that it never
times out by removing the check in the box that says "shutdown worker
processes after being idle for (time in minutes):" I did that, but
I'm still having the same problem.
:(
Lis
the problem of Report Manager being very slow to open for the first
user. I have set the Idle Timeout section in IIS to 480 minutes. I have
created a scheduled report to run every 8 hours. (My client is a 24/7
organization.) I read somewhere that a fix was to refresh a report
every five minutes. I'm not sure how to refresh a report, but I did set
a snapshot to run every hour.
Setting the Idle Timeout to 480 minutes means that within an 8 hour
period the problem is solved. But there is still the problem of the
very slow open for the first user of the shift.
Creating the scheduled report and setting the snapshot have not solved
the problem. I am using Reporting Services 2000 and the scheduled
report and snapshot both contain no data because this client is
connecting to Access databases rather than SQL Server and the Access
database causes problems with both the schedule and the snapshot. Any
suggestions of what I can do to not cause the first user of the shift
to wait a minute or longer for Report Manager to open?
Thanks very much.
LisI would have thought that running a scheduled report every hour would work.
However, I guess because it returns nothing then it isn't doing what it
needs to do to wake up. Before I knew about the IIS configuration (which you
have done) I had a report open on my desktop and I set it to refresh. I did
it every 5 minutes because it was data I wanted to see. You obviously do not
have to have it do that. In layout, Report Menu-> Report Properties.
AutoRefresh
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<info@.techknowsolve.com> wrote in message
news:1168387368.490665.23570@.77g2000hsv.googlegroups.com...
>I have been trying various things I have read about in order to solve
> the problem of Report Manager being very slow to open for the first
> user. I have set the Idle Timeout section in IIS to 480 minutes. I have
> created a scheduled report to run every 8 hours. (My client is a 24/7
> organization.) I read somewhere that a fix was to refresh a report
> every five minutes. I'm not sure how to refresh a report, but I did set
> a snapshot to run every hour.
> Setting the Idle Timeout to 480 minutes means that within an 8 hour
> period the problem is solved. But there is still the problem of the
> very slow open for the first user of the shift.
> Creating the scheduled report and setting the snapshot have not solved
> the problem. I am using Reporting Services 2000 and the scheduled
> report and snapshot both contain no data because this client is
> connecting to Access databases rather than SQL Server and the Access
> database causes problems with both the schedule and the snapshot. Any
> suggestions of what I can do to not cause the first user of the shift
> to wait a minute or longer for Report Manager to open?
> Thanks very much.
> Lis
>|||Hi Bruce - Thanks for the quick reply. I tried scheduling a report
that actually pulls from a SQL Server database and though the
subscription ran just 30 minutes ago, Report Manager still took over a
minute to open... Thanks for the info on refreshing the report.
Unfortunately, that's not really a viable option because I'm trying to
get this to work for a remote client. I don't want anyone there to
have to have anything open on their desktop all day.
Any other suggestions?
Lis|||Other than to tell you that it shouldn't take so long to open Report
Manager. I assume that if you open report manager, close IE, open up IE and
Report Manager the second time it is fast?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<info@.techknowsolve.com> wrote in message
news:1168555000.446295.230260@.o58g2000hsb.googlegroups.com...
> Hi Bruce - Thanks for the quick reply. I tried scheduling a report
> that actually pulls from a SQL Server database and though the
> subscription ran just 30 minutes ago, Report Manager still took over a
> minute to open... Thanks for the info on refreshing the report.
> Unfortunately, that's not really a viable option because I'm trying to
> get this to work for a remote client. I don't want anyone there to
> have to have anything open on their desktop all day.
> Any other suggestions?
> Lis
>|||Yes, it is fast the second time. Here's another thing: yesterday I
read that I could change the idle timeout setting so that it never
times out by removing the check in the box that says "shutdown worker
processes after being idle for (time in minutes):" I did that, but
I'm still having the same problem.
:(
Lis
Wednesday, March 7, 2012
Report Layout
I'm working on a report that could potentially require 13 or so datasets in
order to get the specific fields that I need for each section of the report.
The SQL table is structured as follows:
select
year,
branch,
measure,
jan,
feb,
mar
from tblBPM_BP
I was trying to bring all of the measures in on one dataset, but I need to
be able to further filter the data for each section of the report (i.e. Sales
& headcount). Is there a better technique than using a dataset for each
section of the report?What about using filters.
"DJONES" wrote:
> I'm working on a report that could potentially require 13 or so datasets in
> order to get the specific fields that I need for each section of the report.
> The SQL table is structured as follows:
> select
> year,
> branch,
> measure,
> jan,
> feb,
> mar
> from tblBPM_BP
> I was trying to bring all of the measures in on one dataset, but I need to
> be able to further filter the data for each section of the report (i.e. Sales
> & headcount). Is there a better technique than using a dataset for each
> section of the report?
>|||Can I filter out data in a table w/i the report designer?
"Victor" wrote:
> What about using filters.
>
> "DJONES" wrote:
> > I'm working on a report that could potentially require 13 or so datasets in
> > order to get the specific fields that I need for each section of the report.
> > The SQL table is structured as follows:
> >
> > select
> > year,
> > branch,
> > measure,
> > jan,
> > feb,
> > mar
> > from tblBPM_BP
> >
> > I was trying to bring all of the measures in on one dataset, but I need to
> > be able to further filter the data for each section of the report (i.e. Sales
> > & headcount). Is there a better technique than using a dataset for each
> > section of the report?
> >|||Table properties -> Filters
"DJONES" wrote:
> Can I filter out data in a table w/i the report designer?
> "Victor" wrote:
> > What about using filters.
> >
> >
> > "DJONES" wrote:
> >
> > > I'm working on a report that could potentially require 13 or so datasets in
> > > order to get the specific fields that I need for each section of the report.
> > > The SQL table is structured as follows:
> > >
> > > select
> > > year,
> > > branch,
> > > measure,
> > > jan,
> > > feb,
> > > mar
> > > from tblBPM_BP
> > >
> > > I was trying to bring all of the measures in on one dataset, but I need to
> > > be able to further filter the data for each section of the report (i.e. Sales
> > > & headcount). Is there a better technique than using a dataset for each
> > > section of the report?
> > >|||That will do the trick. Thanks!
"Victor" wrote:
> Table properties -> Filters
> "DJONES" wrote:
> > Can I filter out data in a table w/i the report designer?
> >
> > "Victor" wrote:
> >
> > > What about using filters.
> > >
> > >
> > > "DJONES" wrote:
> > >
> > > > I'm working on a report that could potentially require 13 or so datasets in
> > > > order to get the specific fields that I need for each section of the report.
> > > > The SQL table is structured as follows:
> > > >
> > > > select
> > > > year,
> > > > branch,
> > > > measure,
> > > > jan,
> > > > feb,
> > > > mar
> > > > from tblBPM_BP
> > > >
> > > > I was trying to bring all of the measures in on one dataset, but I need to
> > > > be able to further filter the data for each section of the report (i.e. Sales
> > > > & headcount). Is there a better technique than using a dataset for each
> > > > section of the report?
> > > >
order to get the specific fields that I need for each section of the report.
The SQL table is structured as follows:
select
year,
branch,
measure,
jan,
feb,
mar
from tblBPM_BP
I was trying to bring all of the measures in on one dataset, but I need to
be able to further filter the data for each section of the report (i.e. Sales
& headcount). Is there a better technique than using a dataset for each
section of the report?What about using filters.
"DJONES" wrote:
> I'm working on a report that could potentially require 13 or so datasets in
> order to get the specific fields that I need for each section of the report.
> The SQL table is structured as follows:
> select
> year,
> branch,
> measure,
> jan,
> feb,
> mar
> from tblBPM_BP
> I was trying to bring all of the measures in on one dataset, but I need to
> be able to further filter the data for each section of the report (i.e. Sales
> & headcount). Is there a better technique than using a dataset for each
> section of the report?
>|||Can I filter out data in a table w/i the report designer?
"Victor" wrote:
> What about using filters.
>
> "DJONES" wrote:
> > I'm working on a report that could potentially require 13 or so datasets in
> > order to get the specific fields that I need for each section of the report.
> > The SQL table is structured as follows:
> >
> > select
> > year,
> > branch,
> > measure,
> > jan,
> > feb,
> > mar
> > from tblBPM_BP
> >
> > I was trying to bring all of the measures in on one dataset, but I need to
> > be able to further filter the data for each section of the report (i.e. Sales
> > & headcount). Is there a better technique than using a dataset for each
> > section of the report?
> >|||Table properties -> Filters
"DJONES" wrote:
> Can I filter out data in a table w/i the report designer?
> "Victor" wrote:
> > What about using filters.
> >
> >
> > "DJONES" wrote:
> >
> > > I'm working on a report that could potentially require 13 or so datasets in
> > > order to get the specific fields that I need for each section of the report.
> > > The SQL table is structured as follows:
> > >
> > > select
> > > year,
> > > branch,
> > > measure,
> > > jan,
> > > feb,
> > > mar
> > > from tblBPM_BP
> > >
> > > I was trying to bring all of the measures in on one dataset, but I need to
> > > be able to further filter the data for each section of the report (i.e. Sales
> > > & headcount). Is there a better technique than using a dataset for each
> > > section of the report?
> > >|||That will do the trick. Thanks!
"Victor" wrote:
> Table properties -> Filters
> "DJONES" wrote:
> > Can I filter out data in a table w/i the report designer?
> >
> > "Victor" wrote:
> >
> > > What about using filters.
> > >
> > >
> > > "DJONES" wrote:
> > >
> > > > I'm working on a report that could potentially require 13 or so datasets in
> > > > order to get the specific fields that I need for each section of the report.
> > > > The SQL table is structured as follows:
> > > >
> > > > select
> > > > year,
> > > > branch,
> > > > measure,
> > > > jan,
> > > > feb,
> > > > mar
> > > > from tblBPM_BP
> > > >
> > > > I was trying to bring all of the measures in on one dataset, but I need to
> > > > be able to further filter the data for each section of the report (i.e. Sales
> > > > & headcount). Is there a better technique than using a dataset for each
> > > > section of the report?
> > > >
Saturday, February 25, 2012
Report in CRM ?
Hi All,
I created a report for Microsoft CRM 3.0... Do I have to "deploy" it
to the CRM server in order to use it in CRM or only to "build" the RDL
and add it in CRM ?
Any tips on this will be very helpfull
ThanksRDL is all XML, I dont really think "building" does much
"Frank" <flefe2000@.gmail.com> wrote in message
news:1170335048.873329.127820@.s48g2000cws.googlegroups.com...
> Hi All,
> I created a report for Microsoft CRM 3.0... Do I have to "deploy" it
> to the CRM server in order to use it in CRM or only to "build" the RDL
> and add it in CRM ?
> Any tips on this will be very helpfull
> Thanks
>
I created a report for Microsoft CRM 3.0... Do I have to "deploy" it
to the CRM server in order to use it in CRM or only to "build" the RDL
and add it in CRM ?
Any tips on this will be very helpfull
ThanksRDL is all XML, I dont really think "building" does much
"Frank" <flefe2000@.gmail.com> wrote in message
news:1170335048.873329.127820@.s48g2000cws.googlegroups.com...
> Hi All,
> I created a report for Microsoft CRM 3.0... Do I have to "deploy" it
> to the CRM server in order to use it in CRM or only to "build" the RDL
> and add it in CRM ?
> Any tips on this will be very helpfull
> Thanks
>
Subscribe to:
Posts (Atom)