2005 WebService credentials

We have an app that was running against RS 2000 and we call the web
services for (1) rendering a report and (2) creating subscriptions.
I've changed the web references to look at the ReportExecution2005 and
ReportService2005 web services.
Right now the report renders ok, but when I try to create a
subscription, I get:
"...user data source credentials that are required to execute this
report are not stored in the report server database"
We use impersonation and
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
in each case.
We set rs.url to
http://myserver/ReportServer/ReportExecution2005.asmx
for rendering the report
http://myserver/ReportServer/ReportService2005.asmx
for creating the subscription
I've tried changing the user without effect. The impersonated user has
all possible roles granted in Report Manager.
I have not changed any code going from 2000 to 2005.
Any ideas welcome.
TIA,
JimOk, I'm a bit further.
I went into the data source in Report Manager, and by changing the
credentials
I could save a subscription (although I could not retrieve it with the
guid that resulted).
Right now I'm trying to fing the right setup to allow both the report
execution and the saving of subscriptions.|||Were you able to figure this out?
I am having the same problem. Any help would be greatly appreciated.
"jhcorey@.yahoo.com" wrote:
> We have an app that was running against RS 2000 and we call the web
> services for (1) rendering a report and (2) creating subscriptions.
> I've changed the web references to look at the ReportExecution2005 and
> ReportService2005 web services.
> Right now the report renders ok, but when I try to create a
> subscription, I get:
> "...user data source credentials that are required to execute this
> report are not stored in the report server database"
> We use impersonation and
> rs.Credentials = System.Net.CredentialCache.DefaultCredentials
> in each case.
> We set rs.url to
> http://myserver/ReportServer/ReportExecution2005.asmx
> for rendering the report
> http://myserver/ReportServer/ReportService2005.asmx
> for creating the subscription
> I've tried changing the user without effect. The impersonated user has
> all possible roles granted in Report Manager.
> I have not changed any code going from 2000 to 2005.
> Any ideas welcome.
> TIA,
> Jim
>|||If anyone from Microsoft (or just has the answer to this) is listening...
this is a REAL problem with 2005 reporting services. Storing credentials as
documented does not work and returns an login failure when being used.
These to individuals seemed to be seeing the same problem I'm running into
and no one has offered a suggestion on correction of the issue.
My setup has SQL 2005/RS/IIS on one server so the database is local to RS.
When ever is store the login credentials for the data source, which seems to
be a requred methodology for dynamic subscriptions the result will be a login
failure when attempting to run the report.
"Jessie" wrote:
> Were you able to figure this out?
> I am having the same problem. Any help would be greatly appreciated.
> "jhcorey@.yahoo.com" wrote:
> > We have an app that was running against RS 2000 and we call the web
> > services for (1) rendering a report and (2) creating subscriptions.
> > I've changed the web references to look at the ReportExecution2005 and
> > ReportService2005 web services.
> >
> > Right now the report renders ok, but when I try to create a
> > subscription, I get:
> > "...user data source credentials that are required to execute this
> > report are not stored in the report server database"
> >
> > We use impersonation and
> > rs.Credentials = System.Net.CredentialCache.DefaultCredentials
> > in each case.
> >
> > We set rs.url to
> > http://myserver/ReportServer/ReportExecution2005.asmx
> > for rendering the report
> > http://myserver/ReportServer/ReportService2005.asmx
> > for creating the subscription
> >
> > I've tried changing the user without effect. The impersonated user has
> > all possible roles granted in Report Manager.
> >
> > I have not changed any code going from 2000 to 2005.
> >
> > Any ideas welcome.
> >
> > TIA,
> > Jim
> >
> >