I'm facing an issue with subscription creation. This used to work well and then it broke some time ago. We have an web app that calls RS WS for Subscription creation, namely CreateSubscription(). The client code is very similar to one shown in here. http://msdn.microsoft.com/en-us/library/reportservice2005.reportingservice2005.createsubscription.aspx Now once working code is not working. Obviously some settings were changed. This is now throwing out exception. rsDeliveryError400A subscription delivery error has occurred. http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsDeliveryError&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.4053.00 Microsoft SQL Server Reporting Services9.00.4053.00127Os Independent 1033 Reporting Services Library A subscription delivery error has occurred. Reporting Services Library One of the extension parameters is not valid for the following reason: The account you are using does not have administrator privileges. A subscription cannot be created for test@test.com One thing I noticed is that if I were to use NETWORK SERVICE in TO field, this error is not shown, instead I get slightly different error. ..... You do not have permission to modify the value for "CC". By using Network Service as a TO field alias, RS is satisfied with it. However, it still doesn't have proper permission to set CC. Any help will be greatly appreciated.

Hey seems the error was with access privillege used to create subsciptions. Try giving the admin roles for the user who is used for creating/executing the subscription in the reportserver and Test. Lets check it.Regards, KarthikShanth. "Mark as Answer" if this helps you!

Thank you for replying. Since Network Service was ok with TO address, we gave Network Service the admin right in SQL. That didn't help. I think we are not sure who (or which account) is attempting to create the subscription. It is a web app that is attempting to create subscription. Is there a way to debug this at RS server side?

I would like to inform that I resolve this issue by allowing the user to have Content Manager role. This is, however, a security risk allowing full management to the user. I don't have root cause of this issue and this is just a workaround. I do wish if there is another solution I can try. I did suspect that KB970892 caused the working environment to suddently throw exception but I don't have solid proof of timeline when this start occurring. I would like to hear from others if there is another way out. Thanks.

I just bumped into a similar issue just using ordinary SharePoint Integrated Mode. It seems the equivalent permission required in that scenario is Full Control (gulp) of at least the Report in question. This is just a ridiculous irritation IMO - I cant recommend to take the security risk so users will have to set up Outlook rules etc - not a good solution. And how about some doco on this Microsoft!?