search

pnp / PnP-PowerShell

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

Apply-PnPProvisioningTemplate Not working December Release #1286

Open cloudwhizz opened 6 years ago

cloudwhizz commented 6 years ago

Reporting an Issue or Missing Feature

Apply-PnPProvisioningTemplate : Could not load file or assembly 'System.IdentityModel.Tokens.Jwt, Version=5.1.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. At line:1 char:1

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

Install Latest Version of the PNP Tools and run Apply-PnPProvisioningTemplate

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

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

2.21.1712.1

How did you install the PnP-PowerShell Cmdlets?

KatjaJokisalo commented 6 years ago

I have the same problem. December bits downloaded from GitHub. Previous version uninstalled before installing the new one.

woernere commented 6 years ago

I was able to do what I needed by rolling back to November release, but what would be the risks staying at that release?

ghost commented 6 years ago

I think it impacts all the calls to the Core/Framework/Provisioning. Same error with Import-PnPTermGroupFromXml

jansenbe commented 6 years ago

We've released 2.21.1712.2 to address this problem to PowerShell gallery, the MSI's will be updated later today

sivamsolai commented 6 years ago

I download the latest PowerShell 2.21.1712.2 and run Apply-PnPProvisioningTemplate CMD. getting below error

Apply-PnPProvisioningTemplate : List does not exist. The page you selected contains a list that does not exist. It may have been deleted by another user.

Steps to reproduce behavior

Please follow the below steps Source site

Create a sub site (Team Template) under the source site collection. Create a calendar list on sub site and list name : calendar Add the calendar web par add the web part on sub site home page. run Get-PnPProvisioningTemplate -Out template.xml

Target site

create a sub site (Team template) under the target site collection. create a calendar list and name called “calendar” on target site collection run “Apply-PnPProvisioningTemplate” CMD

note: don’t run the “Apply-PnPProvisioningTemplate” cmd, which sub site already having Calendar list

Frost-on-Web commented 6 years ago

I don't know if this issue is supposed to be close but i was fallen in the original issue :

Apply-PnPProvisioningTemplate : Could not load file or assembly 'System.IdentityModel.Tokens.Jwt, Version=5.2.4.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

I was running version 2.27 with success ; but i did a "Uninstall-Module SharePointPnPPowerShellOnline" before "Install-Module SharePointPnPPowerShellOnline" to have access at the 3.0 last version.

I run my PowerShell window with Administrator rights and i can see the command process throw exception during its "Initializing engine" phase.

Frost-on-Web commented 6 years ago

I confirm that the DLL (System.IdentityModel.Tokens.Jwt.dll) is in the installation folder :

C:\Program Files\WindowsPowerShell\Modules\SharePointPnPPowerShellOnline\3.0.1808.0

I don't know if the "Details" panel of the DLL properties give the right version of this but it's :

File version 4.0.10819.1000

Whereas PowerShell error requested "Version=5.2.4.0"...

Frost-on-Web commented 6 years ago

When i compare Tags https://github.com/SharePoint/PnP-PowerShell/compare/2.28.1807.0...3.0.1808.0 i don't know if the issue is coming from :

"Commands/app.config" : https://github.com/SharePoint/PnP-PowerShell/blob/5beb621203c9a7e9569dc5ae2b3a4cace3444674/Commands/app.config#L53-L56

or

"Commands/packages.config" https://github.com/SharePoint/PnP-PowerShell/blob/5beb621203c9a7e9569dc5ae2b3a4cace3444674/Commands/packages.config#L19 which upgraded "Microsoft.IdentityModel.Clients.ActiveDirectory" version from 2.29 to 3.19.

I have no time to test further, sorry.

adamdale commented 6 years ago

So it looks like August 2018 Intermediate Release 1 has fixed this issue for me :D .

Since I downloaded the latest MSI from GitHub (Cmdlet module 3.0.18.08.1) I haven't had any issues with this.