web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

System Message 6201 in Custom Report

(0) ShareShare
ReportReport
Posted on by

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:

6201-error.png

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

I have the same question (0)
  • Verified answer
    Mark E Profile Picture
    6,451 on at

    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]

  • Community Member Profile Picture
    on at

    OK this did the trick! Can you explain why this would work and granting the same rights/privileges through the GUI wouldn't?

    Thanks!

  • Mark E Profile Picture
    6,451 on at

    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.

  • Community Member Profile Picture
    on at

    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.

  • Mark E Profile Picture
    6,451 on at

    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 608

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 591 Super User 2026 Season 1

#3
CP04-islander Profile Picture

CP04-islander 430

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans