Object Cache User Accounts and the ‘User does not exist or is not unique’ Error Message
August 22, 2012 Leave a comment
SharePoint 2010 uses a cache to power publishing pages and web parts to reduce the load on the SQL Server databases, the latency and increase the throughput. In order to take advantage of this feature we need to configure the object cache user accounts: Portal Super User and Portal Super Reader.
The script to configure it is quite simple:
$wa = Get-SPWebApplication -Identity "http://yourwebapplicationurl.com" $wa.Properties["portalsuperuseraccount"] = "SuperUser" $wa.Properties["portalsuperreaderaccount"] = "SuperReader" $wa.Update()
The trick part is what should be provided as the user names.
If you use Classic Mode Authentication you need to use the format DOMAIN\Username.
If you use Claims Based Authentication you need to use the format i:0#.w|DOMAIN\Username.
If you don’t specify a valid user name in the valid format you should see the following error message:
The user does not exist or is not unique.
This is a very generic error message but I was able to find the explanation on how to solve it on the post “SharePoint 2010: The user does not exist or is not unique“.