Faulting module name: olmapi32.dll

Question

Client has an ERP app written (by me) in MS Access that has been running their business for some 15 years … until mid-morning Friday when it suddenly began to crash every time a quotation was e’Mailed.

Faulting application name: MSACCESS.EXE, version: 16.0.9330.2087, time stamp: 0x5b049173

Faulting module name: olmapi32.dll, version: 16.0.9330.2087, time stamp: 0x5b04968a

Exception code: 0xc0000005

Fault offset: 0x0005015f

Faulting process ID: 0x252c

Faulting application start time: 0x01d3fbf5db117c6f

Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\MSACCESS.EXE

Faulting module path: C:\Program Files (x86)\Microsoft Office\Root\Office16\olmapi32.dll

Report ID: ef0f97aa-b408-42c7-92bb-22bfa56ad6e6

Faulting package full name:

Faulting package-relative application ID

Nothing I can see has changed on the system, and despite endlessly searching the web I’ve found no solution.

Anyone have any insight into this and why it might have suddenly started up ?

Win10 pro - fully patched

Office 365 -  Fully patched and repaired

Outlook - MAPI e'Mail via hosted Exchange provider.

H.

Answer 1

Private Sub cmd_Email_Click()

Dim strObjName As String

Dim strCriteria As String

On Error GoTo Err_Handler

    'save it

    If Me.Dirty = True Then Me.Dirty = False

    strObjName = "rpt_Current_Quote_Email"

    strCriteria = "objID = " & Me.txt_QuoteNo

    'Send the Quote as PDF Attachment to e'mail

    'DoCmd.OpenReport strObjName, acViewPreview, , strCriteria

    DoCmd.SendObject acSendReport, strObjName, acFormatPDF, , , , _

                    "Your Quotation: " & Me.txt_JobTitle, vbCrLf & _

                    "Dear " & Me.txt_Contact & "," & vbCrLf & _

                    "Please find attached our Quotation " _

                    & vbCrLf & "No: " & Me.txt_QuoteNo _

                    & vbCrLf & vbCrLf & _

                    "For: " & Me.txt_JobTitle _

                    & vbCrLf & vbCrLf, -1

Clean_Exit:

    Exit Sub

Err_Handler:

    Beep

    Select Case Err.Number

        Case 2501 'user cancelled

        Case Else

        MsgBox Err.Number & " : " & Err.Description, vbCritical, "Form_frm_Quotes.cmd_Email_Click" & ":"

    End Select

    Err.Clear

    Resume Clean_Exit

End Sub

As i said, It's very old code.

Still works though - Solved the crashing by creating a new Outlook profile for the user. - Go Figure.

Answer 2

You say it crashes when they try to e-mail? Can you post what code it is crashing on? We are in the process of migrating from 2010 to 2016. We have found problems with e-mailing. DoCmd.SendObject doesn't work, it crashes the system. Office Automation has also been problematic especially for certain client levels. Unless Outlook is installed as a desktop app, Office Automation doesn't work.

We have had to use SMTP to send e-mails and that comes with its own problems.

Answer 3

Based on what you describe, my first test would be reverting my installation to a prior build number to see if the issue is caused by a bug in the current build.  See http://www.devhut.net/2017/10/04/microsoft-office-uninstall-an-update/

Answer 4

It could have been an update either to Windows 10 or Office for your client that caused it. Perhaps try seeing what was updated and roll it back.

Thought had occurred to me and I checked into that. Nothing in it.

H.

Answer 5

It could have been an update either to Windows 10 or Office for your client that caused it. Perhaps try seeing what was updated and roll it back.