rs.exe - SetReportDataSources error

Hi,
I wanted to ask if anyone else has found a problem with rs.exe when trying to use the SetReportDataSources method.
The line appears as RS.SetReportDataSources(fullpath, dataSources)
The error is BC30456 - 'SetReportDataSorces' is not a member of 'Microsoft.SqlServer.ReportingServices2005.ReportingService2005'.
The aim is to design a single set of reports, that will be deployed to different folders with a different datasource per folder. Each datasource connects to an cube that is set up on a database of client data. There is therefore one database and one cube per client, and all databases and cubes have the same structure. This is being done to allow outside clients to view their own reports without being able to see other clients data.
Anyone else have a similar problem and fixed it, or could offer any hints?
Many thanks - Leo.

In SQL 2005, the name of this method is now called 'SetItemDataSources'. If you want to use the SQL 2000 RS endpoint, you need to run rs.exe with the -e option.

RS Lag on First Report

When I first call for a report (from URL access or called from ASP 3.0), it
takes about 10 seconds before it appears. Subsequent reports take less than
a second to appear. I'm not really sure where this lag is likely to come
from, e.g. IIS, RS, SQL Server, etc.
Where and how do I configure RS to stay "alive" longer once started (session
expiration? compile options?) and also to decrease the lag time for the
first report? Since my application is used 24x7 as far as I'm concerned it
should always be ready and quick.
Thanks.This is due to IIS.
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.
If you have any activity at all then users should never see a delay.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Don Miller" <nospam@.nospam.com> wrote in message
news:utx6vFLHIHA.3548@.TK2MSFTNGP06.phx.gbl...
> When I first call for a report (from URL access or called from ASP 3.0),
> it takes about 10 seconds before it appears. Subsequent reports take less
> than a second to appear. I'm not really sure where this lag is likely to
> come from, e.g. IIS, RS, SQL Server, etc.
> Where and how do I configure RS to stay "alive" longer once started
> (session expiration? compile options?) and also to decrease the lag time
> for the first report? Since my application is used 24x7 as far as I'm
> concerned it should always be ready and quick.
> Thanks.
>|||Thanks.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eZ5PEWLHIHA.700@.TK2MSFTNGP05.phx.gbl...
> This is due to IIS.
> 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.
> If you have any activity at all then users should never see a delay.
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Don Miller" <nospam@.nospam.com> wrote in message
> news:utx6vFLHIHA.3548@.TK2MSFTNGP06.phx.gbl...
>> When I first call for a report (from URL access or called from ASP 3.0),
>> it takes about 10 seconds before it appears. Subsequent reports take less
>> than a second to appear. I'm not really sure where this lag is likely to
>> come from, e.g. IIS, RS, SQL Server, etc.
>> Where and how do I configure RS to stay "alive" longer once started
>> (session expiration? compile options?) and also to decrease the lag time
>> for the first report? Since my application is used 24x7 as far as I'm
>> concerned it should always be ready and quick.
>> Thanks.
>

RS Hidden parameter error

Hi,
We have a report with parameters which works fine but when we want to
recover a hidden parameter which comes from a query (doesn't appears as a
filter), an exception is thrown. In the report parameters properties, we left
in blank the property "Prompt" so that it is not showed as a filter. The
error is this: "An unexpected error occurred in Report Processing. Exception
of type Microsoft.ReportingServices.ReportProcessing.aw was thrown". [This
error is not given without the use of this parameter, of course].
Thanks in advance!I think you have to use a space instead of a blank.
--
Adrian M.
MCP
"Tomas Martinez" <TomasMartinez@.discussions.microsoft.com> wrote in message
news:D6E81616-1A0F-472C-8F6E-8F679BF2EB6A@.microsoft.com...
> Hi,
> We have a report with parameters which works fine but when we want to
> recover a hidden parameter which comes from a query (doesn't appears as a
> filter), an exception is thrown. In the report parameters properties, we
> left
> in blank the property "Prompt" so that it is not showed as a filter. The
> error is this: "An unexpected error occurred in Report Processing.
> Exception
> of type Microsoft.ReportingServices.ReportProcessing.aw was thrown". [This
> error is not given without the use of this parameter, of course].
> Thanks in advance!
>|||Thanks for your answer but it doesn't work. With a space the parameter
appears as a filter :(
Thanks anyway! :)|||Can you confirm that SP1 or SP2 of RS 2000 installed?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tomas Martinez" <TomasMartinez@.discussions.microsoft.com> wrote in message
news:E1365F37-81E9-4D48-9266-15D8DC4C0BA4@.microsoft.com...
> Thanks for your answer but it doesn't work. With a space the parameter
> appears as a filter :(
> Thanks anyway! :)
>|||Yes, SP1 of RS2000 is installed
"Robert Bruckner [MSFT]" wrote:
> Can you confirm that SP1 or SP2 of RS 2000 installed?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Tomas Martinez" <TomasMartinez@.discussions.microsoft.com> wrote in message
> news:E1365F37-81E9-4D48-9266-15D8DC4C0BA4@.microsoft.com...
> >
> > Thanks for your answer but it doesn't work. With a space the parameter
> > appears as a filter :(
> >
> > Thanks anyway! :)
> >
>
>

RS doesn't works under ASP.NET 2.0?

Hi,
when I switch my reportserver virtual folder to the ASp.net2.0 I receive
this error:
"Failed to load expression host assembly"
this error appears only when I try to render a report, I can list reports or
I can access the webservice without any error.
any solution?
thanks.
Jerome.RS 2000 is not a ASP.Net 2.0 app. It uses the 1.1 framework. RS 2005 is a
ASP.Net 2.0 app.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:%23ndrIwI9FHA.1332@.tk2msftngp13.phx.gbl...
> Hi,
> when I switch my reportserver virtual folder to the ASp.net2.0 I receive
> this error:
> "Failed to load expression host assembly"
> this error appears only when I try to render a report, I can list reports
> or I can access the webservice without any error.
> any solution?
> thanks.
> Jerome.
>|||I know, but, for example Sharepoint works fine under ASP.NET 2.0 and its a
1.1 software.
but if I switch the reportserver virtual directory from v1.1 to v2.0,
rendering a report stop working.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%232wwe4P9FHA.1248@.TK2MSFTNGP14.phx.gbl...
> RS 2000 is not a ASP.Net 2.0 app. It uses the 1.1 framework. RS 2005 is a
> ASP.Net 2.0 app.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
> news:%23ndrIwI9FHA.1332@.tk2msftngp13.phx.gbl...
>> Hi,
>> when I switch my reportserver virtual folder to the ASp.net2.0 I receive
>> this error:
>> "Failed to load expression host assembly"
>> this error appears only when I try to render a report, I can list reports
>> or I can access the webservice without any error.
>> any solution?
>> thanks.
>> Jerome.
>>
>|||If you want RS to work, leave it alone at 1.1 or upgrade to RS 2005. Note
that you can leave SQL Server as 2000 and still upgrade RS to 2005. You do
need a 2005 license though. Beside additional features I noticed significant
performance improvements with RS 2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OrI6xeR9FHA.500@.TK2MSFTNGP15.phx.gbl...
>I know, but, for example Sharepoint works fine under ASP.NET 2.0 and its a
>1.1 software.
> but if I switch the reportserver virtual directory from v1.1 to v2.0,
> rendering a report stop working.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%232wwe4P9FHA.1248@.TK2MSFTNGP14.phx.gbl...
>> RS 2000 is not a ASP.Net 2.0 app. It uses the 1.1 framework. RS 2005 is a
>> ASP.Net 2.0 app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
>> news:%23ndrIwI9FHA.1332@.tk2msftngp13.phx.gbl...
>> Hi,
>> when I switch my reportserver virtual folder to the ASp.net2.0 I receive
>> this error:
>> "Failed to load expression host assembly"
>> this error appears only when I try to render a report, I can list
>> reports or I can access the webservice without any error.
>> any solution?
>> thanks.
>> Jerome.
>>
>>
>

RS Authoring over the Internet

It appears that to enable true authoring over the internet, you need to
create local users on the RS/IIS box, and create identical SQL logins so
remote users can build their DSN's for their reports.
Other ideas?
JeffFor one, use AD groups in SQL.|||Nope, doesn't work. Just tried it again to verify. I created a local user on
the box, added him to a local group, created a login for the group, and
added the login to the database role.
When trying to connect over the internet using ISQLW for example, I get
"login failed for user 'erstesting'". Native SQL logins work just fine.
Jeff
"Jerry Nixon" <jerrynixon@.gmail.com> wrote in message
news:36f558cf.0410131248.5c092472@.posting.google.com...
> For one, use AD groups in SQL.