Sync on Mobile works only randomly

MailEnable Exchange ActiveSync (EAS) - for EAS enabled devices (including iPhone, Windows Phone 7, Android, Nokia, etc).
MailEnable-Ian
Site Admin
Posts: 9460
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Sync on Mobile works only randomly

Post by MailEnable-Ian » Thu Mar 11, 2021 5:26 am

Hi,

In order to capture the problem and errors you may need to disable the automated restarting and have the logging enabled. I know this is tedious but if you restart then you might not be able to determine when the problem occurs.
Regards,

Ian Margarone
MailEnable Support

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Thu Mar 11, 2021 4:59 pm

Hi Ian

Cant afford to lose a client with 200 users on RDP in the datacenters. It pays my rent so I need to run as stable as possible.

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Sat Mar 13, 2021 11:08 am

It seems its related to standby memory allcocated by the server itself.

I disabled the script and ran "emptystandbylist.exe" which runs every minute on a schedule.

It has run stable since then. (24hrs). I will let it run to see if something shows up.

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Mon May 24, 2021 5:03 pm

Now I am back to restarting the server to get mobile sync to work... not even a service restart works.

It needs a complete reboot and then it syncs.

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Mon May 24, 2021 5:24 pm

Getting a shitload of these in event viewer...

Faulting application name: MEHTTPS.EXE, version: 1.0.0.59, time stamp: 0x602b1f03
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff7b084569e
Faulting process id: 0xac4
Faulting application start time: 0x01d7507b32621a60
Faulting application path: C:\PROGRA~2\MAILEN~1\Bin64\MEHTTPS.EXE
Faulting module path: unknown
Report Id: 3b561b03-6a68-4586-a0fe-a8c2f699ff8c
Faulting package full name:
Faulting package-relative application ID:

Combined with these

Failure: (MailEnable HTTPMail Service (C:\PROGRA~2\MAILEN~1\Bin64\MEHTTPS.EXE) error: 10048) - ME-F0090: Unable to bind to IP Address (127.0.0.1), Port (8080), Error (10048). Could not start service. Check that another service is not running or security software has not prevented access to the port.


Nothing changed and everything is fine upon a reboot.

MailEnable-Ian
Site Admin
Posts: 9460
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Sync on Mobile works only randomly

Post by MailEnable-Ian » Thu May 27, 2021 12:41 am

Hi,

The error is reporting that its unable to bind to port 8080. Run "netstat" and check that there is not another service binding on port 8080.
Regards,

Ian Margarone
MailEnable Support

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Fri May 28, 2021 7:39 am

C:\Users\Administrator>netstat -aon | findstr 8080
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 3580
TCP 10.X.10.4:8080 X.241.129.121:46228 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.241.137.58:32302 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.49.44.220:289X ESTABLISHED 3580
TCP 10.X.10.4:8080 X.49.45.199:5272 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.115.165.122:5X1 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.115.165.122:51620 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.115.165.122:52754 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.115.165.122:56499 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.115.165.122:58844 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.26.61.45:36416 ESTABLISHED 3580
TCP 10.X.10.4:8080 X.180.80.22:6379 ESTABLISHED 3580

Nothing but the mailserver itself.

MailEnable-Ian
Site Admin
Posts: 9460
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Sync on Mobile works only randomly

Post by MailEnable-Ian » Mon May 31, 2021 11:15 pm

Hi,

Run

netstat -a -n -b > c:\log.txt


The above will log the processes to see if there another process and not a MailEnable process binding to port 8080.
Regards,

Ian Margarone
MailEnable Support

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Tue Jun 01, 2021 2:06 pm

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
[MESMTPC.EXE]
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:110 0.0.0.0:0 LISTENING
[MEPOPS.EXE]
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:143 0.0.0.0:0 LISTENING
[MEIMAPS.exe]
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING
[MELDAPS.EXE]
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:465 0.0.0.0:0 LISTENING
[MESMTPC.EXE]
TCP 0.0.0.0:993 0.0.0.0:0 LISTENING
[MEIMAPS.exe]
TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING
[MEXMPPS.EXE]
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TermService
[svchost.exe]
TCP 0.0.0.0:5222 0.0.0.0:0 LISTENING
[MEXMPPS.EXE]
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:8072 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
[MEHTTPS.EXE]
TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING
[MERADMS.exe]
TCP 0.0.0.0:8801 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING
EventLog
[svchost.exe]
TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING
SessionEnv
[svchost.exe]
TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING
[spoolsv.exe]
TCP 0.0.0.0:49668 0.0.0.0:0 LISTENING
PolicyAgent
[svchost.exe]
TCP 0.0.0.0:49679 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49690 0.0.0.0:0 LISTENING
[lsass.exe]
TCP 10.xxx.10.4:25 45.148.10.190:43972 TIME_WAIT
TCP 10.xxx.10.4:25 87.246.7.227:39106 TIME_WAIT
TCP 10.xxx.10.4:25 91.191.209.234:56706 TIME_WAIT
TCP 10.xxx.10.4:25 212.70.149.55:2592 ESTABLISHED
[MESMTPC.EXE]
TCP 10.xxx.10.4:25 212.70.149.55:5530 TIME_WAIT
TCP 10.xxx.10.4:25 212.70.149.55:36284 TIME_WAIT
TCP 10.xxx.10.4:139 0.0.0.0:0 LISTENING
Can not obtain ownership information
TCP 10.xxx.10.4:993 xx.xx.246.13:19944 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.13:24515 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.13:29862 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.13:37269 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.13:37861 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.13:43894 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.13:62430 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.13:64779 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:3718 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:4202 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:4286 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:5723 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:5913 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:6410 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:6580 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:7489 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:8232 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:8284 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:8411 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:8837 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:8885 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:9700 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:11477 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:12048 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:12470 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:12536 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:15498 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:15822 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:17816 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:17950 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:19036 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:19578 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:19800 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:20331 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:26623 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:29396 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:30774 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:31729 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:33499 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:36057 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:38914 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:42427 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:43064 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:44116 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:44305 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:46239 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:47199 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:48628 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:51496 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:52222 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:52698 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:53660 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:54233 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:54845 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:55236 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:55630 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:56262 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:57700 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:57747 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:58607 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:59402 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:60433 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:61558 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:993 xx.xx.246.18:63581 ESTABLISHED
[MEIMAPS.exe]
TCP 10.xxx.10.4:3389 10.xxx.1.10:38173 ESTABLISHED
TermService
[svchost.exe]
TCP 10.xxx.10.4:8080 2.111.68.205:38116 ESTABLISHED
[MEHTTPS.EXE]
TCP 10.xxx.10.4:8080 2.111.68.205:43526 ESTABLISHED
[MEHTTPS.EXE]
TCP 10.xxx.10.4:8080 2.111.68.205:52230 ESTABLISHED
[MEHTTPS.EXE]
TCP 10.xxx.10.4:8080 31.208.25.188:6492 ESTABLISHED
[MEHTTPS.EXE]
TCP 10.xxx.10.4:8080 77.241.128.8:49652 ESTABLISHED
[MEHTTPS.EXE]
TCP 10.xxx.10.4:8080 93.160.61.190:56862 ESTABLISHED
[MEHTTPS.EXE]
TCP 10.xxx.10.4:8080 152.115.165.122:61759 ESTABLISHED
[MEHTTPS.EXE]
TCP 10.xxx.10.4:49680 20.54.37.73:443 ESTABLISHED
ProfSvc
[svchost.exe]
TCP 10.xxx.10.4:51421 93.184.220.29:80 ESTABLISHED
[lsass.exe]
TCP 10.xxx.10.4:51435 104.47.70.33:25 TIME_WAIT
TCP 10.xxx.10.4:51443 106.10.248.74:25 ESTABLISHED
[MESMTPC.EXE]
TCP 10.xxx.10.4:51448 40.77.226.250:443 ESTABLISHED
DiagTrack
[svchost.exe]
TCP 10.xxx.10.4:51449 20.62.190.184:443 ESTABLISHED
wuauserv
[svchost.exe]
TCP 10.xxx.10.4:51450 205.185.216.10:80 SYN_SENT
ProfSvc
[svchost.exe]
TCP 127.0.0.1:80 127.0.0.1:51436 FIN_WAIT_2
Can not obtain ownership information
TCP 127.0.0.1:80 127.0.0.1:51446 FIN_WAIT_2
Can not obtain ownership information
TCP 127.0.0.1:783 0.0.0.0:0 LISTENING
[spamd.exe]
TCP 127.0.0.1:3310 0.0.0.0:0 LISTENING
[clamd.exe]
TCP 127.0.0.1:51436 127.0.0.1:80 CLOSE_WAIT
[METray.exe]
TCP 127.0.0.1:51445 127.0.0.1:783 TIME_WAIT
TCP 127.0.0.1:51446 127.0.0.1:80 CLOSE_WAIT
[METray.exe]
TCP 127.0.0.1:55009 127.0.0.1:55010 ESTABLISHED
[spamd.exe]
TCP 127.0.0.1:55010 127.0.0.1:55009 ESTABLISHED
[spamd.exe]
TCP 127.0.0.1:63901 127.0.0.1:63902 ESTABLISHED
[spamd.exe]
TCP 127.0.0.1:63902 127.0.0.1:63901 ESTABLISHED
[spamd.exe]
TCP [::]:80 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:135 [::]:0 LISTENING
RpcSs
[svchost.exe]
TCP [::]:443 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:445 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:3389 [::]:0 LISTENING
TermService
[svchost.exe]
TCP [::]:5985 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:8072 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:8801 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:47001 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:49664 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:49665 [::]:0 LISTENING
EventLog
[svchost.exe]
TCP [::]:49666 [::]:0 LISTENING
SessionEnv
[svchost.exe]
TCP [::]:49667 [::]:0 LISTENING
[spoolsv.exe]
TCP [::]:49668 [::]:0 LISTENING
PolicyAgent
[svchost.exe]
TCP [::]:49679 [::]:0 LISTENING
Can not obtain ownership information
TCP [::]:49690 [::]:0 LISTENING
[lsass.exe]
UDP 0.0.0.0:123 *:*
W32Time
[svchost.exe]
UDP 0.0.0.0:500 *:*
IKEEXT
[svchost.exe]
UDP 0.0.0.0:3389 *:*
TermService
[svchost.exe]
UDP 0.0.0.0:3544 *:*
iphlpsvc
[svchost.exe]
UDP 0.0.0.0:4500 *:*
IKEEXT
[svchost.exe]
UDP 0.0.0.0:5050 *:*
[svchost.exe]
UDP 0.0.0.0:5353 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:5355 *:*
Dnscache
[svchost.exe]
UDP 10.xxx.10.4:137 *:*
Can not obtain ownership information
UDP 10.xxx.10.4:138 *:*
Can not obtain ownership information
UDP 10.xxx.10.4:1900 *:*
SSDPSRV
[svchost.exe]
UDP 10.xxx.10.4:59161 *:*
SSDPSRV
[svchost.exe]
UDP 10.xxx.10.4:60371 *:*
iphlpsvc
[svchost.exe]
UDP 127.0.0.1:1900 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:57477 *:*
iphlpsvc
[svchost.exe]
UDP 127.0.0.1:59162 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:62813 *:*
[MELDAPS.EXE]
UDP [::]:123 *:*
W32Time
[svchost.exe]
UDP [::]:500 *:*
IKEEXT
[svchost.exe]
UDP [::]:3389 *:*
TermService
[svchost.exe]
UDP [::]:4500 *:*
IKEEXT
[svchost.exe]
UDP [::1]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [::1]:59160 *:*
SSDPSRV
[svchost.exe]

MailEnable-Ian
Site Admin
Posts: 9460
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Sync on Mobile works only randomly

Post by MailEnable-Ian » Thu Jun 03, 2021 3:32 am

Hi,

How do you connect to ActiveSync? Is it via the "Synchronization" service via port 8080 or via IIS over port 80 or 443 SSL?
Regards,

Ian Margarone
MailEnable Support

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Fri Jun 04, 2021 5:15 am

8080

MailEnable-Ian
Site Admin
Posts: 9460
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Sync on Mobile works only randomly

Post by MailEnable-Ian » Sat Jun 05, 2021 1:01 am

Hi,

Can you try and setup a host header under the "MailEnable Protocols" website in IIS and connect over port 80 so we can eliminate he sync service being the problem.
Regards,

Ian Margarone
MailEnable Support

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Mon Jun 14, 2021 3:28 pm

We need to do that together since its production and a lot of mobile clients connect via port 8080...

MailEnable-Ian
Site Admin
Posts: 9460
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Sync on Mobile works only randomly

Post by MailEnable-Ian » Tue Jun 15, 2021 2:21 am

Hi,

Sorry what do mean together?
Regards,

Ian Margarone
MailEnable Support

Supermule
Posts: 22
Joined: Tue Mar 09, 2021 12:57 pm

Re: Sync on Mobile works only randomly

Post by Supermule » Wed Jun 16, 2021 6:09 am

I need your help to figure it out and do it...

Since I will disconnect about 200 users from mobile sync when testing.

Post Reply