search

pnp / PnP-PowerShell

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

Update Module: v'2.9.1611.0' of 'SharePointPnPPowerShellOnline'not catalog signed #571

Closed westerdaled closed 6 years ago

westerdaled commented 7 years ago

Not a huge issue I imagine and I can easily -skipPublisherCheck ,

I have not added further detail as thought this was self-explanatory . Please let me know if you need this. 

>Update Module

PackageManagement\Install-Package : The version '2.9.1611.0' of the module 
'SharePointPnPPowerShellOnline' being installed is not catalog signed. Ensure that the 
version '2.9.1611.0' of the module 'SharePointPnPPowerShellOnline' has the catalog file 
'SharePointPnPPowerShellOnline.cat' and signed with the same publisher 'CN=thawte Primary 
Root CA, OU="(c) 2006 thawte, Inc. - For authorized use only", OU=Certification Services 
Division, O="thawte, Inc.", C=US' as the previously-installed module '2.9.1611.0' with 
version '2.6.1608.0' under the directory 'C:\Program 
Files\WindowsPowerShell\Modules\SharePointPnPPowerShellOnline\2.6.1608.0'. If you still want 
to install or update, use -SkipPublisherCheck parameter.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1941 char:20
+ ...           $sid = PackageManagement\Install-Package @PSBoundParameters
+

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:

  1. Are you using Apply-SPOProvisioningTemplate or Get-SPOProvisioningTemplate? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/officedev/PnP-Sites-Core/issues.
  2. Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.
  3. If you think that the functionality might be related to the underlying libraries that the cmdlet is calling (We realize that that might be difficult to determine), please first double check the code of the cmdlet, which can be found here: https://github.com/OfficeDev/PnP-PowerShell/tree/master/Commands. If related to the cmdlet, continue reporting the issue here, otherwise report the issue at https://github.com/officedev/PnP-Sites-Core/issues

Reporting an Issue or Missing Feature

Please confirm what it is that your reporting

Expected behavior

Please describe what output you expect to see from PnP-PowerShell Cmdlets

Actual behavior

Please describe what you see instead. Please provide samples of HTML output or screenshots

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?

gabbsmo commented 7 years ago

How do I use the -skipPublisherCheck switch? It isn't on MSDN https://msdn.microsoft.com/en-us/powershell/reference/5.1/powershellget/update-module

This doesn't work Update-Module -skipPublisherCheck

erwinvanhunen commented 7 years ago

The parameter is indeed not available on Update-Module, it is however available on Install-Module. So I would say:

Uninstall-Module <modulename>
Install-Module <modulename> -SkipPublisherCheck

should do the trick.

westerdaled commented 7 years ago

Yes, I did that a couple of weeks back. Has the underlying issue been resolved?