Hi hussainbte,
as it stated before I can't create a new one as all the CNC licenses are on that particular W2K3 Server :-(
So I would virtualize it before finally crash.
Plamen gave me some instruction, I'll share it soon.
Regards,
Pal
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
Szia Plamen,
Your guideline is perfect with changing the expression at <Reconfiguration name="LsiLogic">. I decided to use "GenericWindows7"
This step helped me to get over the 96% failed situation. Now the converter finishes at 100%.
The size of the VM is about 100 GB and its located on a far server. I made the conversion via a really slow RDP Connection; with 1 M ADSL nowodays Crazy, ah?
So I asked the local tech guy to attach one USB HDD to copy the successfully converted VMDK and the VMX file and bring it to me by the end of the week.
I'll try to run that VM immediately to see if starts ok or BSOD. I'll be back to you to share the rest.
Till that time have a wonderful day:)
Regards,
Pal
↧
↧
Re: Installing VMware vCenter Converter Standalone fails on windows 7 with error : Could not extract file
Hi Damien, did you ever get to the bottom of this? I am having the exact same issue on Windows 7.
↧
Re: Installing VMware vCenter Converter Standalone fails on windows 7 with error : Could not extract file
Could you upload install logs, from %temp%\vm*.log?
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
Szia Plamen,
Got the HDD and opened the successfully converted VMDK. Result is BSOD, which restarts always until shutdown VM.
I tried different settings in Properties, like 3D acceleration off and changing the cores, but still no good result. I'M tring soon the option B, which is your second idea, but I lost with that sentence: "Load Hive" in Registry editor. I have only "import", export" and connect to a "netwok object" functions under File menu.
Also I have no idea which driver could crash and needs to be deleted to perc700 raid controller.
Could you please instruct me to achive this last step?
Prior megathanks,
Pal
↧
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
Szia Pal,
It must be that 'Load hive' is a newer functionality, from a later Windows version. Not sure whether that would work (if the registry binary format is not changed - it should), can you try to attach the vmdk to a newer Windows (7 has it for sure, 2k8 perhaps too)?
I don't know the driver name, but if you manage to attach the registry, searching for 'perc h700' in it may get you some hint.
Crossing fingers,
Plamen
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
Hello Plamen,
So now I have time to play with it. I tried to load hive, but somehow wondows 10 Enterprise doesn't see the mapped X: drive.
However Windows explorer and Total Commander can see without any problem. I "Mapped" the drive as you said.
I run regedit as administrator. VM is located on "E" drive, mapped it's C: drive as a phisical drive to see the files on them, therefore X: is visible.
I tried in HKEY_Local_machine and HKEY_User. Same . May be I forgot something...I sent you a jpg about the situation.
Please advise. Prior thanks.
Regards,
Pal
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
Hi again,
I thought it was a conversion to ESXi, that's why I was thinking to mount form another VM. It is OK from Workstation, too. I suppose you map the vmdk in a way something like that?
This should be fine. I tried that with a 2k3 VM. Windows10 can't load the registry hive but Windows7 can.
↧
Linux P2V Failed at 98% Converter 6.1
Hello
I'm trying to convert a old physical Linux server to a virtual one.
it keeps failing at 98% with a status :
FAILED: An error occurred during the conversion: 'InitrdNativePatcher failed to generate initrd image: /usr/lib/vmware-converter/initrdGenSuse.sh failed with return code: 1, and message: * /mnt/p2v-src-root/dev has 3 files /sbin/mkinitrd: illegal option -- t * user script returning code 1 * unmounting /mnt/p2v-src-root/dev /mnt/p2v-src-root/proc and /mnt/p2v-src-root/sys ERROR:
failed running mkinitrd vmlinuz-2.6.37.6-24-desktop initrd-2.6.37.6-24-desktop with chroot /mnt/p2v-src-root '
Any suggestions ?
↧
↧
'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
Hi,
Trying to install 'vCenter Converter', the installer fails with this error:
- Error -> "Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)"
- Event Viewer -> "The Vstor2 MntApi 2.0 Driver (shared) service failed to start due to the following error: A device attached to the system is not functioning"
Environment is:
- Physical Machine: HP Compaq nw8440 ( laptop )
- Operating System: Windows XP Professional SP3
- Run 'vCenter Converter' installer using 'Administrator' account
There is nothing attached to the laptop when I try to install 'vCenter Converter'
I tried:
- Several versions of 'vCenter Converter' from 4.3.0 to 5.5.3 ( all of them supporting installation in Windows XP ) -> Same error
- Uninstall / Reinstall USB ports ( USB Root Hub ) in the Physical Machine -> Same error
- Restart several times the Physical Machine -> Same error
Attached is the log file the installer generated ( invoking the installer: VMware-converter-all-5.5.0-292238.exe /v"/l*v VMwareInstall.log" ) -> Search for: '29142'
Any idea?
Thanks
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
Why aren't you using the latest version of Converter here?
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
Release Notes for vCenter Converter v.6.1 ( latest version as now ) doesn't seem to list Windows XP as a platform you can install it.
Anyway, I just tried with v.6.1 and I got the same error.
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
Update:
I tried with 'vCenter Converter v.4.0.1', that is a portable application ( it doesn't require installation ).
The cloning process started correctly but stopped at 95% with a error.
Attached goes log files for this execution
↧
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
See if this article helps: https://kb.vmware.com/s/article/1023795
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
Thanks for your support
I reviewed the article but there is not 'vmware-ufad-p2v-XXXXX' subdirectories left in the physical machine neither stcp2v30, vstor2-p2v30, vmware-ufad-p2v-XXXXX and courier-XXXXX keys in the Registry
For the execution I tried with 'vCenter Converter v.4.0.1' ( portable application ), the files attached previously ( 'log_files (vCenter Converter Standalone v.4.0.1-161434).zip' ) could be useful because contains some lines with errors but I would need some expert to review them to figure out what is the problem.
Look at:
File: vmware-converter-agent-4.log -> Searh for: "Vmount library: Error 2 while opening VSTOR2 driver's control device"
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
Hello Plamen,
I travelled 50 miles for a Win7 Enterprise edition to check the solution. That Windows 7 could not open hive from drive X neither
Any other idea? Do I need to find an XP machine? Or may be wrong with the procedure?
Prior thanks,
Pal
↧
Re: Converter Standalone 6.1 for Windows Server 2003 32 bit
Hi Pal,
I am sorry you had to go through this hassle, didn't expect that. Let me reiterate - this is not a supported scenario and I was just thinking of possible hacks to work around. I've tried loading a registry hive of a w2k3 vm in w10 and it didn't work, then it worked from w7. That's all.
The idea of the hack is to remove the raid driver's entries from the registry and then cross fingers Windows will be able to configure itself with the virtual hardware. Loading the hive from another windows machine was just the first idea that came to my mind about how to tweak that registry.
A short googling with "fix registry unbootable windows" yields this: 4 Ways to Edit Registry Key Values Without Booting into Windows • Raymond.CC. I have tried neither. Perhaps there are other ways, too.
Regards,
Plamen
↧
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
Converter 5.5 and moreover 4.x are EOL and there is no support for. Use latest Converter instead of old ones.
Ensure that no other (old) version of vstor2 driver is installed (look for HKLM\CurrentControlSet\Services\vstor2-XXXXX)
Uninstall any Converter version and reboot.
Keep in mind that Workstation also installed some vstor2 version.
Try to install Converter 6.1.x, if not succeeded then install logs are located in %TEMP%\vm*.log
HTH
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
Remove "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\vstor2-mntapi20-shared" from registry, remove "C:\Windows\system32\drivers\vstor2-mntapi20-shared.sys" or :"C:\Windows\SysWOW64\drivers\vstor2-mntapi20-shared.sys" depending on the bitness, reboot, and try installing anew.
If you have other remnants of Converter installation (i.e. it appears in "Progarns and features"), uninstall it too before rebooting.
HTH,
Plamen
↧
Re: 'vCenter Converter' fails to install with 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'
POCEH & Plamen, thanks for your support
In the past I had VMWare Workstation installed in this machine but I removed it to make sure it was no disturbing to the Converter installer
I double checked both in Regissty and file system to be sure 'vstor2' doesn't exist.
Then after rebooting the machine I tried to install Converter v.6.1.1 and the installer continues to shows the same error:
- Error -> "Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)"
- Event Viewer -> "The Vstor2 MntApi 2.0 Driver (shared) service failed to start due to the following error: A device attached to the system is not functioning"
Attached is the installer log file for this execution ( %TEMP%\vminst.log ) -> Search for: 29142
↧