Application crash when Exporting Report as PDF on Windows 10 64 Bit

[Former Member]

Good afternoon from Italy!

My application is developed in VB6 with Cr XI R2 (11.5.12.1838) and continues to work although the components are not more supported.

In the last installation on a Windows 10 / 64 Bit machine my application crashes, when exporting the report as PDF FIle to disk:

the first export works fine

when I exit the Preview and reenter, the second export cause my application to crash (!?)

Here the Text from the Event Viewer (as you ca see it is an italian Windows)

Nome registro: Application

Origine:       Application Error

Data:          21/10/2015 16:47:38

ID evento:     1000

Categoria attività:(100)

Livello:       Errore

Parole chiave: Classico

Utente:        N/D

Computer:      PC01

Descrizione:

Nome dell'applicazione che ha generato l'errore: Merkur.exe, versione: 4.17.0.589, timestamp: 0x51c1b81e

Nome del modulo che ha generato l'errore: MSMAPI32.DLL, versione: 16.0.4229.1029, timestamp: 0x560678bb

Codice eccezione: 0xc0000409

Offset errore 0x000017e8

ID processo che ha generato l'errore: 0x1b00

Ora di avvio dell'applicazione che ha generato l'errore: 0x01d10c0f59c946f5

Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\Merkur\Merkur.exe

Percorso del modulo che ha generato l'errore: C:\Program Files (x86)\Common Files\SYSTEM\MSMAPI\1040\MSMAPI32.DLL

ID segnalazione: db408b55-08ea-467e-8281-313dd5efb9b7

Nome completo pacchetto che ha generato l'errore:

ID applicazione relativo al pacchetto che ha generato l'errore:

XML evento:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-10-21T14:47:38.000000000Z" />

    <EventRecordID>3624</EventRecordID>

    <Channel>Application</Channel>

    <Computer>PC01</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Merkur.exe</Data>

    <Data>4.17.0.589</Data>

    <Data>51c1b81e</Data>

    <Data>MSMAPI32.DLL</Data>

    <Data>16.0.4229.1029</Data>

    <Data>560678bb</Data>

    <Data>c0000409</Data>

    <Data>000017e8</Data>

    <Data>1b00</Data>

    <Data>01d10c0f59c946f5</Data>

    <Data>C:\Program Files (x86)\Merkur\Merkur.exe</Data>

    <Data>C:\Program Files (x86)\Common Files\SYSTEM\MSMAPI\1040\MSMAPI32.DLL</Data>

    <Data>db408b55-08ea-467e-8281-313dd5efb9b7</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Ok, the strange thing is the line

Percorso del modulo che ha generato l'errore: C:\Program Files (x86)\Common Files\SYSTEM\MSMAPI\1040\MSMAPI32.DLL

Why need the export function MAPI, when I only will export to PDF?

Thank you for any suggestion!

Jens

[DellSC · Accepted solution]

Unfortunately, the version of the SDK that you're using went out of support several years ago.  It was never tested on Windows 10, nor will it be updated to work on Windows 10.  Your only option is going to be to upgrade the application to .NET using Visual Studio 2010 or newer and the Crystal for Visual Studio SDK that can be found here:  .

-Dell

[Former Member · Accepted solution]

You are right - I know CrXI R2 is 'old' and also VB6 and in fact I'm moving to .Net; but this will take while...

Thank you.

Jens

[Former Member · Accepted solution]

We have recently faced this issue and have ACTUALLY FOUND A SOLUTION...

Rename the file "C:\Program Files (x86)\Business Objects\Common\3.5\bin\u2dpost.dll" to something else and create a blank text document with the same name in the folder (this avoids our software replacing the missing file)

By removing this file it removes the option to export to "Exchange Folder" (using MAPI to email). We don't use this as a company and by removing (renaming the problem file) it has completely resolved the issue with crashing.

Sean

[Former Member]

This message was moderated.

[former_member292966]

Hi Jens,

The Print Engine will try to load all the drivers you include in your project.  If the install is crashing on MSMAPI32.DLL, remove P2SMAPI.DLL and U2DMAPI.DLL from your install build.  These are what Crystal uses to export to a MAPI client and use Exchange as a datasource.  If you don't need it then remove it and you should get past this error. 

I am in no way suggesting though you continue to use your application on a 64 Bit Windows 10 machine.  As Dell said, that version of Crystal is long since out of support and if it doesn't work there is very little that can be done to help.  You should consider upgrading both Visual Studio and Crystal. 

Good luck,

Brian

[Former Member]

Thank you for the hint too - I'm working on it and will give response soon.

Jens

[Former Member]

Great Workaraound - it solved the problem!

Thank you very much

Jens

[ricardo_pereira6]

Hi Jens.

Try to uninstall the actual MSMAPI32.DLL file, download the new dll file for Windows 10 and register the new file in Windows.

*Before unregister the dll, download the new dll file for windows 10.

Follow the steps:

1- Open the execute in windows (Window + R command)

2- Execute the command "regsvr32 -u C:\Program Files (x86)\Common Files\SYSTEM\MSMAPI\1040\MSMAPI32.DLL"

3- Download the MSMAPI32.DLL for Windows 10 (link for example: http://fix4dll.com/mapi32_dll)

4- Register the new dll in Windows using the command "regsvr32 <file location>\MSMAPI32.DLL"

I hope it works.

Best regards

Ricardo Pereira

[former_member11696]

Moved to Legacy SDK forum

[Former Member]

Thank you for the hint - I'm working on it and will give response soon.

Jens

[Former Member]

Good morning!

First two supplemental informations:

- on the machine is installed Office 2016; the MSMAPI32.DLL is saved in another location: C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX86\SYSTEM\MAPI\1040

- the crash happens only on the second export: so I view the Report in the CRViewer, click the Export Button, walk through the Select and Export options and save the PDF File sucessfully; after I closed the CRViewer and then reopen it for viewing, so the crash happens after the Select Export Dialog.

But I found a 'Workaround' for the problem: when I change the default Mail Program to something else than Microsoft Office (e.g. Windows Mail), the crash not happens.

What kind of relation...

Thank's for any suggestion.

[former_member11696]

HI Jens,

New question, please repost in a new post...

Thanks

[Former Member]

But it refers to the problem described in this post - the crash happens when exporting to PDF and the MAPI seems to be the origin of all...

[former_member11696]

Yes but they are using the Legacy SDK, you are using .NET SDK.

Post in the .NET forum.

Thanks

[Former Member]

Hi Don,

My application is developed in VB6 with Cr XI R2 (11.5.12.1838) and not in .Net; I'm working to upgrading to .Net, but the problem happens with the legacy SDK.

[former_member11696]

Microsoft stopped siupporting the simple MAPI api set and introduced an Extended MAPI API set.

CR XI R2 did not get patched for that change so no way to fix it.

Only option now is to upgrade to VS 2010 or above and CR for .NET to be able to use exporting to MAPI.

You can try using the old MAPI dll's from MS in the recent Office builds but no idea if that would work or not. Nothing we can support...

Don

[Former Member]

Ok, Thank you.