轉 Not have enough privilege to complete Create operation for an Sdk entity" exception when you register a CRM 4.0 plug-i
2009-04-17 11:28
696 查看
CRM 4.0 introduces the concept of plug-ins that will replace the callouts. CRM 4.0 Plug-in is custom business logic that can be integrated into CRM 4.0's platform. Plug-ins are much more powerful than callouts, but require more work to be deployed successfully. It's sometimes not easy to be successful with plug-in registration if you forget about a specific step.
Today we were trying to deploy new plug-in assembly into CRM 4.0 database. First we used Plug-in Registration Tool for CRM 4.0 delivered with CRM 4.0 SDK. After that we were trying to register plug-in assembly with our custom application.
Unfortunately in both cases the operation was unsuccessful and we were getting the strange looking Soap Exception "Not have enough privilege to complete Create operation for an Sdk entity". At the same time we were able to create any other business entities like contacts, accounts...
Unhandled Exception: System.Web.Services.Protocols.SoapException: Server was unable to process request.
Detail:
<detail>
<error>
<code>0x80040256</code>
<description>Not have enough privilege to complete Create operation for an Sdk entity.</description>
<type>Platform</type>
</error>
</detail>
It looked pretty strange because our user had System Administrator role and in CRM it had all the rights. After few attempts we realized that Active Directory account used to deploy and register new assembly into CRM 4.0 database has to be added into Deployment Administrators group in CRM Deployment Manager.
Here are the steps to accomplish this:
1. Open CRM 4.0 Deployment Manager Console (Start -> All Programs -> Microsoft Dynamics CRM -> Deployment Manager).
2. Go to “Deployment Administrators” node and choose “New Deployment Administrator…” option.
![](http://images.cnblogs.com/cnblogs_com/janmson/deploymentmanager.GIF)
3. Insert appropriate user and confirm selection by clicking “OK” button.
After completing this step, both users were able to register and deploy the assembly successfully. So, remember about this when you try to play with plug-ins with user that you added to CRM :)
Today we were trying to deploy new plug-in assembly into CRM 4.0 database. First we used Plug-in Registration Tool for CRM 4.0 delivered with CRM 4.0 SDK. After that we were trying to register plug-in assembly with our custom application.
Unfortunately in both cases the operation was unsuccessful and we were getting the strange looking Soap Exception "Not have enough privilege to complete Create operation for an Sdk entity". At the same time we were able to create any other business entities like contacts, accounts...
Unhandled Exception: System.Web.Services.Protocols.SoapException: Server was unable to process request.
Detail:
<detail>
<error>
<code>0x80040256</code>
<description>Not have enough privilege to complete Create operation for an Sdk entity.</description>
<type>Platform</type>
</error>
</detail>
It looked pretty strange because our user had System Administrator role and in CRM it had all the rights. After few attempts we realized that Active Directory account used to deploy and register new assembly into CRM 4.0 database has to be added into Deployment Administrators group in CRM Deployment Manager.
Here are the steps to accomplish this:
1. Open CRM 4.0 Deployment Manager Console (Start -> All Programs -> Microsoft Dynamics CRM -> Deployment Manager).
2. Go to “Deployment Administrators” node and choose “New Deployment Administrator…” option.
3. Insert appropriate user and confirm selection by clicking “OK” button.
After completing this step, both users were able to register and deploy the assembly successfully. So, remember about this when you try to play with plug-ins with user that you added to CRM :)
相关文章推荐
- CRM安装问题一:Caller does not have enough privilege to set CallerOriginToken to the specified value
- Register ASP.NET 4.0 An error has occurred: 0x8007b799 You must have administrative rights on this machine in order to ru
- org.hibernate.exception.SQLGrammarException: could not inYou have an error in your SQL syntax;完美解决错误
- "Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased."
- Unable to start debugging on the web server. You do not have permission to debug the application. The URL for this project is in
- You do not appear to have the sources for the 3.5.0-23-generic kernel installed
- Caused by: android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an application
- android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an appli
- Scene is unreachable due to lack of entry points and does not have an identifier for runtime access
- How to create .lib file when you only have .dll and .h files
- android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an application
- android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an appli
- Scene is unreachable due to lack of entry points and does not have an identifier for runtime access
- android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an appli
- Caller does not have enough privilege to set CallerOriginToken to the specified value
- android.view.WindowManager$BadTokenException: Unable to add window — token null is not for an appli
- android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an appl
- java.sql.SQLException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for
- Recover a file even if it was not committed but it has to have been added when you use git reset head by mistake.
- Could not install the app on the device, read the error above for details. Make sure you have an And