Forum Discussion
Error when using PnP powershell and CSOM
- Dec 05, 2016
Initially this feels like a conflict between the various versions of the CSOM sdk. The PnP Cmdlets come with the CSOM SDK included, so you don't have to install that SDK. The downloadable SDK is most likely also older than the one that comes with the PnP Cmdlets (the PnP cmdlets are always using the latest SDK, usually before the downloadable package is updated by MS). My initial try would be to uninstall the SDK (which installs the SDK into the GAC, which is generally a 'bad' thing).
- Shubhanshu RajoriyaApr 03, 2019Former Employee
Erwin van Hunen I uninstalled SPO Client Component SDK but still getting the same error.
- AnonymousDec 05, 2016
Thanks for the reply!
I will uninstall the "SharePoint Client Component".
Can I still use the "SharePoint Online Management shell", or can it also cause a conflict?Good to know about the latest SDK being included in the PnP package.
Regards
Simon
- Dec 05, 2016
You can absolutely still use the SharePoint Online Management shell. One of the reasons we renamed the cmdlets from *-SPO* to *-PnP* is to be able to use them side by side without conflicts.