The image was a Linux P2V conversion... I didn't have my ESXi server on the same network, so I just used the bootdisk from Converter 3.0.3 to create my virtual image(RHEL 4), and now I am trying to use converter 4 to convert the image from Server to the ESXi server. When I do a "Convert", I select "VMware Workstation or other VMware virtual machine" choice, browse my virtual machine .vmx file. On the next screen I choose "VMware Infrastructure Virtual Machine" in the drop down and put my server's information, including password, in the boxes below. I click next and that works fine, it connects. From there I leave all the defaults and click next...immedietely at the top of the window I get "The session is not authenticated." I didn't find anything with the search function, apologize if I missed something. Anyone else encountered this?
This happened to me when the time updated on the ESXi box causing a mismatch in the session information on the host which I was attempting to convert.
The fix was to bounce the converter agent on the server you are attempting to convert. Worked for me right away.
No one has seen this at all?
Thread moved to ESXi forum.
I'm having similar issue. I'm trying to use Converter 4 to convert/move "this machine" (which is Windows 2008 located on one ESXi server) to another ESXi server (without shutting down Windows during conversion). When I was using Converter 4 Beta this worked without problems but now after entering second ESXi host, login and password I see list of VM already located on this ESXi server and when I try to press Next I see "The session is not authenticated". This is for sure no timeout (5 seconds of waiting or less). Any idea what could cause this?
EDIT: I'm using Converter 4 build 146302. Both ESXi servers are 3.5 build 143129.
I've just tryed conversion where source is "VMWare Infrastructure virtual machine" and I had exactly the same error in the same conversion step (selection storage and virtual machine name). I've restarted both ESXi servers before conversion.
Same problem. It did work on 2 VMs that I did this morning but now getting this same error. I'm also using Converter 4 build 146302. HELPPPP!!!!
This happened to me when the time updated on the ESXi box causing a mismatch in the session information on the host which I was attempting to convert.
The fix was to bounce the converter agent on the server you are attempting to convert. Worked for me right away.
Hello,
I tried to convert a vmware workstation image to ESXi. Also using the new converter 4.0.0-146302. First time it worked. (Although I cancelled the session because it consumed too much time and CPU).
When I started the convertion job again, I received this error.
What is meant by bouncing the converter???
grtz Ulrik
I´m having the same problem. New to the ESX product so i tried creating a new user and after that it worked a couple of times yesterday, but today it´s the same problem.
Mine was fixed by restarting the computer that was running vCenter Converter Standalone.
Check the date/time settings on the server your trying to convert, if for some reason they dont match the ESXi server, fix it and restart the VMWare converter agent.
This fixed my problem as well, thanks!
It works now. Using task manager I found there were 2 instances of the converter program running. I cancelled both and then restarted the converter. Thanks for all your suggestions.
the converter was running on two sessions on the same VM host machine closed one session the closed the converter, then killed the vm converter process
work liked charm
thanks to all....
Asaf.Moalem
I am having this same issue but this does not seem to fix it in my case. Any other suggestions?
I had the same issue after updating the time on my ESXi server.
Restarting the VMware vCenter Converter service on the server running the converter did the trick for me.
Obviously, I didn't have any tasks running.
-nate
Had the same issue. I actually have VMWare Converter running on my PC (Admin).
Tried resetting matching the time - that didn't work.
Stopped and started the converter services (both) - That worked!
I found there were 2 instances of VMware Converter when I open Task Manager. Cancelled both process and then restarted Converter services fixed the issue.
From what I can tell, those 2 programs are the Services running in background.
Instead of killing them with the Task Manager, you can restart them via the Services MMC in the control panel.
VMware vCenter Converter Agent
VMware vCenter Converter Server
I experienced this problem after reloading the ESXi box with a newer version.
My guess would be the SSL tunnel key had changed, and the Converter was still using the older version.
That's why the reboot or (kill program) method resolved the issue.
Restart both services helped me well.
Try this first
Had the same issue and I stopped and started the converter services (both) from taskmanager and that worked!.