I just had the same on SQL Server 2012. In my case the message doesn't seem to be persistent. What is a more persistent is failure of the "Show Policy...