I see "Bitdefender Virus Shield" as VSSERV service. Disable it or uninstall it and try again.
HTH
And that was it. I uninstalled Bitdefender (I had previously just stopped it) and it is now running. It believes it has 12 hours to go, so I can just let it run.
So, my question now... Apparently 6.2 doesnt support XP. Is there a version I can download that does? Do I just let this run? Or should I stop it and do it with something that is supported?
6.2 does not officially support XP, but the logic is there. This is an issue with antivirus programs. Even if you installed 5.5 (the last version that officially supports XP), you would still need to disable or uninstall AV programs.
So it seems disabling it didnt help, I had to actually completely uninstall it.
6.2 did, indeed create the VM from my xp install.
So, it took about 9 hours to create the VM and the VM booted fine, asked me to re-activate windows, and then loaded in well enough. It did give me a problem trying to open my visual studio product, as if all of my registered components were unregistered. I need to see if that is something that happened during the import process, or if I broke it on the origin server when trying to troubleshoot the VSS snapshot.
Thank for the help, everyone. I'll let you know if the current issue is creation-related.
So yeah... the original machines is still good. Only the VM is having an issue with the controls.
Anyone have any idea how I can handle this without trying to go and find each installation and re-installing all of the installed components?
Die Installation vom Converter Standalone wird immer mit
einer Fehlermeldung beendet. Was ist der Grund?
Willkommen im Forum,
im "%temp%" Verzeichnis müsste eine Installation-Logdatei erstellt worden sein.
Diese sollte Einträge zu der Fehlersituation enthalten. Im Zweifel, häng bitte die Logdatei an Deine nächste Antwort mit an.
André
Discussion moved from Technical Community Resources and Help to Converter Standalone
I will also chime in that this is not working for me either.
I have added Everyone and VM_Conv_SA users to the share with full rights.
The job is logged in as Administrator on both client and server.
It creates a folder for the VM on the server, creates a .vmdk and a .vmx file
and a folder labelled, testpc.vmdk.lck. Inside are two .lck files. Then the job
exits with "Unable to obtain the lock on virtual disks". The above mentioned files
are then deleted.
The remote system is a powered on windows 10 PC with a locally deployed agent.
Well,5 hours of $#@% with this. I could have rebuilt it from scratch by now.
Worthless.
Folks,
We have a Windows 10 Surface Book Pro that we are attempting to P2V.
We are using the stand-alone client and after the process completes we go to startup the machine it keeps looping on the Automatic Repair with no resolution.
Please advise.
Thanks.
-JJ
Converter doesn't support Surface Book and never tested with.
The problem should be with some kind of hardware/drivers, could you upload log bundle for check?
Hello,
I had the same problem with the same error message.
The problem was the network connection. The card used was losing the connection to vCenter or ESX
So for me no problem of disk or service on the physical machine
I believe the issue to be in this instance, the motherboard chipset is nVidia nForce.
The converter software is not able to retrieve complete disk information which may be
a Windows issue. nForce is not a supported Windows 10 chipset, but a machine so
upgraded will continue to function using the previously installed chipset drivers.
I have seen other disk related issues surrounding nForce machines updated to Windows 10.
This is what I am seeing in the log.
2018-02-14T16:15:59.265-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Parsing \\Vm1\u\demo1\demo1.vmx
2018-02-14T16:15:59.281-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] [BaseDiskSetComputer::OpenDiskSet] Will use open retries count 3
2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading partition table
2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, mntapi error: 176
2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition:Invalid sector magic number.
2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition:Invalid sector magic number.
2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] [PopulateCapabilities] Volume-based cloning was disabled due to: <no volumes are recognized>
2018-02-14T16:15:59.314-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] [LogMessagesForQA] System volume is not detected.
2018-02-14T16:15:59.314-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] [BaseComputerImpl::Open] Config file: \\Vm1\u\demo1\demo1.vmx
2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition:Invalid sector magic number.
2018-02-14T16:15:59.316-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ---------------------------
2018-02-14T16:15:59.316-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ....Creating MBR Partition Table ....
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ..... Partition Entry: 0 .....
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] .....Current Partition Offset 0: .....
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Boot Indicator: 0X80
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Partition Type Id 0X7
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Starting Head 32
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Starting Sector 33
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Starting Cylinder 0
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Ending Head 45
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Ending Sector 63
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Ending Cylinder 1023
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Relative Sectors 2048
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Total Sectors 124119040
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] --------------------------
2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition 0: offset: 0
2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk signature found 489802585, disk size in sectors 124125184, sector size 512
2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition found type HPFS/NTFS(7) name:HPFS/NTFS start:2048 size:124119040 attribs:0x0 active primary
2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk with signature 489802585, recognized partitions 1
2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] TargetVmManagerImpl::PartitionTargetDisks: Target Disk Id: disk-5
2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] TargetVmManagerImpl::PartitionTargetDisks: Source volume Id: \WindowsBitmapDriverVolumeId=[59-CB-31-1D-00-00-10-00-00-00-00-00] Target Volume Id: 95;,13=10000010000000000
2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[07292] [Originator@6876 sub=ThreadPool] Thread enlisted
2018-02-14T16:15:59.322-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Scheduled timer canceled, StopKeepAlive succeeds
2018-02-14T16:15:59.391-05:00 info vmware-converter-worker[03856] [Originator@6876 sub=Default] Stopped impersonating in session 52b8335a-5624-fccb-77e6-f9ab9d4dfed8
2018-02-14T16:15:59.391-05:00 info vmware-converter-worker[03856] [Originator@6876 sub=Default] Session is closing, releasing cached session objects
Hello Folks,
I have a scenario to convert the Physical Server to Virtual Servers below are the details
SQL CLUSTER:
OS: Win Srv 2008 R2
APP: SQL 2008 R2
Two SQL Server cluster
Disks are RDM except the local OS
Exchange DAG:
OS: Win Srv 2012 R2
APP: Exchange 2016 CU7
Three Members DAG
Disks are RDM except the local OS
I want to use VMware Converter 6.2, please advise me with some tips and tricks which will be involved for successful migration.
Esxi is 6.5 Enterprise
Thanks,
Arif
In reviewing the logs it appears to be that the ntoskrnl.exe is corrupt.
I have attached the error.
Any thoughts?
Please advise.
Thanks.
John
I'm attempting to convert a physical machine for Workstation 14 Pro with standalone converter 6.2.
It's failing after about 2 minutes with "FAILED: Unable to obtain the lock on virtual disks". The log file shows "Unexpected Exception: converter.fault.DiskLockFault".
The destination folder is empty.
I can manually copy files to the destination folder from the source machine.
The source machine is Windows 7 Ultimate.
The destination machine is Windows 10 Pro.
The destination folder is on a local drive, and it is specified as \\local-machine\local-folder.
In permissions for the folder and sharing, I have given full access to:
Everyone, NETWORK SERVICE, __VMware_Conv_SA__, __vmware__, Administrator, and Administrators.
Please help!
Thanks in advance,
Frank
I've meant converter logs.
Ok, there is a regression with file shares in latest Converter.
Option one - try previous version, option two - install and run Converter on source machine, connect the UI to *local* server (as administrator), and perform conversion of this-local-machine to *local* folder (probably USB drive).
HTH
Thanks. I installed v6.1.1 and the problem disappeared.
Cool it worked for me
Thanks lot
Cheers
I found on different places in the internet this version of Vmware converter 4.3.0, which i need to do a P2V conversion of a very old RedHat box.
I also found those
MD5: 222485c4eb94767378d76237245349cf
SHA1: 173e03fa689155ead54cad7f0c7acc5e363670ed
How can I be sure both file and hashes haven't been tampered with?
VmWare graciously removed from their site a tool I need to process that box.
Any help would be greatly appreciated.
LZ