Addressing Privilege Errors in CRM 2011
With CRM 2011 it’s easier than ever for administrators to identify and resolve user permission errors, and to finely-tune the additional privileges that need to be given to users.
When a user tries to do something and the CRM balks at the operation based on their privileges, the user will see this dialog:
As an admin, you have a few options in order to resolve these types of errors:
- Coordinate a time for the user to reproduce the error, and then enable platform tracing on the CRM server while the user reproduces the error. Dig through the platform trace looking for the error code.
- Guess at the privilege required and start wildly adjusting security roles until the error goes away (my personal favorite prior to 2011).
- Ask the user to download the log file and send it to you.
Let’s explore the last option, since it means almost no work for you, the administrator, and that, as always, is the goal.
The user will send you a text file that look like this:
There are two things you want from this log file:
The Depth will be one of 4 values: Global, Deep, Local, or Basic. This value refers to number of slices of pie that the security role privilege requires (4, 3, 2, 1 respectively). For more information on depth, see the “Access Levels” section of this MSDN article.
The PrivilegeName part of the error message tells you exactly what privilege was missing. Copy the PrivilegeName (in the example above: “prvWriteWorkflowSession”) to your clipboard, and surf over to this MSDN page.
Do a CTRL+F to find your clipboard string. When you find it on the page, you get all the information you need to find and correct the privilege in the CRM Security Role, including the Tab to find it on, the Entity you need to adjust, and the privilege you need to modify to the appropriate Depth.
Change the role as required, save it, and ask the user to try again. You may need to perform these steps iteratively until the permission errors go away, but this approach is preferable to guessing and allows you provide the minimum required privilege.
Make A Comment: ( 1 so far )
One Response to “Addressing Privilege Errors in CRM 2011”
TJ Martin
December 14th, 2011
“Guess at the privilege required and start wildly adjusting security roles until the error goes away (my personal favorite prior to 2011).”
Hahah – mine, too!