I've created a report for a client using a custom view in the application database. I put the report and view on their server, ran Database Maintenance to sync ownership, and added it to Screens and Report Control Maintenance. One user (out of three) can run the report with no issues. The two other users receive the following error:
I have checked the permissions on the view and they look fine. The only group that the good user belongs to that the others don't is the Administrators group; I temporarily added one of the faulting users to that group to test, but it made no difference. I've deleted the ODBC connection for both the app and system databases and recreated them by running another report.
Any suggestions? Thanks in advance.
Stuart Nottingham
SL doesn't use the domain users explicitly in SQL, it uses the E8 user for select, and the MSDSL Application Role through the program.
No, I was actually referring to the SQL Management Studio. I had given the same permissions to those same "users" in the properties window of the view.
By GUI I think you mean within SL. That only controls the screens and reports the user can access, and not the SQL objects like procs & views.
OK this did the trick! Can you explain why this would work and granting the same rights/privileges through the GUI wouldn't?
Thanks!
Did you grant the proper rights within the SQL view like this?
GRANT SELECT ON [dbo].[YourView] TO [E8F575915A2E4897A517779C0DD7CE]
GO
GRANT CONTROL ON [dbo].[YourView] TO [MSDSL]
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156