We have a SSRS service running under a service account (Domain Login) and NT authentication enabled. This service account has admin rights but no remote desktop login permissions on the server where reports are deployed. We are able to deploy the reports with the help of rs.exe command line utility and create subscription using the webservice "CreateSubscription" method. With this approach, we have following issues: i) Created subscriptions are not view-able on browser as we cannot run browser with same login with which report is deployed. So, there is no way to edit the subscriptions once created. I know that we can programatically change subscriptions but given time constraint, it is not possible now. If we deploy reports using one account i.e. 'domain\Service1' and create subscription using another account 'domain\User1', then, when subscription runs, it fails to write the subscription on file share. It fails with "AuthzInitializeContextFromSid: Win32" error. I have gone through following links but found little help: http://msdn.microsoft.com/en-us/library/ms159846.aspx http://support.microsoft.com/kb/842423 We have requirement to run SSRS with service account only. How can we make sure that our reports are deployed and subscriptions are created and executed(written to file share) successfully. Any help is appreciated.ashwin

Hi Ashwin, Thanks for your posting. As we can see from the KB article, the root cause of the "AuthzInitializeContextFromSid: Win32" error should be that the Service Account (not domain\Service1) of SSRS that is installed on the report server computer doesnt have the sufficient permissions to read the TGGAU attributes of the user (i.e. domain\User1) that create the subscriptions. On the server which the reports are deployed to, let assume that the service account that is used to run the SSRS is "domain\Service2". To avoid the issue, please try to add this Service Account to the WAA group on the computer that hosts the report server. For the detailed steps, please see the Method 3 in the following article: http://support.microsoft.com/kb/842423 Hope this helps. Regards, Mike YinMike Yin TechNet Community Support