Apply Pnp Provisioning : List workflow

Copper Contributor

Source sub site contains 1. A list based workflow (2013 version)

1. create using SPD and works successfully - when using Get-PnPProvisioningTemplate it creates a {GUID}.xaml file in the output directory along with the template defintion file. I have reviewed these and all xml tags/formatting appear to be correct.


When using Apply-PnpProvisioningTemplate (with debuggin on) it receive the following out put.

PowerShell_ISE.exe Information: 0 : 2016-12-29 12:22:13.7871 [Lookup Fields] [13] [Debug] Code execution scope started 0ms a1f33407-1bac-4feb-9e7a-9d7d182e894d
PowerShell_ISE.exe Information: 0 : 2016-12-29 12:22:17.9701 [Lookup Fields] [13] [Debug] Code execution scope ended 4183ms a1f33407-1bac-4feb-9e7a-9d7d182e894d
PowerShell_ISE.exe Information: 0 : 2016-12-29 12:22:17.9701 [Workflows] [13] [Debug] Code execution scope started 0ms a1f33407-1bac-4feb-9e7a-9d7d182e894d
PowerShell_ISE.exe Information: 0 : 2016-12-29 12:22:17.9701 [OfficeDevPnP.Core] [0] [Information] File 859710e9-c3c5-447e-9789-6606c27fe302.xaml retrieved from folder  0ms 
PowerShell_ISE.exe Information: 0 : 2016-12-29 12:22:18.4169 [Workflows] [13] [Debug] Code execution scope ended 452ms a1f33407-1bac-4feb-9e7a-9d7d182e894d
PowerShell_ISE.exe Information: 0 : 2016-12-29 12:22:18.4169 [Provisioning] [13] [Debug] Code execution scope ended 119730ms a1f33407-1bac-4feb-9e7a-9d7d182e894d
Apply-PnpProvisioningTemplate : Operation is not valid due to the current state of the object.
At line:2 char:1
+ Apply-PnpProvisioningTemplate -Web $site -Path ".\AAAProvision.xml";
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (:) [Apply-PnPProvisioningTemplate], ServerException
    + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.Provisioning.ApplyProvisioningTemplate


My Assumption is around the workflow, as removing this appears to work successfully.


Any pointers/ideas?


1 Reply
Hi Rod,
I know, this topic is more than three years old, but I'm running into the same issue.
Did you ever find out what was causing this error or even how to circumvent it?