![zimbra outlook wont close zimbra outlook wont close](https://studfile.net/html/2706/1180/html_AV4xGO6vVl.IFnu/htmlconvd-hnc1FJ178x1.jpg)
- ZIMBRA OUTLOOK WONT CLOSE FULL
- ZIMBRA OUTLOOK WONT CLOSE WINDOWS 10
- ZIMBRA OUTLOOK WONT CLOSE TRIAL
- ZIMBRA OUTLOOK WONT CLOSE PC
- ZIMBRA OUTLOOK WONT CLOSE WINDOWS 7
Test addin with a region showing in the inspector: I reproduced the problem.
ZIMBRA OUTLOOK WONT CLOSE TRIAL
(I guess installing the trial version of Zimbra server might work, but it would be a real pain to do so)Īnyway, I tried what you suggested and here are the results: I'm not sure if you managed to do it but I understand this is hard to try to reproduce the problem without it.
![zimbra outlook wont close zimbra outlook wont close](https://image.slidesharecdn.com/2017partnersummitzimbrabytesconsolidated-170810133132/85/zimbra-apxj-partner-summit-2017-zimbra-bytes-58-320.jpg)
I tried to find where you might have been blocked by installing the Zimbra Connector for Outlook in a virtual machine without connecting to a Zimbra server but I couldn't find a way.
ZIMBRA OUTLOOK WONT CLOSE PC
The next step is likely to require that we access your PC remotely (preferably with VS installed) to determine the exact reasons of the problem. If the issue is gone on any step, then at least we will know what forces it to appear. First off, do not show our region in the inspector window, and then remove the entire ADXOlFormsManager component from the test add-in. The message you are talking about seems to be a regular internal Outlook message (WM_USER + id), the infinite appearance of which is a consequence and not the source of the problem. Looping occurs for other reasons that are unknown yet. our add-in is still working and the hook handler reacts to any message that is sent in the current thread. What you see in the debugger is the consequence (aftereffect) of the problem, i.e. Probably we need credentials for Zimbra Colaboration Network, but we don't have them. We installed Zimbra add-in, but have not been able to reproduce the issue, although we believe it exists. I've been stuck on this problem for a while now, and I would very much appreciate your help. This would be easy to say it's Zimbra's fault, but unfortunately we obviously can't release an addin that would not work if our clients happen to use Zimbra, especially when Zimbra on its own works fine. So to sum up, it seems to be an interaction between the Add-in Express advanced form regions, and this "Zimbra Shutdown Addin".
ZIMBRA OUTLOOK WONT CLOSE WINDOWS 10
I don't know what this Windows message means, but I found someone with a strangely similar problem here: - It says that this 0x738 message appeared in Windows 10 1703, which would explain why I can't reproduce the problem on Windows 7.
ZIMBRA OUTLOOK WONT CLOSE FULL
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")
![zimbra outlook wont close zimbra outlook wont close](https://docplayer.net/docs-images/54/9520453/images/page_4.jpg)
I'm not sure if this is related to the problem or important to know. When attaching a debugger to the failing Outlook process and pausing randomly, I sometimes get in some Add-in Express code: AddinExpress.OL.2005.dll!(int code, System.IntPtr wParam, System.IntPtr lParam), or AddinExpress.OL.2005.dll!(int code, System.IntPtr wParam, System.IntPtr lParam) for example. The "Zimbra Shutdown Addin" and my test addin both work properly when they are the only addin loaded. The version of Zimbra is the latest available: 8.) The problem only happens when the "Zimbra Shutdown Addin" is loaded (I disabled everything except this Zimbra addin and my 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.
ZIMBRA OUTLOOK WONT CLOSE WINDOWS 7
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) I've been able to reproduce the problem with a completely new addin project using the latest version, with only an empty advanced region added and configured to show when writing a new mail from an Inspector. I know this looks like a frequent problem related to not properly releasing COM objects, but I believe this is a different scenario.
![zimbra outlook wont close zimbra outlook wont close](https://wiki.zimbra.com/images/a/a6/ZCOLogCtl.jpg)
The problem happens almost every time on some machines, and rarely on others. It's then impossible to reopen it or close it properly without killing the process first. The process stays alive with a grey icon in the systray, and it uses 100% CPU time on one core. I'm working on an Outlook addin and I have a problem: sometimes when the addin is loaded and an Inspector with an advanced form region is open, if I close the Explorer, Outlook never closes completely.