You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
I have Wi-Fi Sync active and it works great unplugged from power -- but when I plug my phone into power and it starts syncing, iTunes says the following:
"iTunes could not connect to this iPhone because an unknown error occurred (0xE800007F)."
Searching gives me zilch. Anyone have an ideas? Everything is running the latest verison of iOS, etc., etc...
Bump.
Same thing. iPhone 4S with WIFI sync turned on. iTunes 10.5.5.3 on Windows Vista 32-bit.
Note: iPad 1 is also hooked to power and has never given this message. Just the iPhone.
Where is the iOS update post-5.0.1 that was supposed to fix the iPhone battery issue, and hopefully the 0xe800007f issue as well?
So annoying! Though not as annoying being a slave laboror at FoxConn so we can all save $65 on the iPhone 5, I imagine :\ First world problems!
I startes Itunes as administrator (right click - run as admin), and now it seems to work....
I cross my fingers :-)
Good luck!
Hey Myhlendorph, it seems to fix my problem as well! Thanks!
Is everyone in this thread running iTunes on a PC? I haven't bothered checking all 18 pages of replies, but my bet is yes. If so, I think Myhlendorph may be onto something.
Nah, I tried and it didn't help. Besides that I also wasn't able to drag and drop files onto iTnues when running the app as admin.
No, there are Mac users with this problem. This is the iTunes for Mac discussion board, after all. ;)
I was thinking it was a permissions issue - at least it would be a straight-forward explanation. Thanks for the clarification, mjolnir1224.
Sory to say it did not help me anyway :-(
win 7 ultimate
Searching online I found a reference to an iOS5 function AMDeviceStartService returning the error value 0xe800007f. I'm not claiming that this is an error from that function, but that the return values from that function might give us a hint as to what's going wrong. The return values are:
* MDERR_OK if successful
* MDERR_SYSCALL if the setsockopt() call failed
* MDERR_INVALID_ARGUMENT if the Lockdown conn has not been established
Perhaps it's an unhandled disconnect from an existing (open but perhaps not active) socket connection to the device? Can someone with the dev toolkit confirm the values of these codes and tell us which one is e800007f?
Run as administrator would an unacceptable fix anyway. Even if the workaround worked for everyone (which it doesn't), in my mind it would still be a bug that needed to be fixed.
globalist wrote:
Nah, I tried and it didn't help. Besides that I also wasn't able to drag and drop files onto iTnues when running the app as admin.
Same here. We need to find the appropriate Apple email and flood their inbox until this issue is corrected. This is ridiculous!
I wouldn't mind so much but it seems to hamstring the application until the dialogs are confirmed. I've had situations where I've had to confirm up to 10 dialogs in quick succession. It's very unfriendly.
Sounds like apple just don't care! Otherwise there would be a reply from them saying when it's going to be fixed. Microsoft are better than this.
I can't believe that they are not warmed to look at the user's forum when a thread reach 18 pages. They certain know that there is a trouble here. But it's very difficult for them to admin it. They release new features. Never bug fix...
iTunes to iPhone "Unknown error 0xE800007F"
