Hi
I'm just getting my feet wet with Scheduled reports in SSRS2005, and have
hit a snag...
The schedule is not working, and when I check the job history on SQL Server
I find the message:
'EXECUTE AS LOGIN' failed for the requested login 'NT AUTHORITY\NETWORK
SERVICE'. The step failed.
I find if I go into Management Studio, I can change the NETWORK SERVICE to a
domain user account, and everything works - but then I can't change the
subscription properties from Report Manager.
SQL Server & SSRS are both running on Windows Server 2003 under a domain
account, and the data/SSRS connection points to an SQL Server 2000 Database
on a different server in the domain.
Any ideas? I've gone through the security recommendations and still can't
find a solution.
Regards
GrantHi
Don't worry about responding to this one - I figured it out...
Fixed it by setting everything to use the NetworkService account, except for
the SQL Agent - I found one of my mistakes was changing the account from the
Service Manager, instead of the SQL Server Configuration Manager.
Anyway - all is well and reports are running as scheduled.
Thanks
Grant
"Grant Morgan" <grantmorgan@.noemail.noemail> wrote in message
news:ujq4Jos3GHA.696@.TK2MSFTNGP03.phx.gbl...
> Hi
> I'm just getting my feet wet with Scheduled reports in SSRS2005, and have
> hit a snag...
> The schedule is not working, and when I check the job history on SQL
> Server I find the message:
> 'EXECUTE AS LOGIN' failed for the requested login 'NT AUTHORITY\NETWORK
> SERVICE'. The step failed.
> I find if I go into Management Studio, I can change the NETWORK SERVICE to
> a domain user account, and everything works - but then I can't change the
> subscription properties from Report Manager.
> SQL Server & SSRS are both running on Windows Server 2003 under a domain
> account, and the data/SSRS connection points to an SQL Server 2000
> Database on a different server in the domain.
> Any ideas? I've gone through the security recommendations and still can't
> find a solution.
> Regards
> Grant
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment