VMware Cloud Community
VipalGujrathi
Contributor
Contributor

Need help with error

All,

I have one basic script to connect vcenter and poweroff all VMs,  two days ago when i ran this script i received below error on powershell window.

If i understood correctly, Stop-VM command was not sent to vCenter but my all VMs were started shutting down,  Please correct if i am wrong. What is the meaning of this error and if commands are not sent to vCenter then why my VMs started shutting down.

Note - before running stop-vm command, vCenter was connected successfully.

Shutting down VMs

Stop-VM : 4/5/2019 3:10:36 AM    Stop-VM        An error occurred while making the HTTP request to https://vCenter/sdk. This

could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This

could also be caused by a mismatch of the security binding between the client and the server.   

At C:\Users\user\Desktop\RP4Vm CleanUP_V1.ps1:148 char:56

+ ... here-object {$_.powerstate -eq "poweredon"} | Stop-VM -Confirm:$false

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

    + CategoryInfo          : NotSpecified: (:) [Stop-VM], ViError

    + FullyQualifiedErrorId :

Client20_QueryServiceImpl_CreateFilter_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.StopVM

Stop-VM : 4/5/2019 3:10:36 AM    Stop-VM        An error occurred while making the HTTP request to https://vCenter/sdk. This could be due to the fact that the

server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between

the client and the server.

At C:\Users\TKMA0XU\Desktop\RP4Vm CleanUP_V1.ps1:148 char:56

+ ... here-object {$_.powerstate -eq "poweredon"} | Stop-VM -Confirm:$false

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

    + CategoryInfo          : NotSpecified: (:) [Stop-VM], ViError

    + FullyQualifiedErrorId : Client20_QueryServiceImpl_CreateFilter_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.StopVM

Get-VMHost : 4/5/2019 3:10:38 AM    Get-VMHost        The HTTP service located at https://vCenter/sdk is unavailable.  This

could be because the service is too busy or because no endpoint was found listening at the specified address. Please

ensure that the address is correct and try accessing the service again later.   

    + CategoryInfo          : NotSpecified: (:) [Get-VMHost], VimException

    + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVMHost

Get-VMHost : 4/5/2019 3:10:38 AM    Get-VMHost        The HTTP service located at https://vCenter/sdk is unavailable.  This could be because the service is

too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service

again later.

0 Kudos
1 Reply
LucD
Leadership
Leadership

This could be related to the TLS settings.

vSphere 6.7 for example only supports TLS 1.2. See KB2145796

Check if the procedure described in KB2137109 helps.


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

0 Kudos