PowerCLI - vSAN Commands doesn't work correctly

[Garimos]

Hello everyone, currently I am confronted with the following problem:

When using the vSAN commands, I keep encountering the following error.

I am connected to one of our vCenter (6.7.0 - Build 18831049) in a test environment - Here I use a specially created a "SuperUser"-Permission Profile with all permissions. The rough configuration of vSAN can be seen in the attached images. 

After a longer research I have not found a solution yet.

I would like to thank you in advance and hope that you could help me as a beginner in PowerCLI.

Thank You

Greetings

Garimos

[LucD]

Which PowerCLI version are you using?

[Garimos]

Currently i am using the following version:

VMware PowerCLI 10.1.0 build 8346946

[LucD]

Any specific reason you are using a rather old version (2018)?
Can you try to upgrade, and check if the issue is still there?

[Garimos]

The vCenter Server and Windows Server are located in a sealed environment. I will download version 12.5.0 as a zip (Command Collection) and integrate it into the environment. Maybe that will be enough to solve the problem. If something comes up, I'll get back to you. 

[Garimos]

 After updating the modules, the following error appears : 

[LucD]

Strange error.
The cmdlet works for me.

Are you sure the PowerCLI installation is correct?
Do a

Get-Module -Name VMware* -ListAvailable

[Garimos]

 

[LucD]

That looks ok.

I suggest opening an SR.

[Garimos]

All right then, I'll open a support request. Thanks a lot for your help!

[pkvmw · Accepted solution]

Hi all,

I've been working on the SR and thought I'll keep everyone updated. I noticed that there're too much modules present, compared to my local setup. So we went ahead removing all modules, reinstalling PowerCLI modules clean and the cmdlet was working again.

Basically, the steps were:

1. To remove all VMware modules:
# Get-Module -Name VMware* -ListAvailable | Uninstall-Module

2. Check if everything was removed:
# Get-Module -Name VMware* -ListAvailable

3. Check if there're still modules left
3.1. User modules: %UserProfile%\Documents\WindowsPowerShell\Modules
3.2. System-wide modules: C:\program files\WindowsPowerShell\Modules

4. Attempt a clean installation of PowerCLI

Regards,
Patrik

[LucD]

What do you mean by "I noticed that there're too much modules present, compared to my local setup."?
That looked to me as a normal 12.5 installation
Are you on an older version?