Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am a System Administrator and System Customizer on our on-premise CRM 2011 installation, which is in development. I have a C# extension program that provides an interface between users and CRM.
With a recent refresh from the legacy system one of our servers in now returning "principal user... is missing prvCreateAsyncOperation privilege" for all functions called from this program. However, these same functions work fine when the program connects to another CRM server, where I have the same Roles, and it worked fine on this server before the refresh.
My web research on this issue turned up one poster who suggested that on the Security Roles page I need Create privileges for System Jobs, but as System Administrator, shouldn't I have full privileges?
Is there a setting I need to check?
Give the system customizator role too, and try then.
Ville, thanks for responding, but I have both System Customizer and System Administrator roles and I am getting this error. Can you think of anything else?
I have seen this issue when a security role is created from scratch rather than modifying an OOB group. Certain functions, like prvtraceLog and prvCreateAsyncOperation system attributes are not available.
this may not fit your situation, however, the prv missing attributes I've had were historically when a CRM Admin created a role from ground up.
K.C., thanks for responding.
When someone reported this issue I thought something had changed for a custom role, however the only two roles I have are System Customizer and System Administrator, both of which are OOB. Privileges are aggregated so being an Administrator should allow me to do everything but it fails for me too.
MeProgrammer, is the extension a plugin you're running within CRM or an external portal type env? If it's a plugin w/in CRM, are you running it in isolation or not?
Are you on prem or online? Just curious. Depending on the execution type, you may have some other issues. Do you have any trace logs and/or event logs with more info?
On premises, as noted in my initial post. The extension is external and is launched by a button click on Account. It was all working a few days ago.
As a system admin you should access. I have seen this before where a suspected operation is running under the context of the logged in user, or a service account that does not have full permission. I would check to see what context your custom logic is executing under.
Good questions but I am passing the user's GUID in to the C# program from the Account's context, which passes it, in turn, to CRM so we can document who did what.
What could have changed?
All, thanks for helping.
I have found a partial answer: The extension program does its work through a WCF service, and there exists an instance of the service for each server.
When the Guid being passed to the Service was validated, the validation failed because that Guid didn't exist on the other server.
In some as yet unknown way, the Settings file for the Service instance in question was re-pointed to the wrong CRM server. I need to determine how this occurred.
I was mistaken: correcting those Settings did not change the outcome and we continue to get the same prv error.
When I connect to the CRM Service from VS and override the endpointConfigurationName with the local host, the process works, but when I use the normal endpoints to instantiate Service1Client, the error comes up.
maybe a bit to late. But I had the same problem and in my case the user that is running the CRM Windows Services (especially the Async Service) had no Systemadministrator Role in CRM. So it was not the user who was owning the failing workflow, that causes the error.
Business Applications communities