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.
-
Thursday, September 02, 2010 4:35 PM
Hi im having the following error in the windows event viewer
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: SHAREPOINT\systemafter this the computer starts working slowly and slowly
The account that the log shows is the aplication pool account of the first site collection I created
I followed the instrucctions in this link:
http://technet.microsoft.com/en-us/library/ff758656.aspx
I set new accounts to the superuser and super reader I also tried using the same account that the first error showed has superuser and super reader
However I always get this error when I try to access the Site Collection after performing this
The user does not exist or is not unique.<nativehr>0x81020054</nativehr><nativestack></nativestack>
In the sharepoint log I get this same error plus this
Could not get token super user token, reverting to system account. User is <"UserAccountIcreated">
and this I get it for both super user and super reader and I can't access the site collection
Can anyone help fix this error plz.
All Replies
-
Wednesday, September 29, 2010 7:34 AM
Hi, I have followed exactly the same link and because we where getting the same event log; we are now getting the same problem, I have opened another question to the forum; and I am hoping to get some resolution as not able to access intranet now.
I even tried the stsadm command as mentioned in the event log message: -
stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue DOMAIN\sp_cachreader -url http://server
Have performed the IISRESET and still nothing; big problem; did you get an answer to this?
Jules
-
Sunday, October 03, 2010 9:19 PM
Read Chris O'Brien's blog :-
http://www.sharepointnutsandbolts.com/2010/09/set-object-caching-user-accounts-with.html
-
Thursday, December 30, 2010 4:08 PM I ran in to the exact same issue. It turns out I had misspelled the names of the domain accounts I had set-up as the super user and super reader. Once I fixed this and ran IISRESET the site collection was accessible again. Make sure the account names are spelled correctly and entered in the format "DOMAIN\accountname".
- Proposed As Answer by Jeff Holliday Thursday, February 24, 2011 11:47 PM
-
Tuesday, March 27, 2012 10:19 AM
Sorry to be repetitive but I know what it's like when you need to solve a problem and have multiple solutions proposed, therefore I would like to draw your attention to airfrog's post. A rookie mistake that I kicked myself for making, I didn't include the domain for the user account so please ensure you include the domain as instructed by airfrog.
Also, a colleague of mine setting up another SP farm found that if the user account is more then (I think from memory) 20 characters long you should truncate the username to fit within this limit, failing that just reconfigure you AD account to be shorter, i.e. SRV-SPSA and SRV-SPSR. Hope this helps.
-
Wednesday, January 09, 2013 12:29 PM
.png){kind=spacer}
