We have installed/configured SQL Server 2008 reporting services on a windows 2008 stand alone server. We can connect to reporting service using other domain accounts, however when we tried to connect using service account (for SQL reporting services), it doesn't connect. It again prompts for username/password. Report url: http://servername/reports-sql1 In system event viewer, we are getting below error message. Log Name: System Source: Microsoft-Windows-Security-Kerberos Date: 8/3/2011 11:44:08 PM Event ID: 4 Task Category: None Level: Error Keywords: Classic User: N/A Computer: <ComputerName.Domain> Description: The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server <SSRS service account>. The target name used was HTTP/<ComputerName.Domain>. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (Domain) is different from the client domain (Domain), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server. But instead of servername if we give IP address, it is able to connect http://IPAddress/Reports_SQL1 We have set the below SPNs for the server. 1. For SQL Server: MSSQLSvc/<ComputerName.Domain>:1433 registered with service account for SQL Server 2. For RS: HTTP/<ComputerName.Domain>:80 registered with service account for SQL Server Reporting We are using different service account for both.

As a workaround, I've removed <RSWindowsNegotiate/> from Authentication Type in rsreportserver.config to use only NTLM autentication. Now I'm able to connect to the report website using reporting service account. So issue seems to be with Kerberos Authentication. Have I made any mistake in creating SPN. However I'm not sure about consequences by doing this. Is there any ?

Hi Mattur, Thanks for your post. Sorry for so delay response. According to your description, you can connect to reporting services using a domain account not the service account (what’s the Service account mean? A build-in account or another domain account, however, it doesn’t matter).By default, the service account is just the account which you used to run your reporting services. While you used the invalid service account to register SPN for your target server, not the domain account which was available to connect to your reporting service, which lead to the issue you faced currently. So I would suggest you to use domain account which was available to use as the services account of your reporting services to register the SPN for your target server, please have a try. More information about how to register a Service Principle Name for a report, please refer to the link below: http://msdn.microsoft.com/en-us/library/cc281382.aspx If you have anything unclear, please feel free to let me know. Thanks, Bill Lu Please remember to mark the replies as answers if they help and unmark them if they provide no help.