We are hoping that you can help. We run Zimbra connector 7.1.1 with Outlook 2010. There is one system (Windows 7) that has four separate users on it. We notice that we get Zimbra dumps in the zco-cores folder for each user at an alarming rate. We get 10-20 of these files per minuteon average which is causing an issue with hard drive space. The users report no issues. I have attached a few logs to this, please let us know what to do.
I should also note the issue also occured with zimbra 6.xxx. We did an upgrade which we thought would fix issue but did not
It looks like it's crashing in the Windows Search stuff. Any chance you could disable that and see if you still get the issue?
Thanks for the quick responce..I just disable search and will monitor. One thing though we get the message everytime we launch Outlook that Windows Search is disabled etc. Our users get a lot of email and do need to search from time to time so this may not be a great work around. I will post results...
FWIW, email search in the Zimbra Web client is a ton better and faster. I actually use Outlook all day, but whenever I want to search, I use the Zimbra Web client.
I personally agree, but some users only know how to do things one way and do not want to deviate...
We let it run over the weekend with Windows search disabled (we are a 24 x 7 company) and did not receive any new crashes. So this apparently was the issue. I guess my next question would be is there another way around it? It seems a bit counter productive to disable a useful Windows function to alleviate this.
Maybe you can just turn off indexing for .zdb files:
Tools, Instant Search, Search Options, Indexing. Uncheck the .zdb file
Then you don't have to disable the whole search capability.
You could also send some zco log files so we could see what was happening when it crashed, but I'm not convinced it would help, but it's possible. We put out logs for zco and searchprotocolhost, so you could post those. Don't set verbose logging on -- just logging and http logging.
But I would try re-enabling windows desktop search, but just turn off indexing for zdb files, and see what that does.