Sending Excel and Word documents as attachments causes the application to crash if the CRMaddin is enabled in Office 2003 SP3

If from within Excel/Word you do the following:

File | Send to | Email (as attachment)

This causes excel/word to crash and the following is logged in the event viewer

Event Type: Error

Event Source: Microsoft Office 11

Event Category: None

Event ID: 1000

Date:  16/03/2010

Time:  15:44:52

User:  N/A

Computer: <MachineName>


Faulting application excel.exe, version 11.0.8233.0, stamp 48a9d694, faulting module crmabp32.dll, version 4.0.7333.2644, stamp 4b67d0bc, debug? 0, fault address 0x0002a732.

This was a known issue with Office 2003. Microsoft has released an update for Microsoft Office Excel 2003 and for Microsoft Office Word 2003. This update corrects a potential problem in which an add-in, a smart tag, or a smart document may not load if the add-in, smart tag, or smart document uses the Microsoft .NET Framework 2.0.

Note This fix is not included in Office 2003 Service Pack 2 or in Office 2003 Service Pack 3.

More details on the fix can be found in the following KB article:

907417  Description of the update for Office 2003: November 8, 2005;EN-US;907417

Please download the fix from the following location:



EMEA Dynamics CRM Team

Comments (2)

  1. Hi, i am experiencing the same issue with Office 2010 says:


    same thing, i have Dynamics Crm 4.0 Outlook client installed and it makes Excel 2010 crash

    when using Send as attachment Within Excel 2010

    is there a fix for 2010 as well?

  2. Event log data says:

    here is the Event log data:

    Faulting application name: EXCEL.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e607

    Faulting module name: unknown, version:, time stamp: 0x00000000

    Exception code: 0xc0000005

    Fault offset: 0x087b22c8

    Faulting process id: 0x1f68

    Faulting application start time: 0x01cc5db7c512ea17

    Faulting application path: C:Program FilesMicrosoft OfficeOffice14EXCEL.EXE

    Faulting module path: unknown

    Report Id: 2f2f208f-c9ab-11e0-85fc-70f3954f9b96

    Event ID: 1000

Skip to main content