Showing posts with label Active Sync. Show all posts
Showing posts with label Active Sync. Show all posts

Tuesday, September 1, 2015

[EX2013] Calendar Sync Issues




Plano de ação para analisarmos os problemas de sincronismo de calendário com dispositivos iOS.


Plano de Ação:
=============
* Antes de reproduzir o problema:
1)    Habilitar o ActiveSync Mailbox logging para a conta afetada;
Set-CASMailbox <user> -ActiveSyncDebugLogging:$true


* Depois de reproduzir o problema:
2)    Recuperar o log de ActiveSync na caixa de correio afetada;
Get-ActiveSyncDeviceStatistics -Mailbox <user> -GetMailboxLog:$true –NotificationEmailAddresses jfeitosa.solve@suzano.com.br

3)    Exportar um dump das propriedades do usuário afetado;
Get-Mailbox <user> | fl

4)    Exportar os dispositivos na conta afetada;
Get-MobileDeviceStatistics -Mailbox <user> | fl DeviceId, DeviceType, DeviceModel, DeviceOS, DeviceFriendlyName, Name, LastS*

5)    Salvar uma cópia dos eventos de Application em formato *csv de todos os servidores CAS que atendem o tráfego do ActiveSync;

6)    Salvar os logs de IIS e IIS http err de todos os servidores CAS que atendem o tráfego do ActiveSync;
a.     IIS logs (Default: C:\inetpub\logs\LogFiles\W3SVC1)
b.     IIS HTTP error logs (Default: C:\Windows\System32\LogFiles\HTTPERR)


Artigos Relacionados:
=============
# Known calendaring issues with iOS 8.x and iOS 7.x devices

# Current issues with Microsoft Exchange ActiveSync and third-party devices

Sunday, August 30, 2015

[EX2010] EAS: 8MB attachment



Event ID 1008: "Maximum Request Length Exceeded"


This is due to the Max Request Length setting being 10MB by default.  So any message with an attachment that is around 8MB or so will fail to send as the request is too big.  The reason I say 8MB is that we have to take into consideration the 33% MIME conversion bloat added to the message after MIME conversion.  Once that 33% is taken into account, we will exceed the 10MB Max Request Length limitation.  The iPhone will continue to try and send the message until it is removed from the device. 

To resolve this issue with iOS devices, we typically recommend increasing the Maximum Request Length parameter on the web.config file for ActiveSync on the Client Access Server(s).   
  • On the CAS servers, browse to the web.config file (under the ClientAccess\Sync folder)
  • Open the web.config file
  • Modify the <httpRuntime maxRequestLength=”10240″/> parameter to a higher value to something higher, such as 15360 (15MB).
  • Save the updated web.config file
  • Restart IIS (IISRESET)
That's it.  Naturally if a larger value is needed then just follow the same steps to increase the value that is required.  We don't recommend getting too carried away with this setting.  Common recommendations are 15-20MB... and usually no higher than 50MB.