PnP provisioning with a custom extensibity provider

Question

We are using PnP Provisioning engine with a custom extensibility provider. When provisioning locally (which means a box with VS installed for development), it all works fine. But when we was running it on the test environment, the provisioning fails trying to bind OfficeDevPnP.Core.XmlSerializers. See log file attached. Any clues? What is the software requirement on the server, where the provisioning is running (components like .NET framework for example)?

Our observation tells us, that it works on a box with Visual Studio installed. On a regular application server or WFE with SharePoint Server 2013, it doesn't.

Any clue?

deleted · Answer

Hi Would need some more info.Which schema are you using and which release from PNP.&nbsp;kr,&nbsp;Paul

deleted · Answer

Hi Paul,&nbsp;OfficeDevPnP.Core.dll is 2.4.1605.0 and the provisioning schema is 2015/12.

deleted · Answer

Hi Jonas,&nbsp;Maybe there is a issue with the Dll's which are not present. Does it crash immediately?&nbsp;kr,&nbsp;Paul

deleted · Answer

No, the extraction of the template is working, until the step where the the custom extensibility provider is called.Please see attached log file.&nbsp;

deleted · Answer

if i look at your log it says:&nbsp;The system cannot find the file specified.&nbsp;i don't know if there is something in you exention. but seems it has a reference to a other path.&nbsp;Kr,&nbsp;Paul

Forum Discussion

PnP provisioning with a custom extensibity provider

7 Replies

Resources