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?
Killed both instances of Converter in Task Manager and worked like a charm.
None of the obove solutions helped me, but I figured it out.
1) Uninstalled the Agent on the server you are trying to P2V
2) Start the process over and let Converter installe the Agent again.
- Worked for me.
I guess that the reason for this problem is that I canceled the P2V task in midprocess because I had some transfer problems. After a restart of the converter process, I guess the Converter service lost the login for the agent it installed, or something. It is not trying to login anyways, and sais: The session is not authenticated.
I just restarted the Server (on the Converter Server) and re-started the converter agent on the machine I wanted to convert.
That did the trick!
I have the same problem , to solve i only kiil the instances of vmware converter stand alone 4 in my task manager and thath solves the proble, thank you for the assistance.
I had the same problem , to solve i only killed the instances of vmware
converter stand alone 4 in my task manager and that solved the problem, thankyou very much
Hi,
i've been getting the same message and on that screen i cannot select virtual hardware version - so - i just restarted the two fckn retarded converter processes on machine that was doing converting proces and that fixed this issue for me.
==============================
Can anyone from vmware please fix this?
To reproduce you have to install & start converter client at day 1, on machine "its-me-converter.domain.local..." , then convert some (1+) machines to server "its-me-esxi4-server.domain.local....", close that retard, wait for day 2 morning and then try to convert on the same machine "its-me-converter.domain.local..." sometning ... to a server "its-me-esxi4-server.domain.local..." you simply can't without restarting that proceses. Hmhmhm epic fail is simply epic, huh?
So I actually had this problem yesterday and it took me some time to figure out the fix. I tried many of the same fixes that people mentioned here to no avail. Rebooted esxi server, restart services, restart converter, upgraded esxi 4 to esxi 4.1, etc
I created another local account on the esxi 4.1 host and gave it admin privileges. Then used the new account when connecting to the esx host in converter. Worked and hasn't broke on me yet.
Hope that helps someone
I have the same issue transfering a VM from a 3.5 ESXi to 5.0 ESX with converter.... I set the time in all servers, but only restarting both Vmware Converse services WORK! Like a charm! Thanks for advice!