Hey Guys,
I implemented z-push 57 and everything works fine on ICS while I tested it on Jelly bean and observing below issues on z-push.log and unable to sync contacts only with jellybean. But at the same time I can sync Calendar as well as Emails properly on Jellybean
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): ZIMBRA Logon URL [https://xxxxxxxxxxx/service/soap/]
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): ZIMBRA soapURL [https://xxxxxxxxxxx:443/service/soap">h ... vice/soap/]
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): Overriding Logon URL with ZIMBRA soapURL [https://xxxxxxxxxxx:443/service/soap">h ... vice/soap/]
12/01/2014 05:37:15 [ 3141] [INFO] [user-10@xxxxxxxxxxx] StatusException: BackendSearchZimbra->GetGALSearchResults(): Range exceeds maximum allowed! - code: 12
12/01/2014 05:37:15 [ 3140] [INFO] [user-8@xxxxxxxxxxx] StatusException: BackendSearchZimbra->GetGALSearchResults(): Range exceeds maximum allowed! - code: 12
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] /usr/share/z-push/lib/request/search.php:287 Undefined index: searchtotal (8)
12/01/2014 05:37:15 [ 3140] [WARN] [user-8@xxxxxxxxxxx] /usr/share/z-push/lib/request/search.php:287 Undefined index: searchtotal (8)
z-push having an issue with Jellybean and ZCS 8.0.4
z-push having an issue with Jellybean and ZCS 8.0.4
Ah, I found the issue and fixed.It was in zimbra.php returning only 99 GAL and increased the limit and all done.
-
liverpoolfcfan
- Elite member
- Posts: 1112
- Joined: Sat Sep 13, 2014 12:47 am
z-push having an issue with Jellybean and ZCS 8.0.4
The error you posted has nothing to do with synching. So, I am not sure what your initial issue was.
The ActiveSync spec says
[QUOTE]If the request does not include a Range element, the default Range value for each Store type is used. The following table identifies the default Range values and maximum results returned for each Store type:
Store Default_range Maximum_results
Mailbox 0-99 100
DocumentLibrary 0-999 1000
GAL 0-99 100
If the Range element value specified in the request exceeds the default range value, a Status element (section 2.2.3.162.12) value of 12 is returned to indicate that the maximum range has been exceeded, as specified in section 2.2.3.162.12.[/QUOTE]
If you are seeing Error 12 - your device is requesting more GAL entries than the max allowed.
The ActiveSync spec says
[QUOTE]If the request does not include a Range element, the default Range value for each Store type is used. The following table identifies the default Range values and maximum results returned for each Store type:
Store Default_range Maximum_results
Mailbox 0-99 100
DocumentLibrary 0-999 1000
GAL 0-99 100
If the Range element value specified in the request exceeds the default range value, a Status element (section 2.2.3.162.12) value of 12 is returned to indicate that the maximum range has been exceeded, as specified in section 2.2.3.162.12.[/QUOTE]
If you are seeing Error 12 - your device is requesting more GAL entries than the max allowed.
-
liverpoolfcfan
- Elite member
- Posts: 1112
- Joined: Sat Sep 13, 2014 12:47 am
z-push having an issue with Jellybean and ZCS 8.0.4
By the way, you can also get rid of these warnings
[QUOTE]12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): ZIMBRA Logon URL [https://xxxxxxxxxxx/service/soap/]
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): ZIMBRA soapURL [https://xxxxxxxxxxx:443/service/soap">h ... vice/soap/]
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): Overriding Logon URL with ZIMBRA soapURL [https://xxxxxxxxxxx:443/service/soap">h ... vice/soap/]
[/QUOTE]
by simply making sure your zimbra_url matches what you have configured as the public URL within zimbra
In this case the right thing to do is probably remove the :443 from zimbra - but you could also add the :443 in the backend config setting ZIMBRA_URL too. Either way should work.
[QUOTE]12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): ZIMBRA Logon URL [https://xxxxxxxxxxx/service/soap/]
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): ZIMBRA soapURL [https://xxxxxxxxxxx:443/service/soap">h ... vice/soap/]
12/01/2014 05:37:15 [ 3141] [WARN] [user-10@xxxxxxxxxxx] Zimbra->GetUserInfo(): Overriding Logon URL with ZIMBRA soapURL [https://xxxxxxxxxxx:443/service/soap">h ... vice/soap/]
[/QUOTE]
by simply making sure your zimbra_url matches what you have configured as the public URL within zimbra
In this case the right thing to do is probably remove the :443 from zimbra - but you could also add the :443 in the backend config setting ZIMBRA_URL too. Either way should work.