ZCO Sync Problems

[mackoftrack]

ZCO 7.x
Release 7.1.3_GA_3346.RHEL5_64_20110928134534 RHEL5_64 NETWORK edition.

We are having lots of issues across our entire company with the latest ZCO. All kinds of local failures, SearchProtocolHost crashes, failed syncs, etc.

I've attached a couple ZCO logs.

Thanks for your help.

[fsiegel]

So the logs you sent don't really show anything, but we would be able to see a lot more if you enable Http logging. Go into ZCOLogCtl, and enable that, but don't enable verbose. If there is a crash (in ZCO, not Search Protocol Host), then there should be a corresponding.dmp file in %TMP%\zco-cores, and you can send that.

If Search Protocol Host is a problem, you should disable it for .zdb files (you should do that anyway). Tools, Instant Search, Search Options, Indexing. Uncheck the .zdb file.

Also, you are using 6.0.8. Ancient.

[mackoftrack]

Originally Posted by fsiegel

So the logs you sent don't really show anything, but we would be able to see a lot more if you enable Http logging. Go into ZCOLogCtl, and enable that, but don't enable verbose. If there is a crash (in ZCO, not Search Protocol Host), then there should be a corresponding.dmp file in %TMP%\zco-cores, and you can send that.

If Search Protocol Host is a problem, you should disable it for .zdb files (you should do that anyway). Tools, Instant Search, Search Options, Indexing. Uncheck the .zdb file.

Also, you are using 6.0.8. Ancient.

Problem still exists with ZCO 7.1.3. I enabled http logging so please see attached log.
Windows Search has been completely disabled, and the problem remains.

Please help!

Thanks

[fsiegel]

Looks like authentication and proxy issues. It looks like you're using proxy settings from Internet Explorer? Are these set up correctly? Perhaps you can change your profile to do No Proxy or manual proxy? (Connection Settings tab)

[mackoftrack]

No proxy is being used.

[fsiegel]

Still not sure what's going on. Looks like you're just using the IE proxy settings, so that should be ok. BTW, the verbose logging really makes it hard to see what is going on. The best would be http logging without verbose.