21178 Views Previous 1 2 3 4 5 6 7 Next 98 Replies Latest reply: Mar 17, 2008 2:50 PM by knc6568 Go to original post
I could not sync this morning for the first time since I got the phone. I disabled airport (on my mac, not on the iphone btw), force-quit iTunes, and restarted. Nothing more, nothing less, and it synced when I re-opened iTunes. As soon as the sync started, I turned airport on and it continued to sync fine. Something must have changed - this is too much of a coincidence. I see a security update that my mac wants to install, but I haven't yet - I don't think I've had any other recent updates.
Having upgrading to Leopard, and subsequently downloaded the patches to the level of 10.5.1, I am unable to sync the iPhone at all. I get the "Sync in Progress" message on the iPhone, and the "Syncing...iPhone" on the iTunes program. I've read the posts here, reset the computer PRAM, reset the sync log in iSync, reloaded iTunes, reset the iPhone, unchecked the items under "Advanced" and generally tried everything I know. I have even "force quit" iTunes any number of times, something I really hate to do. Each time, I have sent the report to Apple, and I would encourage everyone to do that. At this time, I am getting nowhere. My iPhone has not yet synchronized successfully for even the first time. However - I'm lucky in this - nothing has been deleted from my iPhone, either. I'll watch this post to see what occurs, but I predict another Leopard Operating System download soon, for this may be an issue that is beyond any one fix. Good luck to you all!
I guess now the best fix for right now is to avoiding syncing at all cost. lol I'm still happy this isnt bricking my iPhone or anything. I mean we kinda just have to wait until Apple Fixes this. I think Apple might be saving all the updates up so they can blow em out on the MacWorld conference or something.
You can sync successfully if you disconnect your computer from the internet. Alternatively, you can try a iTunes force quit when the sync hangs up, and then restart iTunes manually, leaving your iPhone connected - it will then sync fine. Either works.
Obviously Apple have changed something at their end, which is causing the sync to hang up.
Disconnecting the Internet connection also worked for me. (I saw the MDCrashToo process and killing that helped also.)
Sounds like something wrong with one of Apple's servers. Since it's a holiday week at Apple, there's a good chance nobody is around to discover and fix it.
I also have .Mac email synced to the iPhone (though I never use that account), in case that helps others.
I had the exact same issue starting last night and this morning....whereas I have never had trouble syncing with iTunes before. I decided to also turn off my internet connection like so many have stated in this thread....and that is what finally worked for me. I don't understand why I have to now turn off my internet connection to be able to perform a sync....but I hope whatever the problem is....will be fixed soon!
Hopefully 'Nathan C' or some other expert can pop in here and give us some insight to the problem!
someone at apple said it has to do with .Mac synching the calendars. I've never had a .Mac account and yet this has happened. some change they made is creating a request to check with .Mac and many dont have an account. So with no internet connection, it only syncs locally. Same with iCal turned off, it wont sync calendars. this iSync program (which i never new existed) started to run the first time i synched on leopard and is now causing problems.
this may be a ploy to make people buy .Mac accounts. just like the last security updates resulted in thousands having to buy mac wireless routers.
I too am having this hang at "sync" but not actually starting the sync problem. I have reset sync services, reset the phone, unchecked all syncing in iTunes etc.
I have no airport installed to turn off, bluetooth is off.
My only fix is to force quit the MDCrashReportToo process. Its parent process is iTunes.
My phone will then sync as long as I don't unplug it, doing so requires another force quit of the MDCrashRepoetToo.
I have no idea what this means, but open files and ports reads