Hi,

I tried uninstalling PowerCLI-6.3.0-3737840 and reinstalling again but I have the same problem.

This is the command i run as administrator:

C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile “C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1″ ” & “C:\scripts\vcheck_vcenter\vCheck_atvcen8\vCheck-vSphere-master\vCheck.ps1”

The output is as follows:

Get-VICredentialStoreItem : The term ‘Get-VICredentialStoreItem’ is not
recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At C:\scripts\vcheck_vcenter\vCheck_atvcen8\vCheck-vSphere-master\Plugins\00
Initialize\00 Connection Plugin for vCenter.ps1:53 char:10
+ $Creds = Get-VICredentialStoreItem -Host $VIServer -File C:\credentia …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-VICredentialStoreItem:Strin
g) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

This is how my psmodulepath looks …

PS C:\Users\Administrator> $env:psmodulepath
C:\Users\Administrator\Documents\WindowsPowerShell\Modules;
C:\Program Files\WindowsPowerShell\Modules;
C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;
C:\Program Files\Hewlett-Packard\PowerShell\Modules;
C:\Program Files\EMC\EMC Storage Integrator\;
C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Modules;
C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Modules\;
C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Modules\

And this vim.psc1 file in C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI

1.0

and this is my powershell version

PS C:\Users\Administrator> $PSVersionTable.PSVersion

Major Minor Build Revision
—– —– —– ——–
5 0 10514 6

Regards,

Noel

$loadedSnap = Get-PSSnapin -Name VMware* -ErrorAction SilentlyContinue | where{$_.Name -notmatch 'Core$'} | Select Name
Get-PSSnapin -Name VMware* -Registered | where{$loadedSnap -notcontains $_.Name} | %{Add-PSSnapin -Name $_.Name}

Hope that helps.

Get-PowerCLIVersion : The term ‘Get-PowerCLIVersion’ is not recognized as the
name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Get-PowerCLIVersion
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-PowerCLIVersion:String) [],
CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

I’ve modified the vim.psc1 console file to include the line

because it seems that the only snap-ins that are included are VMware.DeployAutomation and VMware.ImageBuilder but even with that change i’m not having any luck, but now get a different error:
C:\Users\username_admin>powershell.exe -psc “D:\Program Files (x86)\VMware\In
frastructure\vSphere PowerCLI\vim.psc1” -noprofile -command “Get-PowerCLIVersion”

Windows PowerShell terminated with the following error:
There is no Runspace available to run scripts in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The script block you attempted to invoke was: Import-Module VMware.VimAutomation.Cis.Core

I just upgraded from 5.8 R1 to first 6.0 R2 and then 6.0 R3 but this problem is haunting me 🙁

It seems like PSModulePath is correct both for my batch user and for machine. Running Get-Module -ListAvailable shows the modules but autoloading is not working. Running a powershell.exe with the vim.psc1 does not fix this – “Connect-VIServer cmdlet not found”.

One thing I noted is that running Get-Module -ListAvailable shows no exported commands for the VMware modules but for all other and if I read Microsoft Technet[1] correct this needs to be the case for autoloading to work otherwise get-command won’t show them and this is necessary for autoloading to work.

Any ideas on what to look for?

[1] https://technet.microsoft.com/en-us/library/dd878284%28v=vs.85%29.aspx