Thank you Kevin, that was just the information I needed to fix WSS 3.0 search. After changing the default url WSS 3.0 search no longer worked. Changing it back to the default (servername) and then extending the web application (with a custom zone and new url) fixed the search. Now I have the search functioning and the new url!

After a week of googling, applying registry changes recommended by MS, applying other similar solutions provided by other blogs, and so forth, yours was the one that held the key in swapping the default URL....thanks a lot - I actually received a set of search results from the thing for the first time!!

Cheers.

Dude, it worked. I've been looking thru all this other crap on google for hours.
thank you very much.

Hi,

thanks for that entry, it lead me to the right way. I solved it a bit easier. What you got to do (if your default site is https and you got an alternate mapping without https) is switching this two, so that a none https site is the default site (which is used for crawling).

Kevin,

I sure am glad that I came across your article in the midst of hours of searching for a solution to this problem... just wish I would have found it at the beginning of my hunt for a fix!

Thanks,
Mark

Thanks for posting this Kevin - it fixed the problems I was having with search!

Thanks alot. It works for me.

To bad,

Don't work for me.. Hellllppp pls..

Error: (via Central Admin)
File not found...

Here is the eventviewer error

Could not import the registry hive into the registry
because it does not exist in the configuration database.

Context: Application 'b3802962-18be-4c13-88a5-587f07360c36'

I already use the domainname\administrato account but still no luck..

Pingback from keyongtech.com

SBS 08, Event ID 2436 Windows SharePoint Services 3 Search | keyongtech

i tried all the other cr*p and this was the only thing which worked. thank you.

Thanks Kevin,

your posting solves also my search problem. I changed the url with alternate access mapping right in the begining an till now search did not start to work.
So with you hint I changed it back to the server name and add the other url as second address in the Intanet zone and after this search starts to work and I am still able to access the site with the second url.

Thanks a lot
Peter

I like everyone else was having the same problem and I been searching for a fix for at least a month now. Have gone through countless Sharepoint Forums, but no ones solutions were working for me. I tried yours and it did.... immediately. You've definitely made my Monday. Kind of sucks that I've peaked so early in the morning though, nothing else is going to top this today!

Thanks,
Hassan

I have an issue that this may solve. End users have two ways to access our sharepoint. One is http://sharepoint.domain.com" rel="nofollow">http://sharepoint.domain.com and the other is http://sharepoint. We are finding that search does not work if the end user is just accessing sites using http://sharepoint. Ive also found that http://sharepoint is not listed in the area you noted above. Both sites are intranet sites.

Would the search work simply by adding http://sharepoint as an intranet site with the http://sharepoint.domain.com" rel="nofollow">http://sharepoint.domain.com as domain?

Thanks,
Rachel

Dear Kevin, I've encounter the below problem when I was completed the SP3 for WSS 3.0 in my MOSS box.

Category: Gatherer
Type: Warning
Event ID: 2436

The start address <sts3://abc:24326/contentdbid={d5be8157-467c-4fc3-935a-1072c6026ac8}> cannot be crawled.

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

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

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



Could you mind to help !! Thanks !