Showing posts with label mysite. Show all posts
Showing posts with label mysite. Show all posts

14 April, 2014

'We hit a snag' Mysite error - SharePoint 2013

Before I hit the actual scenario, let me share some existing documentation on the same:
1.   Clicking on a followed site returns "We hit a snag" in a publisher-consumer scenario: http://support.microsoft.com/kb/2831053/EN-US

2.   "We’ve hit a snag" error message when a user clicks the Followed Sites or Followed Documents button in a consuming SharePoint Server 2013 farm

Note:
If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Problem description:
I came across this issue with respect to Mysites when I clicked on the section “Sites I’m following”, following the error message:

Error message:
"We hit a snag. This link doesn't work anymore, likely because the item was moved or deleted. You might have luck searching for it and following it in its new location."

Troubleshooting done:
1.   Recycled the app pool but that didn’t solve the issue.
2.   Tested the link by directly opening in browser but that also didn’t solve the issue
3.   Executed IISRESET – resolved the issue temporarily but reoccurred again after some time.
4.   Tried changing the app pool account of Mysites with the Farm account – Success! But this is not a solution for me!

What’s the bottom line? – With the help of 4th troubleshooting step, it’s very clear that Mysites app pool account doesn’t have sufficient permissions.

I have already cross checked that this account (i.e. Mysites apppool account) has sufficient permissions from the SharePoint side but I wasn’t sure about the SQL side.

Finally I got it!

Resolution:
1.   Open the SQL Server management studio
2.   Security -> Logins
3.   You will see the complete list of accounts
4.   Right click on the mysite app pool account -> Properties
5.   Go to User Mapping directly
6.   Click on the specific database where the problem is and database role membership will get highlighted
7.   Select the checkbox ‘SPDataAccess’ and click OK
8.   That’s it – You are done! (FYI – it doesn’t required IISRESET)

Please check the results and let me know in case of any queries. I would be more than happy to help you as well as resolves your issues, Thank you.

Product Applies To:
o   SharePoint 2013

Reference:

25 February, 2012

There are one or more errors with the data you have entered. The site does not contain a default keywords term store


An end user might encounter this error message when trying to close his or her profile after updating the following information: Ask Me About, Skills etc

What is the reason behind this error?
This error can occur when the SharePoint administrator has not configured a Managed Metadata service application and specified the connection as the default keyword term store for the Web application that hosts My Sites.

What is managed metadata service application?
A Managed Metadata service application enables Web applications to store and access keywords from a managed metadata term database.

Resolution:
For My Sites, this functionality is required for users to specify keywords in the Ask Me About section or use keywords for social tagging. A Managed Metadata service application is highly recommended for My Sites. It must be configured as the default keyword term store for the Web application.

If you have 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

19 February, 2012

You do not have access to edit this user profile

Yesterday, one of our user has logged a ticket by mentioning that he is not able to update his skills in mysite.

Error message: You do not have access to edit this user profile

This error is very tricky but simple to understand and troubleshoot where exactly the problem is as per the Microsoft guidelines.

This error can occur if Managed Metadata service application is connected to the Web application that hosts My Sites and the Managed Metadata Service Application connection has only Read Access to Term Store permission. 

What is the role of managed metadata service application?
A Managed Metadata service application enables Web applications to store and access keywords from a managed metadata term database. For My Sites, this functionality is required for users to specify keywords in the Ask Me About section or use keywords for social tagging. A Managed Metadata service application is highly recommended for My Sites.

To resolve this error, please do the following:

1-Central Administration-Click Application Management

2-In the Service Applications section, click Manage service applications.

3-On the Manage Service Applications page, click the User Profile service application that is associated with the Web application that hosts My Sites, and then, in the Operations section of the ribbon, click Permissions.

4-In the Connection Permissions for Managed Metadata Service, click either Read and Restricted Write Access to Term Store or Full Access to Term Store.

After following the above steps, the issue has been resolved and user can update the profile without any problems.

If you have 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