So I've run roughly 150 or so successful conversions of RHEL (3 & 4) and MS Windows OS (200, 2003) into my VI3.5 VC2.5 environment using Standalone Converter 4.0.1 but now seem to be getting this error on almost 90% of my conversion attempts. It seems to be having trouble starting the VM for the bits copy into the new VM. Usually this happens at the beginning of the conversion process and so I never get a VM but occasionally I can go thorough a complete conversion and then the VM won't start AFTER a successful Converter outcome. Logs excerpt in-line, full attached.
EXCERPT ###############
Waiting for vim.Task:task-139151 to complete
TaskImpl has failed with Vmacore::Exception: failed to poweron vm
Volume-based cloning IPremoved.230.15 --> bladesrvr02 updates, state: 4, percentage: 0, xfer rate (Bps):
Failed to perform PostDoRun task in Linux P2V while retrieving the log bundle: helper connection or task hasn't been created
powering off vm after linux p2v ...
Getting VIM connection to IPremoved.1.223...
Reusing existing VIM connection to IPremoved.1.223
Waiting for vim.Task:task-139152 to complete
failed to perform PostDoRun task in Linux P2V: failed to power off vm
ConvertTask updates, state: 4, percentage: 1, xfer rate (Bps):
ConvertTask removing target VM when cloning is Failed/Canceled
Getting VIM connection to IPremoved.1.223...
Reusing existing VIM connection to IPremoved.1.223
Destroying vim.VirtualMachine:vm-648905 on IPremoved.1.223
HTTP Response: Complete (processed 1126 bytes)
User agent is 'VMware-client/4.0.0'
HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
Waiting for vim.Task:task-139153 to complete
RecordOp ADD: event[36], task-5
Converter Task SetError(taskID=task-5)
Completing task task-5 with state=3
Converter TaskManager TaskCompleted
VimConnectionStore stopping keepalive
Scheduled timer canceled, StopKeepAlive succeeds
Converter Task GetEvent(taskID=task-5)
HTTP Response: Complete (processed 1476 bytes)
User agent is 'VMware-client/4.0.0'
HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
User agent is 'VMware-client/4.0.0'
HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
http://Converter.Agent.DiagnosticManagerImpl[task-5] Generating TaskLogBundle.
http://Converter.Agent.DiagnosticManagerImpl[task-5] Generated bundle key = "task-5-ohagcquq.zip"
http://Converter.Agent.DiagnosticManagerImpl[task-5] Bundle will be placed in "C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\log-bundles\"
http://Converter.Agent.DiagnosticManagerImpl[task-5] Archiving logs in "C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\logs"
Destroying VmomiTask2InternalTaskAdapter
Archiving "C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\logs" to "C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\log-bundles\task-5-ohagcquq.zip" succeeded
http://Converter.Agent.DiagnosticManagerImpl Created Log Bundle "task-5-ohagcquq.zip" with size "1365889" and CRC "-880338508"
HTTP Response: Complete (processed 624 bytes)
User agent is 'VMware-client/4.0.0'
HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
http://Converter.Agent.DiagnosticManagerImpl Retrieving log bundle with key "task-5-ohagcquq.zip" at offset = "0" and max size = "1365889".
HTTP Response: Complete (processed 1821641 bytes)
User agent is 'VMware-client/4.0.0'
HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)
http://Converter.Agent.DiagnosticManagerImpl Deleting log bundle with key "task-5-ohagcquq.zip"
Thanks for the reply.
Already unticked though. I get this message most often before the conversion even starts to transfer bits, if I'm lucky to get a full conversion then the vCenter won't let me power it on post-conversion.
I have narrowed it down to a particular vCenter DB instance as I am:
1. Able to convert the same source server to another vCenter instance on a different VI and
2. can convert to the same VI by converting directly to an ESX host rather than the aforementioned vCenter.
If I can get the DBAs to uncover any DB anomalies (and a fix) I'll let you know.
Any update on this? I'm seeing the same thing.
so you still use Converter 4.0.1 with ESX 3.5 ???