SharePoint 2013 - crawler has insufficient permissions to crawl file shares

While setting up an environment for a demo that would be using a search content source that was crawling a file share I ran across this issue.

You are unable to crawl the data in the share regardless of the NTFS or share permissions you set on the directory.

To resolve this issue, assign the Manage Auditing And Security Log permission to the SharePoint 2013 crawler. To do this, follow these steps on the computer that hosts the file shares:

1. Click Start, click Run, type gpedit.msc, and then click OK.
2. Navigate to the following location in the Local Group Policy Editor:
   Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment
3. In the right pane, locate and right-click Manage auditing and security log, and then click Properties.
4. Click the Add User or Group button in the Manage auditing and security log properties dialog box, and then add the crawl account that the SharePoint 2013 crawler uses.
5. Click OK in the Manage auditing and security log properties dialog box.

Note If you assign the Manage Auditing And Security Log permission by using a Group Policy Object (GPO), add the crawl account to the GPO.

This information was pulled from the following technet article
http://support.microsoft.com/kb/2817731

SharePoint 2013 - MySite Newsfeed displays "There was a problem retrieving the latest activity. Please try again later"

As I continue to go into more configuration around 2013 it is bringing back the memories of all the strange things that were encountered when deploying 2010 farms not long after it released. Fortunately 2013 has been out for a little while now and there are a lot of good folk's out there that started digging in early and have posted a lot of really good information on the issues they have run across during their configurations.

This is another one of the many issues that I have run across and was fortunate to find someone else out there that posted a good article on the issue and the resolution.

This error was due to the service account that is used to run the UPA service application not having permissions on the UPA it self. After adding the service account that the UPA application pool runs under to the UPA the My Sites news feed's begain showing up correctly.

Thanks to Andy Dawson for posting his detailed article on the issue with the details of the fix. He also provides a handy powershell script so you can automate this more in your farm configurations.

Article for doing it via Central Admin
http://blogs.blackmarble.co.uk/blogs/adawson/post/2012/10/30/SharePoint-2013-MySite-Newsfeed-displays-There-was-a-problem-retrieving-the-latest-activity-Please-try-again-later.aspx#id_0034c967-d124-45ac-a539-1e710d5f2391

Article on powershell script
http://blogs.blackmarble.co.uk/blogs/adawson/post/2012/11/23/Setting-SharePoint-2013-User-Profile-Service-Application-Permissions-Using-PowerShell.aspx

SharePoint 2013 My Site tasks not updating and show old updated date - Last updated at 1/1/1901 12:00AM

While working through some SharePoint 2013 configuration for an upcoming demo I ran across an issue where when you go to your my site and click on the tasks link you will get the error below

Sorry, we are having trouble refreshing your tasks
or
Last updated at 1/1/1901 12:00AM

After doing some research I ran across the following article that described the issue and provided a fix. It seems that the UPA security setup in 2013 has changed from 2010 as adding additional accounts to the UPA was not required.

For me the issue ended up being that the account I used for the work management service application had not been added to the UPA. After doing this and running an incremental crawl the tasks were showing up from other site collections for the user.

Thanks to Hong Gyem for publishing the information on the issue and the fix
http://honggyem.blogspot.com/2013/05/my-tasks-not-updating-seen-following.html