Zimbra Shutdown Addin prevents Outlook from closing properly

Ask your questions and get help with Zimbra's Outlook Connector.
m.laily
Posts: 3
Joined: Thu Nov 30, 2017 11:12 am

Zimbra Shutdown Addin prevents Outlook from closing properly

Postby m.laily » Thu Nov 30, 2017 2:51 pm

Hi,

I'm currently developing an Outlook addin using Add-in-Express, and I have a problem that is (at least partially) related to this Zimbra Shutdown Addin.
Sometimes, when opening a new mail window (Inspector), then closing the main Outlook window (Explorer), Outlook never stops completely.
The process stays alive with a grey icon in the systray, and it uses 100% CPU time on one core.

What I've found so far:
- The problem only happens on Windows 10 (I tested it on a clean Windows 7 VM (the bug never happens), and a clean Windows 10 VM (the bug seems to always happen), with a release build of my test addin)
- When tested on live Windows 10 machines, it seems to happen more frequently on some machines than on others, but I've not been able to figure out why.
- The problem only happens when the "Zimbra Shutdown Addin" is loaded (I disabled everything except this Zimbra addin and my addin. The version of Zimbra is the latest available: 8.7.10.1711)
- The "Zimbra Shutdown Addin" and my test addin both work properly when they are the only addin loaded.
- When activating the full log for the Zimbra Connector for Outlook, I see that after Outlook tries to close, it gets stuck in an infinite loop processing the same Windows message (from the log: "Dispatching message 0x738")
- I don't know what this Windows message means, but I found someone with a strangely similar problem here: https://fleexlab.blogspot.fr/2017/06/pa ... ezing.html - It says that this 0x738 message appeared in Windows 10 1703, which would explain why I can't reproduce the problem on Windows 7.

So to sum up, it seems to be an interaction between the Add-in Express addin, and the "Zimbra Shutdown Addin", and I believe the Zimbra plugin might be mishandling this new 0x738 Windows message, causing an infinite loop.

This problem seems closely related to that one viewtopic.php?t=62793 that never got any answer...

I'd really appreciate any help on this topic...

Thanks.


pigu
Posts: 2
Joined: Thu Mar 23, 2017 11:34 am

Re: Zimbra Shutdown Addin prevents Outlook from closing properly

Postby pigu » Mon Dec 11, 2017 1:07 pm

hey, we had the same problem.

i've renamed the dll to shutdownaddin_.dll and now its inactive. outlook is working, synchronizing, stops when i close it and opens again without problems.

i dont know what is it for...
m.laily
Posts: 3
Joined: Thu Nov 30, 2017 11:12 am

Re: Zimbra Shutdown Addin prevents Outlook from closing properly

Postby m.laily » Tue Dec 12, 2017 4:49 pm

My best guess is that it does some kind of cleanup work before letting Outlook really close, but something seems to have broken.

And nobody from Zimbra seems to be interested in helping us...


BTW, here is the part of my log that relates to the shutdown addin, in case it can help (it might at least draw more people to this thread if they try to use google on their own log):

Code: Select all

30-11-2017 10:17:06.783 [O16 MAIN     449C] 
30-11-2017 10:17:06.783 [O16 MAIN     449C] 
30-11-2017 10:17:06.783 [O16 MAIN     449C] 
30-11-2017 10:17:06.783 [O16 MAIN     449C] **************************************************************************************************************************************
30-11-2017 10:17:06.783 [O16 MAIN     449C] ************************************************* SHUTDOWN Addin ExplorerClose Begin *************************************************
30-11-2017 10:17:06.783 [O16 MAIN     449C] **************************************************************************************************************************************

30-11-2017 10:17:06.783 [O16 MAIN     449C] >CShutdownExplorerSink::UninitShutExplorerSink
30-11-2017 10:17:06.783 [O16 MAIN     449C]    >Zimbra::Util::IsOutlookAndEmbedding
30-11-2017 10:17:06.783 [O16 MAIN     449C]    <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]    Explorer count is 0. Last explorer going away
30-11-2017 10:17:06.783 [O16 MAIN     449C]    >OnShutdown
30-11-2017 10:17:06.783 [O16 MAIN     449C]       Resetting Outlook 'MaximumAttachmentSize' to 0
30-11-2017 10:17:06.783 [O16 MAIN     449C]       >StoreContextManager::OnShutdown_
30-11-2017 10:17:06.783 [O16 MAIN     449C]          >StoreContextManager::StopAllStoreContextsSynchronizing
30-11-2017 10:17:06.783 [O16 MAIN     449C]             >StoreContext::StopSynchronizing
30-11-2017 10:17:06.783 [O16 MAIN     449C]                >Synchronizer::RequestShutdown
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   >Synchronizer::AbortSync[p:000002024773D210 Synchronizer 'm.laily@REDACTED.com']
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                >Synchronizer::~Synchronizer
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   >ZimbraConnection::~ZimbraConnection[#1, p:0000020246A36310 owner: 'Synchronizer[p:000002024773D210 Synchronizer 'm.laily@REDACTED.com']']
30-11-2017 10:17:06.783 [O16 MAIN     449C]                      >~Connection[#2   SYNCHRONOUS  0000020246AC1530 owner:'#1, p:0000020246A36310 owner: 'Synchronizer[p:000002024773D210 Synchronizer 'm.laily@REDACTED.com']'']
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         >Disconnect
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            >SetTrusted
30-11-2017 10:17:06.783 [O16 MAIN     449C]                               Trusted: 0
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         >UnregisterConnection
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            Unregistering connection: '#2   SYNCHRONOUS  0000020246AC1530 owner:'#1, p:0000020246A36310 owner: 'Synchronizer[p:000002024773D210 Synchronizer 'm.laily@REDACTED.com']'''
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            Active Connections
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            ------------------
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            Connection 1   '#1   SYNCHRONOUS  0000020246AA6720 owner:'UserSession''
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            Connection 2   '#3   ASYNCHRONOUS 0000020246AC1880 owner:'#2, p:0000020246A36AF0 owner: 'GalSynchronizer[p:0000020246D508F0 GALSync m.laily@REDACTED.com]'''
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            Connection 3   '#6   SYNCHRONOUS  000002024AA2F7B0 owner:'Waitset(mail.REDACTED.com)''
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                      <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                >CSignatureSync::~CSignatureSync[p:0000020246A65B30 SigSync]
30-11-2017 10:17:06.783 [O16 MAIN     449C]                <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                >GalSynchronizer::RequestShutdown
30-11-2017 10:17:06.783 [O16 MAIN     449C]                <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                >GalSynchronizer::~GalSynchronizer[p:0000020246D508F0 GALSync m.laily@REDACTED.com]
30-11-2017 10:17:06.783 [O16 MAIN     449C]                <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                >ZimbraConnection::~ZimbraConnection[#2, p:0000020246A36AF0 owner: 'GalSynchronizer[p:0000020246D508F0 GALSync m.laily@REDACTED.com]']
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   >~Connection[#3   ASYNCHRONOUS 0000020246AC1880 owner:'#2, p:0000020246A36AF0 owner: 'GalSynchronizer[p:0000020246D508F0 GALSync m.laily@REDACTED.com]'']
30-11-2017 10:17:06.783 [O16 MAIN     449C]                      >Disconnect
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         >SetTrusted
30-11-2017 10:17:06.783 [O16 MAIN     449C]                            Trusted: 0
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                      <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                      >UnregisterConnection
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         Unregistering connection: '#3   ASYNCHRONOUS 0000020246AC1880 owner:'#2, p:0000020246A36AF0 owner: 'GalSynchronizer[p:0000020246D508F0 GALSync m.laily@REDACTED.com]'''
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         Active Connections
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         ------------------
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         Connection 1   '#1   SYNCHRONOUS  0000020246AA6720 owner:'UserSession''
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         Connection 2   '#6   SYNCHRONOUS  000002024AA2F7B0 owner:'Waitset(mail.REDACTED.com)''
30-11-2017 10:17:06.783 [O16 MAIN     449C]                         
30-11-2017 10:17:06.783 [O16 MAIN     449C]                      <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]                <0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]             <StoreContext::StopSynchronizing 0ms
30-11-2017 10:17:06.783 [O16 MAIN     449C]             >StoreContextManager::StopSyncThread
30-11-2017 10:17:06.783 [O16 MAIN     449C]                Sync thread handle is not closed.
30-11-2017 10:17:06.783 [O16 MAIN     449C]                Sync thread is not terminated.
30-11-2017 10:17:06.783 [O16 MAIN     449C]                Waiting for sync thread to exit.
30-11-2017 10:17:06.783 [O16 MAIN     449C]                >Zimbra::Util::DispatchableWait
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.783 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.783 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0

                                    30-11-2017 10:17:06.783 [O16 SYNCMAIN 25BC]          [+1.611s]

                                    30-11-2017 10:17:06.783 [O16 SYNCMAIN 25BC]          dwWaitResult = 2

30-11-2017 10:17:06.783 [O16 MAIN     449C]                       Dispatching message 0x401. HWND 0x450fd2

                                    30-11-2017 10:17:06.783 [O16 SYNCMAIN 25BC]          default: 2
                                    30-11-2017 10:17:06.783 [O16 SYNCMAIN 25BC]          WM_QUIT message: OL shutdown signalled. Exiting sync thread
                                    30-11-2017 10:17:06.783 [O16 SYNCMAIN 25BC]       <SyncQueue::DispatchSyncRequests 3.834s
                                    30-11-2017 10:17:06.783 [O16 SYNCMAIN 25BC]    <StoreContextManager::SYNCMAIN_Thread 7.836s

30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x401. HWND 0x7a12f0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0xd00. HWND 0xd165a

                                    30-11-2017 10:17:06.788 [O16 SYNCMAIN 25BC] A<StoreContextManager::SyncThreadProc 7.841s

30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x86. HWND 0xd165a
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x43f. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0xd00. HWND 0xd165a
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x44e. HWND 0x2f10d0
30-11-2017 10:17:06.788 [O16 MAIN     449C]                       Dispatching message 0x401. HWND 0x7a12f0
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x113. HWND 0x0
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 30000ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 29984ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 29984ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 29984ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 29984ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 29984ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 29984ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   <Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   TimeLeft 29984ms
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   MsgWaitForMultipleObjects returned
30-11-2017 10:17:06.793 [O16 MAIN     449C]                   >Msg
30-11-2017 10:17:06.793 [O16 MAIN     449C]                       Dispatching message 0x738. HWND 0x630f62
m.laily
Posts: 3
Joined: Thu Nov 30, 2017 11:12 am

Re: Zimbra Shutdown Addin prevents Outlook from closing properly

Postby m.laily » Thu Jan 25, 2018 8:49 am

Hey, Zimbra, would you care to reply to this topic?

I have new information from the Add-in Express team: they were able to reproduce the issue with some Visual Studio add-ins (Team Foundation Add-in and Visual Studio Tools for Office Design-Time Adaptor for Excel)

So it looks a lot like the problem is not on their side...
calandacomp
Posts: 2
Joined: Tue Jun 20, 2017 7:32 am

Re: Zimbra Shutdown Addin prevents Outlook from closing properly

Postby calandacomp » Tue Feb 20, 2018 4:28 pm

Hi there

We've got the same Problems on some Outlook 2016 Clients with the latest Connector installed. It might be a Windows 10/Office 2016 Update issue... We didn't found the cause yet. But if we Disable the Shutdown Addin in Outlook (like pigu mentioned to renade ShutdownAddin.dll).

This fixes the problem, outlook closes directly as it should. What happens if we disable the ShutdownAddin.dll, any issues with that?

Thank you for your info.

kind regards

Return to “Zimbra Connector for Outlook”

Who is online

Users browsing this forum: No registered users and 1 guest