locked
Plug in error RRS feed

  • Question

  • Does anyone know how to resolve the error:

    Event Type: Error
    Event Source: MSCRMWebService
    Event Category: None
    Event ID: 18176
    Description:
    Web Service Plug-in failed in OrganizationId: ; SdkMessageProcessingStepId: ; EntityName: opportunity; Stage: 50; MessageName: Create; AssemblyName: Custom.Crm.Audit, Custom.Crm.Audit, Version=1.0.0.0, Culture=neutral, PublicKeyToken=; ClassName: Custom.Crm.Audit; Exception: Unhandled Exception: System.Web.Services.Protocols.SoapException: Server was unable to process request.
    Detail: <detail><error>
      <code>0x80040220</code>
      <description>SecLib::CheckPrivilege failed. Returned hr = -2147220960, User: , PrivilegeId: </description>
      <type>Platform</type>
    </error></detail>
       at Microsoft.Crm.Extensibility.SdkTypeProxyMetadataServiceWrapper.InternalInvoke(MethodInfo methodInfo, Object[] parameters)
       at Microsoft.Crm.Extensibility.SdkTypeProxyMetadataServiceWrapper.Execute(Object request)
       at Custom.Crm.Audit.Execute(IPluginExecutionContext context)
       at Microsoft.Crm.Extensibility.PluginStep.Execute(PipelineExecutionContext context)

    Thursday, April 8, 2010 3:56 PM

Answers

  • Change plug-in registration setting ‘Run As’ from ‘Calling User’ to user with administrator rights and check if the privilege issue still appear.


    Mariusz
    • Marked as answer by Jim Glass Jr Monday, April 12, 2010 3:09 PM
    Sunday, April 11, 2010 11:32 PM

All replies

  • This error states problem regarding security role..the user who is getting this error does not have previledge to perform the task done by Plug in..

    So if you update relevant user security role then it should fix this issue..

    Thursday, April 8, 2010 4:06 PM
    Answerer
  • thats's exactly what I thought and I gave the user full privelges to that custom entity just to test and the problem still persists... weird.
    Thursday, April 8, 2010 4:08 PM
  • check with which entity this custom entity is related to and give permission to related entity as well..

    for e.g. (if this entity links to Account then user should have permission to Append/Append To Permission as well)

     

    Thursday, April 8, 2010 4:23 PM
    Answerer
  • Security privileges can be hard to debug. Sometimes you may be missing an Append or Append To privilege as opposed to Create, Update, or Read.

    I recommend enabling tracing using this KB article: http://support.microsoft.com/kb/907490. The trace log would give you the GUID fo the missing privilege and then you can get the name of the Privilege from the database with SQL statement such as:

    SELECT * FROM PrivilegeBase where PrivilegeId = {GUID from Trace}

    Obviously, you'll need to access the database as a user who has permission SELECT from the base tables and you need to be very careful when you do that. In addition, Tracing has a significant performance impact and I recommend enabling it, reproducing the error, and disabling it right away.

    Good luck,

    Ivan Kurtev

    Friday, April 9, 2010 5:59 AM
  • Change plug-in registration setting ‘Run As’ from ‘Calling User’ to user with administrator rights and check if the privilege issue still appear.


    Mariusz
    • Marked as answer by Jim Glass Jr Monday, April 12, 2010 3:09 PM
    Sunday, April 11, 2010 11:32 PM