Link to home
Start Free TrialLog in
Avatar of vistasupport
vistasupportFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Sharepoint Foundation Search - crawl cannot be started

Hi all,

I'm getting an issue with one of my Sharepoint web applications not being searchable.  I have two web applications, the other one is indexing fine.

The error in the Application event log is:

-------------------------------
The start address sts4://<servername>/contentdbid={[GUID]} cannot be crawled.

Context: Application 'Search_index_file_on_the_search_server', Catalog 'Search'

Details:
      The object was not found.   (0x80041201)
--------------------------------

From what I can tell, I seem to be missing a root site collection but I can't seem to find anything telling me how to create one!  Can anyone suggest a resolution please?

Many Thanks
Avatar of Justin Smith
Justin Smith
Flag of United States of America image

In Central Admin, Web App Management, there is a link to Create  new site collection.  Just create one at the root URL.  If you already have a root site, the root URL won't be available when you are selecting the URL to create the site at.

Avatar of vistasupport

ASKER

When I create a new site collection, it only allows me to add one below the /sites/ URL.  Does that mean I have a root site?  In which case I guess my problem re the search lies elsewhere?
You may need to disable loopback....

2.Click Start, click Run, type regedit, and then click OK.
3.In Registry Editor, locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

4.Right-click Lsa, point to New, and then click DWORD Value.
5.Type DisableLoopbackCheck, and then press ENTER.
6.Right-click DisableLoopbackCheck, and then click Modify.
7.In the Value data box, type 1, and then click OK.
8.Quit Registry Editor, and then restart your computer.
Yeah, already done that when I was getting access denied on my other web application - this one seems to be a different issue.
Is the problem web app using NTLM authentication?  Or Kerberos?
NTLM, as is the one that's working OK.
ASKER CERTIFIED SOLUTION
Avatar of Justin Smith
Justin Smith
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yes, I can browse http://servername and friendly name (http://intranet) from a workstation, but from the server itself I can only browse to http://intranet - if I try http://servername I get HTTP 404 error.


so you have two url's on the web app.  are your alternate access mappings set correctly?
I thought they were because everything works, but that may be more luck than judgement!! My alternate access mappings are:


Internal URL                                           Zone                                                    Public URL for Zone
http://<servername>                             Default                                                 http://<servername>
http://intranet                                       Intranet                                                http://intranet
http://<public ip>                                  Extranet                                                http://<public ip>

By default, everyone will access http://intranet rather than access by servername.
Those look fine.  Since you can't browse //servername from the server, that is why your search is faling.  This really looks like a loopback issue.  Are you positive you have this disabled?  Do you have a binding in IIS for the server name on port 80 on this site?
Yes, I did that yesterday because my other site was 'Access denied' so the loopback fixed that for me. I've just checked again and all looks again with the registry setting.

I do have a binding is IIS, I have two - the first one (already there) has a blank host name, and I've added one for the servername.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
editing the hosts file resolved the issue.