I'm trying to test an upgrade to reporting services 2005. Most everything
works except subscriptions. When the subscription runs it fails with the
error message:

'EXECUTE AS LOGIN' failed for the requested login 'NT AUTHORITY\NETWORK
SERVICE'. The step failed.

I've tried creating an unattended account to run the job (Domain account),
I've tried changing the service account (Domain account), but whenever the
job is added to SQL Server it shows up to run under NT Authority/Network
Service and then when running fails with the above error. If I manually
change the account it runs under, the job works fine, but then the report
manager can't manage the job any more (since it doesn't own it).

I tried changing the ASP.net account for the ReportServer pool (to a Domain
account) in IIS but then the NT service refuses to start.

In our environment at the moment, both Reporting Services and the
ReportServer databases are on the same box. Data is elsewhere, but each
report has appropriate connection logins for that.

Symptom:
Subscription job failed with the error message:
'EXECUTE AS LOGIN' failed for the requested login 'NT AUTHORITY\NETWORK
SERVICE'. The step failed.

A second symptom is that if you try to change the owner of the job, you will
not find or be able to pick NT AUTHORITY\NETWORK SERVICE even though it's a
logon listed in security.

Solution:
Delete NT AUTHORITY/NETWORK SERVICE SQL Server login

Delete NT AUTHORITY/NETWORK SERVICE *schema* from master, msdb,
ReportServer, ReportServerTempDB

Delete NT AUTHORITY/NETWORK SERVICE *user* from master, msdb, ReportServer,
ReportServerTempDB

Create a new login, NT AUTHORITY/NETWORK SERVICE
Add it to the master, msdb, ReportServer, and ReportServerTempDB databases
with RSExec role.

This fixed my problem.

I am having the same issue as you are. It appears that the Network Service
account is a member of the RSExecRole Role in the Reports database and the
RSEcecRole should have execute access for the "dbo.addevent" stored
procedure which all subscriptions call. But I can't get past this. Have
you figured this out yet?

Thanks,

Yes, see my second post. You probabbably just need to delete the NT
AUTHORITY\NETWORK SERVICE account and re-add it with the exact same
permissions. Note that there is more to do than just removing the login,
should be there in my second post. Hope this works for you, was pretty
frustrating for me :)

[quoted text, click to view]