The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

Issue: The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

Cause: This means that the cache accounts for your web application aren’t properly set and that there will be a lot of cache misses. If a cache miss occurs the page the user requested will have to be build up from scratch again. Files and information will be retrieved from the database and the file system and the page will be rendered. This means an extra hit on your SharePoint and database servers and a slower page load for your end user.

Solution: The domain\super user account needs to have a User Policy set for that gives it Full Control to the entire web application. In order to do this you perform the following steps:

1.     Go to Central Administration

2.     Go to Application Management

3.     Go to Manage Web Application

4.     Select the web application we’re talking about

5.     Click User Policy

6.     Add Users

7.     Click Next

8.     Fill in domain\superuser

9.     Select Full Control

10.  Click OK 

The domain\super reader account needs to have a User Policy set for that gives it Full Read to the entire web application. In order to do this you perform the following steps:

1.     Go to Central Administration

2.     Go to Application Management

3.     Go to Manage Web Application

4.     Select the web application we’re talking about

5.     Click User Policy

6.     Add Users

7.     Click Next

8.     Fill in domain\super reader

9.     Select Full Read

10.  Click OK

1.    If you are using classic mode authentication run the following cmdlets on one of your SharePoint servers:

$w = Get-SPWebApplication "http://<server>/"

$w.Properties["portalsuperuseraccount"] = "domain\superuser"

$w.Properties["portalsuperreaderaccount"] = "domain\superreader"

$w.Update()

2.    If you are using claims based authentication run these cmdlets on one of your SharePoint servers:

$w = Get-SPWebApplication "http://<server>/"

$w.Properties["portalsuperuseraccount"] = "i:0#.w|domain\superuser"

$w.Properties["portalsuperreaderaccount"] = "i:0#.w|domain\superreader"

$w.Update()

After you've run these Power Shell cmdlets you need to perform an IISRESET to finish it off.

Reference from MS:http://technet.microsoft.com/en-us/library/ff758656.aspx.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Rename the User Profile service application databases in SharePoint Server 2013

Rename the User Profile service application databases in SharePoint Server 2013

You typically rename service application databases to remove the GUID from the database name after the databases were created by the SharePoint Products Configuration Wizard, or to bring the databases into alignment with your organization's naming standards.

You can rename a User Profile service application database by using SQL Server tools.

Please check the below Article from MS.

http://technet.microsoft.com/en-us/library/jj714711%28v=office.15%29.aspx 

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Account Deletion issues in SharePoint 2010 User Profile Synchronization

Account Deletion issues in SharePoint 2010 User Profile Synchronization

http://www.harbar.net/archive/2011/02/10/account-deletion-and-sharepoint-2010-user-profile-synchronization.aspx 

I found a Very good article on This from Harbar. Please find the link below.

Thanks to Harbar.

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

List of issues SharePoint Server 2013 SP1 fixes

Issue Description	KB
Metadata is lost when documents that use a custom content type with a "Description" field are opened for editing.	2817429​
When an item is deleted, restored from recycle bin, and then deleted again, there is a primary key constraint error.	2817429​
An error occurs when files are moved between document libraries and the web time zone is behind that of the server.	2817429​
Metadata filtering at list level always lists all metadata terms.	2817429​
The hyperlink popup window drops the selected word to be linked when there is a delay of more than one second in opening the window.	2817429​
Multiple-column, SummaryLinkWebParts with a group heading style of "Separator" are rendered incorrectly.	2817429​
A hash tag that contains a full width space does not get created successfully.	2817429​
Search schema compression is now enabled by default to allow larger search schemas.	2817429​
Highlighting for FQL queries is now enabled for FQL as well as KQL.	2817429​
Opening a custom SharePoint list in datasheet view and applying multiple custom filters, where each filter has more than one condition, can result in an incomplete set of list items.	2817429​
When the "Export to Excel" button is clicked in a SharePoint document library that has the Content Type field displayed, the Content Type field does not appear in the Excel workbook.	2817429​
An error occurs after changing the "Manager" property in EditProfile.aspx page when the My Sites WebApp is not in the same farm as the UPA.	2817429​
SharePoint REST API does not return a well-defined error response for a duplicate key exception.	2817429​
Developers are unable to specify a Content Type ID when creating Content Types in the client object model.	2817429​
On list views in SharePoint sites, the Connect to Outlook button in the ribbon may be erroneously disabled.	2817429​
In some non-English languages of SharePoint, the text displayed in the callout UI for a document or list item, describing who last edited the item, may not be grammatically correct.	2817429​
Copy and Paste in a datasheet does not work correctly with Internet Explorer 11.	2817429​
Pages do not render in Safari for iPad when private browsing mode is used.	2817429​
When editing rich text fields in SharePoint, if the editing session exceeds 30 minutes, the edits may not be saved.	2817429​
An error that says "SCRIPT12004: An internal error occurred in the Microsoft Internet extensions" may occur intermittently when users visit their SkyDrive Pro or other pages on their personal site.	2817429​
InfoPath may crash when a form that points to a SharePoint list, with a lookup to another SharePoint list, is opened.	2817429​
An InfoPath form with extended characters in its name fails to open.	2817429​
An error that says "Security Validation for the form has timed out" may occur when an InfoPath form is digitally signed and hosted in a SharePoint site collection that uses the SharePoint version 2010 user experience.	2817429​
"Show document icon" remains unchecked and the document icon does not show in Edit Properties for a list item.	2817429​
A "Failed tagging this page" error occurs when the "I like it" button is clicked.	2817429​
The wrong term is removed when manually editing a multi-valued taxonomy field.	2817429​
When tagging list items using a language that is different from the term store default language, suggestions for labels are offered in multiple languages. The suggestions appear confusing because both language suggestions are listed without any identification of the language.	2817429​
An error that says "There was an error processing this request" may appear when editing the user profile.	2817429​
Times are missing from Date/Time results in certain filtered list web service calls.	2817429​
Minimal and no metadata are now enabled as supported JSON formats.	2817429​
Actions4 schema workflow actions can't be deployed to SharePoint.	2817429​
Using Client Object Model, Stream.Seek() to seek to a particular position doesn't seek at the proper offset.	2817429​
Refreshing a workflow status page generates the following error: "System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary."	2817429​
Setting custom, non-English outcomes in web pages on tasks in a workflow fails to set the value.	2817429​
Configurations of SharePoint using Azure Hybrid mode and Workflow Manager together can cause workflow callbacks to fail.	2817429​
Workflow task processes on wiki pages won't start.	2817429​
Workflows won't wait for changes to content approval status fields.	2817429​
E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows.	2817429​
Workflows may fail to send an e-mail or send too many e-mails.	2817429​
Association variables do not update correctly for auto-start workflows.	2817429​
A KeyNotFoundException error may occur in a workflow when the associated task list uses unique permissions.	2817429​
Incomplete tasks are deleted when workflow task activities complete.	2817429​
Task activity is suspended when the task is completed using app-only credentials.	2817429​
An error that says "This task could not be updated at this time" occurs when trying to complete a workflow task using the "Open this task" button in Outlook.	2817429​
A workflow doesn't respond properly when waiting for changes in specific types of list columns, such as Boolean, Date Time, and User.	2817429​

For more details, please visit http://support.microsoft.com/kb/2817429

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.