Event ID: 7362: The super user account utilized by the cache is not configured

Problem

You encounter the following error appears in the Windows Application event log:

Log Name:      Application

Source:        Microsoft-SharePoint Products-Web Content Management

Date:          <date>

Event ID:      7362

Task Category: Publishing Cache

Level:         Warning

Keywords:     

User:          <username>

Computer:      <server>

Description:

Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.

 To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.

 Additional Data:

 Current default super user account: [MachineName]\system

SharePoint 2010 is hosted on this machine.

Solution

On new installations, the SharePoint super user account is configured to run under the machine's local System account.  However, this causes complications and thus the warning.  This should be addressed during setup, but isn't included in the setup wizard.  Anyway, resolving it is simple.  There are two ways: using STSADM or using Powershell.  We'll go through both here.

Step 1: Create Super User and Super Reader Domain Accounts

Create super user and super reader domain accounts

Example: DOMAIN\sp_superuser, DOMAIN\sp_superreader

Step 2: Configure Accounts in SharePoint Central Administration

Go to SharePoint CA: Central Admin -> Manage Web Application -> User Policy

Add DOMAIN\sp_superuser – Full Control

Add DOMAIN\sp_superreader – Full Read

Check to make sure these accounts have similar access to the SharePoint databases.  Next, use one of the following steps: A or B.

Step 3A: Using STSADM

Open a command prompt

Execute:

stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue DOMAIN\[sp_superuser] -url [WEBAPPURL]

And

stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue DOMAIN\[sp_superreader] -url [WEBAPPURL]

Step 3B: Using SharePoint Management Shell

Open a shell

Execute the following commands:

$wcm = Get-SPWebApplication -Identity http://[webappurl/]

$wcm.Properties["portalsuperuseraccount"] = “DOMAIN\sp_superuser”

$wcm.Properties["portalsuperreaderaccount"] = “DOMAIN\sp_superreader”

$wcm.Update()

Close the shell

Step 4: Reset IIS

Reset IIS either from the GUI or executing "IISReset" at the command prompt.

Step 5: Test

Opena command prompt

Execute the following:

stsadm -o getproperty -propertyname portalsuperuseraccount -url [WEBAPPURL]

Output should read:

<PropertyExist=”Yes” Value=”DOMAIN\sp_superuser” />

Similarly for the super reader account.  The references below provide good background.
Happy Computing!

References

• Microsoft TechNet - SharePoint - Configure object cache user accounts, 6/16/2010.
• UnderstandSharePoint Blog: Super User Account Utilized by the Cache is Not Configured, 8/2/2011.
• David Sterlings Blog: SharePoint 2010 Slow to render pages/SharePoint Cache, 3/23/2011.
• Global Josh's Blog: Event ID: 7362, Object Cache: The super user account utilized by the cache is not configured.