Previous 1 34 35 36 37 38 Next 929 Replies Latest reply: Apr 14, 2014 10:35 AM by RaghuSatya Go to original post Branched to a new discussion.
  • sdorn Level 1 (0 points)

    I said this much earlier in the thread as well, but I am also on VZ and have never had an apsd crash in my log.  Exchange push has not worked for me for more than an hour or so without stopping.  My practice now is to disable cellular data whenever I am connected to WiFi, and push works just fine while on WiFi as long as I do that.  I have to manually check my email periodically when on cellular data as it doesn't push when cellular data is turned on.  I have also tried just disabling LTE, but that didn't help.

  • Frank Malloy Level 2 (350 points)

    sdorn: if you are going to so much trouble, I would just change from Push to Fetch every 15 mins. It's not optimal, but at least you'll get mail notifications reliably.

  • Clif H Level 1 (115 points)

    VZW iPhone 5 running iOS 6 (now 6.0.1) with push enabled on iCloud and Exchange email. Data roaming off. Use jn/around Boston metro. Push working fine with no apsd crashes here from day one.


    Disclaimer: I'm impatient. Any time I see any issue that affects with network connectivity I use the Reset Network Settings option in Settings-General-Reset to fix.


    Additionally a colleague with iPhone 4 upgraded to iOS 6 and immediately lost push, Exchange calendar meetings were not showing up, and seeing general slowness. Had him go through reset network settings and immediately took care of his issues.


    A different colleague had a VZW iPhone 5 on iOS 6.0 and could never get push working. I could not verify if be had apsw crashes and he never did the network settings reset. I think his "resolution" was returning phone and going with AT&T.


    Nothing's a panacea and sure many have already tried so just throwing out there as personal experience. I always reset network settings after any iOS update to be safe.


    PS: 6.0.1 seems more targeted at resolving the meeting organizer swap bug than push email issues specifically.

  • sdorn Level 1 (0 points)

    Yes, I know fetch is an option.  I've been following (and posting in) this thread since it was only one page long.  It is easier for me to switch it back and forth.  I am on WiFi virtually all of the time except when driving to and from work, and I can't read emails while driving anyway.  I need to know immediately when I get an email.  Fifteen minutes is too long to wait.

  • spidertaker23 Level 1 (10 points)

    The day before iOS 6.0.1 came out I called apple support about the issues I have been having with exchange push. In my case I was having problems with Push for exchange and push for EVERYTHING (fb, gamecenter, etc).  I was getting the aspd crashes on my iPhone 5.  iMessage would also fail to work at the same time push would stop working.  Everything would work for 5 to 15 minutes after the phone was rebooted for airplane mode was toggled.


    Apple support decided to replace my iPhone 5.  They scheduled me an appointment at an apple store yesterday at noon.  They replaced my iPhone 5.  Exactly when they activated my replaced iPhone 6.0.1 came out.  So I updated in the store.  The stupid thing is that I had to come back to the store later that day to get the home button replaced on my replacement iPhone because it would make a double click noise.


    I am happy/sad to report that everything now works accept exchange push email.  All my push notifications work and iMessage works fine.  The only thing that doesn't work is push for my exchange email.


    I work in IT and we have about 9 people in our IT department that have iPhone 5's on Verizon.  We are all experiencing the same problem.  We currently connect to our Exchange 2007 server for Exchange email.  Obviously, we have a bunch of users that have iPhone 5's as well.


    Hopefully this can get fixed sooner rather than later.  Not having push email for work for over a month is not acceptable.

  • lorennerol Level 1 (0 points)

    spidertaker23 wrote:


    We currently connect to our Exchange 2007 server for Exchange email.  Obviously, we have a bunch of users that have iPhone 5's as well.

    There goes my theory that it is an Exchange 2010-specific issue. I know another IT admin running against Exchange 2003 and he is not having any push problems.

  • iSam88 Level 1 (0 points)

    Definitely not Exchange 2010 specific.  We're running Exchange 2007 SP 3.  Works perfectly on all devices with iOS 6 except for the iPhone 5 and Verizon LTE.

  • Clif H Level 1 (115 points)

    Exchange 2010 RU2 here.

  • lorennerol Level 1 (0 points)

    I spent the last couple hours with LTE/4G disabled (Verizon). Push still doesn't stay working.

  • MikefromDK Level 1 (0 points)

    Same problem. (From Denmark).

    We are having 6 iPads (5 iPads nr. 2 and 1 iPad nr. 3) in the office together with 6 iPhones (4x 4s and 2x iPhone4).

    We all updated to iOs6 without any problem on the Exchange. (Running version 2003)

    We updated to a new server (2010) 2 weeks ago and everything went fine.

    But the day after the update I checked my mails on my iPhone 4 and everything went away (Mails, Calendar and contacts). And it said - no contact to the server.

    I checked also my iPad and the same happened - mail, calendar and contacts went away as it was trying to connect to the server.

    Everyone else are running fine in the office (5 other iPads and Iphones) - only my iPhone and iPad (same account details).

    I have deleted the account and everything suggested in here, but still no success and it is driving me crazy, as I need my mails when I travel.

    What I dont understand is that it is only my 2 iOS devices and none of the other 10 devices we have.

    Wondering if it is a App only I have installed or ?!? otherwise it makes no sense it is both the iPad and iPhone.


    Apple and Microsoft - Please tell us something - we need to know you are working on it and when you will have it fixed.


    Also - I was about to buy the new iPhone 5 and iPad 4, but due to this I am waiting.....

  • M&M83 Level 1 (0 points)

    I have to say again,the most frustrating piece of this puzzle for me is the fact that Apple has not publicly acknowledged there is an issue here.  Not having emails pushed to my phone when i do not work in an office and travel every week is a major problem, and i have to imagine this is affecting a vast amount of people.  That said, there seems to be the same people posting in this thread, so maybe its a smaller than i believe it to be.  I feel that with all of the iphones out there, if this is a network or a software issue, there would be so many more complaints about it and we.d have a fix already.


    So its either widespread and a lot of people donT care, or its not as widespread and Apple doesn't care.


    Either way, having to wait another 2 months for the next ios update, as some have suggested here, is just sad on Apples part. . 

  • Frank Malloy Level 2 (350 points)

    MikefronDK - this is a completely different issue and it should be discussed in a different thread.

  • MikefromDK Level 1 (0 points)

    I dont understand why this is another issue. My Exchange connection is not pushing mails through to my ios 6.01 devices.

    Otherwise please tell me what you mean.


    Thanks a lot.

  • Frank Malloy Level 2 (350 points)

    Sounds like you have a more basic problem.


    In our case, when we check mail manually all mails are loaded ok - we have no server issue and no emails/contacts/calendars are lost. The problem is that the notification of our emails is not getting pushed. This is a separate mechanism than the simple server connection/download process.

  • jimwoodard Level 1 (0 points)

    Since my original post, 19 days ago, still no issue. 2 iPhone 5's (64GB AT&T) and now one iPad 3 (64GB, wi-fi only), all with iOS 6 and no push issues with Exchange 2010. I have users with personal iPhone 5's and 4S's with iOS 6 on Verizon and AT&T no issues for them either. I have no Sprint users.


    Only one phone experienced this problem. Attached the phone to a Mac, restored the phone to new, restored the phone to backup, No further problems. As I said, that was 19 days ago. I'm going to call this a win.

Previous 1 34 35 36 37 38 Next