No snap ins have been registered for windows powershell version

I installed vSphere PowerCLI 5.5 on a Windows 7 32bit box and on a Windows 8.1 64bit box.

I try to run a .ps1 script that starts with lines like:

Add-PSSnapin VMware.VimAutomation.Core

Connect-VIServer …

get-vm …

On both PCs I get the same error:

Add-PSSnapin : No snap-ins have been registered for Windows PowerShell version 4. (version 2 for the Windows 7 PC)

In <filename>.ps1:1 car:1

+ Add-PSSnapin VMware.VimAutomation.Core

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (VMware.VimAutomation.Core:String) [Add-PSSnapin], PSArgumentException

    + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand

While installing vSphere PowerCLI 5.5 I got no error.

On the Windows 7 PC there is WMware Player installed, in the Windows 8.1 PC there is VMware Workstation installed.

My scripts worked fine on a Windows XP box.

Is there anything I should do after installing vSphere PowerCLI 5.5?

Is there any releevant step I am missing?

Regards

marius

I am trying to run a Powershell script on a web server where SQL Server Management Studio is not installed but all pertinent packages from the Microsoft SQL Server 2008 R2 SP2 Feature Pack have been installed. You need to install those small bits and pieces in order for Powershell to be able to run SQL commands.

Then I ran this setup script that preps your environment for SQL Server commands run with Powershell:

$ErrorActionPreference = "Stop"

$sqlpsreg="HKLM:\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps"

if (Get-ChildItem $sqlpsreg -ErrorAction "SilentlyContinue")
{
    throw "SQL Server Powershell is not installed."
}
else
{
    $item = Get-ItemProperty $sqlpsreg
    $sqlpsPath = [System.IO.Path]::GetDirectoryName($item.Path)
}



/* Preload the assemblies. Note that most assemblies will be loaded when the provider
 is used. if you work only within the provider this may not be needed. It will reduce
 the shell's footprint if you leave these out.*/

$assemblylist =
"Microsoft.SqlServer.Smo",
"Microsoft.SqlServer.Dmf ",
"Microsoft.SqlServer.SqlWmiManagement ",
"Microsoft.SqlServer.ConnectionInfo ",
"Microsoft.SqlServer.SmoExtended ",
"Microsoft.SqlServer.Management.RegisteredServers ",
"Microsoft.SqlServer.Management.Sdk.Sfc ",
"Microsoft.SqlServer.SqlEnum ",
"Microsoft.SqlServer.RegSvrEnum ",
"Microsoft.SqlServer.WmiEnum ",
"Microsoft.SqlServer.ServiceBrokerEnum ",
"Microsoft.SqlServer.ConnectionInfoExtended ",
"Microsoft.SqlServer.Management.Collector ",
"Microsoft.SqlServer.Management.CollectorEnum"


foreach ($asm in $assemblylist)
{
    $asm = [Reflection.Assembly]::LoadWithPartialName($asm)
}


//Set variables that the provider expects (mandatory for the SQL provider)

Set-Variable -scope Global -name SqlServerMaximumChildItems -Value 0
Set-Variable -scope Global -name SqlServerConnectionTimeout -Value 30
Set-Variable -scope Global -name SqlServerIncludeSystemObjects -Value $false
Set-Variable -scope Global -name SqlServerMaximumTabCompletion -Value 1000


//Load the snapins, type data, format data

Push-Location
cd $sqlpsPath


Add-PSSnapin SqlServerCmdletSnapin100
Add-PSSnapin SqlServerProviderSnapin100 
Update-TypeData -PrependPath SQLProvider.Types.ps1xml  
update-FormatData -prependpath SQLProvider.Format.ps1xml  
Pop-Location

At Add-PSSnapin SqlServerCmdletSnapin100, the script fails with the following error:

No snap-ins have been registered for Windows PowerShell version 2. At
C:\Vantiv\Initialize-SqlpsEnvironment.ps1:75 char:13
+ Add-PSSnapin <<<< SqlServerCmdletSnapin100 #-ErrorAction SilentlyContinue
+ CategoryInfo : InvalidArgument: (SqlServerCmdletSnapin100:String) [Add-PSSnapin], PSArgumentException
+ FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand

I ran a Google search on this error and the only solution I could find was that people were saying my 64-bit Powershell Console shortcut was pointed to the SysWOW64 directory rather than the System32. This is not the case for me. Mine points to System32.

Any ideas? What do I need to do to get Powershell to register those snap-ins?

• 

  Did you run the cmdlet in the proper PowerShell(Maybe it’s 64-bit)? What’s the version of your Exchange Server? Here is one document about the different versions of   importing the Exchange module(Exchange 2007/2010/2013/2016/2019):

  Import Exchange PowerShell Module Opens a new window.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hey I’ve already tried the 64bit version of power shell and get the same issue 😭

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  See if the cmdlet is available for the version of your Exchange Server via the above link. Maybe it’s helpful to you.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hey, Just tried running the following command on my exchange server 

  add-pssnapin microsoft.exchange.management.powershell.snapin

  And i get the error No snap-ins have been registered for Windows PowerShell version 4

  Thanks, 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Looks like the 32 bit version of PowerShell in the screenshot

  Try running PowerShell as Administrator and rerun that command

  Report back findings and a screenshot of any errors.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hey, thank you for your response

  I tried that and I got the same error message

  Thanks

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Did you run the command on your Exchange server(According to the cmdlet, your server seems to be Exchange 2016)? If you did that, try to reboot your Exchange server during non-working hours, maybe the rebooting will help you fix this issue.

  If you run it on the DC or other servers, you may get the «No snap-ins…» error. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hi, it’s been a long time, is there any progress? If the issue has been fixed, you could share the solution or mark the best answer.

  
  Was this post helpful?
  thumb_up
  thumb_down