Previous 1 3 4 5 6 7 Next 104 Replies Latest reply: Jul 10, 2013 7:30 PM by lambe727 Go to original post
  • The Merg Level 1 Level 1

    Well, I just got a new error. Plugged in my iPhone and turned on the monitor and had "iTunes could not connect to this iPhone. An unknown error occurred (0xE8000003)". I don't know if the error popped up before or after I plugged the phone in though.


    - Merg

  • caiomsbr Level 1 Level 1

    Morning, recently I reinstalled all my Windows 7 OS doing complete format of the partition and boom.. No more problems syncing and iTunes never stated that it couldn't find my iPhone anymore. I had also an android and I installed some cross apps to enable me to use iTunes for both phones and I think it messed with the iTunes' method to sync over wifi.


    For those out there who has problems, consider formatting and reinstall the whole operational system from the ground!


    I'm out


  • globalist Level 1 Level 1

    Dumbest advice you could ever possible give.


    FYI Apple has already ninja-fixed this error in the latest iTunes build.

  • MarkkH Level 1 Level 1

    Watch This Video. It will solve the problem.

    Share this for everyone to know

  • vistiphone Level 1 Level 1

    Disappointing to have been posting in this forum for over 6 months, and the problem still exists. Reformatting either PC and/or iPhone are not reasonable solutions. One user has even created a script to clear the annoying pop-ups (kudos), but what we really need is for Apple to either fix the issue or tell us that sync over wifi is not going to happen for users like us.


    Is anyone from Apple listening to this forum? If so, we would all appreciate hearing from you. Thanks.

  • chriskeeble Level 1 Level 1

    You do NOT need to reset your iPhone (which is what the video link posted by @MarkkH tells you to do).


    Just update iTunes and the problem is fixed.

  • vistiphone Level 1 Level 1

    Didn't think anyone would be foolish enough to reset their iPhone or reformat and reinstall Windows. However, the best solution in over 6 months has been to run a script that will dismiss the error messsage. Give credit to lairdb for the time and effort that went into creating it. It's still treating the symptom rather than the cause. Wifi sync was a neat idea and I'm looking forward to seeing it when it works. Until then I'll just plugin like always.

  • chriskeeble Level 1 Level 1

    @vistiphone - are you saying you're still getting the problem?  Everyone else so far is saying that the problem is FIXED ...

  • sailermon Level 1 Level 1

    Well, not everyone that updated iTunes is error message free.  As I indicated previously, I am still getting the errors, although it appears less often and limited to my iPhone's, as the error messages are no longer appearing for my iPads.  It sounds like "The Merg" is still getting errors, as well.


    Unfortunately, "lairds's" fix is not reporting or dismissing the errors either.  Guess I will just have to live with it until Apple finally realizes it is worth fixing the discovery problems between devices and iTunes over WiFi.  I talked to Apple customer support in May and they said they were unaware of this problem...???

  • vistiphone Level 1 Level 1

    Tried returning to wifi sync following the latest update. The news is both good and bad. My iPad synced wirelessly, but choked due to lack of space. It attempted to copy over my entire music library a second time. Ignoring the current version in the library. Re-synced hard wire, choosing transfer all data froim iPad to library. Looked fine until I synced again, same problem. Then allowed iTunes to do a full reset and reload. That worked, but I had to reorganize my desktop apps and folders. Next time it tried to sync wirelessly, it began the same process of reloading all of the existing music.


    I give up on wifi syncing. Just not that critical, and certainly not worth the Apple version of reload your OS, apps and data.

  • lairdb Level 1 Level 1

    sailermon wrote:


    Unfortunately, "lairds's" fix is not reporting or dismissing the errors either.


    sailermon, if my idawse tool isn't dismissing it, the likely explanation is that the error text is slightly different than what i coded it for.


    lairdb wrote:


    - It watches for 'iTunes could not connect to this i' and 'because an unknown error occurred (0xE80000' in the same window, and clicks OK.


    Are you getting text in the error that is, perhaps, slightly different?  If we can figure out the difference, I'm happy to update the tool to handle.


    As long as I'm posting:

    Use of my auto-dismiss utility has declined markedly, as you might expect with most people reporting they're not experiencing the error any more.  This is consistent with my data:


    date ....dismissed


    I note that some errors are still getting dismissed, but it's not a twentieth of what was.  Neither, for that matter, is the usage of the tool -- there are about 7 users still consistently using the tool, and only one of those is actually getting errors dismissed. 


    (If you're the person in or near Carlsbad, CA (according to your IP address) -- you're still getting errors dismissed; have you updated iTunes?  Users not in or near Carlsbad, CA: you can probably quit using the tool, it's not doing anything for you any more.)

  • sailermon Level 1 Level 1

    I am not located in the Carlsbad, CA area.  I am in the Lake Tahoe, CA area, but I haven't been running the fix, because it didn't do anything for me, as previously posted.


    The only message I get now after updating iTunes is, "An iPhone has been detected, but it could not be identified properly. Please disconnect and reconnect the iPhone, and try again."  I assume the fix doesn't look for that message.  I would be happy to try a fix that did dismiss this error message, however.


    This is obviously some kind of discovery problem with the iPhone over WiFi, but it could be due to my firewall settings. I have tried several changes in the settings, with no luck.   I don't get any iPad error messages or the,  '...could not connect due to an unknown error...', anymore, so some progress was made with the latest version of iTunes.

  • appleuserTname Level 1 Level 1

    I didn't read through all these responses, but I also got an error message this morning - the first time I connected my new iphone to my itunes.  I was using the same cord that I use for all our ipods.  I looked at another site and it suggested using the cord that came with the phone (I figured I'd give it a shot).  It worked for me.

  • globalist Level 1 Level 1

    "An error message"?


    Perhaps it said "Error 10054: Connect the orignal iPhone cable"?

  • lambe727 Level 1 Level 1

    if you can i would get rid of the iphone 4 or 5. apple has to much control of it's products. i will never buy another apple iphone

Previous 1 3 4 5 6 7 Next