Results 1 to 6 of 6

Thread: Can't connecto to ESX 4.0 Host

  1. #1
    Junior Member
    Join Date
    Sep 2014
    Posts
    3

    Can't connecto to ESX 4.0 Host

    Hi.

    I'm trying to convert a VMware VM running on a VMware ESX 4.0 host with 5nine's converter.

    If I try to connect to the host directly it fails with a generic "cannot connect to host, IP address, name or userid/password incorrect" type error.

    I checked the convertor.trace file in the converter directory and got this:

    VMware Verbose: 1 : Timestamp: 17/09/2014 05:27:08 p.m.
    Message: VMwareProvider.Authenticate: authenticating user 'root' on host 'bspvirt1.bsp.com.ve'
    Category: VMware
    Priority: -1
    EventId: 1
    Severity: Verbose
    Title:
    Machine: SERVER02
    App Domain: 59Converter.exe
    ProcessId: 4544
    Process Name: C:\Program Files\5nine\5nine EasyConverter\59Converter.exe
    Thread Name:
    Win32 ThreadId:4212
    Extended Properties:
    VMware Verbose: 1 : Timestamp: 17/09/2014 05:27:08 p.m.
    Message: VMwareProvider.Authenticate: updating service URL.
    Category: VMware
    Priority: -1
    EventId: 1
    Severity: Verbose
    Title:
    Machine: SERVER02
    App Domain: 59Converter.exe
    ProcessId: 4544
    Process Name: C:\Program Files\5nine\5nine EasyConverter\59Converter.exe
    Thread Name:
    Win32 ThreadId:4212
    Extended Properties:
    Diagnostic Critical: 999 : Timestamp: 17/09/2014 05:28:18 p.m.
    Message: HandlingInstanceID: b4c4f2aa-95f8-4c83-ad2d-c2177c489e06
    An exception of type 'System.TimeoutException' occurred and was caught.
    -----------------------------------------------------------------------
    09/17/2014 12:58:18
    Type : System.TimeoutException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Message : The request channel timed out while waiting for a reply after 00:00:55.2647292. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
    Source : mscorlib
    Help link :
    Data : System.Collections.ListDictionaryInternal
    TargetSite : Void HandleReturnMessage(System.Runtime.Remoting.Messag ing.IMessage, System.Runtime.Remoting.Messaging.IMessage)
    HResult : -2146233083
    Stack Trace :
    Server stack trace:
    at System.ServiceModel.Channels.RequestChannel.Reques t(Message message, TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.Call(S tring action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannelProxy.I nvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
    at System.ServiceModel.Channels.ServiceChannelProxy.I nvoke(IMessage message)

    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleRe turnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateI nvoke(MessageData& msgData, Int32 type)
    at VimApi.VimPortType.RetrieveServiceContent(ManagedO bjectReference _this)
    at FiveNine.Migration.VMware.VMwareProvider.Authentic ate(String address, String userName, String password)
    at FiveNine.Migration.ProviderFactory.CreateSession(P latform platform, String address, String userName, String password)
    at FiveNine.Migration.EasyConvertor.Wizard.MigrationC ontext.StartVMWareSession(String hostAddress, String userName, String password)

    Additional Info:

    MachineName : SERVER02
    TimeStamp : 17/09/2014 05:28:18 p.m.
    FullName : 5Nine.Migration.Diagnostic, Version=1.0.7.0, Culture=neutral, PublicKeyToken=null
    AppDomainName : 59Converter.exe
    ThreadIdentity :
    WindowsIdentity : SERVER02\Administrator
    Inner Exception
    ---------------
    Type : System.TimeoutException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Message : The HTTP request to 'https://bspvirt1.bsp.com.ve/sdk' has exceeded the allotted timeout of 00:00:59.9810000. The time allotted to this operation may have been a portion of a longer timeout.
    Source : System.ServiceModel
    Help link :
    Data : System.Collections.ListDictionaryInternal
    TargetSite : System.Net.HttpWebResponse ProcessGetResponseWebException(System.Net.WebExcep tion, System.Net.HttpWebRequest, System.ServiceModel.Channels.HttpAbortReason)
    HResult : -2146233083
    Stack Trace : at System.ServiceModel.Channels.HttpChannelUtilities. ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
    at System.ServiceModel.Channels.HttpChannelFactory`1. HttpRequestChannel.HttpChannelRequest.WaitForReply (TimeSpan timeout)
    at System.ServiceModel.Channels.RequestChannel.Reques t(Message message, TimeSpan timeout)

    Inner Exception
    ---------------
    Type : System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Message : The operation has timed out
    Source : System
    Help link :
    Status : Timeout
    Response :
    Data : System.Collections.ListDictionaryInternal
    TargetSite : System.Net.WebResponse GetResponse()
    HResult : -2146233079
    Stack Trace : at System.Net.HttpWebRequest.GetResponse()
    at System.ServiceModel.Channels.HttpChannelFactory`1. HttpRequestChannel.HttpChannelRequest.WaitForReply (TimeSpan timeout)


    Category: Diagnostic
    Priority: 1
    EventId: 999
    Severity: Critical
    Title:Exception
    Machine: SERVER02
    App Domain: 59Converter.exe
    ProcessId: 4544
    Process Name: C:\Program Files\5nine\5nine EasyConverter\59Converter.exe
    Thread Name:
    Win32 ThreadId:4212
    Extended Properties:
    Diagnostic Critical: 999 : Timestamp: 17/09/2014 05:28:18 p.m.
    Message: HandlingInstanceID: 5928bde4-30cc-452b-a085-994556362355
    An exception of type 'System.InvalidOperationException' occurred and was caught.
    --------------------------------------------------------------------------------
    09/17/2014 12:58:18
    Type : System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Message : Failed to connect to host
    Source :
    Help link :
    Data : System.Collections.ListDictionaryInternal
    TargetSite :
    HResult : -2146233079
    Stack Trace : The stack trace is unavailable.
    Additional Info:

    MachineName : SERVER02
    TimeStamp : 17/09/2014 05:28:18 p.m.
    FullName : 5Nine.Migration.Diagnostic, Version=1.0.7.0, Culture=neutral, PublicKeyToken=null
    AppDomainName : 59Converter.exe
    ThreadIdentity :
    WindowsIdentity : SERVER02\Administrator

    Category: Diagnostic
    Priority: 1
    EventId: 999
    Severity: Critical
    Title:Exception
    Machine: SERVER02
    App Domain: 59Converter.exe
    ProcessId: 4544
    Process Name: C:\Program Files\5nine\5nine EasyConverter\59Converter.exe
    Thread Name:
    Win32 ThreadId:4212
    Extended Properties:
    Diagnostic Critical: 999 : Timestamp: 17/09/2014 05:28:18 p.m.
    Message: HandlingInstanceID: 0892397e-ae4c-42a4-b98e-3fb6ae88af80
    An exception of type 'System.InvalidOperationException' occurred and was caught.
    --------------------------------------------------------------------------------
    09/17/2014 12:58:18
    Type : System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Message : Failed to connect to host
    Source : 5Nine.Migration.Diagnostic
    Help link :
    Data : System.Collections.ListDictionaryInternal
    TargetSite : Void RaiseException(System.Exception)
    HResult : -2146233079
    Stack Trace : at FiveNine.Migration.Diagnostic.ExceptionHandling.Ex ceptionPolicy.RaiseException(Exception ex)
    at FiveNine.Migration.EasyConvertor.Wizard.MigrateFro mESXToHyperVMultiple.SelectSource.StartSession(Obj ect context, Int32 i)
    at FiveNine.Migration.EasyConvertor.Dialogs.Backgroun dHyperVMultipleActionDlg.OnDoWork(Object sender, DoWorkEventArgs e)

    Additional Info:

    MachineName : SERVER02
    TimeStamp : 17/09/2014 05:28:18 p.m.
    FullName : 5Nine.Migration.Diagnostic, Version=1.0.7.0, Culture=neutral, PublicKeyToken=null
    AppDomainName : 59Converter.exe
    ThreadIdentity :
    WindowsIdentity : SERVER02\Administrator

    Category: Diagnostic
    Priority: 1
    EventId: 999
    Severity: Critical
    Title:Exception
    Machine: SERVER02
    App Domain: 59Converter.exe
    ProcessId: 4544
    Process Name: C:\Program Files\5nine\5nine EasyConverter\59Converter.exe
    Thread Name:
    Win32 ThreadId:4212
    Extended Properties:

    If I try to connect through vCenter 4.1 it lets me in but I can't see the Hosts.


    Any ideas on what could be going on?

  2. #2
    Administrator
    Join Date
    Jul 2013
    Posts
    118
    Hello Imprecator,

    5nine V2V Easy Converter fully supports ESXi 4.1 and up. ESXi 4.0 may be causing some issues, like yours.

    Which 5nine V2V Easy Converter and which Hyper-V version are you using?

    Alexander

  3. #3
    Junior Member
    Join Date
    Sep 2014
    Posts
    3
    Hello Alexander:

    I am using 5nine V2V Easy Converter Free Edition, version 4.2 and I am attempting to convert the VMs to Hyper-V 2.0 (Windows Server 2008R2).

  4. #4
    Administrator
    Join Date
    Jul 2013
    Posts
    118
    Imprecator, minimum supported version of Hyper-V is 2008 R2 SP1.
    Also, lease make sure, that you are using 5nine V2V Easy Converter for 2008 R2 SP1: you can find it within the package in EasyConverter2008_R2_SP1.ZIP file.

    Alexander

  5. #5
    Junior Member
    Join Date
    Sep 2014
    Posts
    3
    Hello Alexander.

    Yes, I am using Hyper-V 2008 SP1 (on Windows 2008R2 SP1)

    I did try the package mentioned.

    The error seems to be a timeout on VMWare's Web Services. now I am using ESX 4.0, not ESXi, so that's probably why it fails.

    Thanks.

  6. #6
    Administrator
    Join Date
    Jul 2013
    Posts
    118
    You are right, ESX is not supported.