Exchange Email not working after iOS 7 update

See MHCU. It Totally Worked, THANKS!!!

Resetting network settings worked for me too. Thanks mhcu!

Same (or at least a variation) issue for me. Upgraded my iPhone 4S to iOS 7 over the weekend. Accounts seemed to work fine. Now (over the past 48 hours) my Exchange account for work won't sync over any WiFi (or at least the 4 WiFi networks I've tried, which includes the main corporate WiFi) but will sync (send/receive email, sync calendar) over 4G.

I tried resetting network settings without success. Turning off WiFi sort of works, in that the Exchange account will sync over 4G, but as soon as I turn WiFi back on (or re-connect to my WiFi after resetting network settings), I get the Exchange account mail error.

I've contacted our Network IT folks without an answer yet. Their only suggestion was not to upgrade to iOS 7 in the first place, which wasn't tremendously helpful. Any other suggestions that have worked for anyone? Thanks in advance.

Just saw that Apple released an iOS 7 update already (patch for passcode bypass bug, et al, as of 1958 EST, on Sept 26, 2013). My fingers are crossed that this will help with this issue.

On the more likely chance that this update won't fix the exchange/iOS 7 issue, if there are any other suggestions or workaround that folks have found for Exchange/iOS7 connectivity, please keep on sharing them. Much appreciated!

Finished update to iOS 7.0.2. No fix for the Exchange problem, at least for me. Still unable to sync/access exchange email or calendar over WiFi, although 4G works to send email, add new calendar entries, etc.

Tried resetting network settings after update, tried turning off WiFi, etc., no success on my end.

I had the same issue on one of our Exec's Ipad Mini after it got updated to IOS 7.0, Exchange Mail was unable to send mails. What I did that worked for me is removed the Domain address on the Email field. ex. user@apple.com| removed @apple.com after that, my user was able to send mails already. I hope Apple will issue another update to address this bug.

At the University i work at we are having issues too. So far i can replicate it to where every time i add the exchange account it will not work. but if i go to the task manager and close down the email completely and open it back up with the exchange account added it will work like a charm.

(after adding exchange

1.) send a test email (it doesnt work)

2.) double tap home button to get to mulitask manager

3.) close mail completely

4.) open mail back up and send another test (works)

This works for me very time, i have tried 5X times. I hope this works for you. Please let me know if it works or not.

if this doesnt work try to set up your send and outbox in exchange to be pushed.

settings, mail contacts calendars, fetch new data, (exchangeaccounts)

^ set schedule to push

^^Inbox is set by default, now add 'sent' and 'outbox'

Hope this helps!

On Microsoft's recommendation, we have upgraded our CAS servers from SP2 rollup 5R2 to SP3 rollup 2 last night... so far it looks good. The Microsoft rep was able to correlate errors in our IIS activesync logs from IOS7 devices with events in the Application event log. The events look like this:

Log Name: Application

Source: MSExchange Common

Date: 9/25/2013 12:47:56 PM

Event ID: 4999

Task Category: General

Level: Error

Keywords: Classic

User: N/A

Computer: <removed for security>

Description:

Watson report about to be sent for process id: 8512, with parameters: E12, c-RTL-AMD64, 14.02.0328.009, AirSync, M.Exchange.Compliance, M.E.S.C.MessageDigestForNonCryptographicPurposes.HashCore, System.ArgumentOutOfRangeException, 43ba, 14.02.0247.000.

ErrorReportingEnabled: True

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="MSExchange Common" />

<EventID Qualifiers="16388">4999</EventID>

<Level>2</Level>

<Task>1</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-09-25T18:47:56.000000000Z" />

<EventRecordID>8479009</EventRecordID>

<Channel>Application</Channel>

<Computer>REMOVED</Computer>

<Security />

</System>

<EventData>

<Data>8512</Data>

<Data>E12</Data>

<Data>c-RTL-AMD64</Data>

<Data>14.02.0328.009</Data>

<Data>AirSync</Data>

<Data>M.Exchange.Compliance</Data>

<Data>M.E.S.C.MessageDigestForNonCryptographicPurposes.HashCore</Data>

<Data>System.ArgumentOutOfRangeException</Data>

<Data>43ba</Data>

<Data>14.02.0247.000</Data>

<Data>True</Data>

<Data>

</Data>

</EventData>

</Event>

The key points in these events are eventid 4999, the reference to 'AirSync' which indicates an ActiveSync error and the 'ArgumentOutOfRangeException' which seems to be specifically related to the failing IOS7 sync requests.

From parsing the IIS logs, we were seeing thousands of IOS devices stuck doing the 'provision' activesync command. The Microsoft rep said there was a bug on their side and that others had resolved it by upgrading to SP3 rollup 2. Since the upgrade, we are no longer seeing these events being logged. Note that because of the thousands of IOS7 devices attempting to activesync, the activesync process on the CAS servers was generating high CPU load... basicly it was swamped and other non-IOS7 devices were also being impacted.

I want to add that my experience with contacting Apple support was very disappointing... before even hearing the full problem description, the support rep was placing all of the blame on Microsoft. In contrast, the Microsoft support rep was professional and has said nothing disparaging against Apple despite their poor track record with activesync. In my opinion, there is enough blame to be shared between Apple and Microsoft on this one. On Microsoft's part, it appears that there is a bug and kudos to them for having already fixed it in SP3 rollup 2 ...they need to document this in a knowledgebase article which I'm sure they will do when they sufficiently understand the issue. On Apple's part, adding new activesync functionality to actually honour the activesync policy settings from the server is overdue and great to see... you'd think they would have tested this against the most commonly used activesync server and have some advice on supported software levels. In fairness to both Apple and Microsoft, this issue might go unnoticed if you don't have thousands of IOS devices doing activesync against your Exchange environment... we were unable to reproduce it in our test lab.

I've been helped so many times by finding customer solutions posted to forums like this that I felt it important to post this solution... maybe it'll help someone else facing the predicament we've just come through.

Thanks eppNator - easily the most useful response I've seen on this issue. I was seeing the same 4999 errors in our server's Application log, and so have upgraded our servers to SP3 UR2 today. I've already received reports that mail is flowing to user's iPhones again.

all our iPhones and iPads which have been updated to iOS7 do not sync withthe exchange server anymore. As said, before the updatebthe same account was working fime.

Now I found a good workarpund called Samsung Galaxy S3.

sorry, but the exchange accounts are the most important onec for out businesss!

Same issue with my iPhone 5s as I went from a iPhone 4S with no issues. Very frustrating because Exchange emails are so important with work. I tried resetting the network settings, but it didn't work. Strange thing, my iPad 3 pushes the exchange email (wifi only) with no issue. But it's diffidently an iOS 7 / iPhone issue. If I missed anything, please let me know. Send help!!!!

same issue as million others, one thing to get an Android in Apple dress but when exchange doesnt work on any iPhone or iPad send me back to IOS 6 please - come on Apple, why keep hiding

I am using iPad2 and try to log in to Microsoft Outlook Web Access. I am prompted for my password twice every time I try to log in. If I clear cookies and history and log in, my folder list will load. If I clear cookies and history and reset network settings, my inbox will load. In both cases, I cannot open emails, folders, etc. I have tried adding the Exchange account on my iPad, but I can go no further than the 'verifying' screen.

Please help!

Met same thing today after moved users from Exchange 2007 -> 2010 SP3

Seems that when user is moved from 2007 to 2010 Inheritable permissions check box gets cleared.

Our solution was following:

- Open AD Users and Computers,

- In "View" menu check "Advanced Features"

- Open user properties

- Click "Security" Tab

- Click "Advanced"

- Check "Include Inheritable permissions from this object's parent"

- Click OK and OK

After that sync started working.

We have experienced the same issue with our accessing Exchange over ActiveSync. For us, it only affects outgoing email over the AT&T cell network, on iOS 7.0.x. from 5s and 4s devices.

SSL ON outgoing emails fail

SSL OFF outgoing email work

Read other posts on Apple Support Communities talking about the port for SSL changed, but I cannot verify what port SSL on Active Sync is using for the device. I have been able to recreate the problem multiple time, so I am confident that this is the issue, now just to find out the port # so we can open it and see if that fixes the problem.

https://discussions.apple.com/thread/5337946?answerId=23150398022#23150398022&ac_cid=tw123456#23150398