search

pnp / PnP-PowerShell

SharePoint PnP PowerShell CmdLets
https://pnp.github.io/powershell
Other
985 stars 665 forks source link

2013 could not load type when importing cmdlets #1710

Open paulbuzzby opened 5 years ago

paulbuzzby commented 5 years ago

Notice: many issues / bugs reported are actually related to the PnP Core Library which is used behind the scenes. Consider carefully where to report an issue:

Reporting an Issue or Missing Feature

When running the command import-module C:\Tools\PnP-PowerShell\SharePointPnPPowerShell2013\3.1.1809.0\sharepointpnppowershell2013.psd1

I get

import-module : Could not load type 'Microsoft.SharePoint.Client.DocumentSet.DocumentSetTemplate' from assembly 'Microsoft.SharePoint.Client.DocumentManagement, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'. At line:1 char:1

Running the same for the online cmdlets works as expected

Expected behavior

Cmdlets load and become available

Actual behavior

Error as above

Steps to reproduce behavior

Please include complete code samples in-line or linked from gists

Which version of the PnP-PowerShell Cmdlets are you using?

What is the version of the Cmdlet module you are running?

(you can retrieve this by executing Get-Module -Name *pnppowershell* -ListAvailable)

How did you install the PnP-PowerShell Cmdlets?

Save-Module -Name SharePointPnPPowerShell2013 -Path C:\Tools\PnP-PowerShell Save-Module -Name SharePointPnPPowerShell2016 -Path C:\Tools\PnP-PowerShell Save-Module -Name SharePointPnPPowerShellOnline -Path C:\Tools\PnP-PowerShell

erwinvanhunen commented 5 years ago

This is most likely caused by the fact that you have a version of CSOM installed in the GAC that has functionality for the documentset available. While the CSOM assemblies we have available in the folder where the cmdlets reside are the correct one, if a version of CSOM is available in the Global Assembly Cache that one will always 'win'. Please check if that's the case on your environment.