Posts 1 - 10 of 14
First | Prev. | 1 2 | Next | Last
|
|
macroview
Posts: 33
Joined: 2009-05-25
|
Our application uses Add-in Express to add a form to the Outlook Explorer, docked right. When running on Arm64 devices using 64-bit Outlook this causes Outlook to crash on startup.
I have reproduced this issue in a simple test project available here:
https://macroview365-my.sharepoint.com/:u:/g/personal/josh_macroview_com_au/Ec4y2kV_X95DlxCT_RLQkkwBA2qts1YVnhDmmFvWD1ahig?e=yaWNld
This test add-in loads fine on x86 architectures and displays an empty task pane as expected. Loading it on Arm64 using 64-bit Outlook results in Outlook crashing.
Crash dump analysis indicates this is caused by an access violation in USER32.dll, originating from IntResource64.dll.
Faulting application name: OUTLOOK.EXE, version: 16.0.17928.20114, time stamp: 0x66cb8fda
Faulting module name: USER32.dll, version: 10.0.26100.1542, time stamp: 0x56b60c4e
Exception code: 0xc0000005
Fault offset: 0x000000000009b40c
Faulting process id: 0x4868
Faulting application start time: 0x1DB0009635F0462
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
Faulting module path: C:\WINDOWS\System32\USER32.dll
Report Id: 90f9de58-92b7-4c72-b882-75cf552bfa21
ExceptionAddress: 00007ff97987b40c (USER32!UserCallWinProcCheckWow+0x0000000000000144)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000010
Attempt to write to address 0000000000000010
FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_USER32.dll!UserCallWinProcCheckWow
OS Thread Id: 0x26cc (0)
Current frame: USER32!UserCallWinProcCheckWow+0x144
Child-SP RetAddr Caller, Callee
000000cd93d5f0d0 0000000000e17382 IntResource64!AdvancedCommand+0x3842
000000cd93d5f1f0 0000000000e1597e IntResource64!AdvancedCommand+0x1e3e, calling IntResource64!AdvancedCommand+0x3650
000000cd93d5f2a0 0000000000e1686e IntResource64!AdvancedCommand+0x2d2e, calling IntResource64!AdvancedCommand+0x1ca0
000000cd93d5f310 0000000000e18b1b IntResource64!AdvancedCommand+0x4fdb
The edition and the version of your product:
Add-in Express for Office and .NET, Premium
Release 10.2.4714
Operating system, localization and bitness:
Windows 11 24H2, US English, 64-bit Arm64
Host application version, localization, bitness and service packs that you have installed:
Microsoft Outlook for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 64-bit, US English
Development tool, version and build number
Visual Studio 2022 Version 17.11.2 64-bit
Thanks for your assistance,
Josh |
|
Posted 06 Sep, 2024 03:31:34
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Josh,
We suppose an antivirus is blocking IntResource6 which is normally unpacked to the Temp folder and then loaded from there.
Copy IntResource.dll and IntResource64.dll from {Add-in Express installation folder}\Redistributables to the folder where your add-in is registered. On the development machine that would be the output folder of your add-in project; on the target PC that would be the installation folder of your add-in.
Does the issue persist?
Regards from Poland (GMT+2),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 06 Sep, 2024 13:02:47
|
|
Top
|
|
macroview
Posts: 33
Joined: 2009-05-25
|
Hi Andrei
Yes we have already copied both IntResource and IntResource64 to the add-in directory. We’ve also confirmed there is no antivirus software running. We have multiple customers reporting this issue.
Are you able to reproduce the crash using the attached repro project on one of your ARM devices?
Thanks |
|
Posted 07 Sep, 2024 04:25:08
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Josh,
We don't have an ARM64 device at hand. I will be able to check whether we have such a device at all not earlier than in two weeks.
The call stack above mentions IntResource64!AdvancedCommand quite a lot of times. Although we do have such an entry point, and although it does have some implementation, this entry point isn't used in our code: no calls to this method exist.
Do you get that stack trace with your simple test add-in project?
Regards from Poland (GMT+2),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 09 Sep, 2024 13:39:29
|
|
Top
|
|
macroview
Posts: 33
Joined: 2009-05-25
|
Hi Andrei
Yes, that stack trace was taken from the simple test add-in project when it crashed Outlook.
Our advice to customers when this was previously reported was to use 32-bit Office on Arm64 because 32-bit Outlook on Arm64 does not crash using the same code.
Unfortunately it does not appear to be possible to install 32-bit Office on Arm64 devices anymore, so this workaround is no longer possible.
If you don't have access to an Arm64 device you can instead create a Windows 11 Arm64 virtual machine in Microsoft Azure: https://learn.microsoft.com/en-us/windows/arm/create-arm-vm
Perhaps this is the better option for you?
Thanks
Josh |
|
Posted 10 Sep, 2024 01:33:37
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Josh,
Thank you.
Solving organizational issues. We seem to have found an ARM device. There's a suspicion though, this isn't an ARM64 device, though. I hope that we'll run your test add-in on that device tomorrow.
Regards from Poland (GMT+2),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 10 Sep, 2024 17:38:35
|
|
Top
|
|
macroview
Posts: 33
Joined: 2009-05-25
|
Hi Andrei
Were you able to run the test add-in?
Thanks,
Josh |
|
Posted 12 Sep, 2024 07:21:35
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Josh,
Yes, we were able to test it to reproduce the crash. Now we prepare to debug the issue. That may take some time.
Regards from Poland (GMT+2),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 12 Sep, 2024 16:52:54
|
|
Top
|
|
macroview
Posts: 33
Joined: 2009-05-25
|
Hi Andrei
Do you have any update on this issue?
Thanks,
Josh |
|
Posted 30 Sep, 2024 00:47:25
|
|
Top
|
|
Dmitry Kostochko
Add-in Express team
Posts: 2887
Joined: 2004-04-05
|
Hello Josh,
We don't have any news so far, sorry. Hopefully, things will become clearer later this week. |
|
Posted 30 Sep, 2024 12:30:32
|
|
Top
|
|
Posts 1 - 10 of 14
First | Prev. | 1 2 | Next | Last
|