VMware Cloud Community
crazyrobban
Contributor
Contributor

vconverter fails at 98% tried everything!

Hi,

This is yet another thread about vconverter stopping at 98%.


I've been searching for possible solutions and tried suggestions from about five different threads regarding this, as well as a google-translated polish vmware site with possible solutions.

As you can see, I haven't been successfull in this endevour.

The error from my converter-log is:

(converter.fault.ReconfigurationFault) {
   dynamicType = <unset>,
   faultCause = (vmodl.MethodFault) null,
   description = "Unknown exception",
   msg = "",
}
So far, I've tried converting with and without SCSI bus-logic, copied the vmscsi.dll and symmpi.sys from a vm with the OS to the source machine, tried to boot the failed conversion, only to find a simple DOS-screen with a prompt where I can't input anything, and the bios and 2003 install cd doesn't detect any disks.

I've mounted the converted disk to another machine and checked the boot.ini, and it looks just like it should.
Boot.ini:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /fastdetect /NoExecute=OptOut

Does anyone have a clue? Any help at all would be appriciated!
Thanks!
Tags (3)
Reply
0 Kudos
8 Replies
hhmz
Enthusiast
Enthusiast

Which version of vmware converter do you have?

Reply
0 Kudos
markpiontek
Contributor
Contributor

This might seem unrelated, but have you tried without the /NoExecute=OptOut in your boot.ini?

Reply
0 Kudos
crazyrobban
Contributor
Contributor

I've tried using the latest and 3.0.3, as I've seen on a few forums that it could possibly help in some cases.

Reply
0 Kudos
crazyrobban
Contributor
Contributor

I haven't tried that no. What does the parameter do exactly?

Reply
0 Kudos
markpiontek
Contributor
Contributor

Here is info on the parameter: http://msdn.microsoft.com/en-us/library/ff557134%28v=vs.85%29.aspx

Like I said, I know it sounds unrelated, but I had a similar issue when I had the /3GB switch on my Exchange server.  You can probably go ahead and put the switch back after converting -- and it may not even solve the probelm, but I figure it's worth a try.

After fighting and searching for a very long time with my Exchange server, I decided that a "plain" boot.ini is the only way to go.

Reply
0 Kudos
markpiontek
Contributor
Contributor

Also unrelated to your issue, BUT related to Data Execution Prevention: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101386...

Seeing this would be enough to get me to try it.  I know how frustrating this is!

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

Have you tried also the latest version of Converter?

PS: thread moved from ESX to Converter forum.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
continuum
Immortal
Immortal

to attack this problem we need to know what exactly happens when you boot the VM
- post a screenshot
we also need the current vmx-file


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos