SharePoint 2013 Preview Newsfeeds showing nothing

So you've build your farm, configured Manage Metadata, Search, User Profile Service and Mysites. The first thing you obviously want to check out are the cool new social features.
You login and fire off your first post, in anticipation of the reactions of your fellow social pioneers in your company.

A day goes by but, nothing happens… What is going on here?
You check your feed but it keeps saying "We're still collection the latest news. You may see more if you try again a little later."
There must be something wrong here. When you crank up the ULS logs to verbose on the Microfeeds and User Profiles categories in the ULS logs:

"Microfeeds", "User Profiles" | Set-SPLogLevel -TraceSeverity Verbose

you will find a strange message stating the User Profile Service Application Proxy is not available:

nasq    Medium     Entering monitored scope (SPMicrofeedFeedCacheService.GetPublishedFeed). Parent FeedCacheService.GetPublishedFeed    e554c59b-9365-2015-6119-380e065adfbb

d22b    High     Failure retrieving application ID for User Profile Application Proxy 'User Profile Service Application 2': Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: UserProfileApplicationNotAvailableException_Logging :: UserProfileApplicationProxy.ApplicationProperties ProfilePropertyCache does not have 5c3e254a-4ab9-4736-a5f1-58d582d1d6d0 at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties() at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_AppID()    e554c59b-9365-2015-6119-380e065adfbb

ahv64    High     SPMicrofeedFeedCacheService.GetUserProfile() - UserProfileApplicationProxy not available    e554c59b-9365-2015-6119-380e065adfbb

b4ly    Medium     Leaving Monitored Scope (SPMicrofeedFeedCacheService.GetPublishedFeed). Execution Time=2.064    e554c59b-9365-2015-6119-380e065adfbb


At first it did not hit home for me, but then I remembered similar issues when using powershell to manage the UPA back in SharePoint 2010. This was basically solved by granted (sharing) permissions to the UPA proxy.

The problem in this case is that my MySites are hosted in a different application pool from my UPA service application. Although the MySites application pool account is added, the service app application pool account is not.

Either grant the application pool account hosting the UPA Sharing Permissions through Central Admin:




Or use the following powershell script:


$account = New-SPClaimsPrincipal <domain\user> -IdentityType WindowsSamAccountName

$UPA = Get-SPServiceApplication <ID>

$sec = Get-SPServiceApplicationSecurity $UPA

Grant-SPObjectSecurity $sec2 -Principal $account -Rights "Full Control"

Set-SPServiceApplicationSecurity -Identity $UPA -ObjectSecurity $sec


The magic happens, and voila; the feeds start showing!


Comments (10)
  1. Anoop Srivastav says:

    Hello Mark, Nice post

    I am facing same issue in my SP2013 project, I have applied your steps in CA (added my app pool account user and given full permission). Still problem exists.

    Then i have tried with your PS commands that are giving error.

    Can you please give more options with PS or something else ?

  2. Anders Nilsen says:


    I'm also having the same issues as Anoop over here. Did what you suggested, but still no newsfeed.. Any ideas?

  3. Kevin says:

    Thank you…thank you very much!  This security fix resolved an issue in my environment (2013 RTM with March 2013 CU) where the newsfeed showed internal error messages, and ULS was full of cache related items.  You da man!

  4. Bob Hagerman says:

    Thanks Mark. Your post just fixed my problem.

  5. Jyotsna Yendapally says:

    Thank you! This saved us today!

  6. ali says:

    I am getting error at the time of migrating mysite from 2010 to 2013.

    We’re still collecting the latest news. You may see more if you try again a little later.


    We are about to ready!!

    Awaiting your reply!!

    Tanks Ali

  7. Jignesh Patel says:

    if you are doing upgrade it looking for your old mysite application. Please check it may cause this issue

  8. Jason says:

    We have this issue "We’re still collection the latest news. You may see more if you try again a little later." but it only happens maybe 2 out of 10 times, the rest of the time it works. Our rights are correct but it still shows up every once in a while,
    could it be a timer job is set wrong, or SQL slowness issue?

  9. HermanBrood says:

    There is a small error in the script. It should be:

    $account = New-SPClaimsPrincipal -IdentityType WindowsSamAccountName

    $UPA = Get-SPServiceApplication

    $sec = Get-SPServiceApplicationSecurity $UPA

    Grant-SPObjectSecurity $sec -Principal $account -Rights "Full Control"

    Set-SPServiceApplicationSecurity -Identity $UPA -ObjectSecurity $sec

  10. C. T. Haun says:

    I like this article but found two possible problems. First, in Central Admin, I can highlight my UPA Proxy fine but the Permissions option remains grayed out. Not sure why. Same for all my proxies. So i considered the powershell script as a workaround
    but noticed that it uses Get-SPServiceApplication rather than Get-SPServiceApplicationProxy. I thought the idea was to set permissions on the proxy of UPA rather than on the UPA itself. Thoughts? Thanks!

Comments are closed.

Skip to main content