Adress book not synchronised if only group(s) in rights (RU server)

Links used in this discussion

Stéphane DORIGO, User (Posts: 6)

Sep 17, 2019 1:08:14 pm EDT


RU Server [2790]
Windows 10 (1803)

If there is only group (without user from this group) autorized by security rights of an adress book, the adress book not synchronised for a user of this group.
If we add autorisation for user(s) of the group explicitly, adress book synchronised well !
(see images attached to check settings).

Bug ?

Best regards.
Attached Files

Polina Krasnoborceva, Support (Posts: 961)

Sep 17, 2019 5:43:22 pm EDT

Hello Stéphane,

Thank you for your message.

Could you please clarify if you have the auto-logon to the RU Server feature enabled?

Also, here's a relatable Community thread that might be helpful.

Looking forward to your reply.

Stéphane DORIGO, User (Posts: 6)

Sep 18, 2019 5:47:08 am EDT

Hello Polina,

Yes, "auto logon" is enabled, but, "auto logon" enabled or not, the problem still the same.
Logoff / re-logon doesn't work either.

The relatable community thread indicated doesn't help me and conclusions are not clear… It seems doesn't works fine all the time (not like when user is Added explicitly).

One thing is sure, if you add explicitly the user (member of the group) in security rights of the adressbook, it works fine immediatly you valid the modification (therefore, it's not a RU server connection problem…).
If you remove the user and valid the modification, logoff and re-logon, then synchronisation doesn't work again...

Best regards.

Stéphane DORIGO, User (Posts: 6)

Sep 18, 2019 6:06:15 am EDT


After some others tests, It seems you must restart the RU server after adressbook rights modifications !
If you do it and re-login, it seems works fine (but strange thing is if you add user explicitly, you have not to restart the RU server to changes take effect...).

Best regards.

Polina Krasnoborceva, Support (Posts: 961)

Sep 18, 2019 1:59:36 pm EDT

Hello Stéphane,

Thank you for the provided details.

I'm glad to hear you've figured out the issue. Unfortunately, we weren't able to reproduce it yet as it seems that the issue only occurs in some certain conditions. However, in the near future, we are planning to improve the server sign-in and synchronization processes anyway.

Please let us know if the issue reoccurs so we could proceed with the further troubleshooting.

* Website time zone: America/New_York (UTC -4)

This website uses cookies to improve user experience. By using this website you agree to our Terms of Service and Privacy Policy.