- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Get-vsancomponent object reference not set to an instance of an object
Anyone running into issues w/ this cmdlet? Running the below syntax and I keep getting errors.
get-vsancomponent -vsanobject (get-vsanobject -vm nakawindows -type:vdisk)
Get-VsanComponent Object reference not set to an instance of an object.It doesn't seem to matter any object produced by get-vsanobject, cluster/vm, or otherwise returns this error.
Powershell version: 7.1.2
VMware.PowerCLI 12.2.0.17538434
Blog: https://tech.zsoldier.com
Twitter: @zsoldier
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nope, working perfectly for me.
Which OS are you running this in?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MacOS. Guess I'll have to find a windows system to see if I have problems there.
Powershell core for you too right?
Blog: https://tech.zsoldier.com
Twitter: @zsoldier
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hmm, get same response on a windows machine w/ latest powershell core and vmware.powercli module.
@LucD - What version is your target environment?
Blog: https://tech.zsoldier.com
Twitter: @zsoldier
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VCSA 7.0 U1d (build 17491160)
VSAN 7.0 U1
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same response?
You mean same error or same as me?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same error on my setup. Target is 6.7U3. Wonder if it's a target version problem now... <sigh>
Blog: https://tech.zsoldier.com
Twitter: @zsoldier
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would in any case suggest opening an SR
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Guys,
Same issue here, Get-VsanObject working fine but Get-VsanComponent is giving that error. It seems to happen only when the vSAN Cluster is not healthy or some Components have reduced availability.
Any news from anyone to overcome this situation?.
Thanks.