Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1768
  • Last Modified:

VMWare Converter cannot find directory when trying to convert machine, but only on some sources.

OK so this one is really odd...........

I've got 2 x ESXi servers.   I have 1 x XP SP3 workstation running VMWare converter 4.01 standalone with an external USB drive attached.

Each ESXi server has about 5 VM's running on it.  

Lets called them VM1, VM2, VM3 etc for ease of explaining.

So I setup a conversion job on my XP workstation to convert VM1 to an image on the external HDD.   This works perfectly.

Then I setup the same job on the same XP workstation to convert VM2 to an image on the external HDD, that also works.

Then when I try to do exactly the same to VM3 I enter the login details and the name of the machine and it accepts that and moves onto the next stage where it asks for the UNC name for the image files (now this is exactly the same UNC path as the first 2 which worked perfectly but now I get the error "The specified directory \\PCNAME\SHARENAME\ does not exist"

Now of course the UNC name does exist and has worked perfectly for the first 2 with no issues, but won't do this machine, or VM4, but VM5 works perfectly........

Just to see what was going on I deleted the images for VM1 and VM2 I created earlier and recreated the converter jobs and on those servers they work no worries over and over, but for VM3 and VM4 servers I just get this error about the directory not existing..........

I'm confused !

I would have assumed that anything like a restart of the services or the XP workstation wasn't worth trying as the other servers convert perfectly, but I restarted it anyhow and no change.

Any ideas ?
0
rheanz
Asked:
rheanz
1 Solution
 
EikromanCommented:
Hi,

When you specify the destination, the connection is done from the VM itself. It may be that this particular VM can't see the share as you specify it.
Login to VM3 and VM4 via RDP or Console, and check if you are able to access this share via exactly the same path as you type it in the converter?

Are those XPs are in the same domain or workgroup? Do you specify "connect as" in the converter or just connect by default? XPs in a same workgroup will try to authenticate by default using credentials stored locally, however, if those differ from other machines in the same workgoup the auth process will fail and converter display the message that directory doesn't exists.
0
 
Luciano PatrãoICT Senior Infraestructure Engineer Commented:
Hi

Have you try using the ISO vConverter BootCD and do a cold migration on that VM?

Jail
0
 
vmwarun - ArunCommented:
What are the operating systems running on the 5 VMs ?
Are they one and the same with the same service pack level and updates level ?
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
vmwarun - ArunCommented:
What exactly do you mean by image ? Are you trying to copy VMX and VMDK files to the USB Drive ?
0
 
rheanzAuthor Commented:
Alll of the machines are running Windows Server 2003 Standard SP2 with the same service packs.

Some of them are domain controllers and some are just domain members, but they're all on the same domain.

I'll give your tip about connecting to the VM consoles and see if I can get to the resource on the XP workstation.    I have tried with no password and with passwords with no joy.

If I use an incorrect password I get an error saying something like "cannot connect to share" or "cannot find share" which I'd expect and then when I use the correct username or just leave it blank it changes to the message I posted originally, like it can see the share, but can't find the directory for some reason......... maybe permissions, but I'll do the direct connect thing and see what happens.......
0
 
rheanzAuthor Commented:
Even though the machines are part of the domain they can also of course still use local accounts on the server for authentication, so it was just a matter of connecting to the server using the local administrator account and password and then using the connect as option to then connect to the XP Workstation running VMWare converter using the right username and password to authenticate properly.

Connecting to the local console and testing if I could connect to the XP Workstation wasn't really a true way to test things as windows will pass stored authentication possibly, but it pointed me in the right direction and also one of the 3 machines that was failing was having a seperate issue which confused things...... !  That's something seperate I'm going to have to resolve.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now