[reggoboy]

I have a gig tomorrow and the setlist is curated on my MacBook and now I need to get it to my iPad, and the sync gets hung at "Sending database file."

I have tried rebooting both devices, maybe twice. Screen shots of both devices below.

Caveat: This may be the first time I've tried to sync to this iPad, which is a replacement device for my previous iPad, whose backup I used to restore the new iPad. So in theory, the two devices should have identical content. The old iPad always worked fine. The old iPad is gone, so I can't test with it.

Thanks in advance!

   
   

[Zubersoft]

Have you copied over a library backup file (Settings->Backup and Restore->Backup Library) and restored that on the new iPad? I would always recommend that as the first step before synchronizing as it ensures an identical database will be used on each device and also copies over the application settings. Is it necessary to do that? No, but I would like to know if it helps in this case as I'm not sure why the synchronization is not proceeding for you.

Mike

[reggoboy]

Thanks for the reply!

I didn't try that, but I was going to do it if I couldn't get it working.

After apparently getting stuck several times, one time I just left it alone. After I don't know how many minutes (10??) I looked again and saw some progress... it was working its way through songs. But it then stalled out for a long time without showing any progress in the logs again. But I'm not sure at that point that I had the option of canceling, and I didn't want to corrupt anything. When I came back some time later, I found the confirmation message that the sync had completed successfully. A quick check of the recent changes seemed to confirm that it worked. 

For the past couple years, syncs have been very fast. And even back in the day when things ran slower, it didn't get stuck at one place very long. So I don't know what the issue was yesterday. My two hypotheses right now are:

1) something didn't restore cleanly to the new iPad and is confusing MS as it tries to sync; or perhaps MS relies on some hardware identifier that changed after the migration; a restore from backup should resolve this
2) something flaky on my WiFi network is causing comm issues; a router reboot could help if that was the case

Frankly, I'm afraid to touch it right now, with the gig coming up in a few hours. But maybe tomorrow I'll try a fresh sync. 

Thanks!