VMware Cloud Community
winsolo
Enthusiast
Enthusiast
Jump to solution

connect-srmserver: Unable to connect to the remote server

 I read a couple of posts related to this error. But so far I haven't been able to fix it.

Snag_40ff251.png

 

Snag_40f01d7.png

Snag_40f5650.png

Is there anything I can try?

Labels (2)
0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

0 Kudos
9 Replies
LucD
Leadership
Leadership
Jump to solution

Are you already connected to the vCenter?

when you are, did you try the Connect-SrmServer without credentials?

Does adding the Verbose switch show any additional information?

Which PowerCLI version are you using?


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

0 Kudos
winsolo
Enthusiast
Enthusiast
Jump to solution

Yes, I'm connected to the vCenter.

Snag_471e2a5.png

Snag_47318a4.png

In fact, i tried all these combinations

[System.Net.ServicePointManager]::SecurityProtocol =[System.Net.SecurityProtocolType]'Ssl3,Tls,Tls11,Tls12'
Connect-SrmServer -Credential $credential -RemoteCredential $credential
Connect-SrmServer -Port 443 -Credential $credential -RemoteCredential $credential
Connect-SrmServer -Port 443
Connect-SrmServer -SrmServerAddress SRM_Appliance_Hostname -Port 443
Connect-SrmServer -SrmServerAddress SRM_Appliance_Hostname -Port 443 -Credential $credential -RemoteCredential $credential
Connect-SrmServer -SrmServerAddress SRM_Appliance_Hostname -Port 443 -Credential $credential

0 Kudos
LucD
Leadership
Leadership
Jump to solution

Could it be that you are experiencing the same issue as this user?
[Solved]: Connect-SrmServer Unable to connect to the remote server - Ravichandran's blog (ravic499.b...


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

0 Kudos
winsolo
Enthusiast
Enthusiast
Jump to solution

Interesting. As the blog states, let me try to remove PowerCLI 12 and reinstall v11.1. It'd be disappointing if connect-srmserver worked with a previous version of PwerCLI. Thanks @LucD

0 Kudos
winsolo
Enthusiast
Enthusiast
Jump to solution

I upgraded the PowerCLI to 12.1.0.17009493 and tried running connect-srmserver. It now works.

Snag_800b7ec.png

Snag_80429a3.png

0 Kudos
LucD
Leadership
Leadership
Jump to solution

I find it strange that you apparently have duplicate modules with the same version in the same folder.

That is not ok.

Perhaps better remove all PowerCLI modules manually and do a fresh install.


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

winsolo
Enthusiast
Enthusiast
Jump to solution

I was concerned about it too, but the fact that it worked made me continue with the current state.

Does this work?

Get-Module -Name VMware* -ListAvailable | Uninstall-Module -Name $_.Name -Force -Confirm:$false

By the way, something has changed in the community platform, that no longer allows Powershell cmdlets with syntax highlighting. Copying snippets from Visual Studio Code strips the syntax format/highlighting. I wish it worked with the new platform.

Just thought of sharing my opinion.

0 Kudos
LucD
Leadership
Leadership
Jump to solution

Normally that should work, but seen the duplicate entries, I suspect you might need to remove the folder via regular Windows procedures (File Manager, CMD, PS...).

I know, the new Khoros platform, which replaced the old Jive platform, only has a limited set of supported languages for their Code blocks.
And PowerShell is not one of them!


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

0 Kudos
winsolo
Enthusiast
Enthusiast
Jump to solution

I uninstalled and reinstalled it. It appears to be correct. Connect-SrmServer works too. Thanks again.

Snag_8be2a37.png

0 Kudos