Migration assistant pairing fails

Just bought a new Macbook for my wife, OS 10.6.8
She has been using an old G4, OS 10.5.8
I installed the latest updates to both laptops.
Have tried to use migration assistant using an ethernet cable.
In migration assistant, they won't pair - I have never gotten to the point where I am asked to input the passcode.
Have tried manually setting the IP address, but no luck.
Any suggestions?

Perhaps Pondinis'  Excellent Information may be of value to you...
Have a look at this Link...
Using Migration Assistant on Lion
From here
http://pondini.org/OSX/Home.html

Similar Messages

  • Migration Assistant - Computers fail to find each other - Dell Windows 7hp to iMac OS X Mavericks - all firewalls on both machines are disabled

    I dont post here often but after a few days of trying different things I am at a loss so here it goes:
    Previous Machine: c2009 Dell, Windows 7 Home Premium
    New Machine: late 2012 iMac, OS X Mavericks, Parallels 10 Installed
    Both computers connected to existing business network via ethernet. All firewalls and updates are disabled on both computers, screen savers and sleep modes are also disabled.
    The first strategy was to transfer data using the Parallels Migration Wizard. The wizard finds the PC and begins the transfer, but gets to about 1/5 progress and hangs/ stops every time in the same spot. I disabled everything (firewall, etc.) I can think of on the windows PC and it still hangs in the same place every time.
    The second strategy was to use the Migration Assistant that came on the iMac. The computers fail to find each other every time. so I haven't been able to even start the process. Searching on the iMac Network folder I can find and access the Dell (after changing security settings on the Dell to allow this). From the Dell Network folder I am not able to find or access the iMac.
    So, I have submitted a help request to Parallels to see what they can do to help, but I also wanted to reach out here in case someone has experienced this before.
    Thanks

    Migration Assistant - Windows

  • Migration Assistant can't find my external hard drive

    I'm trying to set up my Mac Mini and it isn't working.  Three steps into the process and already I'm locked up.  I'm trying to migrate data from an external FireWire 400 drive.  I have to use an adapter because the Mini only has a Firewire 800 port.  That's not a problem because I've used the adapter several times and it works fine.  The external drive is connected directly to the Mini and turned on.  It's been turned on before I went into this mode.  Now the Migration Assistant is hung up on Select The Source with a spinning circle and the Continue button is greyed out.  I don't want to bypass this step and do everything manually because that's a nightmare and with my schedule it will likely drag out for months.
    Can anyone help?

    Personally I have always used the manual method for moving my files over to a new iMac and never use Migration Assistant.
    Go to the Apple drop down menu and select Force Quit.. and if Migration Assistant has failed, force quit it and try re-launching it again from your Applications Utility folder.

  • HT2518 Migration assistant can't find my external drive - I ran the disk utility on it and it checked out. What can I do - I am trying to transfer PC files to my new MacBook Pro. Thanks

    Hi,
    Wonder if someone has a suggestion for getting Migration assistant to recognize my external drive so that I can transfer some PC files from it to my MacBook Pro? I have been opening files in the drive with the Mac without a problem and I ran the diagnostics utility and the drive verified. Still, migration assistant spins and spins without finding anything. There's a lot of files and doing it manually with take days.
    Thanks!

    Personally I have always used the manual method for moving my files over to a new iMac and never use Migration Assistant.
    Go to the Apple drop down menu and select Force Quit.. and if Migration Assistant has failed, force quit it and try re-launching it again from your Applications Utility folder.

  • Windows migration assistant gives error " An error occurred while preparing your information for transfer " Please suggest how to proceed . Many Thanks .

    Windows migration assistant gives error " An error occurred while preparing your information for transfer " Please suggest how to proceed . Many Thanks .

    To find out what is causing the Migration Assistant to fail, you can check the SystemMigration log located in - C:\Users\[user name]\AppData\Local\Temp\SystemMigration

  • Error "The Connection Failed" in Time Machine, Migration Assistant and Restore From DVD

    I am receiving this error when trying to connect to my Time Machine Backup in my Time capsule. I input the proper password to access my Time Capsule and It returns me to the screen with the caption "The connection failed" under the Time Capsule name in the "Select your Disk" screen. What would cause this error. I am connecting via WIFI (AirPort) and have full signal. I am using Mac OSX 10.6.8
    I recently had my 1TB hard drive replaced and I am attempting to restore using Time Machine, migration assistant or from the startup dvd (tried multiple ways, no success). The initial setup of mac OSX 10.6 would not let me connect or other attempts after erasing hard drive and reinstalling OSX from disk.
    Worked on it all weekend and don't have enough beer to drown the frustration, any help is appreciated.

    You are correct TM is not at all easy to do a full restore.
    To answer your question: Yes TM disk does show up in finder.
    After my initial startup setup I was able to start TM and access all my previous backups. I migrated some files and was able grab the data from finder. Not satisfied with that I tried to do a restore to that previous date, to no success. I then erased the HD and reinstalled OSx and tried again from the setup screen. That didn't work, sulked over some beers. I then tired with Migration assistant...same result (more beer).
    In starting TM after trying MA, only one backup was showing in the Star screen (today). None of my previous backups were showing. Since exiting TM it has been "Making Backup Disk Available" ( xGB of 6.29GB). Considering the size, I can only assume that these are my previous backups.
    I have reviewed Pondini's posts, FAQs, and tutorials. I am a little scared to try and locate the drives through Terminal as in Pondini's TS #6 guide. If I can get my previous backups to show up, I will be happy with dragging files from Finder to restore my data and slowly work at restoring my settings/applications.

  • Migration Assistant fails after showing 157 KB or 0 KB to transfer

    I spent 4 days trying to get OS X Migration Assistant to successfully migrate between two desktop machines, both running Mavericks 10.9.3.
    The two machines were connected by an ethernet cable, and all migrations would fail after 16-24 hours, with the progress bar stalling out at "Less than one minute remaining".
    Before every failed transfer, Migration Assistant would inaccurately show "157 KB selected" for transfer if the "Computer & Network Settings" option was checked, or "0 KB selected" for transfer if only the "Applications" or "Documents & Data" options were checked.
    I finally realized that the migrations were failing because I was opening and clicking through Migration Assistant on both the source and target machines at around the same time.
    The eventual solution was to open Migration Assistant on the source machine first, and click through as far as I could until the source machine was actively looking for other machines on the network.
    As long as I waited until then to open Migration Assistant on the target machine, it would correctly calculate the size of the files to be transferred and the migration would succeed.
    So, the order in which you open Migration Assistant seems to make a big difference: source first, then target.
    My problem is solved, but only after several days of hassle, so I wanted to post this in case other people had a similar issue.
    (I tried many suggested fixes that did not work, included reinstalling OS X on the target machine, running disk repair and fixing permissions on both source and target, changing file sharing on the source machine to include the whole drive, trying to migrate Applications and Documents & Data separately, turning off wifi before the transfer, etc.)

    Thanks for posting this.  I was having the same problem.  You saved me hours, maybe days, of frustration!

  • Migration Assistant fails on non-existent file

    Here's an interesting one. I made a bootable clone of my harddrive (with SuperDuper) that works like a champ. Bought a new (much larger) hard drive for my Macbook, installed OS X with no problem, got it all updated. Then went to use Migration Assistant to import my user from the clone, and it fails on trying to copy an invisible file (begins with .) that actually doesn't exist (I have Finder set to show hidden files). This causes the whole import to fail and MA says the user can't be created. Is there any way to tell it to skip this "file"? Other suggestions welcome.

    Yeah, that didn't work so well since SuperDuper ran across repeated errors trying to do so; I suspect it's something to do with the drive. (SuperDuper complains about WD's MyBook, which is what the drive is.) Because SD stops the entire copy operation on single errors, it'd be a painstaking process.
    Besides that, I like doing fresh installs of all the bits.

  • Migration assistant fails to *find* machine

    Very simple, thought I'd fire it up before going to sleep and have a baseline to tune from in the morning. No such luck -- just a band-new 10.5.7 MBP seeking to slurp from a couple year old 10.5.7 Core2Duo iMac. I haven't any FW800 small-port cables, but neither on a dedicated point-to-point ethernet nor on the regular network does migration ***'t get past "looking for other machines" stage after specifying who is sending and who is receiving. I presume this is either a sign I shouldn't bother with it or some completely braindead thing done on my part.

    Thanks, Pondini, but the Time Machine disk passes the Disk Utility repairs and only the spinning wheel was visible under both the Setup Assistant and the Migration Assistant.
    I now have some good news, and some bad.
    First the good news: Lion's Migration Assistant offers the option to copy user (and other) files from the previous OSX disk, not just the Time Machine disk. If this option was already in Snow Leopard, then I missed it.
    Now the bad news..
    I spent several hours reading (Pondini's and others') suggestions to ensure that my Time Machine is as seamless as possible, namely, for the next backup to be incremental. No luck: all user data are copied. Until the interface of Time Machine stops trying so hard to shield us naive users from making decisions on our own, one idea is to keep the iPod and pictures/video collection backed-up by the straight-forward rsync. Then whether Time Machine is really incremental will not matter, and in any case a spare copy of the documents you wrote by hand is nice in case the some blocks of the disk fail.
    But I may have been the one who messed it. In Preferrences \ Time Machine \ Options... I excluded all users except the user "Admin" who restored the user accounts. The idea was to test first whether the mildest user will get a full backup. It may be that Time Machine does not look in the history to see if a given file or set of files already have some copy in the past. If a file does not exist in the very last backup, it is saved to the Time Machine disk.
    If you're reading this and are keen on an incremental backup, try this: restore your user accounts using a user Admin, but do not start to backup until after the accounts are restored. Will the backup afterwards be incremental?

  • Migration assistant fails repeatedly

    I just bought a new MB and have been trying to transfer info from my old one. I have run Migration Assistant multiple times, but it fails at a certain point. After moving a lot of my info, it eventually hangs and says that "The other Mac is not responding. Make sure that all of your network devices are connected and turned on." It has a button to continue, but that never works. I have no idea why it would quit as I have not touched anything. Any advice would be appreciated. TIA

    Perhaps Pondinis'  Excellent Information may be of value to you...
    Have a look at this Link...
    Using Migration Assistant on Lion
    From here
    http://pondini.org/OSX/Home.html

  • HT4796 Migration assistant failed after 90% of the way; where are the files now and how do I get rid of them?

    Migration assistant failed after 90% of the way; where are the files now and how do I get rid of them?

    Hello.  It looks like I recovered all my keywords attached to photos.  What I did:
    First I located all photos without keywords using a metadata search.
    I found that it seemed to be certain groups of photos that had no keywords.  I decided to at least get the main keyword on all of those in a particular group, like Canyonlands. 
    Once I added one of the keywords, the others all showed up magically!  I then went to each group of photos and added the main keyword, and the others came along and attached to the photos.
    Don't understand why this occurred or why it got fixed, since it was so random.  But, I'm glad to have my keywords restored (I had divided flowers by color, etc. so it was a lot of work!)
    Thanks for the discussion and help.

  • Migration Assistant fails or freezes every time

    2008 iMac running Mavericks to a new iMac over ethernet connection.
    I have run software update on both iMacs, I have run "repair disk" and "fix permissions" on both.
    Every time i run migration assistant, it never completes.  it looks like its running, and the esitmated time left begins to count down, but eventually it just stays at 2hrs remaining, or 2hrs 30 minutes remaining.  And I let it run for 15 hours.
    I am forced to reboot the computers to get them back, and the new iMac has NO data transferred, and the old Mac remains as is (as expected).
    Also, Time Machine fails on the 2008.  I have tried to run time machine to more than one firewire drive.
    Not sure how to proceed.

    Sounds like you've been through the ringer . After Apple replaced FW with Thunderbolt my boss tasked one of the techs and me to investigate alternatives. We both found WiFi useless for anything more than a couple GB of data and even then we experienced too many failures to recommend it. Theoretically migrating with Ethernet should be a good choice but once again we experienced failures we couldn't explain. That led us to recommend users back up via clone or TimeMachine to an external drive and migrate using the external drive.
    That should have ended the matter but I've since added a qualifier to that recommendation; a USB external drive may be your best option. We've always known that some FW chipsets were flaky but an additional layer of flakiness has been added with the Thunderbolt/FireWire adaptor.

  • Migration Assistant fails with MacPro6,1

    I bought a Mac Pro a few months ago and kept getting kernal panic's after running migration assistant from a MacPro1,1 which I have had for about 8 years.  I went back and forth with Apple, and they decided it was defective and sent me a new one which took a while to get through the university bureaucracy. I ran Migration Assistant from a MacPro1,1 running OS 10.7.5, and again got a kernal panic on restarting but was able to do a safe-boot successfully ((previous MacPro even this failed).  I updated the OS X software and tried to turn off stuff that might be interfering but still get kernal panic's on restarting sometimes. Also received alerts that a variety of system extensions "were not installed properly". Clearly, the system IS NOT that stable so I erased the hard disk and will do a manual restore app by app so no preferences or systems-related software gets transferred.
    This problem is very surprising to me since I have never had problems with Migration Assistant before and we have plenty of macs here. I must have tried a dozen times with the first Mac Pro using either the old mac in firewire mode or using the time-machine backup but nothing worked. I wonder if anyone else has seen this and if the new Mac Pro has an issue in this regard.
    On the positive side, Migration Assistant probably moved a bunch of obsolete software/files from the 8-yr old Mac which was migrated from an older Mac (and the older Mac was migrated from a an even earlier Mac).  A clean install at this point may be worth doing but a hassle.

    Your conclusion that Migration assistant fails is not supported by the evidence you presented. You said you got kernel panics AFTER you restarted -- these are not caused by inherent Vice in Migration Assistant, which appears to have completed successfully.
    Kernel panic is not ONE problem, it is one of hundreds to thousands of problems, and if you would like help debugging that, you could post a kernel panic log for readers to help you interpret.
    Mac OS X: How to log a kernel panic
    If you approach Apple for help with this issue, they will check for machine-check reports, run diagnostics, then send you home to erase your drive and re-Install Mac OS X from scratch (which effectively removes third party add-ons in the process).

  • After using migration assistant to a new Mac 10.9.5, Outlook failed to open...mssge "Could not rebuild database -18000"

    After using migration assistant to my new MacBook Retina 10.9.5, Outlook failed to open...mssge "Could not rebuild database -18000"

    See if this previous discussion/link to microsoft support helps
    Re: There is a problem with the Outlook database.  Your database could not be rebuilt. [-18000]

  • Migration Assistant fails to recognize a Time Machine disk (itself migrated using Disk Utility)

    So I outgrow my Time Machine disk. I listen to the advice (repeated in multiple places) that one can simply use Disk Utility's Restore tab, select the old time machine disk as source and the new one as destination, and click restore to copy block-by-block, then rename the disk.
    This works very well. I have indeed been able to use Time Machine on the new disk without losing any of the history.
    But now I am in trouble. I am also outgrowing my MacBook disk. I put a larger disk in and install Snow Leopard from scratch. Now Migration Assistant does not recognize the new Time Machine disk (perpetually spinning wheel). Renaming the disk to the old name does not help. M.A. does recognize the old Time Machine disk, but that means manually managing the changes (and giving up on the larger TM disk). I reinstall Snow Leopard and do not miss that time the option to restore from Time Machine, but it still does not see the new Time Machine disk.
    How does one convince Migration Assistant to use a Time Machine disk that duly has Backups.backupdb as a root folder and where "ignore ownership on this volume" is not set?

    Thanks, Pondini, but the Time Machine disk passes the Disk Utility repairs and only the spinning wheel was visible under both the Setup Assistant and the Migration Assistant.
    I now have some good news, and some bad.
    First the good news: Lion's Migration Assistant offers the option to copy user (and other) files from the previous OSX disk, not just the Time Machine disk. If this option was already in Snow Leopard, then I missed it.
    Now the bad news..
    I spent several hours reading (Pondini's and others') suggestions to ensure that my Time Machine is as seamless as possible, namely, for the next backup to be incremental. No luck: all user data are copied. Until the interface of Time Machine stops trying so hard to shield us naive users from making decisions on our own, one idea is to keep the iPod and pictures/video collection backed-up by the straight-forward rsync. Then whether Time Machine is really incremental will not matter, and in any case a spare copy of the documents you wrote by hand is nice in case the some blocks of the disk fail.
    But I may have been the one who messed it. In Preferrences \ Time Machine \ Options... I excluded all users except the user "Admin" who restored the user accounts. The idea was to test first whether the mildest user will get a full backup. It may be that Time Machine does not look in the history to see if a given file or set of files already have some copy in the past. If a file does not exist in the very last backup, it is saved to the Time Machine disk.
    If you're reading this and are keen on an incremental backup, try this: restore your user accounts using a user Admin, but do not start to backup until after the accounts are restored. Will the backup afterwards be incremental?

Maybe you are looking for