Delete Step Errors - Audit Plug-In

Aug 3, 2009 at 2:47 AM

Any suggestions or resolution for the error on Delete Step; details below.  Occurs on Image and Live CRM 4.0 systems.  UR3 and UR5 tested.

  1. All steps are configured related to contact and work appropriately, except delete step . 
  2. Relationship configured 1-to-Many Contact to Audit
  3. Test Create, Update, State Change, Assign.   All successful. 
  4. Test Delete; no error on delete (and no audit as it is not configured)
  5. Add the Delete Step
  6. Test Create, Update, State Change, Assign; all successful
  7. Test Delete Record
  8. Error at delete:
    1. The requested record was not found or you do not have sufficient permissions to view it. 
    2. The record is not deleted (Delete “Test Step 13b” – GUID 90B804DC-CB7F-DE11-A310-0003FFD0167C)
    3. Event Log ASP 2.0.50727.0 Error (on GUID 90B804DC-CB7F-DE11-A310-0003FFD0167C)

Event Type:        Warning

Event Source:    ASP.NET 2.0.50727.0

Event Category:                Web Event

Event ID:              1309

Date:                     8/2/2009

Time:                     6:23:15 PM

User:                     N/A

Computer:          CRM-SRV-01


Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 8/2/2009 6:23:15 PM

Event time (UTC): 8/3/2009 1:23:15 AM

Event ID: 8b1983e5626d466983d8aeaba0439056

Event sequence: 3276

Event occurrence: 1

Event detail code: 0


Application information:

    Application domain: /LM/W3SVC/691827/Root-1-128935342954142416

    Trust level: Full

    Application Virtual Path: /

    Application Path: C:\Inetpub\wwwroot\CRM\

    Machine name: CRM-SRV-01


Process information:

    Process ID: 5020

    Process name: w3wp.exe



Exception information:

    Exception type: CrmObjectNotFoundException

    Exception message: contact With Id = 90b804dc-cb7f-de11-a310-0003ffd0167c Does Not Exist


Request information:

    Request URL: http://crm/Contoso/_grid/cmds/dlg_delete.aspx?iObjType=2&iTotal=1&iIndex=0&iId={90B804DC-CB7F-DE11-A310-0003FFD0167C}

    Request path: /Contoso/_grid/cmds/dlg_delete.aspx

    User host address:

    User: CONTOSO\Administrator

    Is authenticated: True

    Authentication Type: Negotiate

    Thread account name: NT AUTHORITY\NETWORK SERVICE


Thread information:

    Thread ID: 10

    Thread account name: NT AUTHORITY\NETWORK SERVICE

    Is impersonating: False

    Stack trace:    at Microsoft.Crm.Application.Utility.Util.RaiseXMLError(Exception exception)

   at Microsoft.Crm.Dialogs.DeleteDialogPage.ConfigureForm()

   at Microsoft.Crm.Application.Controls.AppUIPage.OnPreRender(EventArgs e)

   at System.Web.UI.Control.PreRenderRecursiveInternal()

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

 Custom event details:



Nov 5, 2009 at 1:52 AM

Did you have any luck finding a fix for this?


Nov 6, 2009 at 2:54 PM

No we abandoned using this and just use the workflow audit.  It was a real problem for us.

Linda Dienberg

Sikich - Microsoft Gold Certified Partner

Microsoft Dynamics Inner Circle Partner

T: 630.566.8386   F: 630.236.6672

To learn more about our technology services, view our e-brochure


From: jknibb []
Sent: Wednesday, November 04, 2009 7:53 PM
To: Linda Dienberg
Subject: Re: Delete Step Errors - Audit Plug-In [crmaudit:64249]

From: jknibb

Did you have any luck finding a fix for this?


Read the full discussion online.

To add a post to this discussion, reply to this email (

To start a new discussion for this project, email

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at



This e-mail is intended only for the use of the individual or entity 
to which it is addressed and may contain information that is 
privileged, confidential and exempt from disclosure under 
applicable law. If the reader of this e-mail message is not the 
intended recipient, or the employee or agent responsible for 
delivery of the message to the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this 
communication is prohibited. If you have received this e-mail in 
error, please notify us immediately by telephone at 630.566.8400 
or the relative office number and also indicate the sender's name. 
Thank you.

Jun 15, 2010 at 12:09 PM
Edited Jun 15, 2010 at 12:09 PM

I changed the Delete step the following way:

With contact entity (as an example):

- In the Delete step change "Eventing Pipeline Stage of Execution" to "Post stage"
- In the Delete step change "Execution Mode" to "Asynchronous"
- In the Image set "Image Type" to "Pre Image" (I had to delete and recreate the image for this, update doesn't work)
- In the Image set Parameter to mandatory field "lastname" (for a contact entity)

Hope this helps.

Jun 16, 2010 at 12:43 PM

Daniel001 is right, the Delete step is wrongly documented, remove Post Image (since it will not exist as error message implies) and you will be fine.

Jun 29, 2010 at 9:53 AM

Is there any reason for wich i need the Delete step for audit? How can i acces this audit entry if the entity for which the audit is created do not exists anymore. (i am excluding the fact that i can display the list of all audit entries in the settings screen for example).

Does anyone knows if the delete step will remove all the audit entries for an entity (to avoid unnecessary used space on db)?



Dec 27, 2010 at 10:57 PM

@ birsan.  You don't need to audit deletes, it's up to you.  For us we track that because it's useful in case somebody accidentally deleted a record (or maliciously deleted a record).  You can't view it from the deleted record (obviously, it's gone) but you can view it in the full list of audit records.  By default this isn't visible anywhere but you can add it to your settings area or whever by modifying the entity in settings.  The delete step does not remove all audit entries for that record, quite the opposite.  It adds an entry for the delete action.  If you wanted to do this you would need to cascade delete all related entities for the relationship between your audited entity and the audit entity.