Logon failure: the user has not been granted the requested logon t

I get the following error when I try running a report using Reporting
Services 2005. The Data Source gets to SQL Server using a domain account. The
Application Pool is running under NETWORK SERVICE.
I see a lot of postings about allowing for Logon Locally. I am sure this
could fix the issue, but why is that standard practice? I don't allow that
for impersonating a user in a standard web application (with web.config --
impersonate user).
===== Error ========= An error has occurred during report processing.
Cannot impersonate user for data source 'DataSourceName'.
Logon failed.
Logon failure: the user has not been granted the requested logon type at
this computer. (Exception from HRESULT: 0x80070569)We don't use logon locally rights...
Instead, we grant NETWORK SERVICE account the right to connect to the SQL
Server database (the specific database) instead.
Some administrators would flip out if they had to change their local
security policy. At least as a DBA I can make this change without having to
involve layers of people to get it implemented.
=-Chris
"Sanjay T" <SanjayT@.discussions.microsoft.com> wrote in message
news:2D831614-9BF9-4C7A-B290-13A1DCD23498@.microsoft.com...
>I get the following error when I try running a report using Reporting
> Services 2005. The Data Source gets to SQL Server using a domain account.
> The
> Application Pool is running under NETWORK SERVICE.
> I see a lot of postings about allowing for Logon Locally. I am sure this
> could fix the issue, but why is that standard practice? I don't allow that
> for impersonating a user in a standard web application (with web.config --
> impersonate user).
>
> ===== Error =========> An error has occurred during report processing.
> Cannot impersonate user for data source 'DataSourceName'.
> Logon failed.
> Logon failure: the user has not been granted the requested logon type at
> this computer. (Exception from HRESULT: 0x80070569)