itunes could not connect to this iphone because an unknown error occurred (0xE800007F). wifi sync

Thanks for that. Got Downcast and it's 100%.

bye bye iTunes......

I am having a similar issue

I have rebooted my windows 7 PC and all iOS devices. After rebooting wifi syncing worked normally for around 12-24 hours, the PC and iTunes running the entire time. I have since returned to my PC and found the following errors.

iTunes could not connect to this iphone because an unknown error occurred (0xE800007F)

The iPad "Nathan's iPad" could not be synced because the iPad could not be found on the network

An iPad has been detected, but it could not be identified properly. PLease disconnect and reconnect the iPad, then try again.

that last error appeared 38 times. after clicking OK on all 38 errors I can then use iTunes again and both iOS devices appear in iTunes. However one or both will fail to sync over Wifi and will have the triangle ! symbol next to the device name in iTunes under devices or the device name will disappear from the device list in iTunes to later reappear.

This is a very common. I leave this PC running 24/7 with iTunes open so I can sync my podcasts before work.

The iPhone 4S wifi sync seems to have the most trouble, but neither are functioning properly.

extremely annoying

Thank you for the reply, the channel was set to auto which it always had been but when I changed it to manual and selected one, the issues went away for phone, printer, etc. THANKS.

Natesac, Per my message to Burfot, you might consider using Downcast to keep your podcasts up to date adn turn off WiFi sync to iTunes or leave iTunes closed most of the time. Otherwise, until/unless Apple addresses the problem, such errors will continue to accumulate.

Here's a video of my computer with these errors

http://www.youtube.com/watch?v=vjoiFoSKhe8&feature=youtube_gdata_player

Everyone following this issue should go to the first post in this thread and click the "I have this question too" link. That might draw some more attention.

I like having WiFi sync available, even if it's not behaving and self-invoking quite as expected. So, on the theory that the error is annying, and probably means a sync has failed to start, but is otherwise benign -- except that it blocks further iTunes function:

I have written an utility (using AutoIt) that watches for the specific error and clicks OK to dismiss it. I've been running it for several days now, and it seems to work fine.

Specific notes and disclosure:

- It lives in the tray, as a little blue musical note; primary click gives you 'Exit' and 'Check for update' options.

- Hovering over the icon will tell you the total times it's dismissed the Annoying Error.

- It anonymously reports usage to me, just for my own interest. It reports a machine hash as a unique (but non-reversible) ID, starts and stops, and the number of times it has dismissed the annoying message.

- All reporting can be disabled by invoking the exe with '-nousage' on the command line.

- It anonymously checks for updates (but does not auto-install them.) The '-nousage' switch also disables the update check, though it can still be invoked from the tray icon.

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

- If it is unable to dismiss the error, it exits with a message, rather than get into an endless cycle.

- It does have to bring the error window to the foreground in order to dismiss it. This could theoretically be disruptive to you, if it happened during interactive use. My own experience it that it happes when I'm in another room, connecting or disconnecting the phone from a separate power brick, but YMMV.

Use at your own risk, no responsibilty, YMMV, do not taunt Happy Fun Ball, etc.

Feel free to download and use; comments and suggestions welcomed.

exe

zip of exe (It's not much smaller, but in case you prefer downloading a zip.)

MD5s (computed by FCIV):

8e43d86f5837ef37fc4a16054c61f98b itunesdismissannoyingwifisyncerror.exe

b756544242aa81e61fb5269d0e9c6fd7 itunesdismissannoyingwifisyncerror.zip

You Sir, are a scholar and a hero!

Lairdb, I seem to be having trouble with your DL links. It might be broken. Im very interested to try your workarond.

Let's try that again; sorry. Typos in the links. (Weird, I thought i checked them.)

exe

zip of exe

It's my week for typos. For those of you running the first version, it had a once-a-day bug, that would result in a crash. New version posted.

exe

zip

MD5:

1bfcd7c45bccbb7f2914a9d864a98dd9 itunesdismissannoyingwifisyncerror.exe

efd87cf9859bf289cee7ca51ef87a825 itunesdismissannoyingwifisyncerror.zip

This neat little workaround has solved my issues. If only apple can just fix it so this wouldn't be needed. It's really just as simple as having iTunes ignore the "errors" altogether.

After not quite a week, 13 of you are using the utility and allowing it to report. It has dismissed the Annoying Dialog 112 times.

The grand champion individual user has been dismissed 26 times, though they are not the user who had the maximum-per-clock-hour of 5 dismissed in the same hour. The average user has been dismissed 9 times.

Looks great, but I'm on Lion -- any solutions?

Thanks

ssorgs@ wrote:

Looks great, but I'm on Lion -- any solutions?

Well, I won't savage you for posting in the Windows forum...

Maury Mccown wrote:

No it isn't. I started this thread, and I posted it here in the Mac forum for a REASON: I'm expereinceing this on my Mac. The Windows Users are the ones that can't seem to navigate and post in the correct forums.

...but I don't have a direct solution for you; AutoIt (the scripting language in which I wrote "iTunesDismissAnnoyingWiFiSyncError") is tightly coupled with Windows.

AppleScript and AppleScript GUI Scripting should allow you to write an similar-functionality utility, though; if you start tackling it, I'm happy to share my conceptual outline.

In the meantime:

• 25 of you are using idawse, or at some point* have used it, and allowed it to report. (*If you rebooted, it doesn't autostart or anything; you have to manually start it, or put it in your Startup folder, or scheduled tasks, or some similar mechanism. If you discontinued using it because of a problem, let me know; I'm curious.)
  
• The grand champion has had 47 Annoying Errors dismissed automatically; that's almost exactly 20% of the total of 236 Annoying Errors dismissed. (It's not me, by the way; I'm actually well below the median, with only 16 dismissed even though I had a several day headstart while testing.)