Issue with ZCO after doing NG Migration: Difference between revisions
mNo edit summary |
|||
Line 2: | Line 2: | ||
__FORCETOC__ | __FORCETOC__ | ||
<div class="col-md-12 ibox-content"> | <div class="col-md-12 ibox-content"> | ||
=ZCO, IMAP, POP do not sync after NG Migration= | |||
=ZCO, IMAP, POP not | |||
<hr> | <hr> | ||
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|}} | {{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|}} | ||
Line 12: | Line 9: | ||
===Problem=== | ===Problem=== | ||
After doing a Migration of ZCS using the NG Migration | After doing a Migration of ZCS using the NG Migration tools, accounts configured with MAPI, IMAP, POP protocol stop syncing with the existing profile. | ||
===Analysis=== | ===Analysis=== | ||
NG export import is designed in such a way that it only deals with user data and not the server side data | NG export-import is designed in such a way that it only deals with user data and does not deal with the server side data, including Tokens. Tokens act as an index between the 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==== | ====User-Side Data==== | ||
Line 33: | Line 30: | ||
====Error Logs==== | ====Error Logs==== | ||
We can get the below log pattern on mailbox.log when | We can get the below log pattern on mailbox.log when a sync request comes from a migrated but 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 | 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 | We can get the following 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 | 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 | ||
Revision as of 17:28, 9 June 2020
ZCO, IMAP, POP do not sync after NG Migration
Problem
After doing a Migration of ZCS using the NG Migration tools, accounts configured with MAPI, IMAP, POP protocol stop syncing with the existing profile.
Analysis
NG export-import is designed in such a way that it only deals with user data and does not deal with the server side data, including Tokens. Tokens act as an index between the 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 a sync request comes from a migrated but 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 following 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 |