androidwog
Lurker
I have been having issues with a particular user and his Samsung Galaxy Note 3 phone. We are using 'Office 365 / Exchange Online' but a lot of this topic applies to on-premise Exchange Server as well.
I enabled ActiveSync logging for the user's device via OWA > Settings > Phone This is a pretty good link about how to collect EAS logs:
blogs.technet.com/b/jasonsla/archive/2013/03/19/exchange-activesync-mailbox-logging.aspx
Note: though you can also retrieve the logs via OWA, I found this powershell command to be beneficial:
Get-MobileDeviceStatistics -Mailbox alias -GetMailboxLog:$true | Out-File c:\scripts\test.txt
This is because:
-Sometimes collecting long duration logs from OWA results in the emailed attachment coming through as an empty .gzip file. The text output doesn't seem to suffer from this
-Running the command produces the text file as well as sends you an email (instead of emailing the user)
-Using the command doesn't disable the logging; using OWA to retrieve logs stops the logging
Using this parser for the log.txt files is really handy:
mailboxlogparser.codeplex.com
The log shows a cyclical behavior- about 5 to 10 minutes of success followed by about 20-25 minutes of failure. When the device is blocked, the logged events go from HTTP 200 success status codes to:
Http Status: 503
AccessState: Blocked
AccessStateReason: SyncCommands
The individual blocked transactions also contain:
X-MS-ASThrottle: SyncCommands
It appears Office365/Exchange Online is throttling this active sync device.
I also noticed that a good number of the
I enabled ActiveSync logging for the user's device via OWA > Settings > Phone This is a pretty good link about how to collect EAS logs:
blogs.technet.com/b/jasonsla/archive/2013/03/19/exchange-activesync-mailbox-logging.aspx
Note: though you can also retrieve the logs via OWA, I found this powershell command to be beneficial:
Get-MobileDeviceStatistics -Mailbox alias -GetMailboxLog:$true | Out-File c:\scripts\test.txt
This is because:
-Sometimes collecting long duration logs from OWA results in the emailed attachment coming through as an empty .gzip file. The text output doesn't seem to suffer from this
-Running the command produces the text file as well as sends you an email (instead of emailing the user)
-Using the command doesn't disable the logging; using OWA to retrieve logs stops the logging
Using this parser for the log.txt files is really handy:
mailboxlogparser.codeplex.com
The log shows a cyclical behavior- about 5 to 10 minutes of success followed by about 20-25 minutes of failure. When the device is blocked, the logged events go from HTTP 200 success status codes to:
Http Status: 503
AccessState: Blocked
AccessStateReason: SyncCommands
The individual blocked transactions also contain:
X-MS-ASThrottle: SyncCommands
It appears Office365/Exchange Online is throttling this active sync device.
I also noticed that a good number of the