Being mobile is extremely important these days, as users will most likely be checking their mail on their phone. To insure that your system is mobile friendly across multiple phone OS’s, take the necessary precautions when adding mobile configurations. In some cases iOS 6.1 or 6.1.1 does not work as expected and causes the system to consume excess resources, thus lowering your entire systems speed. If this issue continues it will only create more problems for every user on the system.
This issue happens when a user on an iOS 6.1 or 6.1.1 device begins to sync with Exchange Server 2010. In some cases the user can receive the following error message:
- Cannot Get Mail The connection to the server failed.
The only option for the user is to click OK.
When reviewing the Exchange ActiveSync (EAS) mailbox log, the following message may appear:
- RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=user1@contoso.com&DeviceId=ApplDMPFXZABDFHW&DeviceType= iPad&Cmd=MeetingResponse HTTP/1.1 Connection: keep-alive Content-Length: 55 Content-Type: application/vnd.ms-sync.wbxml Accept: */* Accept-Encoding: gzip, deflate Accept-Language: en-us Authorization: ******** Host: mail.contoso.com User-Agent: Apple-iPad2C1/1002.141 X-MS-PolicyKey: 2429156470 MS-ASProtocolVersion: 14.1 RequestBody : 1 5 5:5 2013-02-06T22:00:00.000Z MeetingResponseCommand_OnExecute_Exception : Microsoft.Exchange.Data.Storage.WrongObjectTypeException: The object was bound to a wrong object type. ObjectClass = IPM.Schedule.Meeting.Request, Intended Type = Microsoft.Exchange.Data.Storage.CalendarItem. at Microsoft.Exchange.Data.Storage.StoreObject.DownCastStoreObject[T]() 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) at Microsoft.Exchange.AirSync.MeetingResponseCommand.GetOccurenceId(StoreObjectId mailboxRequestId, ExDateTime instanceId) at Microsoft.Exchange.AirSync.MeetingResponseCommand.ProcessCommand() at Microsoft.Exchange.AirSync.MeetingResponseCommand.OnExecute() AccessState : Allowed AccessStateReason : Global ResponseHeader : HTTP/1.1 200 OK MS-Server-ActiveSync: 14.2 ResponseBody : 4
And in Exchange server on-premises installations only, the following text is continually repeated in the Internet Information Services (IIS) log files on the Client Access Server (CAS):
- 2013-02-06 23:41:59 192.168.137.11 POST /Microsoft-Server-ActiveSync/default.eas User=user1@contoso.com& DeviceId=ApplDMPFXZABDFHW&DeviceType=iPad&Cmd=Sync&Log=[truncated] 443 user1@exchlab.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 User=user1@contoso.com& DeviceId=ApplDMPFXZABDFHW&DeviceType=iPad&Cmd=MeetingResponse&Log=[... Error:WrongObjectTypeException …] 443 user1@exchlab.com 192.168.137.246 Apple-iPad2C1/1002.141 200 0 0 140
Note: The Error:WrongObjectTypeException may not be present in all cases.
A simple resolution is available that will fix your issues as well as fix the users mobile problems. All you need to do is update the iOS 6.1 or 6.1.1 device to the recently released iOS 6.1.2.
Additionally there is a workaround available for devices that have not undergone the update yet. You should not process Calendar items such as meeting requests on iOS 6.1 or 6.1.1 If the problem continues you can following these steps:
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=MeetingResponse
- This workaround will allow administrators to block the repeating Meeting Response attempt using either a perimeter device rule or the URL Rewrite Method 2.0v for Internet Information Server 7 and 7.5, for Windows Server 2008 and Windows Server 2008 R2.
- Warning: This solution may not work in some scenarios where perimeter devices, such as some network load balancers, are in use. In this case you should contact the vendor to verify if the solution cannot be implemented on the perimeter device prior to modifying IIS.
- Once the URL rewrite is implemented, iOS 6.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 users
- You can block iOS 6.1 and 6.1.1 users by using the Exchange Server 2010 Allow/Block/Quarantine feature. This feature will not fix the problem, but it will resolve your server issues that are present.
In order to avoid these issues, you should alsways check out what devices are supported and if any of these devices have conflicting issues that are present in the current mobile OS platform. To do so, check the manufacturer’s information on any related issues or check the current release notes of your mobile OS. This information is a workaround and not a solution; continue to look for updates or hot-fixes.
The post iOS 6.1 Devices can Cause an Enormous Amount of Data Usage on Exchange 2010 appeared first on Email management, storage and security for business email admins.
