Tag: sharepoint2013

Managed Metadata field error on SharePoint 2013 “The given guid does not exist in the term store”

We recently migrated our SharePoint 2010 content database to SharePoint 2013.

In SharePoint 2013, users tried to use a MMD field/column on a new item form and received this error: “The given guid does not exist in the term store”

After researching the issue, it appears that the error is due to a disconnect between the list column and the MMD values. I remembered the MMD database/terms for the Managed Metadata Service Application is separate from the content database.

I opened the Managed Metadata Service Application on SharePoint 2013 and confirmed there were no terms present:

Optional: To confirm the term store structure back on SharePoint 2010, I opened the Managed Metadata Service Application on the SharePoint 2010 farm, the terms were indeed present:

Since we only migrated the SharePoint 2010 content database (not the Managed Metadata Service Application data), the MMD field fails to retrieve the values from the new SharePoint 2013 farm.

Solution: You will have to migrate the Managed Metadata Service Application from SharePoint 2010 to SharePoint 2013.

For more information on how to upgrade the Service Applications, see http://technet.microsoft.com/en-us/library/jj839719.aspx

“When you upgrade from SharePoint 2010 Products to SharePoint 2013, you must use a database attach upgrade, which means that you upgrade only the content for your environment and not the configuration settings. After you have configured the SharePoint 2013 environment, and copied the content and service application databases, you can upgrade the service applications to SharePoint 2013. This article contains the steps that you take to upgrade the service applications.”

SharePoint 2013 error A potentially dangerous Request.Path value was detected from the client (%) on intranet/mysites access requests from email link

I had a link in my email inbox for “User wants access to ‘Intranet'” sent from the user to myself. I am the Intranet site Owner and recieve access requests.

There is a link to “Accept or Decline this request”

If I click accept from the email Link, I get a SharePoint error:

Sorry, something went wrong
An unexpected error has occurred.

Correlation ID: 00000000-0000-0000-0000-000000000000

Date and Time: 8/5/2013 3:19:39 PM

Go back to site

I took a look in the ULS logs and found this error when I requested the page:

08/05/2013 14:56:19.09 w3wp.exe (0x2BCC) 0x26C4 SharePoint Foundation Runtime tkau Unexpected System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (%).    at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()     at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)

08/05/2013 14:56:19.09 w3wp.exe (0x2BCC) 0x26C4 SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (%).     at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()     at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)

08/05/2013 14:56:19.09 w3wp.exe (0x2BCC) 0x26C4 SharePoint Foundation General aat87 Monitorable

08/05/2013 14:56:19.10 w3wp.exe (0x2BCC) 0x26C4 SharePoint Foundation General ajb4s Monitorable ViewStateLog: Failed to write to the velocity cache: https://intranet/Access Requests/pendingreq.aspx

The URL from the email is: https://intranet/sites/BI/Access%2520Requests/pendingreq.aspx

The link was %2025, as soon as I went to Site Settings > Access requests and invitations, The page loaded and the URL was https://intranet/sites/BI/Access%20Requests/pendingreq.aspx#InplviewHash45f07088-94ce-4184-8700-e90e139485fb=#InplviewHashb2af6c82-aa6b-402e-97f7-b7503c93b415=

Note how the URL is %20, not %2520. This was the cause of the error.

Environment: Windows Server 2012 with SharePoint 2013 March 2013 Public Update.

For now, use the UI or manually change the link. I am reporting this issue to Microsoft and will update this if I find anything out.