Outlook 2019 crash with Axigen 10.2.2.95 connector

Support Tools
1

Hello Axigen-Team.

Since installing Axigen Connector (v10.2.2.95) and adding a mailbox on my Axigen server (Axigen 10.3.3.18 on Docker) to my Outlook2019 ProPlus 32bit profile, Outlook is crashing.
When I remove the Axigen mailbox from the Outlook profile, Outlook is working fine. But I want to migrate my data to the Axigen mailbox, so I need multiple accounts in one Outlook profile.

Can I upload the crash dump files to get them analyzed and fixed?

/Timo.

Log Name: Application
Source: Windows Error Reporting
Date: 2021-06-27 19:51:38
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: …
Description:
Fault bucket 1896035505507968987, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: OUTLOOK.EXE
P2: 16.0.14026.20308
P3: 60cadf31
P4: StackHash_f10d
P5: 10.0.19041.1023
P6: f739c3a5
P7: c0000374
P8: PCH_ED_FROM_ntdll+0x00072F8C
P9:
P10:

Attached files:
\?\C:\Users…\AppData\Local\Temp{D03907FF-EA89-4A3A-A5B8-EA2CBD211DC4} - OProcSessId.dat
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6081.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6BDC.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C0C.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C1A.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C59.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OUTLOOK.EXE_cd26e333f8a859edb1c24af53a5468a3ecdbf_8c9e902e_4e42a601-7306-42b6-b898-4e4b6ea4ee91

Analysis symbol:
Rechecking for solution: 0
Report Id: f5047c7b-0301-4156-920a-bce68272cb15
Report Status: 268435456
Hashed bucket: 07764b05f0d65eb37a50123f2354a7db
Cab Guid: 0

Log Name: Application
Source: Application Error
Date: 2021-06-27 19:51:32
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: …
Description:
Faulting application name: OUTLOOK.EXE, version: 16.0.14026.20308, time stamp: 0x60cadf31
Faulting module name: ntdll.dll, version: 10.0.19041.1023, time stamp: 0xf739c3a5
Exception code: 0xc0000374
Fault offset: 0x000e6bb3
Faulting process id: 0x2bdc
Faulting application start time: 0x01d76b7d040c279e
Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: f5047c7b-0301-4156-920a-bce68272cb15
Faulting package full name:
Faulting package-relative application ID:

2

Hi,
do you have a Virusscanner active? If yes, please deactivate and try again.

Apart from that: When exactly does the crash happen? Does AxiOLK start synching?

JK

3

Hello Jeroen.

Only default Windows Defender is active. I did not get any potential malware alert. Disabling AntiVirus is not an option.

Crash happens some seconds after starting Outlook. I do not get any activity info or error message.

/Timo.

4

Hi Timo,

sorry for the late reply, I missed your reply somehow.

So far, I have had two issues, which caused this behaviour.
First was the “infected” message I mentioned, where my AV software removed the temporary downloaded file, before Outlook could process it.
Second: Malformed appointments / calendar entries. Certain meeting requests or recurring appointments sent to my by external partners were seen as “malformed” by Outlook.
Fun fact: This only happened, when I mainly used Caldav on several different Linux Clients. The moment I tried to use Outlook in parallel, these appointments would crash Outlook, as soon as I would close the reminder of that appointment.
As soon as I modified the appointment in Axigen WebClient and removed the reminder, Outlook wouldn’t crash anymore.
(Response to this by Axigen was rather … unsatisfactory. It still isn’t possible to work with Caldav.)

Regards
JK