SharePoint server running Server 2008 R2, SharePoint 2010 and SQL Server 2008
1 Teamsite
CPU utilization is good however the server is running extremely low on memory, even after performing memory improvement steps below:
* doubled RAM to 12GB
* lowered amount of SQL Server memory
* configured all SharePoint application pools to recycle twice a day
The SharePoint server is reporting event# 7362 "Object Cache: The super user account utilized by the cache is not configured. etc...". My main goal here is to free-up memory while fixing my SharePoint WebApp configuration to stop event# 7362 from reporting.
After reading this article it appears that the Object Cache could possibly be the reason for high memory utilization. Also see here for Microsoft's support link.
I verified that there is no super cache Reader or super cache User accounts specified for the TeamSite (Sharepoint - 80) Web Application User Policy in Central Administration. I can create these accounts in AD and add these accounts say-- (sp_ObjectCacheUser and sp_ObjectCacheReader) to the TeamSite Web App.
The two accounts listed in the User Policy for the (SharePoint - 80) Web App are: NT AUTHORITY\LOCAL SERVICE and the Crawling Acct (domain\serviceacct). So if I have this correct, after performing the steps above there should be four accounts listed in the User Policy for the SharePoint - 80 Web App:
1. NT AUTHORITY\LOCAL SERVICE
2. Crawling Acct (domain\serviceacct)
3. Domain\sp_ObjectCacheUser (Full Control)
4. Domain\sp_ObjectCacheReader (Full Read)
My main concern is that I do not need a user (or myself) to see an Access is Denied message when trying to authenticate - which is explained as a possibility in the links above.
Apparently this will happen if the Domain\sp_ObjectCacheReader is not added with Full Read-Only access.
Questions.
If for some reason I do experience the "Access is Denied" message:
1. What would I need to do to get authentication and access working again?
2. If I decide to roll the changes back, should it be as simple as making the changes back in CA for the Sharepoint - 80 Web App?
3. Is it required for either of these AD accounts to have access to SharePoint databases to resolve the Access is Denied message? See here.
1 Teamsite
CPU utilization is good however the server is running extremely low on memory, even after performing memory improvement steps below:
* doubled RAM to 12GB
* lowered amount of SQL Server memory
* configured all SharePoint application pools to recycle twice a day
The SharePoint server is reporting event# 7362 "Object Cache: The super user account utilized by the cache is not configured. etc...". My main goal here is to free-up memory while fixing my SharePoint WebApp configuration to stop event# 7362 from reporting.
After reading this article it appears that the Object Cache could possibly be the reason for high memory utilization. Also see here for Microsoft's support link.
I verified that there is no super cache Reader or super cache User accounts specified for the TeamSite (Sharepoint - 80) Web Application User Policy in Central Administration. I can create these accounts in AD and add these accounts say-- (sp_ObjectCacheUser and sp_ObjectCacheReader) to the TeamSite Web App.
The two accounts listed in the User Policy for the (SharePoint - 80) Web App are: NT AUTHORITY\LOCAL SERVICE and the Crawling Acct (domain\serviceacct). So if I have this correct, after performing the steps above there should be four accounts listed in the User Policy for the SharePoint - 80 Web App:
1. NT AUTHORITY\LOCAL SERVICE
2. Crawling Acct (domain\serviceacct)
3. Domain\sp_ObjectCacheUser (Full Control)
4. Domain\sp_ObjectCacheReader (Full Read)
My main concern is that I do not need a user (or myself) to see an Access is Denied message when trying to authenticate - which is explained as a possibility in the links above.
Apparently this will happen if the Domain\sp_ObjectCacheReader is not added with Full Read-Only access.
Questions.
If for some reason I do experience the "Access is Denied" message:
1. What would I need to do to get authentication and access working again?
2. If I decide to roll the changes back, should it be as simple as making the changes back in CA for the Sharepoint - 80 Web App?
3. Is it required for either of these AD accounts to have access to SharePoint databases to resolve the Access is Denied message? See here.
JCashon