VMware Cloud Community
AreasCorp
Contributor
Contributor

Connect-HVserver error

Hi all,

I'm getting this error when I try to connect with the Horizon Api :

Connect-HVServer : The request channel timed out while waiting for a reply

after 00:01:39.9989768. 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.

At D:\ListadoVDD.ps1:53 char:1

+ Connect-HVServer -server myserver.fqdn.corp -User $vcAdmin

-Password $v ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~

    + CategoryInfo          : NotSpecified: (:) [Connect-HVServer], Exception

    + FullyQualifiedErrorId : System.Exception,VMware.VimAutomation.HorizonVie

   w.Commands.Cmdlets.ConnectHVServer

Any ideas?

Thank you very much.

0 Kudos
12 Replies
LucD
Leadership
Leadership

Can you open the Admin Page from that same station where you run the Connect-HVServer cmdlet?

Both are going to the same Connection Server, using the same protocol, so both should be working, or not working afaik.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
AreasCorp
Contributor
Contributor

Yes I do. I can open the view admin page from the station runnin the power cli.

Thank you.

0 Kudos
LucD
Leadership
Leadership

Try disabling the Web timeout (default is 300 seconds) with

Set-PowerCLIConfiguration -Scope AllUsers -WebOperationTimeoutSeconds -1 -Confirm:$false

Note that you'll have to stop/start your PowerShell session to activate the new setting.

There have been mentions that the -1 value didn't work, in that case try setting the timeout to high value, for example 3000.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
AreasCorp
Contributor
Contributor

Got the same error after the change:

Connect-HVServer : The request channel timed out while waiting for a reply

after 00:01:39.9843939. 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.

PowerCLI C:\> get-PowerCLIConfiguration | Format-List

DefaultVIServerMode         : Multiple

ProxyPolicy                 : NoProxy

ParticipateInCEIP           : True

CEIPDataTransferProxyPolicy : UseSystemProxy

DisplayDeprecationWarnings  : True

InvalidCertificateAction    : Unset

WebOperationTimeoutSeconds  : 3000

VMConsoleWindowBrowser      :

Scope                       : Session

DefaultVIServerMode         : Multiple

ProxyPolicy                 :

ParticipateInCEIP           : True

CEIPDataTransferProxyPolicy :

DisplayDeprecationWarnings  :

InvalidCertificateAction    :

WebOperationTimeoutSeconds  :

VMConsoleWindowBrowser      :

Scope                       : User

DefaultVIServerMode         :

ProxyPolicy                 : NoProxy

ParticipateInCEIP           :

CEIPDataTransferProxyPolicy :

DisplayDeprecationWarnings  :

InvalidCertificateAction    :

WebOperationTimeoutSeconds  : 3000

VMConsoleWindowBrowser      :

Scope                       : AllUsers

Thank you

0 Kudos
LucD
Leadership
Leadership

Which PowerCLI and which Horizon View version are you using?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
AreasCorp
Contributor
Contributor

Hi again,

Horizon 7.03 and powercli 6.5 R1.

Thank you.

0 Kudos
LucD
Leadership
Leadership

The only difference I see, is that I'm using 6.5.1 (which comes after 6.5R1).

But other than that I see no way to replicate the error you are seeing.

You could try a PowerCLI upgrade?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
AreasCorp
Contributor
Contributor

Updated to 6.5.1 and got the same error:

PowerCLI Version

----------------

   VMware PowerCLI 6.5.1 build 5377412

---------------

Component Versions

---------------

   VMware HorizonView PowerCLI Component 7.1.0 build 5307191

   VMware Cis Core PowerCLI Component 6.5 build 5374323

   VMware VimAutomation Core PowerCLI Component 6.5 build 5374329

   VMWare ImageBuilder PowerCLI Component 6.6 build 5299608

   VMWare AutoDeploy PowerCLI Component 6.6 build 5299608

   VMware SRM PowerCLI Component 6.5 build 5374694

   VMware Licensing PowerCLI Component 6.5 build 5375648

   VMware Vds PowerCLI Component 6.5 build 5374428

   VMware vROps PowerCLI Component 6.5 build 5375723

   VMware HA PowerCLI Component 6.0 build 5314477

   VMware Cloud PowerCLI Component 6.5 build 5375799

   VMware PCloud PowerCLI Component 6.5 build 5376282

   VMware Storage PowerCLI Component 6.5 build 5374001

   VMware vSphere Update Manager PowerCLI 6.6 build 5301639

more ideas?

Thank you very much

0 Kudos
LucD
Leadership
Leadership

I'm afraid not, besides trying from another PC.

Looks like an issue, perhaps you should raise a SR.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
eliranbd9
Contributor
Contributor

Hi

Any news with that??

i have the same problem

0 Kudos
FranklinS
Enthusiast
Enthusiast

I am currently experiencing this same issue.  Did you ever find the solution?

0 Kudos
Magneet
Hot Shot
Hot Shot

for my customer it was upgrading to 10.1.1 that fixed it

0 Kudos