Michael Green
asked on
The start address cannot be crawled. Context: Application 'Search index file on the search server', Catalog 'Search'
Hi,
I'm getting the following two messages every five minutes in the Application log. This is a NEW Small business Server 2008 server.
Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 9/08/2010 9:15:14 PM
Event ID: 2436
Task Category: Gatherer
Level: Warning
Keywords: Classic
User: N/A
Computer: TMGS02.TheMineraGroup.loca l
Description:
The start address <sts3s://remote.theminerag roup.com.a u:987/cont entdbid={4 7084d13-37 15-4ec5-a0 15-651e65c 3a61b}> cannot be crawled.
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3 Search" />
<EventID Qualifiers="32768">2436</E ventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2010-08-09T11: 15:14.000Z " />
<EventRecordID>7515</Event RecordID>
<Channel>Application</Chan nel>
<Computer>TMGS02.TheMinera Group.loca l</Compute r>
<Security />
</System>
<EventData>
<Data>
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)</Data>
<Data>sts3s://remote.themi neragroup. com.au:987 /contentdb id={47084d 13-3715-4e c5-a015-65 1e65c3a61b }</Data>
</EventData>
</Event>
Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 9/08/2010 9:15:14 PM
Event ID: 2424
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: TMGS02.TheMineraGroup.loca l
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Application 'Search', Catalog 'index file on the search server Search'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3 Search" />
<EventID Qualifiers="32768">2424</E ventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2010-08-09T11: 15:14.000Z " />
<EventRecordID>7516</Event RecordID>
<Channel>Application</Chan nel>
<Computer>TMGS02.TheMinera Group.loca l</Compute r>
<Security />
</System>
<EventData>
<Data>
Context: Application 'Search', Catalog 'index file on the search server Search'</Data>
</EventData>
</Event>
How do I fix these ?
I'm getting the following two messages every five minutes in the Application log. This is a NEW Small business Server 2008 server.
Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 9/08/2010 9:15:14 PM
Event ID: 2436
Task Category: Gatherer
Level: Warning
Keywords: Classic
User: N/A
Computer: TMGS02.TheMineraGroup.loca
Description:
The start address <sts3s://remote.theminerag
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3 Search" />
<EventID Qualifiers="32768">2436</E
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2010-08-09T11:
<EventRecordID>7515</Event
<Channel>Application</Chan
<Computer>TMGS02.TheMinera
<Security />
</System>
<EventData>
<Data>
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)</Data>
<Data>sts3s://remote.themi
</EventData>
</Event>
Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 9/08/2010 9:15:14 PM
Event ID: 2424
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: TMGS02.TheMineraGroup.loca
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Application 'Search', Catalog 'index file on the search server Search'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3 Search" />
<EventID Qualifiers="32768">2424</E
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2010-08-09T11:
<EventRecordID>7516</Event
<Channel>Application</Chan
<Computer>TMGS02.TheMinera
<Security />
</System>
<EventData>
<Data>
Context: Application 'Search', Catalog 'index file on the search server Search'</Data>
</EventData>
</Event>
How do I fix these ?
what account are you using for content access (crawl account)? is there a web application policy giving it READ access to all your web apps?
Any progress SGSMikeG?
ASKER
Hi,
I reviewed this :
http://support.microsoft.com/kb/927012
which seems to make some sense.
The question I have is this - why would a NEW Small Business Server install configure the Search Service Account to use 'Local Service' when even the help text on the web page says :
"The search service account must not be a built-in account in order to access the database. Examples are Local Service and Network Service"
Is this a Microsoft bug in the setup ?
I reviewed this :
http://support.microsoft.com/kb/927012
which seems to make some sense.
The question I have is this - why would a NEW Small Business Server install configure the Search Service Account to use 'Local Service' when even the help text on the web page says :
"The search service account must not be a built-in account in order to access the database. Examples are Local Service and Network Service"
Is this a Microsoft bug in the setup ?
Just the way it has always been. I always set to a domain account, fix iis loopback, and it works from there.
ASKER
So any special requirements for the domain account ? Just use an administrator account ?
Sorry missed your reply (in fact I recally typing a reply, but obviously did not press submit).
You can use any account that has access to all the pages that need to be crawled. In "SBS Land" you can probably get away with just using the adminisrator account. But it is probably cleaner to creae a special account for this purpose.
useful tip to force a full crawl:
#> Stsadm -o spsearch -action fullcrawlstart
You can use any account that has access to all the pages that need to be crawled. In "SBS Land" you can probably get away with just using the adminisrator account. But it is probably cleaner to creae a special account for this purpose.
useful tip to force a full crawl:
#> Stsadm -o spsearch -action fullcrawlstart
ASKER
Wouldn't it be better to create a dedicated account ? That way it would be easier to pin down other errors ? Does that separate account need to have Adminitrator access ?
So fix is :
1. Create separate account for Sharepoint
2. Grant it domain adminstrator (or lesser required access)
3. Run :
Stsadm -o spsearch -action fullcrawlstart
Correct ?
So fix is :
1. Create separate account for Sharepoint
2. Grant it domain adminstrator (or lesser required access)
3. Run :
Stsadm -o spsearch -action fullcrawlstart
Correct ?
Yes
And Disable IIS loopback checking if it still does not work
http://support.microsoft.com/kb/896861
And Disable IIS loopback checking if it still does not work
http://support.microsoft.com/kb/896861
Do NOT give your crawl account domain admin privledges. Like I asked you before, the account should have a web app policy giving it READ access to all sites. This can be set manually (Cent Admin - App Mgmt - Policy for web app), but it should set auto once you assign a crawl account.
ASKER
I'm assuming the new account will need 'Log on a a Service' ?
Yes. and a few others
Although this is written for SP2007, I believe same applies to WSS3.
http://www.shareesblog.com/?p=247
Domain Users, Local Administrator on each front-end server, Member of IIS_WPG, WSS_WPG, and WSSAdmin_WPG, Impersonate a client after authentication. Log on as a service
Although this is written for SP2007, I believe same applies to WSS3.
http://www.shareesblog.com/?p=247
Domain Users, Local Administrator on each front-end server, Member of IIS_WPG, WSS_WPG, and WSSAdmin_WPG, Impersonate a client after authentication. Log on as a service
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://support.microsoft.com/kb/896861
Method 2: Disable the loopback check (less-recommended method)
The second method is to disable the loopback check by setting the DisableLoopbackCheck registry key.
To set the DisableLoopbackCheck registry key, follow these steps:
1. Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
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\
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.