Issue with ZCO after doing NG Migration

Revision as of 07:39, 29 May 2020 by Sam4wiki (talk | contribs) (Created page with "{{BC|Certified}} __FORCETOC__ <div class="col-md-12 ibox-content"> =ZCO, IMAP, POP not re syncing after NG Migration= <hr> {{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8.x}}}} {{WIP}}...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

ZCO, IMAP, POP not re syncing after NG Migration


   KB 24094        Last updated on 2020-05-29  




0.00
(0 votes)


Problem

After doing a Migration of ZCS using the NG Migration method accounts configured with MAPI, IMAP, POP protocol stops syncing with the existing profile.

Analysis

NG export import is designed in such a way that it only deals with user data and not the server side data namely Tokens. Tokens are the one that act as an index between server and MUA. When an index is broken the existing profile does not know from where to start the sync and as a result it fails.

User-Side Data

  • Emails and Attachments
  • Folders (local and shared)
  • Calendars
  • Documents (for 6.x exports)
  • Briefcases
  • Tasks
  • User Preferences


Server-side Data

  • COSs
  • LDAP user Configs (such as External Auth)
  • Domain Settings

Error Logs

We can get the below log pattern on mailbox.log when an sync request comes from an migrated existing ZCO profile

2020-04-23 06:10:46,621 WARN  [qtp1225197672-10057://example.com/service/soap/WaitSetRequest] [name=user@domain.com;mid=30;ip=192.168.0.1;port=60872;ua=Zimbra-ZCO/8.8.15.1867 (10.0.18363  en-US) P2440 T4bd0 R17;soapId=264f7b68;] SoapEngine - handler exceptioncom.zimbra.common.service.ServiceException: permission denied: can not access account 7a9bef11-558a-4bdf-b3e7-d25577438541

We can get the below log pattern on mailbox.log when an sync request comes from an migrated existing ZDesktop profile

2020-04-23 06:23:52,915 INFO  [qtp1225197672-10084://pudge.ursolutions.ph/service/soap/AuthRequest] [ip=172.104.101.223;port=50522;ua=Zimbra Desktop/7.3.1_13063_Windows;soapId=264f7b9e;] SoapEngine - handler exception: authentication failed for [7a9bef11-558a-4bdf-b3e7-d25577438541], account not found

Solution

The only solution for this is to re create the profiles once again.

To avoid this we recommend to do Rsync method of migration, which will avoid re creating of profiles after migration. This wiki contains more information.
Submitted by: Samrat Sarkar
Verified Against: ZCS 9.0, ZCS 8.8.x Date Created: 2020-05-29
Article ID: https://wiki.zimbra.com/index.php?title=Issue_with_ZCO_after_doing_NG_Migration Date Modified: 2020-05-29



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »


Jump to: navigation, search