SPMicrofeedFeedCacheService.GetUserProfile() - UserProfileApplicationProxy not available 0e49dc9b-d278-1089-b021-6e2138766eae

To correct this issue, complete the following steps:

Log onto the SharePoint 2013 Central Administration site as a farm administrator

Navigate to 'Manage Service Applications'

Highlight the User Profile Service Application

Click the 'Permissions' ribbon toolbar button:

Add the account that is used to run the User Profile Service Application and give it full control:

Click OK

At this point it is usual to see the following displayed in the 'Everyone' tab of the user's MySite:

It's worth checking the SharePoint logs at this point to see what additional errors may be reported (note that you will see 'We're still collecting the latest news' if no users have posted anything, so create a post to ensure that you have something waiting in the queue). In my case, I saw the following:

The default communication scheme for many of the SharePoint 2010 Service Applications is ‘http’ (i.e. unsecured). This can be changed easily in the GUI by selecting the service application and clicking the ‘publish’ ribbon button:

It should however be noted that a number of Service Application communication schemes run by default over https and cannot be modified, these are:

Application Discovery and Load Balancer Service Application

Search Administration Web Service

Secure Store Service Application

Security Token Service Application

The communication scheme of a few Service Applications cannot be inspected using the GUI (and the publish ribbon button remains greyed out when they are selected):

SharePoint Server ASP.NET Session State Service

SharePoint Session State Service Application

WSS_UsageApplication

Modifying the communication scheme of all of the Service Applications can be time consuming and can be error prone, especially when using SharePoint 2010 Enterprise and the Office Web Applications with all of the Service Applications available configured for use. With this in mind, the following PowerShell will change the communication scheme of all of the Service Applications where it is possible to do so to https: