Additionally, Office 365 Exchange Online users receive an error message that resembles the following on an iOS 6.1 or 6.1.1-based device:
The following additional symptoms can occur.
EAS Mailbox logging
When you review an Exchange ActiveSync (EAS) Mailbox log, you may see the following:
RequestHeader :IIS Logs
Accept-Encoding: gzip, deflate
<?xml version="1.0" encoding="utf-8" ?>
Microsoft.Exchange.Data.Storage.WrongObjectTypeException: The object was bound to a wrong
object type. ObjectClass = IPM.Schedule.Meeting.Request, Intended Type =
at Microsoft.Exchange.Data.Storage.ItemBuilder.ItemBind[T](StoreSession session, StoreId
storeId, Schema expectedSchema, MapiMessageCreator mapiMessageCreator, ItemBindOption
itemBindOption, ICollection`1 propertiesToLoad)
at Microsoft.Exchange.Data.Storage.ItemBuilder.ItemBind[T](StoreSession session, StoreId id,
Schema expectedSchema, ICollection`1 propertiesToLoad)
at Microsoft.Exchange.Data.Storage.CalendarItem.Bind(StoreSession session, StoreId id)
mailboxRequestId, ExDateTime instanceId)
HTTP/1.1 200 OK
<?xml version="1.0" encoding="utf-8" ?>
In Exchange Server on-premises installations only, the following text is continually repeated in the Internet Information Services (IIS) log files on the CAS.
2013-02-06 23:41:59 192.168.137.11 POST /Microsoft-Server-ActiveSync/default.eas Userfirstname.lastname@example.org&Note: The Error:WrongObjectTypeException may not be present in all cases.
DeviceId=ApplDMPFXZABDFHW&DeviceType=iPad&Cmd=Sync&Log=[truncated] 443 email@example.com 192.168.137.246
Apple-iPad2C1/1002.141 200 0 0 187
2013-02-06 23:41:59 192.168.137.11 POST /Microsoft-Server-ActiveSync/default.eas Userfirstname.lastname@example.org&
DeviceId=ApplDMPFXZABDFHW&DeviceType=iPad&Cmd=MeetingResponse&Log=[... Error:WrongObjectTypeException …]
443 email@example.com 192.168.137.246 Apple-iPad2C1/1002.141 200 0 0 140
Install the following update rollup:
Apple posts the following article to address the issue.
iOS 6.1: Excess Exchange activity after accepting an exception to recurring calendar event
Apple has also announced the availability of iOS 6.1.2 to address this issue.
If the problem continues, use one of the following methods to work around the issue.
Note: The workarounds below have been modified from the original recommendations. Specifically, the recreation of the partnership and the suggested throttling settings for Exchange ActiveSync have been removed. Analysis found they were insufficient to preserve server performance. The current methods reflect the best options.
Method 1: Use URL Rewrite to block Cmd=MeetingResponseA workaround has been identified that will allow administrators to block the repeating MeetingResponse attempt using either a perimeter device rule or the URL Rewrite Module 2.0 for Internet Information Server 7 and 7.5, for Windows Server 2008 and Windows Server 2008 R2. See the following article from the TechNet Wiki online.
Using URL Rewrite to block certain clients from Exchange
Warning: This solution may not work in some scenarios where a perimeter device, such as some network load balancers, are in use. You should contact the vendor to verify that the solution cannot be implemented on the perimeter device prior to modifying IIS.
Once the URL rewrite is implemented, iOS6.1 and 6.1.1-based devices can sync and receive updates. However, responses to meeting items from the device are rejected by the server. We recommend that users respond to meetings via Outlook Web App (OWA), Microsoft Outlook, or a non-iOS 6.1 or 6.1.1-device.
Method 2: Block iOS 6.1 or 6.1.1 usersYou can block iOS 6.1 and 6.1.1 users by using the Exchange Server 2010 Allow/Block/Quarantine feature. For more information about this feature, see the following Exchange Team blog post:
Also, for updated information about how to use Exchange Management Shell for Allow/Block/Quarantine, see the following Microsoft website:
- Unable to create a profile on the device
- Unable to connect to the server
- Mail issues
- Calendaring issues
- Delays on device/CAS performance
To identify this issue in your organization, you can also use one of the methods in this section. Office365 Exchange Online users can use only the EAS Mailbox logging option and look for repeated instances of the Status 4 response that is noted in the "Symptoms" section.
Method 1: Obtain EAS Mailbox logging for a userTo obtain EAS Mailbox logs, follow the steps in the following article in the Microsoft Knowledge Base:
Method 2: Collect and parse IIS logsCheck for the recurrence pattern of Cmd=Sync and Cmd=MeetingResponse, possibly paired with Error:WrongObjectTypeException, for the iOS 6.1 or 6.1.1 devices. A continuous pattern will indicate that the device user is processing Meeting Requests from the device and encountering the device bug.
You can also use Log Parser Studio to parse by using the following query:
SELECT COUNT(*),MyDeviceId AS DeviceId,TheUserId AS UserId,MajAgent,MinAgent
EXTRACT_VALUE(cs-uri-query,'DeviceId') AS MyDeviceId,
EXTRACT_VALUE(cs-uri-query,'User') AS TheUserId,
TO_INT(SUBSTR(SUBSTR(cs(User-Agent),INDEX_OF (cs(User-Agent), '.'),4),1,3)) AS MinAgent,
TO_INT(SUBSTR(SUBSTR(cs(User-Agent),INDEX_OF (cs(User-Agent), '/'),5),1,4)) AS MajAgent
FROM '[LOGFILEPATH]' WHERE cs-uri-query LIKE '%MeetingResponse%' AND (MajAgent=1002 AND MinAgent<146)
GROUP BY DeviceId,UserId,MajAgent,MinAgent
ORDER BY COUNT(*) DESC