I'd check these items:
Since it ran in development, most likely the first item.
Stored credentials
The report must use stored credentials or no credentials to retrieve
data at run time. You cannot subscribe to a report that is configured to use
the impersonated or delegated credentials of the current user to connect to
an external data source. The stored credentials can be a Windows account or
a database user account. For more information, see Specifying Credential and
Connection Information for Report Data Sources
User dependent values in a report
For standard subscriptions only, you can create subscriptions to
reports that incorporate user account information in a filter or as text
that appears on the report. In the report, the user account name is
specified through a User!UserID expression that resolves to the current
user. When you create a subscription, the user who creates the subscription
is the considered the current user.
No model item security
You cannot subscribe to a Report Builder report that uses a model as a
data source if the model contains model item security settings. Only reports
that use model item security are included in this restriction.
Parameter values
If the report uses parameters, a parameter value must be specified with
the report itself, or in the subscription you define. If default values have
been defined in the report, you can set the parameter value to use the
default. For more information, see Setting Parameters in a Subscription.
Thanks,
Steve MunLeeuw
RJM2 - 11 Jul 2008 17:34 GMT
On Jul 11, 12:04 pm, "Steve MunLeeuw" <steve.munle...@gmail.com>
wrote:
> I'd check these items:
> Since it ran in development, most likely the first item.
[quoted text clipped - 28 lines]
> Thanks,
> Steve MunLeeuw
Steve,
Thanks for the response. I have checked all of those items, and again
it works as a scheduled report on our development server.
I think it has more to do with the user context of the scheduler
trying to access the database driver itself.
Thanks,
Rob
Steve MunLeeuw - 11 Jul 2008 18:01 GMT
Ah, I should have paid more attention to the error message. Looks like the
subscription account requires folder permissions that the driver is in.
http://www.experts-exchange.com/Web_Development/Miscellaneous/Q_21979676.html
Hmmm,
We want specific user credentials for personalized content, but a different
execution account for granting folder permissons. Not sure what the best
answer is for that.
Thanks,
Steve MunLeeuw
RJM2 - 11 Jul 2008 18:18 GMT
> Ah, I should have paid more attention to the error message. Looks like the
> subscription account requires folder permissions that the driver is in.
[quoted text clipped - 8 lines]
> Thanks,
> Steve MunLeeuw
Steve,
I'm not a member of Experts Exchange and couldn't see the answers to
the question. Any chance you feel like summarizing?
Thanks,
Rob
Steve MunLeeuw - 11 Jul 2008 18:42 GMT
I don't have access either, but if you scroll to the bottom past the blanked
out responses they are repeated without the distortion.
Answer:
Do those groups have access to the folder the db2 driver is in?
I'd check the event logs and see if there are any security errors.
From Poster:
Yes both groups have access to the folder. And there are no security errors
logged.
Please ignore my previous comment. It turns out that the account in the
groups is an ASPNET account from the domain instead of the local ASPNET
account. Now I added the local ASPNET account to the group and everything
worked.
Thank you,
Steve MunLeeuw