September 29, 2010 at 5:57 am
Hi All
I say fun but more like 1.5 days of frustration, really pulling my hair out here with this one and hope someone can point out what is going on.
Summary
Basically, I have created a normal testuser1 domain user (basic rights) in Active directory who is a member of a SQL Server 2008 AD reporting group. This domain group is added to Report Manager (Browser Role), so anyone in that group can at least view reports.
The reports share a data source which is using Windows Integrated Security for credentials.
There are no SQL Logins associated with either testuser1 or reportinggroup, but yet all users can execute reports.
The problem
When running the same reports on the production server the users get
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'sharedDS'. (rsErrorOpeningConnection)
Login failed for user 'mydomain\myuser'.
The only way round this to great a corresponding SQL login in the database engine and grant the connect, select and execute rights
Please can someone help me understand and find out (i.e. the steps needed) to discover why a SQL login for the AD group is needed on production server, BUT not on the sandbox server?
Many Thanks
netvbonline
October 5, 2010 at 11:54 am
Is the architecture the same? In other words:
client -> reporting services server -> sql server
Where each of these are on separate computers? Or are they combined reporting services & sql server on the same computer in sandbox?
If that's the case (different architectures), has Kerberos delegation been set up in production?
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply