SharePoint Services 3 Search event errors and update problems

I have written before here about this and mentioned to change the search account, but as now known this will create problems installing updates like SharePoint 3 Service Pack 2.

So changing the accounts is no solution because it creates new problems. Additional information about this problem is found here.

Browsing above problem I found another possible sollution for solving the Event ID:
2436 Windows SharePoint Services 3 Search

The start address cannot be crawled.
Context: Application ‘Search inde file on the search server’, Catalog ‘Search’
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. (0×80041205)

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
3. Right-click MSV1_0, point to New, and then click Multi-String Value.
4. Type BackConnectionHostNames, and then press ENTER.
5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Value data box, type the URL mentioned in the above warning event, and then click OK. (With URL is meant only the remote.domain.com part.)
7. Quit Registry Editor, and then restart the IIS service.

Source: the Official SBS Blog

Posted in Blog, SBS 2008 by ronnypot at December 15th, 2010.
Tags: , ,

One Response to “SharePoint Services 3 Search event errors and update problems”

  1. I just like the valuable information you supply to your articles. I will bookmark your blog and check again right here regularly. I’m moderately sure I will learn many new stuff proper right here! Best of luck for the next!

Leave a Reply

Sharing Buttons by Linksku