What is the os from your gw Server?
wich gw Version and Build do you have?
ask for the new gms Version and Build, may be gms 24.3 Build 11256?

Hi Greiner,

My OS across all Gw servers are SLES15sp5

GW 24.2 build 145595

Dont knwi if i want to change becaus eof a Sumsang update ..or is this how it works?  .. will a gms24.3 work on my gw24.2 ...my lessons form gms is if you egt a version that is stable ..keep as long as you can..had some terrible versions last couple of years ..i am sort of AFRAID to do anything on GMS ones you get it to a stable release....

Open a case and you will hear if this trouble is known and how to Resolve it

i am on the latent Versions and Build for gw24.3 and gms24.3, also messenger24.3 and this is very stable

we use only Apple iPhone, iPads and not samsung! No Experience with there os, i think Android!

Build 24.2 11249 is a bit older, in the field we usually use 24.3 and the latest build if possible. In Mobility there is also Android with the latest firmware, so far no problem with the sync could be detected.

A mail to a user in Datasync arrives almost simultaneously with a mail that is reported in the GWClient. This is how it is in our system in the company

The first place I would go is the mcheck. The recommendation is to run a general health check first and use mcheck to analyze the users that are affected. There are many more points in the analysis, first of all mcheck.

After mcheck analysis, it continues to /var/log/datasync. In this directory there are important logs concerning the function of Syncenginge, GroupWise Engine

In point still, is there a commercial certificate or a commercial wildcard certificate in the GMS. Is a sellf signed used? Is the server mapped externally and internally with FQDN?

George

I suggest to set the debug log level and after the GMS restart try to connect with a problem device to see if actually the device connects or it looks like it doesnt as the mobility-agent.log should show the connections and errors when there. Also as Georg mentioned the external certificate used on GMS should be a commercial one as devices have more and more issues with self signed ones.

Also is there a MDM in between the device and GMS that might be an issue?

So start with logs and if needed open a case the have some help looking at this