- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am trying to convert a windows 2008 R2 system to a VM and using VMware converter v6. but the task fails at 1% with an error A file I/O error occurred while accessing ''.
please find the screenshot of the error and logs.
Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Should you upload log bundle?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The most important log in this case: the agent's one is missing, find it in the source machine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
how i can solve it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i can reach source server from vcenter and all port open between them, so where is the problem ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The agent logs are placed on source machine (i.e. machine to be converted) and this log will help us to understand where the problem is.
I can't say why you can't see the problem, but from my (remote) perspective, there is no chance to help, at least, without log files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The worker log mentions that the agent log has been retrieved. Export the failed task log bundle, it should be in it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi
i solved the problem the port between Source and ESXi Host close after open it the process work Port is 902
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
if it helps anyone, I had the same issue. for me the fix was the source machine could not resolve the names of the esxi hosts. manually adding them and the vcenter IP's to the hosts file fixed it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That was wracking my brain, Updating the host file with the ESXi host name on the source machine, sorted the problem
Thanks