Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
netvbonline
Starting Member
1 Post |
Posted - 2010-09-28 : 17:01:35
|
Hi AllI 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.SummaryBasically, 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 problemWhen running the same reports on the production server the users getAn 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 rightsPlease 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 Thanksnetvbonline |
|
|
|
|