Skip navigation
VMware

This Question is Answered (go to answer)

2 "helpful" answers available (6 pts)
47,230 Views 26 Replies Last post: Aug 10, 2010 10:05 AM by jkordish RSS
1 2 Previous Next
keninem Novice 18 posts since
Jan 9, 2009
Currently Being Moderated

Feb 20, 2009 7:37 AM

"The session is not authenticated" when trying to convert VMWare Server machine to Infrastructure Machine

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?

RDPetruska Guru User Moderators vExpert 16,760 posts since
Jan 11, 2005

Thread moved to ESXi forum.

Webio Enthusiast 63 posts since
Aug 31, 2008

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.

tbokman Novice 28 posts since
Feb 18, 2009

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!!!!

DREED Novice 2 posts since
Feb 25, 2009

 

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.

 

 

uvdl Lurker 1 posts since
Mar 29, 2007

 

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 

 

 

PatrikHansson Lurker 2 posts since
Feb 26, 2009

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.

PatrikHansson Lurker 2 posts since
Feb 26, 2009

Mine was fixed by restarting the computer that was running vCenter Converter Standalone.

DREED Novice 2 posts since
Feb 25, 2009

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.

tbokman Novice 28 posts since
Feb 18, 2009

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.

Asaf.Moalem Lurker 3 posts since
Nov 9, 2008

 

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

 

 

paulkc Novice 8 posts since
May 31, 2009

I am having this same issue but this does not seem to fix it in my case.  Any other suggestions?

natetrim Lurker 2 posts since
Jun 9, 2009

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

Bookmarked By (0)

Share This Page

Communities