Groups | Blog | Home
all groups > sql server reporting services > july 2006 >

sql server reporting services : Security Troubleshooting?


Aaron Haley
7/31/2006 1:01:25 PM
We just migrated from 2000 to 2005 on a new box. The migration
documentation was wonderful for 2005 and it answered all of our
questions. Our main reporting page should allow all users of a group to
browse, but it no longer seems to accept the integrated security login
for access. It ends up giving them the HTTP Error 401.1 - Unauthorized:
Access is denied due to invalid credentials error. What's the best
place to start looking to fix this error? I've re-run the config tool
and checked all teh security settings on the current pool and virtual
directories but get the same errors on those users. Administrators of
the box and domain can continue to use the site. very strange.
Aaron Haley
7/31/2006 2:16:54 PM
The domain security group has permission on the reportserver in the
browser role. It's possibly a file permission issue but the
reportserver web directories already have the
reportingserviceswebserviceuser and the reportserveruser listed as
having read and execute.

[quoted text, click to view]
Ben Watts
7/31/2006 3:47:06 PM
We had a similar problem, but it was because the admins had access to
read\write to a specific file or folder and everyone else did not have those
permissiosn. Might want to check folder and file access permissions.

[quoted text, click to view]

Ben Watts
7/31/2006 3:49:39 PM
and did you give the specific group certain permissions on the actual report
server? The group on the domain has certain permissions but you also have
to grant them more permissions via the report server.

[quoted text, click to view]

Ben Watts
7/31/2006 5:02:47 PM
The problem lies with Windows Server 2003 SP1!!!

to resolve, pls refer to http://support.microsoft.com/kb/896861/

I found something that might help.


[quoted text, click to view]

Aaron Haley
7/31/2006 7:59:30 PM
I haven't tried that yet but I might. The application pool account
doesn't seem to be trusted by the AD for kerberos delegation. The
server is checked for delegation and the application pol security is
using a domain account, if I don't use a domain account I get this...
The request failed with HTTP status 401: Unauthorized.
Sounds the exact same as a problem on the MSDN SQLRS forum that someone
else was having. I shouldn't need to edit the SPN with setspn since I'm
trying to connect to the local AD DNS server name should I?
Very strange.

[quoted text, click to view]
Aaron Haley
8/1/2006 8:08:16 AM
Dang. Finally!! The problem was that the SQL server was running under a
domain account. So RS only worked when the app pool was running under a
domain account but then only for domain admins. I needed a SPN for the
SQL server as well.

Use setspn.exe to list SPNs registered to domain user "SQLUser":

setspn.exe -L DOMAIN\SQLUser

To add a SQL SPN:

setspn.exe -A MSSQLSvc/SQLSERVER.domain.com:1433 DOMAIN\SQLUser
{Assigns SQN SQL instance on port 1433 to DOMAIN user "SQLUser"}

[quoted text, click to view]
AddThis Social Bookmark Button