Asked by:
User Subscription. Failure sending mail: The report server has encountered a configuration error. Mail will not be resent.
Question
-
Hello,
I have the following problem in SQL2008 SP1 Report Server Native mode. The report has a few subscriptions. If subsription is organized by report server Administrator it works fine. But if it is created by regular user with correspondent permisions two issues are observed:
1. Email is not picked up automatically it should be name@domain.com. But only name is picked up. However owner name is correctly set up: domain\name
2. The subscription rises subj exception.
I tried to compare admin and user subscriptions, they are identical. Then I have changed OwnerID field in ReportServer..Subscriptions table. After that subscription works fine.
But I do not like this solution. If I change ownership, the user would not be able neither modify nor browse the subscription.
May be something wrong with impersonation of user subscrioption, not sure. But I have no such kind of problems in Sharepoint mode.- Edited by Andrew_Butenko Friday, July 24, 2009 4:33 AM spelling
All replies
-
-
Yes, I can see the following log entries:
library!WindowsService_0!79c!07/24/2009-08:00:43:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. , AuthzInitializeContextFromSid: Win32 error: 5; possible reason - service account doesn't have rights to check domain user SIDs.;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
library!WindowsService_0!604!07/24/2009-08:00:43:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
I gess I have to change service account from NETWORK SERVICES to domain one
Thanks for the tip. -
-
Check this link for the login issue http://blogs.msdn.com/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx
-
According to this article to work under domain account I have to get rid of <RSWindowsNegotiate/> entry in the following configuration section:
<AuthenticationTypes>
<RSWindowsNegotiate/>
<RSWindowsNTLM/>
</AuthenticationTypes>
When I switch to domain account with NTLM authentication I am able to to avoid authorization dialog to get access to report manager. But I have got new error like this.
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing.
What is that? Domain account can not get access to sql server? That is weird, I used to use this account in all sql tasks, even sql server works under that account on the same box.
The more I dig, the more problems I have. -
I think I have got this issue: http://support.microsoft.com/?kbid=842423
When I try to switch to domain account I have another problem: when user get access to report manager first of all he sees the authorization dialog which does not accept user credentials at all. So, Network Service account allows to get access to report manager smoothly, but does not work with Active Directory and vice-versa.
As it was advised in Method 1 of kb, ReportServerMachineName\Network Service account should be added to AD the Pre-Windows 2000 Compatibility Access group. I am not sure that is the best solution.
Therefore, I have to rephrase my question: How to avoid authorization dialog to get access to report manager if Report Server service account is under domain user?
In RS 2005 there was anonymous access IIS settings. In 2008 I can't change this behaviour in RS configuration snap-in.- Proposed as answer by Kiran1980 Monday, November 15, 2010 4:37 PM
-
-
We had the same issue and managed to solve it using the steps set out in http://support.microsoft.com/?kbid=842423
We had to apply Method 1 and Method 2.
We added the service account running the SQL Agent + Reporting Services to the Active Directory security group “Windows Authorization Access Group”, this allows those accounts to read all user properties in the domain, this is only applicable to domains running in Windows 2003 Native Mode. It’s basically just the steps in method 2 + 3 combined although the MS doc never mentions you need to do it on the Agent service account as well but it is indeed needed.