Previous 1 2 3 4 5 Next 69 Replies Latest reply: May 28, 2014 5:41 PM by ivanivk Go to original post
  • whatisdamon Level 1 Level 1 (0 points)

    I'm having this same thing happen to me. I like the wi-fi sync.. don't see why it has to be so difficult.

     

    Very often I've been getting errors about iTunes not being able to connect to my iPhone with some 0x00FF7494237 error code (that's random numbers, can't remember the code itself right now). But this is the first time I had the alert mentioned in this thread.

     

    Real pain in the butt :/

  • ShavedApe Level 1 Level 1 (0 points)

    I also have this issue, so frustrating there are so many to close. Can we please have a comment Apple I doubt very much that you are unaware of the issue so a comment even to say your looking into it is better than faining ignorance.

  • RedAvenger Level 1 Level 1 (0 points)

    You know, I've never seen this error show up on an Android phone talking to WinAmp, and if Apple can't even acknowledge it's happening, that's going to be my next setup.

  • BraEric Level 1 Level 1 (0 points)

    I'd just like to add my voice to this.  iPad 2, iPhone 4s. Has been happening ever since I started using wifi sync.

  • bbnew01 Level 1 Level 1 (0 points)

    I also have this exact problem.  I have an iphone 4 and a 4s.  I have tried turning one off of wifi sync and then the other.  When there is only one device, I still get the message, but it is few and far between and usually there is only one.  The really sad part is that everything WORKS!.  Apple.....WHY DO WE HAVE TO PUT UP WITH THIS?  How hard could it be to add a check box that says "Don't show this message again".  Or if not, at least do not display the window more than once.  Message pops up.....if it is not cleared yet DO NOT display it again.

    Oh I know....this will be one of the things that the iPhone 5 fixes, so we can all go out and buy the new iPhone when it comes out to avoid clicking on hundreds of messages.  And by the way, we all know this, but just in case you are reading this and don't know, you can not do anything in iTunes until all of these messages are cleared.

    Pretty slick!

  • lutef1sk Level 1 Level 1 (0 points)

    This is really kind of a dumb problem to have but I'm used to Apple annoyances by now.  I'm sure they'll eventually fix it but suprised how long it's been an issue.

  • Alex997tt Level 1 Level 1 (0 points)

    I am using...

     

    OS: Windows 7

    iTunes: 10.6.3.25

    Devices: iPad 2 (errors), iPhone 4 (errors), iPhone 3 (no errors)

     

    This pop-up issue for me seems to be getting worse daily!  If you eject the device then it just tries to auto-reconnect over WiFi.  Sometimes it reconnects just fine, other times you get these endless pop up errors.

     

    Please fix this Apple!

  • BigMike535 Level 1 Level 1 (0 points)

    It could be too soon to tell, but since upgrading iTunes to Monday's new version (10.6.3) this has stopped. 

     

    It's been 2 days without an error.  I think.  The power went out Tuesday morning so I can't confirm there weren't any at that point.  But I checked Monday night before bed and again just now.  Still nothing. 

     

    Anyone else have the same luck?

  • Mattamattica Level 1 Level 1 (0 points)

    Same problem here.  2x iphone 4s's, 2x gen 1 ipad's, Win7 64. 

     

    Every night, dozens and dozens, possibly hundreds.  I don't count them.  But they happen nearly constantly while syncing too, making it impossible to finish a sync anymore.

     

    I find that if I restart my PC, not just iTunes, this will not happen for the first sync.  But nearly all syncs after that experience these message popups, it gets worse the longer itunes runs. 

     

    Nightly syncing actually worked better using the jailbreak wifi sync tool than it does using the official apple solution, which is disappointing to say the least. 

     

    It doesn't help that iTunes seems to have a memory leak issue as well.  After days of running it is eating up gigs of RAM for no apparent reason.  I close it and reopen it and its back down to a few hundred megs again.  But after a few days its back up to 3-4 gigs again.  All the while all it did is fail to sync on a nightly basis.

     

    iTunes has always been a pretty serious fail for a windows app, but it seems like lately Apple believes that windows users (which account for more iPhone/ipod/ipad users than osX users) are not important. 

     

    I am hoping the 10.6.3 build fixes this error message popup problem.  The other issues I have dealt with forever.  Maybe one day Apple will actually start acting like the company everyone believes them to be and fix these problems and release software that just works (which is of course their old marketing campaign, which they have long since abandoned).

  • SPXOSDER Level 1 Level 1 (0 points)

    Sorry to say BigMike, but I have upgraded to the new version of iTunes and I still receive the issue.  I hope the issue has gone away for you though...

  • BigMike535 Level 1 Level 1 (0 points)

    I think it's safe to say the problem has gone away for me.  I've been syncing every night without a single popup.

     

    Does anyone have PeerBlock installed?  I unblocked all of Apple's IP addresses this week too.  But only on 1 of 2 computers.  I wanted to see if it was the update or PeerBlock that solved the issue.  Neither computer is getting popups now, which leads me to believe that it was the update that solved it.  But if you have PeerBlock installed, it's worth trying to unblock Apple's servers.  I just opened iTunes over and over until I allowed all the IPs.

  • gizzmogeek Level 1 Level 1 (0 points)

    BigMike, can you expand upon that a little. I'm not sure I follow what you are saying. I am syncing over wifi for multiple iPads and iPhones to the same Win7 pc like everyone else and I get the lovely "an ipad has been detected, but it could not be identified properly. please disconnect and reconnect the ipad, then try again" messages for every device a hundred times too.  Are you saying that we need to allow the Apple IP addresses through on our router even though the issue appears to be an internal network issue?  Sorry, I'm just trying to make sure I understand what I should be setting on my Verizon Fios router as I'm not sure I understood what you meant.

  • prepaidburrito Level 1 Level 1 (0 points)

    I updated itunes and still had the error. I also noticed my itunes Home Share streaming wasn't working the past few weeks and stumbled across a post about disabling IPv6 in my LAN settings. Doing so fixed my Home Share right away. So then I reset my PC, started up iTunes and one at a time I reconnected my devices with USB. Each device resinstalled a driver and synced. Then I did wifi syncs simultaniously with all three devices (2 iphone & 1 ipod touch). They all synced fine. Two days later all devices have synced daily and no errors as of yet.

     

    Heres the post about the Home Share issue.

     

    https://discussions.apple.com/message/18376580#18376580

     

    If my errors come back I'll post an update.

     

    Good Luck.

  • Mattamattica Level 1 Level 1 (0 points)

    Well, I already had IPv6 disabled and was still getting the errors.  So that was not it entirely.  But after updating to 10.6.3.25 I am not getting any sync errors within the last 4 days even after at least 5 wireless syncs between different iphones and ipads.  This may be a coincidence, so if i get any more errors I will update the thread.

     

    So again I was having the errors, as my previous post mentioned, all along.  I also had IPv6 previously disabled on a Win 7 64 machine.  That did not seem to have any effect on itunes pre 10.6.3.25.  Now with 10.6.3.25 and ipv6 still disabled I am not seeing any further issues.  Problem seems resolved, and for me it was updating to 10.6.3.25.

     

    Please note that ipv6 caused all sorts of previous issues, so for me this has been a default thing to disable on ALL network adapters.

     

    Good luck to everyone.

  • Steve Shevell Level 1 Level 1 (0 points)

    Problem solved with 10.6.3.25.  About time.