Sign up ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have a SharePoint 2013 Provider Hosted App (on premise). When I try to make a social rest call I get the following error code:

-2146232832, Microsoft.Office.Server.UserProfiles.SPS2SAppResourcePolicyException

with the following error message:

An app requested information that is not available from this location

MSDN doesn't provide any clarification on this

share|improve this question

2 Answers 2

I think I'm 100% wrong, but let me give you something to go on with. Do you think maybe you need to ask permission to use the User Profiles?

It doesn't make sense to me why you'd need the user's permission for it, but it's better than the no responses you're getting now, right? Hopefully it's a starting point.

share|improve this answer
Yeah - I read up on permissions and you need Read permissions on User Profiles and write permissions at the Tenant level. – Blake Blackwell Mar 19 '13 at 13:37
So were you able to get it to work using that method? If so, this would be a great Community topic to keep here. I haven't done much Windows 8 development but from all the seminars and workshops I've seen getting system permission is done the way I show in the screenshot I attached.That's why my first thought was that SharePoint probably does it the same way. – EHorodyski Mar 19 '13 at 15:29
Sorry - I meant to say that those are the permissions I have set according to the documentation. Unfortunately those permissions still don't allow access. – Blake Blackwell Mar 19 '13 at 19:14
Could you modify your question to include the REST call as well as your AppManifest.xml? – EHorodyski Mar 19 '13 at 23:52

I encountered this same issue recently and it took me a while to figure out that my distributed cache service instance was corrupted.

If you have the same problem as I had then you should be able to access


but not

~webAppUrl/_api/social.feed/my/feed or ~webAppUrl/_api/social.feed/my/news

Make sure your DC configuration is correct and then run the two lines below with admin rights. Note: I could not manually start the DC service.


As soon as the DC was working properly I was able to access the two feed URLs above.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.