Current filter:
                                You should refresh the page.
                                  • Hello Dear Devexpress Support,

                                    following Situation

                                    in each DxP-Version 18.2 - 19.1.5.

                                    If a customer opens a Report and presses

                                    "Send as Mail", after exporting the XtraReport the Devexpress Modules crash with an unhandled Exception.

                                    So i have problems in sending you a Stacktrace or anything else, or code has handled Exceptions around that.

                                    The WindowsEventLog prints that

                                    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
                                    - <System>
                                      <Provider Name=".NET Runtime" />

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

                                      <Level>2</Level>

                                      <Task>0</Task>

                                      <Keywords>0x80000000000000</Keywords>

                                      <TimeCreated SystemTime="2019-08-19T11:35:17.000000000Z" />

                                      <EventRecordID>302009</EventRecordID>

                                      <Channel>Application</Channel>

                                      <Computer>SQL.lingenberg.local</Computer>

                                      <Security />

                                      </System>

                                    - <EventData>
                                      <Data>Anwendung: IwmClient.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 12CA9C40</Data>

                                      </EventData>

                                      </Event>

                                    ,

                                    - <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="2019-08-19T11:35:17.000000000Z" />

                                      <EventRecordID>302010</EventRecordID>

                                      <Channel>Application</Channel>

                                      <Computer>SQL.lingenberg.local</Computer>

                                      <Security />

                                      </System>

                                    - <EventData>
                                      <Data>IwmClient.exe</Data>

                                      <Data>19.1.28.1</Data>

                                      <Data>5c50621d</Data>

                                      <Data>mso.dll</Data>

                                      <Data>15.0.5153.1000</Data>

                                      <Data>5cff9df6</Data>

                                      <Data>c0000005</Data>

                                      <Data>00829c40</Data>

                                      <Data>2474</Data>

                                      <Data>01d556820f92fd82</Data>

                                      <Data>C:\Program Files (x86)\iwm Informationstechnik GmbH\IwmClient\IwmClient.exe</Data>

                                      <Data>C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll</Data>

                                      <Data>6a9f5d16-c275-11e9-82c2-00155d217206</Data>

                                      <Data />

                                      <Data />

                                      </EventData>

                                      </Event>

                                    The Content of that message and of that screenshot are privat informations.

                                Show all comments
                                • Michi^ 08.19.2019

                                  I could not add anymore additional information before the Form here prevented to type in more.

                                  Our Technical Support just reinstalled Microsoft Office, dunnow if it leads to that bug.

                                  The lower event is from out Application (which not accesses the Office interop Stuff) and u see there that the failure happens in working together with the mso.dll of office, if you press send as Mail in the XtraReport .

                                • Yaroslav (DevExpress Support) 08.19.2019

                                  Hi Michi,
                                  Our XtraReports Suite uses a special subset of Windows API called Messaging Application Programming Interface (MAPI) to launch a default e-mail client registered on the current machine. As I understand, in your case the default e-mail software is MS Outlook, but there are other MAPI-compatible programs such as "Thunderbird" or "The Bat". To verify whether the behavior you observe is specific to a particular workstation/operating system, I've attached a sample project that implements the same MAPI interface without our components. Please try running it on the affected PC and let us know the results you get, both with MS Outlook and other MAPI-compatible e-mail clients.
                                  I look forward to your results.

                                  Regards,
                                  Yaroslav

                                • Michi^ 08.20.2019

                                  Hi Yaroslav,

                                  do you mean the examples on the Microsoft Website?
                                  Because i see no attachment in your message.

                                  I will try it with one of these

                                • Yaroslav (DevExpress Support) 08.20.2019

                                  Oops, it look like I forgot to attach the project in question. My apologies. Here it is.
                                  Try it and let us know your results.

                                  Regards,
                                  Yaroslav

                                • Michi^ 08.20.2019

                                  Hi Yaroslav,

                                  i converted the Testproject to the actual Devexpress-Version where the failure happens aswell and it works fine.
                                  On my machine and the customer machine.

                                  I should add as Information that is only crashes if you press send via mail.
                                  Than you save the .pdf and if Outlook should opens it crashes.

                                  Saving the file and sending manual for example works without the mentioned Problem but it not respects changes of the Standard Email-App.
                                  I tested it with Outlook and Microsoft Mail (Windows 10 Mail Client), even after rebooting and changing the standard app it still opens Outlook.

                                  I want to give you all Information i have about this Problem:

                                  In past if that problem occur it helped to create a new .ost-Profile, i researched old devexpress support topics and microsoft support topics in past that lead me in past to this workaround.

                                  In the new Version of Office and in combination with a exchange Account (maybe that Information helps) it works not anymore.
                                  Could be a Windows Update too i actually dunnow.

                                • Yaroslav (DevExpress Support) 08.20.2019

                                  >>i converted the Testproject to the actual Devexpress-Version where the failure happens aswell and it works fine.
                                  The project I shared represents the managed MAPI wrapper that we use internally. Basically, I copied and pasted the required code, so the project itself does not make use of any DevExpress assemblies.

                                  >>I should add as Information that is only crashes if you press send via mail. Than you save the .pdf and if Outlook should opens it crashes.
                                  I understand the situation but I find it confusing as the sample project I shared above works for you (again, it's the same code in both cases). Try changing the platform target from x86 to x64. Does the issue persist?

                                  >>tested it with Outlook and Microsoft Mail (Windows 10 Mail Client), even after rebooting and changing the standard app it still opens Outlook.
                                   The Windows 10 default Mail app does not support MAPI at all. To check whether this issue is Outlook-specific, I suggest that you try "Thunderbird" or "The Bat".

                                  >>In past if that problem occur it helped to create a new .ost-Profile, i researched old devexpress support topics and microsoft support topics in past that lead me in past to this workaround.
                                  I'm not aware of such a problem. Can you share any relevant link describing the issue and its workaround?

                                  >>Could be a Windows Update too i actually dunnow.
                                  Since we're talking about the native Windows API, everything is possible. What particular Windows 10 build are you running?

                                  Regards,
                                  Yaroslav

                                • Michi^ 08.21.2019

                                  >>i converted the Testproject to the actual Devexpress-Version where the failure happens aswell and it works fine.
                                  The project I shared represents the managed MAPI wrapper that we use internally. Basically, I copied and pasted the required code, so the project itself does not make use of any DevExpress assemblies.

                                  -well I am used to this problem at well I see It like this way if something works 99% of all time and in 1% of all cases not that these cases are the most important ones to make a Software most stable as possible

                                  >>I should add as Information that is only crashes if you press send via mail. Than you save the .pdf and if Outlook should opens it crashes.
                                  I understand the situation but I find it confusing as the sample project I shared above works for you (again, it's the same code in both cases). Try changing the platform target from x86 to x64. Does the issue persist?

                                  -Somehow the example Program works with 64Bit and 32Bit as platform target, but the Office Version is always 32Bit (I can’t use 64Bit Office due to incompatibility of Partner Products)

                                  >>tested it with Outlook and Microsoft Mail (Windows 10 Mail Client), even after rebooting and changing the standard app it still opens Outlook.
                                   The Windows 10 default Mail app does not support MAPI at all. To check whether this issue is Outlook-specific, I suggest that you try "Thunderbird" or "The Bat".

                                  -I will definitive try that!

                                  >>In past if that problem occur it helped to create a new .ost-Profile, i researched old devexpress support topics and microsoft support topics in past that lead me in past to this workaround.
                                  I'm not aware of such a problem. Can you share any relevant link describing the issue and its workaround?

                                  -Yes sadly I not bookmarked the Devexpress Support Ticket link I found before which leaded me to the Microsoft sites about the .ost-Profile problem

                                  But there are really many topics about that in different Microsoft Sites, with different Workarounds
                                  I will name in short form some possible Workarounds
                                  -Splitting .ost-Profile because it’s to big
                                  -Converting the .ost-Profile to a different format
                                  -Fixing registry entries that lead to the Office mso.dll
                                  -checking the return value of importing the mso.dll
                                  -Creating a new .ost-Profile and delete the old one (the one which only worked for us in past)
                                  -Calendar Entrys synced with Apple
                                  -Corrupt mso.dll -> rename and then repair Office

                                  Here to provide you links about partly close

                                  https://support.office.com/de-de/article/microsoft-outlook-startet-nicht-oder-der-fehler-„kann-microsoft-office-outlook-nicht-starten-das-outlook-fenster-kann-nicht-geöffnet-werden-erscheint-d1f69da6-b333-4650-97bf-4d77bd7abb85

                                  https://answers.microsoft.com/en-us/msoffice/forum/all/msodll-crash-on-start-of-outlook/b5856418-423c-4cbb-9c92-4ef7060f379a

                                  https://social.technet.microsoft.com/Forums/office/de-DE/fa776b9a-8e72-4470-8fe6-0434401c98d7/outlook-2013-appcrash-msodll?forum=outlook

                                  -this one I will try next and check the registry

                                  https://support.office.com/en-us/article/repair-outlook-data-files-pst-and-ost-25663bc3-11ec-4412-86c4-60458afc5253

                                  https://www.stellarinfo.com/blog/error-solved-the-file-username-ost-is-in-use-and-cannot-be-accessed/

                                  https://docs.microsoft.com/pl-pl/office/client-developer/outlook/mapi/how-to-use-the-mapi-crash-recovery-api

                                  -          This one has maybe some good Information for you

                                  https://docs.microsoft.com/en-us/exchange/troubleshoot/outlook-crashes/crash-issues

                                  https://social.msdn.microsoft.com/Forums/office/en-US/a2e731ff-0e68-4d6d-b117-67816c2704f3/crash-initializing-the-mapi-mapi-extended-or-simple-using-the-access-database-engine-2016?forum=outlookdev

                                  -          This maybe aswell

                                  https://social.technet.microsoft.com/Forums/ie/en-US/2ace3748-8f81-462a-b249-661d761d88a5/ost-files-causes-outlook-to-crash?forum=officeitproprevious

                                  https://community.spiceworks.com/canonical_answer_pages/134613-microsoft-outlook-has-stopped-working-outlook-2016

                                  >>Could be a Windows Update too i actually dunnow.
                                  Since we're talking about the native Windows API, everything is possible. What particular Windows 10 build are you running?

                                  -I use Windows 1809 and the newest Version of Office 365 (32-Bit), the customer uses a TerminalServer Session of Windows Server 2012 and the newest Version of Office 365(32-Bit), before they used Office 2013 and there it was still able to workaround the bug by recreating a new .ost-Profile each 1-2 Monthes it was already a routine. Sadly, I can’t provide the information yet which Office Version they used 1 year ago were the Problem seems to be not existing

                                • Michi^ 08.21.2019

                                  I guess if found a solution for the mso.dll but I will provide the Information after I tested it in all ways.

                                • Michi^ 08.21.2019

                                  First i found a new Bug.

                                  I have Outlook as Standard App, and thunderbird installed aswell on my developer Machine.

                                  Now it opens only thunderbird even if it's not the standard application for E-Mails (i even restarted the machine)

                                • Michi^ 08.21.2019

                                  Found no Solution for the Problem but with Thunderbird it would work excellent.

                                  With Office365 not it just crashes.

                                • Michi^ 08.21.2019

                                  I can add as Information that -> Like we see above in the snippet of the event log

                                  it crashes because it uses the MSO.DLL of Office Version 15 which is Office 2013.

                                  But... Office 365 (and Office 2016-2019) use the Folder of Office 16 -> and the mso.dll contained in it

                                  So it should not be Version 15!

                                  But it not changes even if I delete all paths of Version 15, I wonder where Mapi get the Path for the mso!
                                  Can it be defined or especially called like in the Microsoft Thread about the mso.dll Mapi bug between Access and sending Mails?

                                  May this would answer why the small Test Program works and the one contained in ours not. May its saved in Appdata File or Registry but I dunnow, have no experience with Mapi .

                                  Will add new Informations if I find them

                                • Michi^ 08.21.2019

                                  I found now out that even if i replace all registry entries about the different .mso-Files that the one our program uses with Devexpress still uses the .mso-File from Office 2013 (OFFICE15)

                                  Do you have a explaination for that.

                                  That now where my magic ends i don't have any Idea why and where it could be cached.

                                  I sended here before a link where people used MAPI had the problem that the wrong mso.dll was used, i see not in your example that it is used at all. In fact i don't even know what it does

                                  But as you see in the Eventlog it uses the wrong version, may you have a idea what i can do that the right mso.dll gets used between DevExpress and Office.

                                  https://social.msdn.microsoft.com/Forums/office/de-DE/a2e731ff-0e68-4d6d-b117-67816c2704f3/crash-initializing-the-mapi-mapi-extended-or-simple-using-the-access-database-engine-2016?forum=outlookdev

                                  May still not will solve the .ost-Profile bug but would possibly make it start office again.

                                1 Solution

                                Creation Date Importance Sort by

                                I found the answer to the question.

                                Our Software uses other modules of a Partner of us (Sage).

                                Sage uses (in Germany) Access 2013 Office15 and our Software works with Sage.

                                This MAPI seems to use the already used mso.dll if ones its open.

                                Sage works in Background with it and opens a OLEDB Connection over the access modules.

                                If you press in the Report -> Send as Email -> it uses the already open mso.dll -> From Sage -> Office15
                                And tried to control with it an Office16 (Office 365 / Office 2016 / Office 2019)

                                If i replace the Office15 dll with the Office16 dll (which we not use in our Software but we host Sage components)

                                The Software breaks together if tried to control over Mapi Office Components never than OFFICE15 (Office 2013) .

                                • Yaroslav (DevExpress Support) 08.21.2019

                                  Hi Michi,
                                  So, if I understand everything correctly, the reason for this issue, and the reason why my sample works while your project does not, is the "mso.dll" that is loaded by the application (because of the OLEDB data provider for MS Access). When any MAPI method is called, this loaded native DLL is used (not the one that from the "Program Files" directory). The solution here is to manually load the Office 2016 version of "mso.dll". Can you confirm that?

                                  Regards,
                                  Yaroslav

                                  P.S. Would you mind making this thread public? The information provided here can be of great help for other DevExpress customers who may run into a similar issue.

                                • Michi^ 08.21.2019

                                  Hi Yaroslav,

                                  exactly!
                                  It's not done by our software but by third party components of the Software we support.
                                  They use in Background still the Access Engine.

                                  We just call a session to the partner Software over they're components.

                                  The mso.dll of this OFFICE15 is already in use than.

                                  If we try to send a mail over the Devexpress Ribbon Report Preview it tries to open a OFFICE16(No matter if Office 365, Office 2016, Office 2019).

                                  It caused before other bugs like destroyed .ost-Profiles and now it not works anymore.

                                  Thanks for your help Yaroslav and ofc you can make this Thread public.

                                • Yaroslav (DevExpress Support) 08.22.2019

                                  You're welcome! I'm really happy to hear that you managed to get this issue resolved and that things are working for you.
                                  This ticket is public now.

                                  Regards,
                                  Yaroslav