Open Glober777 opened 5 years ago
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
By the way, I tried removing the PSGallery edition of the module and installing via the MSI but I doesn't work either
we have the exact same behavior.
Which version of the PnP-PowerShell Cmdlets are you using? PnP PowerShell for SharePoint 2013 PnP PowerShell for SharePoint 2016 . . : : PnP PowerShell for SharePoint Online
What is the version of the Cmdlet module you are running? . . : : 3.9.1905.2 && 3.9.1905.3
How did you install the PnP-PowerShell Cmdlets? MSI Installed downloaded from GitHub . . : : Installed through the PowerShell Gallery with Install-Module Other means
Same issue on Windows 10 fresh build. I tried also installing normal SharePoint Online commandlets but still no go.
Which version of the PnP-PowerShell Cmdlets are you using? . . : : PnP PowerShell for SharePoint Online
What is the version of the Cmdlet module you are running? . . : : 3.10.1906.0
How did you install the PnP-PowerShell Cmdlets? . . : : Installed through the PowerShell Gallery with Install-Module
I suspect that the issue is coming from the order in which the Initial Bind occurs in .NET (GAC comes prior to probing other locations). I wonder if the fix for this would be handling load of the assemblies through AppDomain.AssemblyResolve Event
Not sure exactly what it was, but when I tried importing the module of version 3.12.1908.1 the issue was no longer reoccurring, however, as soon as I updated to the latest version through PSGallery (3.17.2001.2) the issue reappeared, but it was complaining about another type from the SharePoint library.
Same behaviour using 3.21.2005.1 on SharePoint 2013 Server
Did we found solution for the above issue ? I am facing the issue while trying to import 3.12.1908.1.
To resolve the issue, (1) Navigate to C:\Windows\Microsoft.NET\assembly\GAC_MSIL (2) Remove the Microsoft.SharePoint.* assemblies (3) Uninstall the module with Uninstall-Module -Name Microsoft.Online.SharePoint.PowerShell
After reinstalling the module from the PowerShell gallery, the module worked flawlessly.
Thanks a lot. We can not take the approach in a production farm. Also i am referring the dlls from a temp folder. Just wondering how this conflict is possible.
Reporting an Issue
I'm getting an error message when trying to import the module on one of my Windows Servers.
Expected behavior
The module should import without any errors (as it does on my other servers).
Actual behavior
The error that I'm seeing is:
Steps to reproduce behavior
Import-Module SharePointPnPPowerShellOnline
The only difference of this server with others (where the module works just great) is that it has SharePoint DLLs already available in GAC (supposedly through MS Exchange 2016 and Skype for Business 2019 modules that were installed through MSI)
I have Fusion logs available from both servers (working and non-working) if needed.
Which version of the PnP-PowerShell Cmdlets are you using?
What is the version of the Cmdlet module you are running?
3.9.1905.2
How did you install the PnP-PowerShell Cmdlets?