Potter,
I have a shared datasource that is using the SA account as the user account.
Now the reports are being used internal only. What is puzzling is that once
I fire the reports from the Report Server directly then fire them from the
browser they work fine. It is when I do not launch the reports locally from
the Report Server that they fail to get a connection. If a report does not
come up right away, I RDP into the Report Server and launch the reports
directly from the server and then try them through the browser and they fire
with no problem. The Security model for SQL is Mixed. The Virtual directory
is set to Integrated Security. The credentials are stored for the database
connections.
This is a little unnerving. You think that you have it fixed and then wham
it shows it's ugly face. Thanks for your help.
Michael W. Krout, MCSE, MCT
[quoted text, click to view] "Potter" wrote:
> What's you SQL security model? Windows or Mixed? How is your report
> datasource security figured? Windows or stored credentials or prompted?
> How is the security configured for the report server virtual directory?
>
> This is a stab in the dark, but if everything is configured as Windows
> and you're coming over the web to your report, you're hitting a site
> that isn't trusted and you're trying to query the db as the anonymous
> user and getting denied.
>
> Andy Potter
>