Quantcast
Channel: Exchange Server 2013 - Mobility and ActiveSync forum
Viewing all articles
Browse latest Browse all 1206

ActiveSync crashes - Exchange 2007

$
0
0

Hi,

Within recent week our mobile devices started to lose connections to the server, in some cases some phones weren't able to connect at all, the others showed that they're connected but the Inboxes weren't getting updated. It appears that for some reason ActiveSync crashes and the only solution to reconnect ActiveSync functionality is to restart the mail server.

Looking through the Event Log, I've noticed an excessive amount of requests from one of the users Android phone trying to receive an attachment which is too large, these requests were being executed every 2-3 seconds. Is it possible that these requests are causing the ActiveSync to crash?

These are the Event Viewer entries, first is the request from the Android and the other two are ActiveSync errors.

Any help would be greatly appreciated.

Request Warning:

An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization.

URL=/Microsoft-Server-ActiveSync/default.eas?Cmd=GetAttachment&AttachmentName=6%3a9254%3a5&User=ysato&DeviceId=androidc1121192633&DeviceType=Android
--- Exception start ---
Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
Exception message: The size of attachment 6:9254:5 is bigger than unlimited, which is the size limit that is defined in the Exchange ActiveSync mailbox policy.
Exception level: 0
HttpStatusCode: 413
AirSyncStatusCode: 0
XmlResponse:
This request does not contain a WBXML response.
Exception stack trace:    at Microsoft.Exchange.AirSync.GetAttachmentCommand.Execute()
   at Microsoft.Exchange.AirSync.Command.WorkerThread()
Inner exception follows...
Exception type: Microsoft.Exchange.AirSync.DataTooLargeException
Exception message: Data size -1 exceeds the configured limit of 10240000.
Exception level: 1
HttpStatusCode: 500
AirSyncStatusCode: 0
XmlResponse:
This request does not contain a WBXML response.
Exception stack trace:    at Microsoft.Exchange.AirSync.AttachmentHelper.GetAttachmentItself(Attachment attachment, Stream outStream, Int32 offset, Int32 count, Int32& total)
   at Microsoft.Exchange.AirSync.AttachmentHelper.GetAttachment(MailboxSession mailboxSession, String attachmentId, Stream outStream, Int32 offset, Int32 count, Unlimited`1 maxAttachmentSize, ItemIdMapping idmapping, Int32& total)
   at Microsoft.Exchange.AirSync.GetAttachmentCommand.Execute()
--- Exception end ---

Error 1014

The Microsoft Exchange ActiveSync process has been shut down Process id: [10796]. This event typically results from a shortage of system memory from overload.  If this event is logged frequently, review the Application log for related events.  The Client Access Server that the Microsoft Exchange ActiveSync service runs on may need to be load balanced to reduce system overload.

Error 1016

Exchange ActiveSync has encountered repeated failures when it tries to access data on Mailbox server [XXXXXXX2.XXXXX.local]. Exchange ActiveSync will temporarily stop making Exchange ActiveSync requests to the Mailbox server. The process will be postponed for [60] seconds. This may be caused if the Mailbox server is overloaded. If this event is frequently logged, review the Application log for other events that could indicate the root cause of performance problems on the Mailbox server specified in the event description.


Viewing all articles
Browse latest Browse all 1206

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>