Activesync Error Log
Contents |
Troubleshooting Exchange ActiveSync and reading IIS logs In this article I will try cover my way of troubleshooting Exchange ActiveSync issues from Server side activesync error 500 and client side. Recently I had an issue where users on one
Activesync Error 500 Exchange 2013
of the Exchange 2007 servers "ONLY" weren't able to sync their mobile device. My way of troubleshooting
Activesync Error 1053
flows this way which I will explain in detail: Isolate the issue be for user, device, server or organization wide Testexchangeconnectivity.com and a test mobile device Read IIS
Activesync Error 403
logs and look at the error's if any Confirm Authentication settings on IIS VDir's for CAS and MBX roles Look at CPU utilization for w3wp.exe on all CAS servers Read event logs and filter MSExchange ActiveSync event in 10xx series Confirm ADPermission for internet facing CAS servers on "ms-Exch-EPI-Token-Serialization" Isolate the issue be for user, device, server or exchange activesync error 1016 organization wide This is the primary focus area or we will be going in circles. Let's split this into 4 different scenario and the issue should be isolated to one of these: Issue with one single user only: First thing I would look for is to check the OMA AD property enabled or not. Navigate to Active Directory Users and Computers à Search for the user à Exchange Feature tab à Ideally, if this all set to enable, the attribute "msexchOMAAdminWirelessEnable"will be
- MSFTMarch 19, 201335 0 0 0 Applies to: Exchange 2007, 2010, 2013 Exchange ActiveSync (EAS) mailbox logs are protocol-level logs that show the traffic between Exchange and the EAS device. This is assuming of course, exchange activesync error 1008 that the device actually connects, gets past IIS, and into Exchange code. activesync error codes When troubleshooting EAS issues, this is often the most useful piece of information. Gathering these logs can be quick activesync error 503 if you use PowerShell to do so, versus gathering them via ECP under Options -> Phone -> Mobile Phones. PowerShell Method Enable the logging on the affected mailbox: Set-CASMailbox alias http://msexchangeguru.com/2012/02/01/exchange-activesync/ -ActiveSyncDebugLogging:$true Note: Get-CASMailbox will not show whether ActiveSyncDebugLogging is on or off unless you add the-ActiveSyncDebugLogging parameter. Reproduce whatever issue you're dealing with, then gather the logs: Get-ActiveSyncDeviceStatistics -Mailbox alias -GetMailboxLog:$true -NotificationEmailAddress yourEmailAddress@contoso.com This will output the log to the screen (in 2010 and above), and email a copy of it to your email. Easy! Note that these cmdlets will https://blogs.technet.microsoft.com/jasonsla/2013/03/19/exchange-activesync-mailbox-logging/ work in all versions of Exchange from 2007-2013, however in 2013 we've deprecated Get-ActiveSyncDeviceStatistics in favor of Get-MobileDeviceStatistics, and in 2007 the cmdlets don't actually do anything (see the Exchange 2007 note below). The cmdlet is otherwise the same. By default, these logs will have truncated tags. The data for most tags is removed, and replaced with a tag attribute indicating how many bytes the data contains. For example, the subject of an email may look like this:
Team GFI Top posts Bloggers Contact Menu Like what you see? Subscribe to our blog feed and never miss a post. How to troubleshoot Exchange http://www.gfi.com/blog/how-to-troubleshoot-exchange-activesync-connections/ ActiveSync connections Staff Writer on October 24, 2014 (1 votes, average: 5.00 out of 5) 2 comments In this mobile-first world, your end users can’t live without their smartphones. If they cannot https://justaucguy.wordpress.com/2013/07/13/exchange-activesync-and-diagnostic-logging/ get to email from anywhere at any time, deals could fall through and that just can’t happen. Ensuring that Exchange ActiveSync is working properly on both your Exchange infrastructure and your users’ activesync error myriad mobile devices is one of the most important things you can do. Usually, EAS works perfectly well, so this is not a problem for you. But occasionally, things do fail, so knowing what to look at and how to troubleshoot are critical skills. This article should help get you started. Basics Make sure DNS is properly resolving the autdiscover.example.com name, that the user activesync error 500 is attempting to use valid credentials that aren’t locked out, and that the certificate on the CAS server has not expired. It is amazing how many times sysadmins let a certificate expire, so don’t overlook that! There are actually several things you can check on your CAS, but you can first just check your phone to be sure it still works. True, if you have multiple CAS servers you need to make sure your phone and the affected user’s phone are both being serviced from the same CAS or CAS array. On the server side Ultimately, EAS is provided by your Exchange Client Access Server (CAS) server(s,) so knowing what to look at and where to check on things is key. And since you can reach right out and touch your CAS servers, this is probably the first place to start. Logs Always check the logs to see what they can tell you. Far too many admins make checking logs the last thing they do, rather than the first. Quarantine If you are using EAS Quarantine, check to make sure the device has not been quarantined. It could be t
to comments So. You've got Exchange 2013 now right? CU1? (Why not CU2? … it's out now…) Well, either way you're using Exchange 2013. Now all of your users want to connect their iPhones, Androids, Windows Phone, and BlackBerries to your shiny new server. As you deploy them, 90-99% go perfect. No issues, no complaints…. But then you get a few scattered reports of issues. Well, how do we troubleshoot these issues in Exchange 2013? Let's turn on Diagnostic Logging! But wait…. where is it? It's not in the ‘GUI' or EAC if you will… you need to program this via PowerShell. Of all the things I get complaints about, this is the biggest. Simple features that would be much easier to point, click and change like we did in 5.5, 2000, 2003, 2007 and 2010…. now we need PowerShell. To tell the truth I am a fan of Powershell; just not for cases like this. Turning on Diagnostic Logging for Active Sync Active Sync has two Event Logs you can turn on - Active Sync Requests and Active Sync Configuration. For now we can just turn on the Requests one since we are dealing with the random user issues and not all users. To turn on Diagnostic Logging for Active Sync requests you can first check the current level with: get-eventloglevel "MSExchange ActiveSync\Requests" If this is set to the default level, you will see the following: 0 = Lowest for Event Log levels. Now, depending on your comfort/experience level, you can either set the logging to 5 (high) or 7 (expert). Let's set it to 5 for now: Once we do that we should get some events to look at in the event log like this: In the case of my ActiveSync issue, the account I was using had administrative rights and thus needed the Inherit rights checkbox checked before the first successful sync takes place. After that is done I should see no more Active Sync issues with this particular user. After completing your troubleshooting, remember to reset the event log level to 0 to reduce server load. Just for reference, the following numbers are valid for Event Log Levels: 0 - Lowest 1 - Low 3 - Medium 5 - High 7 - Expert Rate this:Share this:TwitterFacebookLike this:Like Loading... Related Categories: Exchange, Exchange 2013 Comments (0) Trackbacks (0) Leave a comment Trackback No comments yet. No trackbacks yet. Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/C