I'm attempting to ude the email notification through a subscription in SSRS 2008 R2 but am getting the following error: An error has occurred during report processing. The logs say: library!WindowsService_19!720!09/24/2010-10:10:25:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 5; possible reason - service account doesn't have rights to check domain user SIDs., Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ; processing!WindowsService_19!720!09/24/2010-10:10:25:: e ERROR: An exception has occurred in data set 'ComponentList'. Details: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. processing!WindowsService_19!720!09/24/2010-10:10:25:: i INFO: DataPrefetch abort handler called for Report with ID=. Aborting data sources ... processing!WindowsService_19!720!09/24/2010-10:10:25:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: , Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. --- End of inner exception stack trace ---; processing!WindowsService_19!720!09/24/2010-10:10:25:: w WARN: Data source ' Data source for shared dataset': Report processing has been aborted. processing!WindowsService_19!720!09/24/2010-10:10:25:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: , Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. --- End of inner exception stack trace ---; library!WindowsService_19!720!09/24/2010-10:10:25:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties. notification!WindowsService_19!720!09/24/2010-10:10:25:: e ERROR: Error occured processing subscription 9c61fb9c-8ce7-4687-870b-7433b53e422a: An error has occurred during report processing. What am I doing wrong?

Hi Dan, Based on the "possible reason - service account doesn't have rights to check domain user SIDs" logs, this is a permission issue. I would suggest you configure the Reporting Services to run under a domain user account, to do it, open Reporting Services configuration manager tool->Service Account->type a domain user who has permission to check domain user SIDs. See http://support.microsoft.com/kb/842423 for more methods to resolve this issue. thanks, Jerry

Thanks Jerry - we had done this prior to my post - but it did not work. A few additional questions would help clarify: 1. Does the Service Account need to be a Service Principle Name (SPN)? 2. We ran the SSRS Service account under a domain user account. Since SSRS Subscriptions require SqlAgent to be running, does SqlAgent also need to be running under a domain user account for email notifications to work? 3. The thing we haven't tried was to have the SSRS Execution account run under a domain user account. It didn't seem like it should have to. Is this something we should try to troubleshoot the problem?

Hi Dan, This might be caused because the reporting services server and the smpt sever are in different domain. So, the domain user of reporting services domain don't have rights to check the other domain user Sid. To solve it, 1. If possible, create a trust between the 2 domain. 2. As you said, register the SPN for the service account so that the user can check the other domain user sids. 3. Ran through the steps listed in Method 3 at http://support.microsoft.com/kb/842423 to give non-admin users read privileges on the SSRS service account. After this emails sent successfully from subscriptions created by those non-admin users. please try any one of the above, and give us a feedback. thanks, Jerry

Thanks Jerry! Will try all 3 and report back. Been called away on other responsibilities - so it may take me a week to get to this challenge. thanks for your patience...

Jerry, Yes changing to Doman user fixed it but I would like to understand why. If SQL 2005 Ent / Windows 2003 Ent environment has no issues for subscription then why does SQL 2008 R2 Ent/ Windows 2008 R2 Ent have issues when the reporting services in both cases has been configured extactly the same way?