Activesync troubleshooting                  architecture      connectivity                  troubleshooting   performance
Activesync - architectureSecurity• SSL for encryption and server ID validation• AD credentials or client certificates for ...
Activesync - architectureSecurity• SSL for encryption and server ID validation• AD credentials or client certificates for ...
Activesync – architecture -ABQ                                                                                            ...
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ - Block
Activesync – architecture -ABQ   a   c                                 t   pABQ – BlockIIS logs - Provisioning       V0   ...
Activesync – architecture -ABQ                                              a    c                                        ...
Activesync – architecture -ABQ   a   c                                 t   pABQ – Block
Activesync – architecture -ABQ                                                                                            ...
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ                                                                a   c                       ...
Activesync – architecture -ABQ                     a   c                                                   t   pABQ – Quar...
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ   a   c                                 t   pABQ – Quarantine
Activesync – architecture -ABQ             a   c                                           t   pABQ – Limitations•   User ...
Activesync - architecture                                                a   c                                            ...
Activesync - architecture   a   c                            t   pISAPI
Activesync - architectureInternet facing CAS- [internal site CAS]- XSO RPC MBX                        architecture      co...
Activesync - architectureInternet facing CAS- [internal site CAS]- XSO RPC MBX                        architecture      co...
Activesync - architecturePartnership                   architecture      connectivity                   troubleshooting   ...
Activesync - architecturePartnership                   architecture      connectivity                   troubleshooting   ...
Activesync - connectivityAutodiscover                   architecture      connectivity                   troubleshooting  ...
Activesync - connectivityDirect Push                   architecture      connectivity                   troubleshooting   ...
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   p
Activesync - connectivity   a   c                            t   pAffinity
Exchange ActiveSync Common Status Codes                Ping Command Status        Value   Meaning        1       The heart...
Exchange ActiveSync Common Status Codes                 Sync Command Status       Value   Meaning       1       Success.  ...
Exchange ActiveSync Common Status Codes                Search Command Status        Value   Meaning        1       Success...
Exchange ActiveSync Common Status Codes                FolderSync Command Status      Value   Meaning      1       Success...
Example of PING Server Response
Activesync - troubleshootingScoping questions:• Is the device reaching the Internet facing CAS?• Are all mobile devices af...
Activesync - troubleshootingTroubleshooting service•   the browser testhttps://CAS.contoso.com/microsoft-server-activesync...
Activesync - troubleshootinghttps://www.testexchangeconnectivity.comTest-ActiveSyncConnectivityEvent logs (Source: MSExcha...
https://www.testexchangeconnectivity.com
Test-ActiveSyncConnectivity cmdlet
Event Log Example
W3SVC Log Example                                                                     _Fid:10_Ty:Em_Filt3_S t:S_Sk:2063964...
W3SVC Log Breakdown - Elements  Letter       Element  identifier   name           Definition                           Pos...
W3SVC Log Breakdown - Elements St     Sync type      The type of synchronization thats being performed.                 Va...
W3SVC Log Breakdown - Elements Ssp    SharePoint         The number of files that were accessed from Windows             P...
W3SVC Log Breakdown - Elements  Oof        OOf action        The action that is performed on the Out of      Value Meaning...
W3SVC Log Breakdown - Elements  Pfs     PerFolderStatus  BR      BodyRequested  BPR     BodyPartRequested  LdapC   LdapCou...
W3SVC Log Breakdown - Elements    DevAgent    DeviceInfoUserAgent    Rto         RequestTimedOut    Erq         EmptyReque...
W3SVC Log Breakdown - Elements    RR         NumberOfRecipientsToResolve    Fb         "Fb"=AvailabilityRequested    Ct   ...
W3SVC Log Example                                                                     _Fid:10_Ty:Em_Filt3_S t:S_Sk:2063964...
W3SVC Log Example Breakdown           Server Stats                                               Adds           6Protocol ...
W3SVC Log Sample – Break it Down!   Example Ping command:   &Log=V120_Hb780_S1
W3SVC Log – Too Easy! Protocol Version 12 Heartbeat Interval 780 sec (13min) Status 1 (Success)
Log Parser Query and Results
Export-ActiveSyncLog Example
Export-ActiveSyncLog Example
Get-ActiveSyncDevice cmdlet
EAS Mailbox Logging         http://msexchangeteam.com/archive/2007/05/30/439568.aspx
EAS Mailbox Logging
EAS Mailbox Logging
EAS Mailbox Logging
EAS Mailbox Logging – WP7Log Entry: 70-----------------RequestTime :10/20/2011 11:00:19Identifier :70F0FE13
EAS Mailbox Logging – WP7MS-ASProtocolVersion: 14.1
EAS Mailbox Logging – WP7<Sync xmlns="AirSync:">       <HeartbeatInterval>1380</HeartbeatInterval></Sync>WasPending :[Resp...
EAS Mailbox Logging – WP7ResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1                             <SyncKey>26...
EAS Mailbox Logging – WP7<Sync xmlns="AirSync:">      <HeartbeatInterval>1380</HeartbeatInterval>      <Partial/></Sync>
EAS Mailbox Logging - iPhoneLog Entry: 61-----------------RequestTime :10/20/2011 12:29:45Identifier :6E3B9610WasPending :...
EAS Mailbox Logging - iPhoneResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1        <Status>2</Status>           ...
EAS Mailbox Logging - iPhone Log Entry: 62-----------------RequestTime :10/20/2011 12:31:01                      <Collecti...
EAS Mailbox Logging - iPhoneResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1                             <SyncKey...
EAS Mailbox Logging - iPhone Log Entry: 63-----------------RequestTime :10/20/2011 12:31:01Identifier :3BB1439B           ...
EAS Mailbox Logging - iPhoneResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1ResponseBody :<?xml version="1.0" enc...
EAS Mailbox Logging – iPhone ???        <SyncKey>644101135</SyncKey>
EAS Mailbox Logging – iPhone ???</Sync>SyncCommand_GenerateResponsesXmlNode_AddChange_ConvertServerToClientObject_Exceptio...
Log Entry: 69-----------------RequestTime :10/20/2011 12:49:23ServerName :E2K10CHAssemblyVersion :14.01.0325.000Identifier...
EAS Mailbox Logging - iPhone Log Entry: 70-----------------RequestTime :10/20/2011 13:01:53Identifier :24B088EB           ...
EAS Mailbox Logging - iPhoneLog Entry: 71-----------------RequestTime :10/20/2011 13:15:21Identifier :47C28128            ...
EXTRA
http://blogs.technet.com/b/exchange/archive/2007/09/17/3403937.aspx
appPoolId="MSExchangeSyncAppPool"statusCode="401.3"triggerStatusCode="401.3"timeTaken="0"
">C:Program FilesMicrosoftExchange ServerV14ClientAccesssyncdefault.eas<FILE_CACHE_ACCESS_START
<Data Name="ContextId">{00000000-0000-0000-CB00-0080000000F5}</Data><Data Name="Successful">false</Data><Data Name="FileFr...
Activesync - performanceThrottling•   EASMaxConcurrency             : 10•   EASPercentTimeInAD            :•   EASPercentT...
Activesync - performance                                                                                                  ...
Activesync - performanceLog Parser Studio#demo                    architecture      connectivity                    troubl...
Performance Monitor                                                   a                                                   ...
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Exchange Active Sync Troubleshooting
Upcoming SlideShare
Loading in …5
×

Exchange Active Sync Troubleshooting

21,080 views
20,781 views

Published on

Exchange 2010 Active Sync Troubleshooting

Published in: Education, News & Politics
0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
21,080
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
411
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide
  • architecture tidbits and connectivity discussion to ensure the troubleshooting portion is well digestedwon’t be going into extreme depth, but there are some great blogs on Exchange API spottinghttp://blogs.msdn.com/b/exchangedev/archive/2011/08/19/provisioning-policies-remote-wipe-and-abq-in-exchange-activesync.aspxhttp://blogs.msdn.com/b/exchangedev/archive/2011/07/29/working-with-meeting-responses-in-exchange-activesync.aspxhttp://blogs.msdn.com/b/exchangedev/archive/2011/07/22/working-with-meeting-requests-in-exchange-activesync.aspxhttp://blogs.msdn.com/b/exchangedev/archive/2011/07/08/autodiscover-for-exchange-activesync-developers.aspx
  • #mention SSL version and cipher strength#auth – password is saved, mailbox policy will help determine pin complexity for device login-client cert can eliminate need to change password on the device and also control what devices can be used#mailbox policies – wiki updated by community and individual vendors to announce what policies are supported#recommended RIM put their supported mailbox policies herehttp://en.wikipedia.org/wiki/Comparison_of_Exchange_ActiveSync_Clientshttp://social.technet.microsoft.com/wiki/contents/articles/exchange-activesync-client-comparison-table.aspx#Remote wipe-device needs to connect successfully in order to wipe-mention sandbox behavior in Win8 CSP-From AD canonicalName is what we use for wiping
  • ABQ + remote wipewhat should be done first? block the id or wipe the devicewhat happens when unfortunately the -Characteristic option only accepts as possible entries “DeviceType or DeviceModel”
  • When you go to this portion of the ECP as an Exchange administrator you can specify the default Activesync connection settings by selecting the Edit link.From here I’ve set the default Activesync settings for the Organization to disabled [blocked].  All new users and all devices will be blocked.  Even current users will be blocked.  The only exception is migrated users who already have mobile device partnerships from Exchange 2003 or Exchange 2007 mailboxes.  By default they have a 7 day grace period before those devices then become blocked.  There are ways to deal with them however...Set-ActiveSyncOrganizationSettings
  • Custom message:-phone number?-published Internet site?-nastygram?
  • The actual experience from a mobile deviceIt appears that the device configuration is successful.  After entering all the right server and user information required [depending on Autodiscover and the mobile device attempting to provision], it seems the device is ready to sync, however no data is synchronized.  This makes sense, because if the device is approved later, the user doesn’t need to re-enter all that information again.  Here’s sample screenshots from an iPhone running IOS 4.01
  • Folder hierarchy
  • No Calendar info
  • No Contact info
  • If anything further is attempted to synchronize, you get this error:
  • On the CAS, we find in the IIS logs that the initial provisioning was completed successfully, just far enough to get all the device and user information needed to allow an administrator to allow that device for that user if wanted.  No calendar data or contact data is synced. No mailbox items whatsoever.
  • now we get blocked, but still have 200 HTTP status success
  • Telling the device user:From OWA or Outlook or another client, the user gets an email letting them know their device has been blocked.  A custom message can be configured here to detail the process blocked users should follow in their organization.
  • First, no email is sent to the administrators configured above that a device was blocked.  Depending on the custom message the user receives in their regular mail client, they need to initiate contact.  Once they do, creating a personal exemption is tedious if you don’t like Powershell
  • received 1 message in the Inbox indicating it was quarantined with the same custom message configured from above.  The difference between quarantine and block is that I can create calendar and contact items on my mobile device under the account I’ve attempted to provision and these items are indeed synchronized to the server 1-way.  This doesn’t seem to be a security concern.  However, the folder hierarchy of the mailbox is also synchronized to the device - this could inadvertently reveal sensitive information such as project codenames or whatever people name their folders.
  • received 1 message in the Inbox indicating it was quarantined with the same custom message configured from above.  The difference between quarantine and block is that I can create calendar and contact items on my mobile device under the account I’ve attempted to provision and these items are indeed synchronized to the server 1-way.  This doesn’t seem to be a security concern.  However, the folder hierarchy of the mailbox is also synchronized to the device - this could inadvertently reveal sensitive information such as project codenames or whatever people name their folders.
  • After a period of time that relied on the DiscoveryMailbox, here’s the 1 message that is synced to the device.
  • GAL search fails still
  • Folder Hierarchy revealed, but not unread message count.
  • Quarantine Device calendar
  • Actual Calendar
  • Quarantined Device Contacts
  • Actual Contacts
  • The real difference is how much easier it is to allow this device for full access or to completely block.  Here’s the message that’s sent to administrators that contains information about how the device applies the default Activesync policy, the device user agent and a link that takes the administrator directly to the management UI in the Exchange Control Panel where they can allow or block the device.
  • simple ECP management
  • You can also choose to create a new device rule from here allowing any future devices like this or blocking the rest.
  • user agent - RFCshttp://www.w3.org/Protocols/rfc2616/rfc2616-sec14.htmlhttp://tools.ietf.org/html/rfc2616#section-14.43 [SHOULD, but don’t have to]user agent – how to block if it is givenIIS 7.x URL rewrite to block the user agent from each MSAS virtual directoryhttp://learn.iis.net/page.aspx/803/using-custom-rewrite-providers-with-url-rewrite-moduleExchange 2010 sp2 ru2 includes a fix to ensure user agent is updatedTMG/UAG signature to block the Touchdown user agent for OWA path rulecustom ISAPhttp://blogs.technet.com/b/exchange/archive/2008/09/05/3406212.aspx Understanding Mobility – mainly ABQhttp://technet.microsoft.com/en-us/library/ff959225.aspx#controllingNew-ActiveSyncDeviceAccessRulehttp://technet.microsoft.com/en-us/library/dd876923.aspx
  • Airsync Protocol versions2.x = Exchange 200312.0 = Exchange 2007 RTM12.1 = Exchange 2007 SP114.x = Exchange 2010 +open specificationsAll of the protocol documents describing this protocol in detail can be found on Microsoft’s Open Specifications site. Underneath the Exchange Server Protocols section, one will find every document describing this protocol to begin with [MS-AS (AS denoting ActiveSync). All of the documents in question are as follows:[MS-ASAIRS].pdf[MS-ASCAL].pdf[MS-ASCMD].pdf[MS-ASCNTC].pdf[MS-ASCON].pdf[MS-ASDOC].pdf[MS-ASDTYPE].pdf[MS-ASEMAIL].pdf[MS-ASHTTP].pdf[MS-ASMS].pdf[MS-ASNOTE].pdf[MS-ASPROV].pdf[MS-ASTASK].pdf[MS-ASWBXML].pdf
  • Outlook profile needs to be online mode not cached-E2k7 is different than E2k3 which was Root\\non_IPM_Subtree\\Microsoft-Server-Activesync\\&lt;deviceID&gt;-in Exchange 2010, partnership information located in same place in MBX but also located in AD leaf under user object
  • Outlook profile needs to be online mode not cached-E2k7 is different than E2k3 which was Root\\non_IPM_Subtree\\Microsoft-Server-Activesync\\&lt;deviceID&gt;-in Exchange 2010, partnership information located in same place in MBX but also located in AD leaf under user object
  • 451 redirect when mailbox moves cross site or upgraded from E2k7 to E2k10 if device claims 12.1 AS protocol version.http://blogs.technet.com/b/exchange/archive/2009/12/08/3408985.aspx
  • http://technet.microsoft.com/en-us/library/aa997252.aspx
  • Time = 0
  • Time = 0
  • Time = 0
  • Time = 0
  • Time = 0
  • Time = 0
  • Time = 0
  • OverviewMaintaining a connection, thus, is entirely the client’s responsibility. The client sets up the connection, chooses the appropriate heart beat timer, issues the periodic commands required to keep the connection open, and tears down and re-establishes the connection if and when it deems necessary.The configuration of this on the server and device end will be covered in the configuration section later in this documentation.At the highest level, the design works by the client establishing an HTTP connection with the server, and preventing it from being torn down by periodically sending traffic on it. The server uses this connection to issue notifications to the client.More specifically: The client establishes a connection with the server by issuing an HTTP AirSync PING command.The client optionally informs the server of the list of folders {F} that it expects to receive notifications on.Based on operator network requirements, the client chooses an appropriate heartbeat interval h that will ensure that the connection is not torn down. If no changes occur within h minutes, the server returns OK and the client reissues its original request, thereby keeping the connection open.When changes occur the server tells the client which folders changed, and the client syncs them The contract between the server and the client is, thus: “Inform me whenever changes occur on folders {F} in the next h minutes”
  • Here’s a great slide deck from Andrew Ehrensing:http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/EXL307http://media.ch9.ms/teched/na/2011/ppt/EXL307.pptxauthorization header is base64 encoded – easlily decrypted to reveal username/password treat with care!
  • Server Response Status Codes:Server informs the device that there is mail in specific folder(s). Device then syncs only those folders, (though it may choose to sync others as well). The status code is used to indicate success, failure, timeout and other error conditions.HTTP 200 OKContent-Type: ms.wbxmlPragma: no-cache &lt;Status&gt; 2 &lt;\\Status&gt;&lt;Folders&gt;&lt;Folder&gt; 1234 &lt;/Folder&gt;&lt;/Folders&gt;
  • Some of the cases where we would get a status code error 2 are: Invalid Store name (anything other than GAL) Empty query string Invalid Range, example: (without a zero based index, exceeding range max value of 9999) Exceeding the search query string max length of 256 characters
  • Taking another look, we see that the Server responds to the device stating there are changes in Folder 1234
  • ExMon on the MBX server of the person having a problemhttp://technet.microsoft.com/en-us/library/bb508855(v=EXCHG.65).aspx#mention caveat with latest version Version: 14.2.247.5 Date published: 12/5/2011#run from command line if crashing but don’t start it in the directory the executable is in#for ex. c:\\&gt; c:\\exmon\\exmon.exe userxyz.etlOWA breadcrumbstail powershell commandpoint device internally thru wifi to CAS fqdnget-logonstatistics – doesn’t work for EAS, but does work for MAPI, and EWS in E2k10HOSTs file?Current issues with Microsoft Exchange ActiveSync and third-party deviceshttp://support.microsoft.com/kb/2563324
  • Based on this, we see that ISA cannot authenticate the device with 403 Access is Denied. This is because this device type is sending the appended / after the Microsoft-Server-ActiveSync and the ISA server publishing rule path does not include the * after the trailing /Microsoft-Server-ActiveSync
  • Example of Successful Test using cmdlet
  • Example of Mailbox Server being too busy to accept the request. This could potentially be due to RPC Requests building up on the Mailbox Server. RPC Request Maximum is 500 for Exchange 2007 and 2010.This value should not average above 70.If the RPC Requests are climbing on the mailbox server, some questions to ask may be… Are there any iphone 4.0 devices (801.293) or is this mailbox server Exchange 2010 SP1 and do I have Outlook 2003 client connecting to it for Public Folders?
  • W3SVC Log example of WP7 syncing mail and calendar items
  • Now Can we break this down based on the elements we just reviewed???See next slide for details of breakdown
  • Break down of the highlighted elements earlier 
  • Break this down. What does this mean?See next slide for details…
  • Example of Log Parser query and output
  • Example of Export-ActiveSyncLogcmdlet and output
  • The Users provides the devices, users, hits and sync requests for various mailbox itemsThe Hourly CSV shows unique devices and sync requests per hourThe Policy Compliance provides which devices are compliantThe Servers show which servers the device is connecting toThe StatusCodes show the number of times various HTTP codes were returnedThe UserAgents provides the User Agent and number of hits for each User AgentNOTE: The Users CSV Contains much more data, however unlike the Log parser, we do not have the User Agent field next to the device, therefore we do not know which User Agent is causing the behavior from this log. The UserAgent.csv is available, however it only contains the User Agents syncing to the Exchange server
  • Get-ActiveSyncDevicecmdlet and the output; We can now see that test-apple has a device user agent of 808.7
  • Example Mailbox logging for WP7:Here is a breakdown of the above:- Log Entry #- Request Time that the device request was madeExchange CAS ServerExchange Version (14.01.x) we see this is Exchange 2010 SP1Identifier is important and identifies the sync session of the device. It’s possible that other logs will occur, and we would then see a log with the same identifier that contains the Server response
  • Example Mailbox logging for WP7:Here is a breakdown of the above:RequestHeader contains the device sync information such as Command (in this case, it is Sync); DeviceID, DeviceType, Language, etc…And we see MS-ASProtocolVersion which is AirSync 14.1
  • Example Mailbox logging for WP7:Here is a breakdown of the above:Check out the heartbeat interval and hanging sync We see the RequestBody which contains the xml version and Sync body.The Sync Body contains the Collections which is the Collection of Collection ID and SyncKey along with WindowSize for each.The CollectionID identifies the folder attempting to be synchronizedThe HeartbeatInterval specifies the time in Seconds the device would like to keep the sync open forWasPending:[Response was pending] -&gt; This identifies that we have sent a sync request with heartbeat for various folders and will wait for the server to respond with changes or not. This can be considered the text that identifies the hanging sync
  • Example Mailbox logging for WP7:Here is a breakdown of the above:And the server now completes the hanging sync by pushing the change directly to the device.In this case, we are Adding CollectionID 5 with a specific identified item as 11, therefore the ServerID 5:11 is the Folder:Item being added.And it finishes with the Response Time.The way to identify the Server AirSync traffic compared to the Device AirSync traffic is that it begins with a Server Response Header.
  • Now the device completing another Partial hanging sync for just the Collection (Folder) it previously pushed changes forWe can identify the Partial Sync by the XML tag as seen above.
  • Now the iPhone… this is the difference of when an iphone syncing new changes from the server… the next few slides show the ping with Was Pending… then the server responding with Status 2 – Changes… then the device Getting Estimate, the server responding and then the device fetching the changes and the server responding with the additions
  • Server responds stating there are changes to sync (Folder 5)In this case, Folder 5 is the same as our CollectionID 5 seen in the earlier slides
  • Device then requests the changes for CollectionID 5
  • The Server responds with what changes are available to Sync. In this case, we can see that The change is ServerID 5.10
  • And finally, the phone Fetches (using cmd=sync) ServerID 5:10 (specific item in folder 5)
  • And the Server responds with a successful sync (or fetch from iphone in this case) and the item is successfully synced to the device.
  • Here is a common exception you will see in logs when syncing with the iPhoneThis is the beginning of the request, see next slide…
  • Then this happens… and the device continues to send a new sync request like nothing happened. It’s common; It seems we are attempting to find and sync something that has already been synchronized from the server.
  • The next few logs show how the iPhone increases, then decreases the heartbeat interval during the ping attempts to the server. And in addition, the iphone is not receiving any response from the server once the heartbeat is reached.This could indicate a potential problem with the device sync request or the server not being able to respond to the sync request.Here, we see the HB is 700 seconds
  • The next few logs show how the iPhone increases, then decreases the heartbeat interval during the ping attempts to the server. And in addition, the iphone is not receiving any response from the server once the heartbeat is reached.This could indicate a potential problem with the device sync request or the server not being able to respond to the sync request.No response from the server, yet theiphone increases the HB to 801 seconds
  • And then still no response from the server and the device now lowers the HB to 700 seconds. Unsure what is going on here…Earlier iOS version of iphone would send 3 sync attempts in the HB interval. Androids seem to follow suite with the 3 sync attempts per HB interval. This is always subject to change as you can see from the new behavior above with iPhone 4.3.2The log below in the notes shows the difference between the WP7 and iphone sync attempts.WP7 Log example:----------------- Log Entry: 70----------------- RequestTime : 10/20/2011 11:00:19 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 70F0FE13 RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?Cmd=Sync&amp;DeviceId=DCBDD36BB0199E795529F37F7&amp;DeviceType=WP HTTP/1.1Cache-Control: no-cacheConnection: Keep-AliveContent-Length: 112Content-Type: application/vnd.ms-sync.wbxmlAccept-Language: en-usAuthorization: ********Host: mail.exchlab.comReverse-Via: EXCHLAB-ISAMS-ASProtocolVersion: 14.1X-MS-PolicyKey: 1087184048  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;1771316587&lt;/SyncKey&gt; &lt;CollectionId&gt;1&lt;/CollectionId&gt; &lt;WindowSize&gt;25&lt;/WindowSize&gt; &lt;/Collection&gt; &lt;Collection&gt; &lt;SyncKey&gt;1235562199&lt;/SyncKey&gt; &lt;CollectionId&gt;10&lt;/CollectionId&gt; &lt;/Collection&gt; &lt;Collection&gt; &lt;SyncKey&gt;1625655252&lt;/SyncKey&gt; &lt;CollectionId&gt;2&lt;/CollectionId&gt; &lt;WindowSize&gt;25&lt;/WindowSize&gt; &lt;/Collection&gt; &lt;Collection&gt; &lt;SyncKey&gt;446359207&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;/Collection&gt; &lt;/Collections&gt; &lt;HeartbeatInterval&gt;1380&lt;/HeartbeatInterval&gt;&lt;/Sync&gt; WasPending : [Response was pending] ResponseHeader : HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1  ResponseBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;268775212&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;Status&gt;1&lt;/Status&gt; &lt;Commands&gt; &lt;Add&gt; &lt;ServerId&gt;5:11&lt;/ServerId&gt; &lt;ApplicationData&gt; &lt;To xmlns=&quot;Email:&quot; bytes=&quot;35&quot;/&gt; &lt;From xmlns=&quot;Email:&quot; bytes=&quot;43&quot;/&gt; &lt;Subject xmlns=&quot;Email:&quot; bytes=&quot;23&quot;/&gt; &lt;DateReceivedxmlns=&quot;Email:&quot;&gt;2011-10-20T15:01:44.212Z&lt;/DateReceived&gt; &lt;DisplayToxmlns=&quot;Email:&quot; bytes=&quot;9&quot;/&gt; &lt;ThreadTopicxmlns=&quot;Email:&quot; bytes=&quot;23&quot;/&gt; &lt;Importance xmlns=&quot;Email:&quot;&gt;1&lt;/Importance&gt; &lt;Read xmlns=&quot;Email:&quot;&gt;0&lt;/Read&gt; &lt;Body=330 bytes/&gt; &lt;MessageClassxmlns=&quot;Email:&quot;&gt;IPM.Note&lt;/MessageClass&gt; &lt;InternetCPIDxmlns=&quot;Email:&quot;&gt;28591&lt;/InternetCPID&gt; &lt;Flag xmlns=&quot;Email:&quot;/&gt; &lt;ContentClassxmlns=&quot;Email:&quot;&gt;urn:content-classes:message&lt;/ContentClass&gt; &lt;NativeBodyTypexmlns=&quot;AirSyncBase:&quot;&gt;2&lt;/NativeBodyType&gt; &lt;ConversationIdxmlns=&quot;Email2:&quot;&gt;C24A58AC863F4BC9902D9149540C7C6D&lt;/ConversationId&gt; &lt;ConversationIndexxmlns=&quot;Email2:&quot;&gt;CC8F392E0C&lt;/ConversationIndex&gt; &lt;Categories xmlns=&quot;Email:&quot;/&gt; &lt;/ApplicationData&gt; &lt;/Add&gt; &lt;/Commands&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; ResponseTime : 10/20/2011 11:01:46  ----------------- Log Entry: 71----------------- RequestTime : 10/20/2011 11:01:51 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 1F6A921A RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?Cmd=Sync&amp;DeviceId=DCBDD36BB0199E795529F37F7&amp;DeviceType=WP HTTP/1.1Cache-Control: no-cacheConnection: Keep-AliveContent-Length: 37Content-Type: application/vnd.ms-sync.wbxmlAccept-Language: en-usAuthorization: ********Host: mail.exchlab.comReverse-Via: EXCHLAB-ISAMS-ASProtocolVersion: 14.1X-MS-PolicyKey: 1087184048  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;268775212&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;/Collection&gt; &lt;/Collections&gt; &lt;HeartbeatInterval&gt;1380&lt;/HeartbeatInterval&gt; &lt;Partial/&gt;&lt;/Sync&gt;  iPhone iOS 4.3.2 (user agent – 808.7)----------------- Log Entry: 61----------------- RequestTime : 10/20/2011 12:29:45 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 6E3B9610 RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Ping HTTP/1.1Connection: Keep-AliveContent-Length: 0Accept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody :   WasPending : [Response was pending] ResponseHeader : HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1  ResponseBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Ping xmlns=&quot;Ping:&quot;&gt; &lt;Status&gt;2&lt;/Status&gt; &lt;Folders&gt; &lt;Folder&gt;5&lt;/Folder&gt; &lt;/Folders&gt;&lt;/Ping&gt; ResponseTime : 10/20/2011 12:30:30  ----------------- Log Entry: 62----------------- RequestTime : 10/20/2011 12:31:01 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 94FB25 RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Sync HTTP/1.1Connection: Keep-AliveContent-Length: 69Content-Type: application/vnd.ms-sync.wbxmlAccept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;1116787565&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;GetChanges/&gt; &lt;WindowSize&gt;25&lt;/WindowSize&gt; &lt;Options&gt; &lt;FilterType&gt;2&lt;/FilterType&gt; &lt;MIMETruncation&gt;1&lt;/MIMETruncation&gt; &lt;MIMESupport&gt;0&lt;/MIMESupport&gt; &lt;BodyPreferencexmlns=&quot;AirSyncBase:&quot;&gt; &lt;Type&gt;1&lt;/Type&gt; &lt;TruncationSize&gt;500&lt;/TruncationSize&gt; &lt;/BodyPreference&gt; &lt;/Options&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; LogicalRequest : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;1116787565&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;GetChanges/&gt; &lt;WindowSize&gt;25&lt;/WindowSize&gt; &lt;Options&gt; &lt;FilterType&gt;2&lt;/FilterType&gt; &lt;MIMETruncation&gt;1&lt;/MIMETruncation&gt; &lt;MIMESupport&gt;0&lt;/MIMESupport&gt; &lt;BodyPreferencexmlns=&quot;AirSyncBase:&quot;&gt; &lt;Type&gt;1&lt;/Type&gt; &lt;TruncationSize&gt;500&lt;/TruncationSize&gt; &lt;/BodyPreference&gt; &lt;/Options&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; AccessState : Allowed AccessStateReason : Global ResponseHeader : HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1  ResponseBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;2657206&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;Status&gt;1&lt;/Status&gt; &lt;Commands&gt; &lt;Add&gt; &lt;ServerId&gt;5:10&lt;/ServerId&gt; &lt;ApplicationData&gt; &lt;To xmlns=&quot;Email:&quot; bytes=&quot;37&quot;/&gt; &lt;From xmlns=&quot;Email:&quot; bytes=&quot;43&quot;/&gt; &lt;Subject xmlns=&quot;Email:&quot; bytes=&quot;83&quot;/&gt; &lt;DateReceivedxmlns=&quot;Email:&quot;&gt;2011-10-20T16:30:26.924Z&lt;/DateReceived&gt; &lt;DisplayToxmlns=&quot;Email:&quot; bytes=&quot;10&quot;/&gt; &lt;ThreadTopicxmlns=&quot;Email:&quot; bytes=&quot;83&quot;/&gt; &lt;Importance xmlns=&quot;Email:&quot;&gt;1&lt;/Importance&gt; &lt;Read xmlns=&quot;Email:&quot;&gt;0&lt;/Read&gt; &lt;Body=46 bytes/&gt; &lt;MessageClassxmlns=&quot;Email:&quot;&gt;IPM.Note&lt;/MessageClass&gt; &lt;InternetCPIDxmlns=&quot;Email:&quot;&gt;28591&lt;/InternetCPID&gt; &lt;Flag xmlns=&quot;Email:&quot;/&gt; &lt;ContentClassxmlns=&quot;Email:&quot;&gt;urn:content-classes:message&lt;/ContentClass&gt; &lt;NativeBodyTypexmlns=&quot;AirSyncBase:&quot;&gt;2&lt;/NativeBodyType&gt; &lt;ConversationIdxmlns=&quot;Email2:&quot;&gt;1C129CFEE3B849428AD64E640C7E6FBE&lt;/ConversationId&gt; &lt;ConversationIndexxmlns=&quot;Email2:&quot;&gt;CC8F459293&lt;/ConversationIndex&gt; &lt;Categories xmlns=&quot;Email:&quot;/&gt; &lt;/ApplicationData&gt; &lt;/Add&gt; &lt;/Commands&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; ResponseTime : 10/20/2011 12:31:01  ----------------- Log Entry: 63----------------- RequestTime : 10/20/2011 12:31:01 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 3BB1439B RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Sync HTTP/1.1Connection: Keep-AliveContent-Length: 75Content-Type: application/vnd.ms-sync.wbxmlAccept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;2657206&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;GetChanges&gt;0&lt;/GetChanges&gt; &lt;Options&gt; &lt;FilterType&gt;2&lt;/FilterType&gt; &lt;MIMESupport&gt;2&lt;/MIMESupport&gt; &lt;BodyPreferencexmlns=&quot;AirSyncBase:&quot;&gt; &lt;Type&gt;4&lt;/Type&gt; &lt;TruncationSize&gt;32768&lt;/TruncationSize&gt; &lt;/BodyPreference&gt; &lt;/Options&gt; &lt;Commands&gt; &lt;Fetch&gt; &lt;ServerId&gt;5:10&lt;/ServerId&gt; &lt;/Fetch&gt; &lt;/Commands&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; LogicalRequest : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;2657206&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;GetChanges&gt;0&lt;/GetChanges&gt; &lt;Options&gt; &lt;FilterType&gt;2&lt;/FilterType&gt; &lt;MIMESupport&gt;2&lt;/MIMESupport&gt; &lt;BodyPreferencexmlns=&quot;AirSyncBase:&quot;&gt; &lt;Type&gt;4&lt;/Type&gt; &lt;TruncationSize&gt;32768&lt;/TruncationSize&gt; &lt;/BodyPreference&gt; &lt;/Options&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; AccessState : Allowed AccessStateReason : Global ResponseHeader : HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1  ResponseBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;530022051&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;Status&gt;1&lt;/Status&gt; &lt;Responses&gt; &lt;Fetch&gt; &lt;ServerId&gt;5:10&lt;/ServerId&gt; &lt;Status&gt;1&lt;/Status&gt; &lt;ApplicationData&gt; &lt;To xmlns=&quot;Email:&quot; bytes=&quot;37&quot;/&gt; &lt;From xmlns=&quot;Email:&quot; bytes=&quot;43&quot;/&gt; &lt;Subject xmlns=&quot;Email:&quot; bytes=&quot;83&quot;/&gt; &lt;DateReceivedxmlns=&quot;Email:&quot;&gt;2011-10-20T16:30:26.924Z&lt;/DateReceived&gt; &lt;DisplayToxmlns=&quot;Email:&quot; bytes=&quot;10&quot;/&gt; &lt;ThreadTopicxmlns=&quot;Email:&quot; bytes=&quot;83&quot;/&gt; &lt;Importance xmlns=&quot;Email:&quot;&gt;1&lt;/Importance&gt; &lt;Read xmlns=&quot;Email:&quot;&gt;0&lt;/Read&gt; &lt;Body=1947 bytes/&gt; &lt;MessageClassxmlns=&quot;Email:&quot;&gt;IPM.Note&lt;/MessageClass&gt; &lt;InternetCPIDxmlns=&quot;Email:&quot;&gt;28591&lt;/InternetCPID&gt; &lt;Flag xmlns=&quot;Email:&quot;/&gt; &lt;ContentClassxmlns=&quot;Email:&quot;&gt;urn:content-classes:message&lt;/ContentClass&gt; &lt;NativeBodyTypexmlns=&quot;AirSyncBase:&quot;&gt;2&lt;/NativeBodyType&gt; &lt;ConversationIdxmlns=&quot;Email2:&quot;&gt;1C129CFEE3B849428AD64E640C7E6FBE&lt;/ConversationId&gt; &lt;ConversationIndexxmlns=&quot;Email2:&quot;&gt;CC8F459293&lt;/ConversationIndex&gt; &lt;Categories xmlns=&quot;Email:&quot;/&gt; &lt;/ApplicationData&gt; &lt;/Fetch&gt; &lt;/Responses&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; ResponseTime : 10/20/2011 12:31:01----------------- Log Entry: 66----------------- RequestTime : 10/20/2011 12:33:45 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 724485E6 RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Ping HTTP/1.1Connection: Keep-AliveContent-Length: 0Accept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody :   AccessState : Allowed AccessStateReason : Global ResponseHeader : HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1  ResponseBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Ping xmlns=&quot;Ping:&quot;&gt; &lt;Status&gt;2&lt;/Status&gt; &lt;Folders&gt; &lt;Folder&gt;5&lt;/Folder&gt; &lt;/Folders&gt;&lt;/Ping&gt; ResponseTime : 10/20/2011 12:33:45  ----------------- Log Entry: 67----------------- RequestTime : 10/20/2011 12:33:46 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : F0088D7 RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Sync HTTP/1.1Connection: Keep-AliveContent-Length: 68Content-Type: application/vnd.ms-sync.wbxmlAccept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;644101135&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;GetChanges/&gt; &lt;WindowSize&gt;25&lt;/WindowSize&gt; &lt;Options&gt; &lt;FilterType&gt;2&lt;/FilterType&gt; &lt;MIMETruncation&gt;1&lt;/MIMETruncation&gt; &lt;MIMESupport&gt;0&lt;/MIMESupport&gt; &lt;BodyPreferencexmlns=&quot;AirSyncBase:&quot;&gt; &lt;Type&gt;1&lt;/Type&gt; &lt;TruncationSize&gt;500&lt;/TruncationSize&gt; &lt;/BodyPreference&gt; &lt;/Options&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; SyncCommand_GenerateResponsesXmlNode_AddChange_ConvertServerToClientObject_Exception : Microsoft.Exchange.AirSync.ChangeTrackingItemRejectedException at Microsoft.Exchange.AirSync.ChangeTrackingFilter.Filter(XmlNodexmlItemRoot, Nullable`1[] oldChangeTrackingInformation) at Microsoft.Exchange.AirSync.SyncCollection.ConvertServerToClientObject(ISyncItemsyncItem, XmlNodeairSyncParentNode, SyncOperationchangeObject, GlobalInfoglobalInfo) at Microsoft.Exchange.AirSync.SyncCollection.&lt;&gt;c__DisplayClassd.&lt;GenerateCommandsXmlNode&gt;b__4(SyncOperationchangeObject) LogicalRequest : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;644101135&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;GetChanges/&gt; &lt;WindowSize&gt;25&lt;/WindowSize&gt; &lt;Options&gt; &lt;FilterType&gt;2&lt;/FilterType&gt; &lt;MIMETruncation&gt;1&lt;/MIMETruncation&gt; &lt;MIMESupport&gt;0&lt;/MIMESupport&gt; &lt;BodyPreferencexmlns=&quot;AirSyncBase:&quot;&gt; &lt;Type&gt;1&lt;/Type&gt; &lt;TruncationSize&gt;500&lt;/TruncationSize&gt; &lt;/BodyPreference&gt; &lt;/Options&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; AccessState : Allowed AccessStateReason : Global ResponseHeader : HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1  ResponseBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Sync xmlns=&quot;AirSync:&quot;&gt; &lt;Collections&gt; &lt;Collection&gt; &lt;SyncKey&gt;644101135&lt;/SyncKey&gt; &lt;CollectionId&gt;5&lt;/CollectionId&gt; &lt;Status&gt;1&lt;/Status&gt; &lt;/Collection&gt; &lt;/Collections&gt;&lt;/Sync&gt; ResponseTime : 10/20/2011 12:33:46  ----------------- Log Entry: 68----------------- RequestTime : 10/20/2011 12:33:57 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : D272FA RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Ping HTTP/1.1Connection: Keep-AliveContent-Length: 0Accept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody :    ----------------- Log Entry: 69----------------- RequestTime : 10/20/2011 12:49:23 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 7FF1CC78 RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Ping HTTP/1.1Connection: Keep-AliveContent-Length: 15Content-Type: application/vnd.ms-sync.wbxmlAccept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Ping xmlns=&quot;Ping:&quot;&gt; &lt;HeartbeatInterval&gt;700&lt;/HeartbeatInterval&gt;&lt;/Ping&gt;  ----------------- Log Entry: 70----------------- RequestTime : 10/20/2011 13:01:53 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 24B088EB RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Ping HTTP/1.1Connection: Keep-AliveContent-Length: 15Content-Type: application/vnd.ms-sync.wbxmlAccept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Ping xmlns=&quot;Ping:&quot;&gt; &lt;HeartbeatInterval&gt;801&lt;/HeartbeatInterval&gt;&lt;/Ping&gt;  ----------------- Log Entry: 71----------------- RequestTime : 10/20/2011 13:15:21 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 47C28128 RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Ping HTTP/1.1Connection: Keep-AliveContent-Length: 15Content-Type: application/vnd.ms-sync.wbxmlAccept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Ping xmlns=&quot;Ping:&quot;&gt; &lt;HeartbeatInterval&gt;700&lt;/HeartbeatInterval&gt;&lt;/Ping&gt;  ----------------- Log Entry: 72----------------- RequestTime : 10/20/2011 13:28:08 ServerName : E2K10CH AssemblyVersion : 14.01.0325.000 Identifier : 7C6F960C RequestHeader : POST /Microsoft-Server-ActiveSync/default.eas?User=test-apple&amp;DeviceId=Appl889333NP&amp;DeviceType=iPhone&amp;Cmd=Ping HTTP/1.1Connection: Keep-AliveContent-Length: 15Content-Type: application/vnd.ms-sync.wbxmlAccept: */*Accept-Language: en-usAuthorization: ********Host: mail.exchlab.comUser-Agent: Apple-iPhone2C1/808.7Reverse-Via: EXCHLAB-ISAMs-Asprotocolversion: 14.0X-Ms-Policykey: 2891930116  RequestBody : &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;&lt;Ping xmlns=&quot;Ping:&quot;&gt; &lt;HeartbeatInterval&gt;600&lt;/HeartbeatInterval&gt;&lt;/Ping&gt;
  • EXTRA example and output
  • Once the trace has been stopped, the ETL file must be uploaded to Microsoft for review. These files contain code level information in the traces and Microsoft is unable to share this information.
  • This is the best way to capture data using network capture and Exchange ActiveSync… otherwise, the data is all SSL and cannot be read
  • This shows the initial portion of the log from FREB logging; notice the 401.3 and the Application Pool which we are attempting to process the request
  • Event before the Error Event is thrown and we can see that we were accessing default.eas (Sync Directory)
  • Based on this data, we see that there is a problem with accessing the default.eas &lt;Sync Directory&gt;; there seems to be an underlying permissions issue there 
  • New in sp1 – we delay instead of reject – better experience for the device userhttp://msexchangeteam.com/archive/2010/08/27/456040.aspx
  • with Exchange 2010 we started storing the Activesync device partnerships in AD under the user object [which is why we have the new EAS throttling policies EASMaxDevices and EASMaxDeviceDeletesPerMonth by the way]. Sooo, we can use other AD tools instead of just powershell commands to get to this information.  Here’s an example getting just the deviceID combined with the user DN, last logon from the device, when the partnership was created, and the useragent of the device…
  • http://blogs.technet.com/b/exchange/archive/2012/03/07/introducing-log-parser-studio.aspx
  • On Mailbox: http://technet.microsoft.com/en-us/library/bb201689(EXCHG.80).aspxFor Mailbox, see http://technet.microsoft.com/en-us/library/ff367871.aspx Exchange 2007: On CAS: http://technet.microsoft.com/en-us/library/bb201674(EXCHG.80).aspxFor CAS: http://technet.microsoft.com/en-us/library/ff367877.aspxOne great example of what you might run into is where all the RPC Requests have been consumed on the mailbox server and the Server is too busy to receive any new RPC traffic. For Exchange 2007 and 2010, the Maximum RPC Requests is 500 therefore no Exchange ActiveSync traffic will be able to get through if that threshold is being reached.The iPhone 4.0 exposed this and requests continued to build up on the server until the limit was reached. There are other issues that may cause this behavior as well, such as in .NET if the handle is not released after making a RPC Operation to Public Folders. See http://support.microsoft.com/default.aspx?scid=kb;EN-US;2535105
  • Questions?calcheckIIS log parsing
  • Exchange Active Sync Troubleshooting

    1. 1. Activesync troubleshooting architecture connectivity troubleshooting performance
    2. 2. Activesync - architectureSecurity• SSL for encryption and server ID validation• AD credentials or client certificates for authentication• Activesync Mailbox policies• Remote Wipe architecture connectivity troubleshooting performance
    3. 3. Activesync - architectureSecurity• SSL for encryption and server ID validation• AD credentials or client certificates for authentication• Activesync Mailbox policies• Remote Wipe architecture connectivity• Allow/Block/Quarantine• Throttling troubleshooting performance
    4. 4. Activesync – architecture -ABQ a c t pLogic Flow• Is the mobile device authenticated? If not, challenge the mobile device for the correct credentials. Otherwise, go on to the next step.• Is Exchange ActiveSync enabled for the current user? If not, return an "access restricted" error to the device. Otherwise, go on to the next step.• Are the mobile policy enforcement criteria met by the current mobile device? If not, block access. Otherwise, go on to the next step.• Is this mobile device blocked by a personal exemption for the user? If so, block access. Otherwise, go on to the next step.• Is this mobile device allowed by a personal exemption for the user? If so, grant full access. Otherwise, go on to the next step.• Is this mobile device blocked by a device access rule? If so, block access. Otherwise, go on to the next step.• Is this mobile device quarantined by a device access rule? If so, quarantine the device. Otherwise, go on to the next step.• Is this mobile device allowed by a device access rule? If so, grant full access. Otherwise, go on to the next step.• Apply the default access state per the Exchange ActiveSync organizational settings. This grants access, blocks access, or quarantines the current device, depending on the organizational settings.
    5. 5. Activesync – architecture -ABQ a c t pABQ - Block
    6. 6. Activesync – architecture -ABQ a c t pABQ - Block
    7. 7. Activesync – architecture -ABQ a c t pABQ - Block
    8. 8. Activesync – architecture -ABQ a c t pABQ - Block
    9. 9. Activesync – architecture -ABQ a c t pABQ - Block
    10. 10. Activesync – architecture -ABQ a c t pABQ - Block
    11. 11. Activesync – architecture -ABQ a c t pABQ - Block
    12. 12. Activesync – architecture -ABQ a c t pABQ - Block
    13. 13. Activesync – architecture -ABQ a c t pABQ - Block
    14. 14. Activesync – architecture -ABQ a c t pABQ – BlockIIS logs - Provisioning V0 200
    15. 15. Activesync – architecture -ABQ a c t pABQ – BlockIIS logs - Attempted Foldersync Error:DeviceIsBlockedForThisUser_As:BlockedG 200
    16. 16. Activesync – architecture -ABQ a c t pABQ – Block
    17. 17. Activesync – architecture -ABQ a c t pABQ – Block - Cons• Telling the Admins• No auto email• Can only allow the device by using PowershellGet-ActiveSyncDevice -mailbox ceo | where{$_.devicemodel -eq "iPhone"} | Set-CASMailbox -id CEO -ActiveSyncAllowedDeviceIDs ($_.DeviceId)
    18. 18. Activesync – architecture -ABQ a c t pABQ – Quarantine
    19. 19. Activesync – architecture -ABQ a c t pABQ – Quarantine• Account seems to sync fine• At first nothing is synchronized• GAL search fails• No calendar or contact information synced to device from mailbox• After the discovery process complete, the quarantine message is delivered to the device
    20. 20. Activesync – architecture -ABQ a c t pABQ – QuarantineIIS logs - Discovery As:DeviceDiscoveryG 200
    21. 21. Activesync – architecture -ABQ a c t pABQ – Quarantine
    22. 22. Activesync – architecture -ABQ a c t pABQ – Quarantine
    23. 23. Activesync – architecture -ABQ a c t pABQ – Quarantine
    24. 24. Activesync – architecture -ABQ a c t pABQ – Quarantine
    25. 25. Activesync – architecture -ABQ a c t pABQ – Quarantine
    26. 26. Activesync – architecture -ABQ a c t pABQ – Quarantine
    27. 27. Activesync – architecture -ABQ a c t pABQ – Quarantine
    28. 28. Activesync – architecture -ABQ a c t pABQ – Quarantine
    29. 29. Activesync – architecture -ABQ a c t pABQ – Quarantine
    30. 30. Activesync – architecture -ABQ a c t pABQ – Quarantine
    31. 31. Activesync – architecture -ABQ a c t pABQ – Quarantine
    32. 32. Activesync – architecture -ABQ a c t pABQ – Limitations• User Agent• Zero day exploits• Firmware level agnostic• ISA / TMG / other firewall solutions• manual powershell after the fact
    33. 33. Activesync - architecture a c t pAirsync ProtocolActivesync features available in Exchange 2007 sp3http://msdn.microsoft.com/en-us/library/aa996303(v=EXCHG.80).aspxActivesync feature available in Exchange 2010 sp2http://technet.microsoft.com/en-us/library/bb123484List of Activesync build / features and what mobile devices implementhttp://en.wikipedia.org/wiki/Comparison_of_Exchange_ActiveSync_Clients
    34. 34. Activesync - architecture a c t pISAPI
    35. 35. Activesync - architectureInternet facing CAS- [internal site CAS]- XSO RPC MBX architecture connectivity troubleshooting performance
    36. 36. Activesync - architectureInternet facing CAS- [internal site CAS]- XSO RPC MBX architecture connectivity troubleshooting performance
    37. 37. Activesync - architecturePartnership architecture connectivity troubleshooting performance
    38. 38. Activesync - architecturePartnership architecture connectivity troubleshooting performance
    39. 39. Activesync - connectivityAutodiscover architecture connectivity troubleshooting performance
    40. 40. Activesync - connectivityDirect Push architecture connectivity troubleshooting performance
    41. 41. Activesync - connectivity a c t p
    42. 42. Activesync - connectivity a c t p
    43. 43. Activesync - connectivity a c t p
    44. 44. Activesync - connectivity a c t p
    45. 45. Activesync - connectivity a c t p
    46. 46. Activesync - connectivity a c t p
    47. 47. Activesync - connectivity a c t p
    48. 48. Activesync - connectivity a c t p
    49. 49. Activesync - connectivity a c t pAffinity
    50. 50. Exchange ActiveSync Common Status Codes Ping Command Status Value Meaning 1 The heartbeat interval expired before any changes occurred in the folders being monitored. The client should reissue the Ping command request. 2 Changes occurred in at least one of the folders that were being monitored. The response includes the folders in which these changes have occurred. 3 The client Ping command request did not specify all of the necessary parameters. The client is expected to issue a Ping request that includes both the heartbeat interval and the folder list. 4 There has been a general error in the Ping request issued by the client, which can be caused by poorly formatted WBXML. 5 The heartbeat interval specified by the client is outside the range set by the server administrator. If the specified interval was too great, the returned interval will be the maximum allowable value. If the specified interval was too low, the returned interval will be the minimum allowable value. 6 The Ping command request specified more folders to monitor for changes than is allowed by the limit configured by the server administrator. The response specifies the limit in the MaxFolders element. 7 The client specified a folder that has been moved or deleted or the server that the client has been accessing has been upgraded from Exchange Server 2003 SP1 to SP2. The client should issue a FolderSync request.
    51. 51. Exchange ActiveSync Common Status Codes Sync Command Status Value Meaning 1 Success. 2 Protocol version mismatch. 3 Invalid sync key. 4 Protocol error. 5 Server error. 6 Error in client/server conversion. 7 Conflict matching the client and server object. 8 Object not found. 9 User account may be out of disk space. 10 An error occurred while setting the notification GUID. 11 Device has not been provisioned for notifications yet.
    52. 52. Exchange ActiveSync Common Status Codes Search Command Status Value Meaning 1 Success. 2 Protocol Error. 3 An error on the Exchange server occurred. 4 Bad Link. 5 Access Denied. 6 Not Found. 7 Connection Failed. 8 Too Complex. 9 Index not loaded. 10 TimeOut. 11 NeedToFolderSync. 12 EndOfRetrieveableRangeWarning.
    53. 53. Exchange ActiveSync Common Status Codes FolderSync Command Status Value Meaning 1 Success. 2 A folder with that name already exists. 3 Folder is a special folder. 4 Folder not found. 5 The specified parent folder was not found. 6 An error on the Exchange server occurred. 7 Access denied. 8 The request timed out. 9 Sync key mismatch or invalid sync key. 10 Misformatted request. 11 An unknown error occurred.
    54. 54. Example of PING Server Response
    55. 55. Activesync - troubleshootingScoping questions:• Is the device reaching the Internet facing CAS?• Are all mobile devices affected?• Which CAS do we need to troubleshoot?• Is this an issue that’s well known? architecture connectivity troubleshooting performance
    56. 56. Activesync - troubleshootingTroubleshooting service• the browser testhttps://CAS.contoso.com/microsoft-server-activesync/default.eashttps://mail.contoso.com/microsoft-server- architecture connectivityactivesync/default.eas [501 method not implemented is the expectedresponse] troubleshooting performance
    57. 57. Activesync - troubleshootinghttps://www.testexchangeconnectivity.comTest-ActiveSyncConnectivityEvent logs (Source: MSExchange ActiveSync) architecture connectivityIIS logs (requests to /microsoft-server-activesync)EAS Mailbox device loggingWindows Mobile emulator troubleshooting performanceFailed request tracingPerfmon
    58. 58. https://www.testexchangeconnectivity.com
    59. 59. Test-ActiveSyncConnectivity cmdlet
    60. 60. Event Log Example
    61. 61. W3SVC Log Example _Fid:10_Ty:Em_Filt3_S t:S_Sk:2063964464_SsCmt1_Srv:6a0c0d0s0e0r0A0sd_BR1_BPR0_ _LdapC23_RpcC116_RpcL203_Pk1087184048_S1_As:AllowedG_Mbx:E2K10M.x.ExchLab.loc al_Throttle0_Budget:(
    62. 62. W3SVC Log Breakdown - Elements Letter Element identifier name Definition Possible values V Protocol The protocol version the device is Value Meaning version using to synchronize with the 120 Version 12 Exchange server. 25 Version 2.5 21 Version 2.1 20 Version 2.0 10 Version 1.0 Ty Type The type of folder thats being Value Meaning synchronized. Em E-mail Co Contacts Ca Calendar Ta Tasks Fid Folder ID The ID of the folder thats being Positive Integer synchronized. Fc Folder count The number of folders that are Positive Integer being synchronized. Filt Filter type The data that the user requested. Value Meaning E-mail? Calendar? Tasks? 0 No filter Yes Yes Yes 1 1 day back Yes No No 2 3 days back Yes No No 3 1 week back Yes No No 4 2 weeks back Yes Yes No 5 1 month back Yes Yes No 6 3 months back No Yes No 7 6 months back No Yes No 8 Incomplete No No Yes
    63. 63. W3SVC Log Breakdown - Elements St Sync type The type of synchronization thats being performed. Value Meaning F First sync S Subsequent R Recovery sync I Invalid sync Sk Sync key The actual sync key thats used between the mobile phone and Positive integer the Exchange server. Cli: Client Stores the count of each type of activity from the Client. Output Identifier value statistics is in the form Cli: 0A0C3D1F0E. Meaning A Adds C Changes D Deletes F Fetches E Errors Svr: Server Stores the count of each type of activity from the server. Output Identifier Meaning statistics is in the form Svr:2A0C2D1F1E. A Adds C Changes D Deletes F Fetches E Errors E Number of The number of errors encountered in a request. Positive integer errors Io Items opened The number of items that were opened. This feature hasnt yet Positive integer been implemented. Hb Heartbeat The Heartbeat interval thats used for the PING command. Positive integer interval
    64. 64. W3SVC Log Breakdown - Elements Ssp SharePoint The number of files that were accessed from Windows Positive integer documents SharePoint Services. Sspb SharePoint bytes The number of bytes that were accessed from Windows Positive integer SharePoint Services. Unc UNC files The number of files that were accessed through Windows Positive integer file shares. Uncb UNC bytes The number of bytes that were accessed through Windows Positive integer file shares. Att Attachments The number of attachments that were retrieved. Positive integer Attb Attachment bytes The number of bytes that were retrieved for attachments. Positive integer Pk Policy key The element thats used by the client and server to Not applicable received correlate acknowledgements to a particular policy setting. Pa Policy The element that indicates success if all the policy settings Value Meaning acknowledge were applied correctly. 1Policy was status successfully applied 2Policy was partially applied 3Policy was not applied
    65. 65. W3SVC Log Breakdown - Elements Oof OOf action The action that is performed on the Out of Value Meaning Office status stored on the Exchange GetRetrieves the OOF status and server. message SetSets the OOF status and message UserInfo User The parameter that specifies retrieval of Get information the user information data. action DevModel Device model The device information that is supplied by Possible values include the device manufacturer. manufacturer name, model name, and model number. DevIMEI IMEI The International Mobile Equipment String Identity (IMEI). It is a 15-digit code thats assigned to each device. DevName Device friendly This element stores the users description String name of their device. DevOS Device OS The operating system that is running on String the device. DevLang Device OS The localized language of the device String language operating system. Error Error The error section of the request. String S Status This element returns the status of the String device. R Not Relevant This element returns a count of items that Positive integer have changed but arent relevant to the mobile phone or device.
    66. 66. W3SVC Log Breakdown - Elements Pfs PerFolderStatus BR BodyRequested BPR BodyPartRequested LdapC LdapCount LdapL LdapLatency RpcC RpcCount RpcL RpcLatency E NumErrors Io NumItemsOpened
    67. 67. W3SVC Log Breakdown - Elements DevAgent DeviceInfoUserAgent Rto RequestTimedOut Erq EmptyRequest Ers EmptyResponse Cpo CompletionOffset Fet FinalElapsedTime DevEnaSMS DeviceInfoEnableOutboundSMS DevMoOp DeviceInfoMobileOperator
    68. 68. W3SVC Log Breakdown - Elements RR NumberOfRecipientsToResolve Fb "Fb"=AvailabilityRequested Ct CertificatesRequested Pic PictureRequested As AccessStateAndReason Ssu Ssu Mbx MailboxServer Dc DomainController Throttle ThrottledTime
    69. 69. W3SVC Log Example _Fid:10_Ty:Em_Filt3_S t:S_Sk:2063964464_SsCmt1_Srv:6a0c0d0s0e0r0A0sd_BR1_BPR0 _LdapC23_RpcC116_RpcL203_Pk1087184048_S1_As:AllowedG_Mbx:E2K10M.x.ExchLab.loc al_Throttle0_Budget:(
    70. 70. W3SVC Log Example Breakdown Server Stats Adds 6Protocol Version 14.1 Changes 0Type E-mail Deletes 0Folder ID 10 Soft-Deletes 0Folder Count 5 Errors 0Filter Type 3 days back LDAPCount 23Sync Type Subsequent sync RPCCount 116Sync Key 2063964464 RPCLatency 203Status Success PolicyKey 1087184048BodyRequested 1 Status 1 AccessStateandReason AllowedBodyPartRequested 0 Mailbox E2k10 Throttle 0
    71. 71. W3SVC Log Sample – Break it Down! Example Ping command: &Log=V120_Hb780_S1
    72. 72. W3SVC Log – Too Easy! Protocol Version 12 Heartbeat Interval 780 sec (13min) Status 1 (Success)
    73. 73. Log Parser Query and Results
    74. 74. Export-ActiveSyncLog Example
    75. 75. Export-ActiveSyncLog Example
    76. 76. Get-ActiveSyncDevice cmdlet
    77. 77. EAS Mailbox Logging http://msexchangeteam.com/archive/2007/05/30/439568.aspx
    78. 78. EAS Mailbox Logging
    79. 79. EAS Mailbox Logging
    80. 80. EAS Mailbox Logging
    81. 81. EAS Mailbox Logging – WP7Log Entry: 70-----------------RequestTime :10/20/2011 11:00:19Identifier :70F0FE13
    82. 82. EAS Mailbox Logging – WP7MS-ASProtocolVersion: 14.1
    83. 83. EAS Mailbox Logging – WP7<Sync xmlns="AirSync:"> <HeartbeatInterval>1380</HeartbeatInterval></Sync>WasPending :[Response was pending]
    84. 84. EAS Mailbox Logging – WP7ResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1 <SyncKey>268775212</SyncKey> <CollectionId>5</CollectionId> <Status>1</Status> <Commands> <Add> <ServerId>5:11</ServerId> <ApplicationData>ResponseTime :10/20/2011 11:01:46
    85. 85. EAS Mailbox Logging – WP7<Sync xmlns="AirSync:"> <HeartbeatInterval>1380</HeartbeatInterval> <Partial/></Sync>
    86. 86. EAS Mailbox Logging - iPhoneLog Entry: 61-----------------RequestTime :10/20/2011 12:29:45Identifier :6E3B9610WasPending :[Response was pending]
    87. 87. EAS Mailbox Logging - iPhoneResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1 <Status>2</Status> <Folder>5</Folder>ResponseTime :10/20/2011 12:30:30
    88. 88. EAS Mailbox Logging - iPhone Log Entry: 62-----------------RequestTime :10/20/2011 12:31:01 <CollectionId>5</CollectionId> <GetChanges/>
    89. 89. EAS Mailbox Logging - iPhoneResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1 <SyncKey>2657206</SyncKey> <Add> <ServerId>5:10</ServerId>
    90. 90. EAS Mailbox Logging - iPhone Log Entry: 63-----------------RequestTime :10/20/2011 12:31:01Identifier :3BB1439B Cmd=Sync <SyncKey>2657206</SyncKey> <CollectionId>5</CollectionId><Fetch> <ServerId>5:10</ServerId></Fetch>
    91. 91. EAS Mailbox Logging - iPhoneResponseHeader :HTTP/1.1 200 OKMS-Server-ActiveSync: 14.1ResponseBody :<?xml version="1.0" encoding="utf-8" ?><Sync xmlns="AirSync:"> <Collections> <Collection> <SyncKey>530022051</SyncKey> <CollectionId>5</CollectionId> <Status>1</Status> <Responses> <Fetch> <ServerId>5:10</ServerId> <Status>1</Status>
    92. 92. EAS Mailbox Logging – iPhone ??? <SyncKey>644101135</SyncKey>
    93. 93. EAS Mailbox Logging – iPhone ???</Sync>SyncCommand_GenerateResponsesXmlNode_AddChange_ConvertServerToClientObject_Exception :Microsoft.Exchange.AirSync.ChangeTrackingItemRejectedException at Microsoft.Exchange.AirSync.ChangeTrackingFilter.Filter(XmlNode xmlItemRoot, Nullable`1[] oldChangeTrackingInformation) at Microsoft.Exchange.AirSync.SyncCollection.ConvertServerToClientObject(ISyncItem syncItem, XmlNode airSyncParentNode,SyncOperation changeObject, GlobalInfo globalInfo) at Microsoft.Exchange.AirSync.SyncCollection.<>c__DisplayClassd.<GenerateCommandsXmlNode>b__4(SyncOperationchangeObject) <SyncKey>644101135</SyncKey>
    94. 94. Log Entry: 69-----------------RequestTime :10/20/2011 12:49:23ServerName :E2K10CHAssemblyVersion :14.01.0325.000Identifier :7FF1CC78 & Cmd=PingX-Ms-Policykey: 2891930116<Ping xmlns="Ping:"> <HeartbeatInterval>700</HeartbeatInterval></Ping>
    95. 95. EAS Mailbox Logging - iPhone Log Entry: 70-----------------RequestTime :10/20/2011 13:01:53Identifier :24B088EB &Cmd=PingX-Ms-Policykey: 2891930116<Ping xmlns="Ping:"> <HeartbeatInterval>801</HeartbeatInterval></Ping>
    96. 96. EAS Mailbox Logging - iPhoneLog Entry: 71-----------------RequestTime :10/20/2011 13:15:21Identifier :47C28128 & Cmd=PingX-Ms-Policykey: 2891930116<Ping xmlns="Ping:"> <HeartbeatInterval>700</HeartbeatInterval></Ping>
    97. 97. EXTRA
    98. 98. http://blogs.technet.com/b/exchange/archive/2007/09/17/3403937.aspx
    99. 99. appPoolId="MSExchangeSyncAppPool"statusCode="401.3"triggerStatusCode="401.3"timeTaken="0"
    100. 100. ">C:Program FilesMicrosoftExchange ServerV14ClientAccesssyncdefault.eas<FILE_CACHE_ACCESS_START
    101. 101. <Data Name="ContextId">{00000000-0000-0000-CB00-0080000000F5}</Data><Data Name="Successful">false</Data><Data Name="FileFromCache">false</Data><Data Name="FileAddedToCache">false</Data><Data Name="FileDirmoned">true</Data><Data Name="LastModCheckErrorIgnored">true</Data><Data Name="ErrorCode">2147942405</Data><Data Name="LastModifiedTime"></Data><Opcode>FILE_CACHE_ACCESS_END</Opcode> <freb:Description Data="ErrorCode">Access is denied.(0x80070005)</freb:Description>
    102. 102. Activesync - performanceThrottling• EASMaxConcurrency : 10• EASPercentTimeInAD :• EASPercentTimeInCAS : architecture connectivity• EASPercentTimeInMailboxRPC :• EASMaxDevices : 10• EASMaxDeviceDeletesPerMonth : troubleshooting performance
    103. 103. Activesync - performance a c t pTrending analysis• using AD tools since partnership is kept in leaf objectCsvde –d “cn=users,DC=Contoso,DC=com” –r (objectclass=msexchactivesyncdevice) -ldn,msExchDeviceUserAgent,whenChanged,whenCreated –fc:allExchange2010mobiledevicepartnerships.csv"CN=iPhone§Appl87831W4QY7H,CN=ExchangeActiveSyncDevices,CN=e14MobileTester,CN=Users,DC=Contoso,DC=com",20101111173928.0Z,20101111173948.0Z,Apple-iPhone1C2/802.117"CN=PocketPC§BAD73E6E02156460E800185977C03182,CN=ExchangeActiveSyncDevices,CN=e14manager,CN=Users,DC=Contoso,DC=com",20101231183218.0Z,20101231183326.0Z,MSFT-PPC/5.2.5001"CN=WP§C01D49121ABAFAFD3C72924235668667,CN=ExchangeActiveSyncDevices,CN=wp7user,CN=Users,DC=Contoso,DC=com",20110421115008.0Z,20110421115100.0Z,MSFT-WP/7.0.7390"CN=iPhone§Appl87831W4QY7H,CN=ExchangeActiveSyncDevices,CN=iuser01,CN=Users,DC=Contoso,DC=com",20110426120447.0Z,20110426120505.0Z,Apple-iPhone1C2/803.148…• Compare this to the shell approach. From Management ShellGet-Mailbox alias | Get-ActivesyncDeviceStatistics | ft identity,DeviceType,DeviceModel
    104. 104. Activesync - performanceLog Parser Studio#demo architecture connectivity troubleshooting performance
    105. 105. Performance Monitor a t c p http://technet.microsoft.com/en-us/library/ff367877.aspx http://technet.microsoft.com/en-us/library/ff367871.aspx

    ×