Search crawl - Could not Connect to the server
My search stopped working out of nowhere on SharePoint 2007. In the crawl log in CA I am getting the error "Could not Connect to the server. Please make sure the site is accessible." This is what I've done so far, I rebooted the server, restarted IIS, verified the default content access account, changed the default content access account, I changed the value of DisableLoopbackCheck in regedit, resetted all crawl content and restarted the service "Office SharePoint Server Search". Would anyone have any other ideas what the problem can be? Here are the two errors in my event viewer when I run a full crawl.
Event Type: Warning
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2436
Date: 11/3/2009
Time: 11:35:41 AM
User: N/A
Computer: MYSITE
Description:
The start address <http://mysite/site1> cannot be crawled.Context: Application 'MySharedServices', Catalog 'SP_Content'
Details:
Could not Connect to the server. Please make sure the site is accessible. (0x80041209)For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
---------------------------------------
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2424
Date: 11/3/2009
Time: 11:35:41 AM
User: N/A
Computer: MYSITE
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.Context: Application 'MySharedServices', Catalog 'SP_Content'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Answers
- I think you may have done everything from the standpoint of SharePoint but have you checked to see if the Content Access account have at least Read Permissions on the Source. Could somone have changed permission on the Content Source? could the path to the Content Source change? have you gone verbose in the 12 Hive Logs, that may give you more insights?
- Marked As Answer byGuYumingMSFT, ModeratorThursday, November 05, 2009 9:32 AM
- Thank you for the quick reply. I figured out the problem. I was pointing to the wrong IP in my hosts file.
- Marked As Answer byGuYumingMSFT, ModeratorThursday, November 05, 2009 9:32 AM
All Replies
- I think you may have done everything from the standpoint of SharePoint but have you checked to see if the Content Access account have at least Read Permissions on the Source. Could somone have changed permission on the Content Source? could the path to the Content Source change? have you gone verbose in the 12 Hive Logs, that may give you more insights?
- Marked As Answer byGuYumingMSFT, ModeratorThursday, November 05, 2009 9:32 AM
- Thank you for the quick reply. I figured out the problem. I was pointing to the wrong IP in my hosts file.
- Marked As Answer byGuYumingMSFT, ModeratorThursday, November 05, 2009 9:32 AM

