SharePoint Search Fails with Correlation ID Provided

After performing a SharePoint 2013 upgrade we were having trouble with our search functions and got a rather generic error message.

After doing a migration upgrade of SharePoint 2010 to SharePoint 2013, search failed with:

Sorry, something went wrong. A correlation id is provided.

We checked our Content Sources from Central Administration->Manage Services on Server->SharePointServer Search->Search Service Application->Content Sources  and found that Full Crawls had completed successfully.

You will find a TON of log enties for that correlation id, so finding the root cause is daunting.  Buried in the results you will find a 500 Service Unavailable error connecting to the Metadata Management Service.

In the Search Service Application, we saw that in Queries and Results->Search Dictionaries, we had an error:


Managed Meta Data Error

The Managed Metadata Service or Connection is currently not available.  The Application Pool or Managed Metadata Web Service may not have been started.

We verified that the IIS->Application Pool had all pools started.

We verified that Central Administration->Manage Services on Server->Managed Metadata Web Service was started.  (This service is generating the 500 Service Unavailable.)

We then found that when we select Central Administration->Manage Service Applications->Managed Metadata Service Application (your name may be slightly different) and click Properties from the ribbon, we saw the same error shown in Search:

The Managed Metadata Service or Connection is currently not available.  The Application Pool or Managed Metadata Web Service may not have been started.

There are a lot of suggestions for solving this, but we fixed ours when we:

In Central Administration->Manage Service Applications, we deleted the Managed Metadata Service Application Proxy and the Managed Metadata Service Application.  (Don’t delete the data when you do this or you will lose your SQL Server database.)

We then repeated our PowerShell actions from the migration/upgrade:

$applicationPool = Get-SPServiceApplicationPool -Identity ‘SharePoint Web Services default’

$mms = New-SPMetadataServiceApplication -Name ‘Managed Metadata Service Application’ -ApplicationPool $applicationPool -DatabaseName ‘Managed Metadata Service_Acumen’

New-SPMetadataServiceApplicationProxy -Name ‘Managed Metadata Service Application Proxy’ -ServiceApplication $mms -DefaultProxyGroup

Change your Name and DatabaseName values.
Our first search test failed, but while we were watching the ULS Viewer, we saw lots of entries with the same correlation ids.  We tried search again after about 3 minutes and it worked.

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"Sorry, Word Web App can't open this ... document because the service is busy." Office WebApp

Problem: Intermitten requests are not returning the pdf/word documents.  Most requests are working and occasionally 1 request doesn't work.  Every 4th request tries to get the pdf to display on Office Web Apps for a few minutes without any error message and then stops trying and displays the message "Sorry, Word Web App can't open this ... document because the service is busy." Initial Hypothesis: Originally I thought it was only happening to pdfs but it is happening to word and pdf documents (I don't have excel docs in my system).  My monitoring software SolarWinds is badly configured on my OWA servers as the monitor is showing green, drining into the servers monitoring the 2 application monitors are failing.  The server should go amber if either of the 2 applications fail and in turn red after 5 minutes.  At this point I notice that I can't log onto my 4 OWA/WCA server.  Web request are not being returned.  I look at my KEMP load balancer and it says al
Continue Read

Unable to create a "Send to Connection"- verification failed -url is a not a valid routing destination

ISSUE : Unable to successfully create a send to connection. When creating the Send to connection from Sharepoint 2010 Central Administration and click on Test URL for the Destination URL , we get the following error "verification failed -url is a not a valid routing destination" we see the following entry in the ULS logs Url validation failed for http://gmallya.test.com/sites/testrecordcenter/_vti_bin/OfficialFile.asmx   during Record and document center connection configuration with exception The request failed with HTTP status 401: Unauthorized .:  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)     at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)     at Microsoft.SharePoint.OfficialFileSoap.GetServerInfo()     at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.<>c__DisplayClass2.&l
Continue Read