"This path does not exist" error importing XP pvm

Discussion in 'Windows Virtual Machine' started by FlorenC, Jan 15, 2011.

  1. FlorenC

    FlorenC Bit poster

    Messages:
    3
    Extracted a pvm from a real Windows XP machine to an external disk using Transporter Agent for Windows 6
    Copied pvm to mac (10.6.6).
    Clicked on Import from the list of Virtual Machines in PDesktop for Mac 6. Transporter is launched.
    I select External Storage device under Migration Method
    I select the Windows XP pvm file and click Open,
    but when I click on Continue I get an error "This path does not exist" but the file is there.

    I get the same error if I try to open the pvm from the external device.

    Any ideas what may be wrong?
     
  2. SheilaG

    SheilaG Bit poster

    Messages:
    2
    Same Issue

    I am having the same problem with a Vista import - (I note another thread with the same problem for VMWare with no resolution either - does anybody answer these issues?)

    I have upgraded to the latest build but still the issue persists

    Help!
     
  3. FlorenC

    FlorenC Bit poster

    Messages:
    3
    In my case I resolved this issue by using an Administrator account in the mac for the Transporter process and the first time use of the pvm.
    After that, if you leave the pvm in a Shared folder, I could run the pvm via a normal user account with no problems.
     
  4. SheilaG

    SheilaG Bit poster

    Messages:
    2
    Thanks for the reply FlorenC, but I am using an admin account already :(
     
  5. umo

    umo Bit poster

    Messages:
    1
    transporter problem: also: "path does not exist"

    I am having the same problem. I am running the latest version of the MAC OS on a brandnew MACBOOK Air and using the latest Parallels release, downloaded 2 days ago as a trial version. Tried first to do a transport from a windows PC to the MAC by using transport over the network; this always stopped in the middle. Then used an external harddisk. Everything goes fine on the windows side (Windows 7, all updates installed). Then, when I try to transfer the file from the external harddisk to the MAC everything goes allright with transporter until the message pops up: "this path does not exist". The .vpm file is clearly there on the HD and can also be seen and marked in the MAC directory. Its name is correctly transcribed into Parallels Transporter, but then the error message happens. btw: I am running on MAC with admin rights.

    What to do? I was ready to buy Parallels, but now I am no longer sure?? Is there an easy solution to my problem?
     
  6. Jorisv

    Jorisv Bit poster

    Messages:
    2
    Path does not exist: ready to buy without this message

    Same for me: as owner of Parallels 4 I was ready to upgrade ad get rid of this bulky HP laptop I hate.
    I have to use Windows for work, but this error message is a pain in the %^&.

    Please help.
     
  7. FlorenC

    FlorenC Bit poster

    Messages:
    3
    I never managed to overcome that error with a direct transfer from the Windows machine to an external disk. This is what worked for me in addition to the above.

    - Connect the Windows laptop to the mac with an ethernet cable using the network ports.
    - Open Transporter in the windows machine and then in the mac, use the network transfer method, select the laptop from the list.
    - Let Transporter create the pvm in in the mac
    - Open the pvm and log in etc,....check it works.
    - Close the windows session and then MOVE the pvm to the external disk.

    This worked for me for a Windows XP machine.
     
  8. Jorisv

    Jorisv Bit poster

    Messages:
    2
    Thanks for responding.
    Busy doing the ethernet cable procedure now: 4 hours to go.
    What strikes me is that there is no proper KB within Parallels to tangle this issue.
     
  9. annel

    annel Bit poster

    Messages:
    1
    Is the hard disk "read only"

    My external drive marked my .pvm as a read only file. As soon as I removed that attribute (in Windows), the "this path does not exist" error went away and process proceeded smoothly.
     

Share This Page