Search EggHeadCafe's Job Board
EggHeadCafe Silverlight WPF ASP.NET VB.NET C# Excel SQL Server SharePoint
search
SharePoint GroupsView
Sharepoint Portalserver
Sharepoint Portalserver Development
Sharepoint Windowsservices
Sharepoint Windowsservices Development
Sharepoint Design_And_Customization
Sharepoint Development_And_Programming
Sharepoint General
Sharepoint Setup_And_Administration

Group SummariesView
.NET Framework
Access
BizTalk
Certifications
CRM
DDK
Exchange Server
FoxPro
French
French .NET
Games
German
German .NET
Graphic Design
IIS
Internet
ISA Server
Italian
Italian .NET
Maps
MCIS
Miscellaneous
Mobile Apps
Money
MSN
Networking
Office
Ops Mgr
Publisher
Security
SharePoint
Small Business
Spanish
Spanish .NET
SQL Server
Systems Management Server
Transaction Server
Virtual PC / Virtual Server
Visual Studio
Win32
Windows 2000
Windows 2003 Server
Windows 7
Windows Live
Windows Media
Windows Update
Windows Vista
Windows XP
 

View All Microsoft Sharepoint Windowsservices Posts  Ask A New Question 

WSS 3.0 Search Crawler causes 2436 gatherer events

MarcelABernard posted on Thursday, June 07, 2007 9:13 AM

I read countless weblogs and googled and tried several solutions.
Still, no lucj to get this search thing working.

I have a fresh 3.0 WSS install running on a VMWare server
Windows 2003 SP1 . latest patches applied.

Running SQL 2005 remote
I have created 3 sites http://blogs http://ictweb and http://wssdemo
They use host headers DNS CNAME aliases for resolving the real Hostname.
I extended one of the sites using an alternate port number on the current
nodename, no luck so far.

It uses NTLM authentication and it uses a domain account DOMAIN\MOSSCAS to
crawl the tree. This account has acces to all content, which I checked by
loggin in to the sites with that account.

The search service still compains about insufficient access rights to crawl
the content.

I'm stuck here
Any ideas left ?
--
Marcel A. Bernards
reply

 

Hi Marcel,what info can you see in the event log?Logs in sharepoint?

Daniel Bugday posted on Thursday, June 07, 2007 1:12 PM

Hi Marcel,
what info can you see in the event log?

Logs in sharepoint?

/Daniel Bugday
reply

WSS 3.0 Search Crawler causes 2436 gatherer events

MarcelABernard posted on Friday, June 08, 2007 3:40 AM

Event Type:	Warning
Event Source:	Windows SharePoint Services 3 Search
Event Category:	Gatherer
Event ID:	2436
Date:		8-6-2007
Time:		8:55:00
User:		N/A
Computer:	ECNSPS1
Description:
The start address
crawled.

Context: Application 'Search index file on the search server', Catalog
'Search'

Details:
Access is denied. Check that the Default Content Access Account has access
to this content, or add a crawl rule to crawl this content.   (0x80041205)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:

I got 401's in the IIS logfiles too, which explains the event.
I tried to change the IIS application pool to the MOSS Service account
instead of the Network Service account, but that stopped the site completely.
It logged a 3760 Sharepoint event failing to access the database

Still puzzled why searching on a fresh WSS 3.0 out of the box installation
does not work. I am about to dump the Databases and do a complete
reinstallation
I also logged a MS Call for this case.

--
Marcel A. Bernards
reply

I finally figured out what was happening here.

MarcelABernard posted on Thursday, June 14, 2007 11:42 AM

I finally figured out what was happening here.
It was not related to user crawler permissions at all.

This had hit us before in the WSUS beta 2 we runned.
for some reason the crawler did crawl itself on its' own node but it uses
the proxy server. Our proxy system manager saw 5 minute blurbs in his
proxyserver log.
The autoproxy scripts should route the server adress as LOCAL when crawling,
but it did not for unknown reasons. We hav a few systems here which behaves
this way.
This was one of them. it might be related to a security feature/fix, dunno.
Browsing the pages with IE in the foreground works perfect though.

How did I solve the crawler issue?

I did a RunAs Domain\crawler Iexplore.exe and disabled automatic detect
proxy and
pooffff, it started to crawl the whole shebang.

Windows Authentication does not work any more if you run crawls trough a
proxy hop, hence the errors in the application event log.

Why some systems do not correctly use the autoproxy javascript correctly is
still a mystery to us. Might be script engine problems. javascript autoproxy
scripts are very hard to debug.

--
Marcel A. Bernards
reply

Hi Marccel,I have the same issue you've experienced.

Lp1 posted on Monday, July 30, 2007 2:16 AM

Hi Marccel,
I have the same issue you've experienced. Can you please guide me on your
solution? I couldn't understand the Run as command, where and how to execute
it?
I'm a newbie to the system side of WSS.
Thanks a lot in advance.
reply

 
 

Previous Microsoft Sharepoint Windowsservices conversation.