Web Application not showing in search results

Hi!

We have SP2013 enterprise edition

Last week we had an update from MS and now our SP search isn't picking up the "main" site.  it shows the "Mysites"(seperate web application).

The search worked perfect before the update....We've been on a ton of blogs but nothings seems to work.

We've mapped the server mapping, checked permissions...  

http://sharepoint.stackexchange.com/questions/17635/search-crawl-access-denied

https://support.microsoft.com/en-us/kb/896861


I'm losing hope!

August 27th, 2015 5:04pm

Hi

From your description, after you install an update to SharePoint, the Web Application is not showing in search results.

For your issue, I suggest you check whether the web application is added to the content source.

Check the crawl log.

Check the ULS log to determine the exact cause of the error. ULS log is at:      

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

Best Regards,

Lisa Chen

                              

Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 2:35am


The web application is in the content source.  I recreated it too just to be sure.

Crawl is showing a lot of this...

Component and System=Content1-a94e47de-21bc-47ed-b7c3-86f8d06f7b8d, Correlation ID=c265f64b-ed99-4584-8ef8-59ceaa188aa4, Tenant ID=0c37852b-34d0-418e-91c6-2ac25af4be5b Error code=3011, Flow Name=Microsoft.CrawlerFlow, Operator Name=InjectedOpForExceptionHandling/EventStarted_DocumentRetrieval, Message=The processing of item fails with error Failed to retieve blob from URI <path>

I've added the alias to the Server mapping

I've added the alias Alternative Mapping

We've changed registry keys:

http://sharepoint.stackexchange.com/questions/17635/search-crawl-access-denied

I've followed this blog:

https://social.technet.microsoft.com/Forums/lync/en-US/95f57fb3-6b14-479b-8f6e-d39f1f634343/failed-to-retrieve-blob-from-uri-error-in-sharepoint-2013-search-crawl-logs?forum=sharepointsearch

my folder is named different but I've added the permissions as suggested.  still nothing.


August 29th, 2015 9:08am

MICROSOFT!!!!  this is a bunch of crap!!!  Why is there NO help on this subject....?  I 've seen many questions related to this subject and yet there IS NO clear answer as to why this happens or what to do about it.  We've followed every Registry change, permission change, server mapping, Alternative mapping..etc trying to figure this out....  A ton of man hours!!! and nothing....  This all happened after the MS update on August 20.

Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2015 10:24am

Hi Larry,

After you patched the update, did you run the configuration wizard on all the servers in the farm? Have you tried an index reset, then a full crawl?

Best Regards,

David

September 3rd, 2015 6:50am

Hi David!  

Thanks for responding...

We have not re-run the configuration wizard?  Why would we have to do that? I will do that today.  

We have tried to index and re-crawl everything...Deleted and recreated the service EXACTLY like the test environment and it still doesn't work. 

Larry


Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2015 10:39am

okay....so we did that (Config wizard)

Errors encountered:

A Database column (dbo.DataRange > LowerSubRangeMode) must be unique...I found this in table in the Service Application Service Analytics DB and App Services DB...  I deleted the App Service is that isn't working proper anyway...I thought this is pretty odd, since they are the ones creating the DB's

After that deletion the configuration wizard completed.

That still didn't fix this issue.  It was now saying it couldn't find the Proxy, so I deleted the search service application, created it again.

NOW here is where the problem I think shows itself...

When you create a Search Service it is supposed to "by default" find the SharePoint "local" SharePoint sites...

The only sites it's showing is the 2nd Web Application for the users...  "UserSite:8080"

IT DOES NOT SHOW THE "MainSite:80" ROOT SITE WHERE EVERYTHING "LIVES"

Larry

September 3rd, 2015 6:19pm

Hello Larry,

Thanks for your detailed information. Could you please share us the screenshot of Manage web application and content source in the search service application? Thanks.

Best Regards,

David

Free Windows Admin Tool Kit Click here and download it now
September 4th, 2015 1:12am

Hi David!

I'm attaching the pictures as requested with the log info.

I did re-index the site, ran a full crawl...  took less than 2 hours. Good sign!

You'll see that I'm at least getting successes up in the 30,0000 plus... Good sign!

The errors are know errors...  Someone modified a Library page and it broke it.   

The warnings are about documents being to large... (not concerned with that now)

When searching for say SOPs, it will pull everything from the File server and the 8080 site...AND it shows the "AppStore" site which a site under the root site.  MainSite:80/site/AppStore

This is the ONLY item that shows when you search under the main site in the search results.  There are NO restrictions on the Results page of the search.

What I have found interesting and I think that maybe if I can solve this it may help or solve this issue too, is that we are unable to follow documents as well.  

We are getting:  "Unexpected response from server. The status code of response is '400'. The status text of response is 'Bad Request'

There is no other information on this error.

Thank you David!!!  I appreciate the help....  let me know what else you need.


September 4th, 2015 2:26pm

Hi Larry,

Error code 400 indicates that the request contains incorrect syntax. Could you please check the request if there is any syntax error?

Also you mention that we are unable to follow documents, may I know if we can open the documents with no error?

Best Regards,

David

Free Windows Admin Tool Kit Click here and download it now
September 6th, 2015 1:09am

Hey David,

Sorry for the late reply, I'd been on vacation...saw this, tried to respond throw phone and didn't work.... (any way)

Yes we can open the documents no problem.

We used a Template after we installed SP2013 for the pages.

Larry

September 9th, 2015 10:32am

Right, first things first: 'Searching' for content is a waste of time. You can see if something has been indexed by using the crawl history and searching by URL. Use the root URL for the web application and see if it's worked or not. You have no top level errors which is a good sign.

Have you re-added the content web application to the local SharePoint sites content source?

Free Windows Admin Tool Kit Click here and download it now
September 9th, 2015 6:51pm

Hi Alex,

Yes...I've added the content web application to the content source (Although it should've have shown by default, like the My site web application)

I see this:

http://mainsite Deleted by the gatherer ( The start address or content source that contained this item was deleted and hence this item was deleted. )

Then  

http://mainsite crawled

Then

http://mainsite  Error while crawling LOB contents. ( Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException The shim execution failed unexpectedly - Exception has been thrown by the target of an invocation..: System.Web.Services.Protocols.SoapException There was an error processing this request.; SearchID = 

Then http://mainsite/ <crazy GUID>

Thoughts?

Larry

September 10th, 2015 5:34pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics