Get-vSanView: Throws an error when this cmdlet is executed

[Adv-CODE-R]

Hello, 

I have encountered a new issue while running this cmdlet "Get-vSanView".

The error messages are :

1.) Core_BaseCmdlet_UnknownError, VMware.Vimautomation.Storage.Commands.Cmdlets.Vsan.GetVsanView.

2.) Vsan_GetVsanView_WriteNotFoundError, VMware.Vimautomation.Storage.Commands.Cmdlets.Vsan.GetVsanView.

Versions:
1. vCenter - v7

2. PowerCLI - v12.70

We upgraded the module to the latest version since it threw the same error message from above in the "PowerCLI v11"

We can connect to the vCenter without any problem, but errors out when we want vSan health check. We tried to connect to different vCenters to check if that's a problem but no luck. 

We can see the cmdlets loaded into the PowerShell ISE (attached screenshots). Not sure what is that we are missing out here. Should I check anything at the vCenter level?  or if something that is blocking it?

Kindly help. 

Thanks in advance. 

[LucD]

Which PowerShell version are you using?

$PSVersionTable

[Adv-CODE-R]

Hi LucD,

Thank you. 

PS C:\Users\a_200779653> $PSVersionTable

Name                           Value                                                                                
----                           -----                                                                                
PSVersion                      5.1.14393.5127                                                                       
PSEdition                      Desktop                                                                              
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                              
BuildVersion                   10.0.14393.5127                                                                      
CLRVersion                     4.0.30319.42000                                                                      
WSManStackVersion              3.0                                                                                  
PSRemotingProtocolVersion      2.3                                                                                  
SerializationVersion           1.1.0.1  

OS - windows server 2016 standard.

[LucD]

Are you connected to only 1 vCenter?

$global:defaultVIServers

[Adv-CODE-R]

Yes, connected to only one vCenter and verified it and it was one. 

[LucD]

And your vCenter is not running in linked mode?
Did you try a Connect-VIServer with the -AllLinked:$false switch?

If that doesn't help, I suggest opening an SR