CXN COM addin crashes Excel 2007

Hi,

when the "CXNSharedAddin", which was installed with Marvin Beans, is active MS Excel 2007 crashes on exit. Disabling this COM addin solves the issue. I could reproduce this problem on other machines running MS Office 2007, but not with Office 2003^[1] or Office 2010.

Not 100% sure, but I think this effect was introduced with Marvin Beans 5.9.0. Would be great if this could be fixed in upcoming versions or this addin could be desactivated during the installation.

[1] I'm not sure if the addin gets loaded in Excel 2003. The registry entries exist, but the addin does not appear in the addin manager.

Please try out 5.9.2 patch. So far we have not got such a problem yet though.

 

I have just tested our

https://www.chemaxon.com/download.php?d=/data/download/marvin/5.9.2/marvinbeans-5.9.2-windows.exe

Marvin build on a clear environment

Windows7 64 bit and Office 2007 32 bit and 32 bit Marvin WIndows installer

Excel is loaded, SharedAddin is loaded, no exception occurs.

Please test it as well on your environment.

 

I've just tested this on another machine:

• Windows XP Professional (32bit, French) with all security updates


• Office 2007 SBE (French) with all security updates


• Marvin Beans 5.9.2 (installed with default options)

Steps to reproduce:

• Open an Excel-document (or Excel with an empty spreadsheet)


• Close Excel --> Excel crashes and wants to send an error report to MS (see screenshots)

After desactivation of the CXNSharedAddin the issue disappears and returns when the addin is again activated.

Well, the test systems are not "clean", but production systems. Will reproduce in a VM when I find time.

 

Best regards

Thank you , we try to do same on a separate virtual machine. I will let you know about the result.

We managed to reproduce the issue on a machine and found the problem.

This will be fixed soon this Friday or Next Monday when the 5.9.4 comes out. The fix will also be in 5.10 line as well.

hamoriviktor wrote:

We managed to reproduce the issue on a machine and found the problem. This will be fixed soon this Friday or Next Monday when the 5.9.4 comes out. The fix will also be in 5.10 line as well.

Hi,

This is indeed strange, because all my attempts to reproduce the effect in a VM failed. Finally I could not track down what the difference between the setup in the VM and the 4 affected machines (all others have Office 2003 or 2010) is.

Even better that you could isolate the problem.

Thanks a lot!