SharePoint 2016 DLP: Value cannot be null. Parameter name: site
As more people start playing with Data Loss Prevention (DLP) in SharePoint 2016, some of them have come across an “Unexpected” error when applying a DLP Policy to a Site Collection.
The error message in the ULS Log for your correlation ID would be similar to the following line:
Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.ArgumentNullException: Value cannot be null. Parameter name: site
This error most commonly arrives when you try to setup a policy for a Site Collection that is not in the same Web Application as your Policy Center. Due to Security reasons, the Compliance Policies can only apply DLP Policies to the same Web Application, so if you want to apply a policy to a Site Collection in a different Web Application, you would need a Policy Center Site collection in that Web Application.
I know the previous paragraph might sound confusing a bit, but to put it a different way, you need to create a Policy Center Site Collection in every Web Application that you want to apply DLP Policies in. If you try to apply a DLP Policy to a Site Collection in a different Web App, you will get the error above!
If you want an overview of Data Loss Prevention in SharePoint 2016, check out my CMSWire article over here: http://www.cmswire.com/information-management/under-the-hood-with-sharepoint-2016-data-loss-prevention/
For a step by step tutorial on how to setup DLP in SharePoint 2016, check out my blog : https://vladtalkstech.com/2015/12/configure-dlp-in-sharepoint-2016-step-by-step-tutorial.html
Follow me on Social Media and Share this article with your friends!
|Leave a comment and don’t forget to like the Absolute SharePoint Blog Page on Facebook and to follow me on Twitter here for the latest news and technical articles on SharePoint. I am also a Pluralsight author, and you can view all the courses I created on my author page.|