Exception when starting debugging from VS2019

Add-in Express™ Support Service
That's what is more important than anything else

Exception when starting debugging from VS2019
 
ewessely




Posts: 55
Joined: 2019-01-31
Hi,
after successfully used ADX for some years, I get now an exception when I try to debug my project when excel ist starting.

Managed Debugging Assistant 'PInvokeStackImbalance' : 'A call to PInvoke function 'AddinExpress.MSO.2005!AddinExpress.MSO.GetTempMemoryDelegate::Invoke' has unbalanced the stack. This is likely because the managed PInvoke signature does not match the unmanaged target signature. Check that the calling convention and parameters of the PInvoke signature match the target unmanaged signature.'


I'm not sure what causes the problem. I updated (patched) VS2019 and also updated to the latest ADX version.

Unregistering / registering my project works without any problem. My AddIn also works fine when I only start excel (not from VS).

Also reinstalling ADX (with clearing the GAC) did not solve the issue.
The issue also appears in a brand new project.

In VS I could disable this exception but is it wise and safe to do so? Is there any other solution to fix that?

Best regards
Erich
ew
Posted 09 Jan, 2022 09:28:45 Top
Andrei Smolin


Add-in Express team


Posts: 18183
Joined: 2006-05-11
Hello Erich,

We can't reproduce the issue. Do you maybe have a test XLL project reproducing it?

Regards from Poland (CET),

Andrei Smolin
Add-in Express Team Leader
Posted 11 Jan, 2022 10:03:14 Top
ewessely




Posts: 55
Joined: 2019-01-31
Hello Andrei,
thanks for your reply!

Sure, I'll send it via mail - it's a plain empty xll...

Regards
Erich
ew
Posted 11 Jan, 2022 10:12:12 Top
Andrei Smolin


Add-in Express team


Posts: 18183
Joined: 2006-05-11
Thank you! I've received the project and passed it to our guys for studying.

Regards from Poland (CET),

Andrei Smolin
Add-in Express Team Leader
Posted 11 Jan, 2022 10:18:02 Top
Andrei Smolin


Add-in Express team


Posts: 18183
Joined: 2006-05-11
Hello Erich,

We can't reproduce the issue using your project. That exception type is enabled but we don't get it.

Regards from Poland (CET),

Andrei Smolin
Add-in Express Team Leader
Posted 17 Jan, 2022 05:27:50 Top
Andrei Smolin


Add-in Express team


Posts: 18183
Joined: 2006-05-11
Are other Excel add-ins and COM add-ins turned off? Is VBA code involved?

Regards from Poland (CET),

Andrei Smolin
Add-in Express Team Leader
Posted 17 Jan, 2022 06:02:35 Top
ewessely




Posts: 55
Joined: 2019-01-31
Hello Andrei,
all other add-ins are turned off, there is no VBA code involved. I just start debugging...

Regards
Erich
ew
Posted 17 Jan, 2022 10:06:55 Top
ewessely




Posts: 55
Joined: 2019-01-31
Hello Andrei,
I did a little bit more research:
I reverted to 9.5.4661 and replaced the loader files.
Result: I can run the sample project from debugger without any problem.
After deinstalling and installing 10.0.4700 and replacing the loader (let adx do it automatically when loading the project and also tried manually) again the error came up when starting the debugger.
I once again reverted to 9.5.4661 -> no error when starting the debugger. After updating to 10.0.4700 the error will also appear again.
So it seems to be a problem with 10.0.4700.

If you need more details or want to see the error I can offer a remote session.

Regards
Erich
ew
Posted 17 Jan, 2022 10:57:46 Top
Andrei Smolin


Add-in Express team


Posts: 18183
Joined: 2006-05-11
Hello Erich,

We've reproduced the issue on another machine. Looking into it.

Regards from Poland (CET),

Andrei Smolin
Add-in Express Team Leader
Posted 19 Jan, 2022 03:37:10 Top
Andrei Smolin


Add-in Express team


Posts: 18183
Joined: 2006-05-11
Hello Erich,

Alas, there will be no quick solution to this. Turn off that exception type to bypass this issue.

Regards from Poland (CET),

Andrei Smolin
Add-in Express Team Leader
Posted 19 Jan, 2022 05:51:23 Top