Hi,

I am getting the following error when using Converter Server to import Hyper-V and Powered-on machines - Permission to perform this operation was denied

I have installed Converter directly on the machine that was getting the same issue and it imports fine!

I have disabled UAC on Converter Server, reinstalled it, built a new VM and installed Converter again!

There is a few errors in the logs

2013-11-04T14:21:04.551+13:00 [02076 error 'Ufa.HTTPService'] Failed to read request; stream: <io_obj p:0x01fd94ec, h:-1, <pipe '\\.\pipe\vmware-converter-server-soap'>, <pipe '\\.\pipe\vmware-converter-server-soap'>>, error: class Vmacore::TimeoutException(Operation timed out)

I have disabled SSL on the Converter Server worker process but this didn't work

I have 30 Hyper-V VMs to import and cannot do this one by one!

Cheers,

Matt

I am running Converter on Windows 7 ans trying to make a virtual machine of the current installation to upgrade to Windows 10.

Whenever I start to use the converter I get this error message "Unable to complete Converter agent installation on Dell-9020.  Another version of this product is already installed.

I have looked around the machine and the only one I can find is the current installation.

Anyone any ideas.  Thanks

Hello everyone,

I am trying to hot-P2V a Win8 64bit OS which came pre-installed on my new notebook (it's an OEM license so I don't have the OS installation discs and thus cannot create a VM from scratch).

Unfortunately, like many people before me, I experienced this error while reconfiguring the newly-created virtual hard disk.

I read that the cause of this problem is an inaccurate BCD configuration: VMware KB: P2V conversion using VMware Converter fails with the error: Unable to find the system volume, reconfigura…

This post states that I'm supposed to import the virtual machine to vCenter Server and repair the VM's BCD from there.

Unfortunately I do not own this software and tried to import the VM in VMware Converter and run "Configure Machine" to fix the BCD data but no, I get the same error.

I should also mention that I did NOT install VMware Tools on this VM.

I spent some time reading articles about what BCD actually is and I more or less understood WHAT to do but still need a hand on HOW to do it.

Comparing my BCD with my Control Panel --> Disk Management it looks like the partitions are laid out correctly:

the first is a Win rec. partition (400Mb), then you have the boot partition (260Mb) and then the OS partition (drive C:).

The Z: volume is merely a data partition where I put music and movies and was not included in the VM.

Finally, the D: volume is a Hewlett Packard rec. partition. - this was not included in the VM either.

The BCD says the {bootmgr} is '\Device\HarddiskVolume2', so it seems to mirror the Disk Management structure.

But I'm no expert at all so here I am, asking for help.

I am attaching VMware Converter's logs and screenshots of my Win8 BCD and Disk Management.

Apart from solving my issue I'm especially interested in understanding WHY this problem occurs so I can learn and be better prepared for the next time.

Thanks a lot for your help,

Regards.

Stef

I've been trying to download a copy of a couple of my SuSE Linux servers so I can test doing upgrades but I keep experiencing failures with the subject line error message.  I used to be able to do this process all of the time but apparently times and technology has changed and it fails now.

I'm working with the following:

vCenter 6.0 appliance, build 3617395

vCenter Converter Standalone 6.1.1 build 3533064 running on Windows 10 x64 version 1607

First I create a clone instance of the server that I want to get a backup of so I can have it in an "off" state to run the converter process.

I run vCenter Converter "as Administrator" and fill in the blanks to copy the clone from vCenter to a local folder on my PC.  vCenter Converter is installed with both the client and server components on my local system.

The process runs and gets to 99%, I can verify that the files have copied to the directory on my local machine and then it experiences the error "The session does not have the required permissions."

The copy of the VM on my local machine vanishes and I'm stuck scratching my head trying to figure out what I'm missing.

I did grab the log files but I'm not experienced at reading them and they don't make much sense to me other than around the time of failure I'm seeing Unexpected Exception and faultCause = null

I really need to test these upgrades, any advice to getting this resolved?

Trying to migrate 4 VMs from 2012 R2 Hyper-V Server to a mixed vSphere 6/6.5 cluster via VMware converter 6.1.1 . I have tried converting and choosing mutliple types of disk controllers and it doesn't seem to matter I get a BSOD on VM startup with an Inaccessible_Boot_Device.

Anyone have any other ideas?

Tried the steps in the following articles

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2002106

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005208

These are all Gen1 Hyper V vms with IDE virtual disks.

I also tried this with no luck.

https://community.spiceworks.com/topic/1450429-inaccessible-boot-device-error-while-booting-windows-2012-r2

Blue screen 0x0000007B boot error with 64-bit Windows 2003 virtual machine converted from physical machine.

I am running VMWare Converter Starter Edition version 3.0.0 build-39557 installed on a Dell PowerEdge 2950 (a couple of months old) running Windows Server 2003 Enterprise x64 R2 (version 5.2.3790, SP1 with all the latest updates). The server has SCSI RAID drives (2 separate arrays for a physical C: and D: drive).

The physical machine is a new clean installation of 64-bit Windows Server 2003 with no other software installed except for VMWare Server and Converter.

I am attempting to create a virtual machine from this machine to run in VMWare Server (version 1.0.1 build-29996) on the same physical machine. The conversion appears to succeed, but when I attempt to start the new virtual machine, it begins to boot, displays the Windows 2003 startup screen briefly, and then fails with a blue screen with the following error:

STOP: 0x0000007B (0xFFFFFADFD520F3C0, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

I understand the "0x0000007B" means that it can't access the boot device for some reason. I have searched these forums and the knowledge base, but haven't found a solution to this problem.

I have been able to successfully convert and boot a 32-bit Windows Server 2003 physical machine as a virtual machine running in this same VMWare Server. I don't have any other 64-bit machines to test this with.

I am logged in directly to the console of the physical machine with the administrator account. I enabled virtualization in the BIOS. I have tried various combinations when building the virtual machine (customizing or not, fixed or variable disk sizes, importing both C: and D: drives or importing only the C: drive, etc). I have the SYSPREP files from the x64 installation disks locally on the server, and I have run SETUPMGR in this folder to create a SYSPREP.INF file. All of these various attempts have failed with the same boot error.

Is it possible to build a 64-bit virtual machine using VMWare Converter Starter Edition? Any suggestions on how to resolve this issue?

Hi everybody,

I ran across this infamous error now on my machine. I tried several other suggestions from other posts with no luck. I am trying to convert a powered off VMware Infrastructure machine (template) into a Workstation image. I get this error immediately after I select the template as the source and click next.

Any hints? I even tried to reinstall Converter (5.5) completely...

Hi,

I'm running my ESX 3.5 during the 60 days trial mode, and during this period I need to test our main servers in VM mode. For this reason I donloaded VMWare Converter 3.0.2u1 and converted two Win2003 server. But at the en of the job I was unable to login onto the new VMs because windows "must be activated". Is there a way to perform the conversion by exactly cloning the two systems, without asking for activation ? This conversion is for test only, so I cannot dismiss the real server by now. What I would like to do is convert the real server comlletely, keeping the same names, IP, etc, then switch off the real servers, power on the VMs and see if all goes ok. So, I will not run the real and virtual machine at the same time, but I need to keep the real servers ready and activated.

Is there a solution for this issue ? Thanks and bye, Stefano

Hi,

May sound like a really simple question, but I can't afford to get it wrong.

We have Windows 2003 R2 servers, which are file servers, with 100 users connected, who rely on these servers to be up during work hours. They are critical machines, and we can't really afford ANY downtime, a few seconds is fine as long as nobody notices, and that any open files that people are working on do not get lost.

Because the server has upto 1TB of data on it, we can't really estimate how long it will take to do the P2V. So we'd ideally like to start this in a morning, then perhaps do the switchover at the end of our working day, so as to not upset any of our users.

Can we do this? Can we do a P2V, and then re-run the process to find any changes that may of happened between it finishing the 1st run?

Basically, we can't really sit and watch it run all the way through, then make the switch when it's finished, because we have no way of knowing if it will finish outside working hours or not, and obviously we can't wait all night either!

We have at least 4 servers to do like this, any ideas really appreciated.

Many thanks, Alan

We're using Vcenter to P2V some of our servers. Most have worked, but the ones that fail, fail with a description that is not helpful at all.

mostRecentError = (converter.fault.CloneFault) {

--> dynamicType = <unset>,

--> faultCause = (vmodl.MethodFault) null,

--> description = "Unknown exception",

--> msg = "An error occurred during the conversion: 'Unknown exception'",

--> },

--> numConsecutiveErrors = 1,

We're tried several different ways of cloning including matching the hardware, not thin provisioning, setting permissions, using a domain admin account and still we get this error.

has anyone else had this error and figured out a solution?

Thanks.

I have read the best practices guide for converting DCs. I see that the guide does not recommend it. I do see where some say they don't ever have a issue converting DCs. I am looking for some real world feedback.

I have 2 DCs. One of which is the "backup DC" I would like to convert first. It also has several other roles along with hosting a bunch of different shares etc... I am trying to avoid having to re-setup all the other roles, services, and permissions outside of the DC role. 

What are your thoughts on me demoting the DC, converting it to a VM, and then promoting it to the DC role following the conversion?

Any guidance would be greatly appreciated.

Thanks!

Jason

Hello,

I am testing the converter standalone with some VMs after some changes in my configuration.

I have a two hosts cluster with HA and DRS and some simple VMs inside (all Ubuntu, 20 to 40GB disks, 1 to 4 vcpus, 2 to 4GB RAM).

I power off one of them, put it through the converter to a Workstation directory on the PC where the converter is installed.

I now want to get it back, I use the converter from Workstation to VMware infrastructure virtual machine and I get the message : "a component of the virtual machine is not accessible on the host".

All the same with other VMs.

I don't understand what is happening. Some blogs write about a CD ROM still connected to an ISO but it is not the case here.

Another gave a possible tip towards the fact it is a cluster but VMware does not confirm it when I look for some KB or official explanation. The cluster and some pool resources are the only changes made since the last time I converted a VM in the same way.

Is someone able to explain it, please ?

Community, be greeted.

A short backstory. I recently converter 120+ VM's from ESXi 4.1 (running clustered with vCenter) to ESXi 6.5 standalone host (standard license).

These conversions were made with vmware converter and all went by with flying colors. Now the issue is that now I'm totally unable to convert anything from the new 6.5 host. This is a must-need-feature as our users constantly move these VM's from the host to their player/workstation infrastructure.

1) First error is with the converter. Some VM's convert okay but most of them give the "Not enough permissions" at 98%

2) Second error is with the export function in ESXi 6.5 (okay, a bit off-topic). Export goes pretty far but eventually gives network/time-out error.

3) Third error is with the newest converter 6.2. This version gives me the "cannot lock disks" error straight up. It doesn't matter, whether I'm using a NFS share or trying to convert to my local disk.

So far, it might have something to do with the ctb being enabled. Permissions should be okay as I'm having the issues with full root permissions.

Any clues to any of the issues mentioned above? All help is highly appreciated. Currently the only option for moving the VM's is through sftp and it doesn't sound like a plan for tomorrow

Cheers,

Pekka

This topic has been written by automatic translation.

Please forgive me bad English.

I tried to convert the local machine of Windows 7 64 Bit.

However, the conversion does not complete with an error at 98%.

The content of the error is "FAILED: Unable to reconfigure the destination virtual machine."

A vmx file and a vmdk file are created at this point, but a blue screen error (0x7B) occurs when trying to start it.

I also tried unlocking the / 3GB switch according to vmware's KB, but it has no effect.

My Windows 7 is 64 Bit, so this KB will not be helpful.

I will attach an error log here.

i need your help.

Thank you.

There have been many complaints about transfer rate degradation in Converter 5.0.

Converter uses NFC (a proprietary VMware protocol) for cloning to managed destination. Security has been enhanced in Converter 5.0 by encrypting the data transfer. Unfortunately this has caused a more severe performance degradation than expected.
Switching off SSL encryption is a way to work around this issue. Here is how it is done:

1. Open the converter-worker.xml configuration file. It is located in "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone" folder for Windows Vista or newer or in "%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone" for older Windows versions.
2. Set the key Config/nfc/useSsl to false and save the configuration file.
3. Restart "VMware vCenter Converter Standalone Worker" service.

I.e. it should look like:

    ...    <nfc>       <readTimeoutMs>120000</readTimeoutMs>       <useSsl>false</useSsl>    ...

I've got a machine that I've been tasked to virtualize, but I never get any farther than 1%, which is wierd because a collegue of mine P2Ved this server a couple months ago and it went through. (we had to delete that VM because it wasn't brought online in time.)

The conversion doesn't fail, it just stays at 1%.

Server is a Windows Server 2003 R2 box and it's main role is Raisers Edge. I turned off all the SQL services per another post. I'm not quite sure what else to include, other than the logs.

Thanks.

Message was edited by: Awanogardn Scrubbed the logs.

Converter version: 6.2.0 build-7348398

OS: Windows 10 Pro, 64Bit, Fall Creators Update, December patch installed

Tried to convert the powered machine into a vm. I used as destination system my Unix based NAS mapped to Windows. The converter wasn't able to lock the destination and started to loop.

I cancelled the process in order to use a USB drive as destination.

When I restarted the converter, I got the the error message "Permission to perform this operation was denied." both using the "Next>" button as well as pressing "View source datails..." on the Source System step of the wizard.

I rebooted the system, I uninstalled and reinstalled the converter - nothing changed. I assume the converter didn't remove a lock entry.

I'm frustrated, each support would be appreciated.

Thanks a lot,

Peter

Using converter standalone 5.1 converting RHEL 5 to use with VMware workstation. I get the below error.

I have taken a couple of approaches to convert an existing Windows 98 physical machine to run in VMware (I am new to this, BTW).  I first tried converting the machine using the remote option but I got an error when it was attempting to install the agent.  Next I pulled the hard disk from the PC and put it in the same PC that I plan to run the VM on (WinXP Pro).  I used the local machine option and chose the hard disk containing the Windows 98 installation.  But the Wizard balked at not being able to find the OS and continuing led to eventual failure.  Not one to give up, I downloaded and installed Ghost 10 and successfully built an .sv2i image.  However, when I go to build the new vm from this standalone vm using this image I get an error when it tries to detect the operating system (Unable to determine guest operating system) and I cannot continue.

So, I thought Windows 98 was supported in a vm but am I wasting my time in trying to do this?

Thanks

Pete

The system is an ubuntu 10 system. The error I get is "FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: Installing GRUB1 on (hd0)... /vmware-updateGrub.sh: 59: grub:
not found Error installing GRUB Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root '"

The log highlights show "Error: Unable to configure the destination virtual machine"

I was so thrilled when I saw how fast the conversion was moving along. I am using vCenter Converter Standalone 5. I know I've been asking a lot of questions over the past few days and I really really appreciate all the help. Please, help me again!! Thanks,