WSS 3.0 on SBS2003 event 2436 error after install WSS SP3

Have you tried setting the DisableLoopbackCheck in the registry?  Some recent updates from Microsoft are enforcing a rule to block loopback's on the same server which raises problems with Sharepoint.

Thanks - I tried that along with another related MS KB. Good thought though.

The reason I recommended that setting is the sts3 syntax is using the Sharepoint Web Service to execute the search.  This article talks extensively about the topic:
http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/2b760f44-3eed-4ab0-96fb-fdccffe0cfdd

So, we have to determine what the crawler or indexing account can't access the web service.

Okay what would suggest next? I read the article, but I don't exactly see what to look at next.

Check your content scope, maybe we could try changing it to do a http search instead.

I'm knowledgable to the point of being dangerous. How do I check and/or change the content scope?

In the search administration there is an option to set 'Content Sources' (sorry I gave you the wrong term)  If you look closely one will be set for the site you are searching.  In the options you can change the starting URL for the search.

Yes - I check that. It matches the site I want to search.

What are the settings for it?  Can you list them here?

Sorry for being slow. What do you mean by setting?

Are you refering to content databases under application management or sevices under operations on the WSS 3.0 central admin panel?
 

No I mean the content source settings.  You have to edit the content source to see them.

Database server  
 HHVHSRV1\Microsoft##SSEE  
 
SQL Server database name  
 WSS_content  

Database status  
  Ready
 
Database authentication  
 Windows authentication  
 
Search Server  is HHVHSRV1
 
 the URL for the site HHVHSRV1:1730

This is an internal sharepoint. I have no external facing sites, FTP, etc.

I had the same error after installing Service Pack 2 for MOSS. It was Windows SharePoint Services Search.

Here's how I resolved/worked around:

1) Find the offending Database. Use Management Studio "Select name from <configDB>.dbo.objects where id ='<error guid>'". Yours should look like "Select name from Sharepoint_Config.dbo.objects where id ='60864f21-6eda-4db0-a7fc-052c5797fedc'"

2) In your case it looks like it's on a different port, so probably not a main content db. For me it was the SSP content db and I really didn't need to index anything on that site.

I went to Application Management --> Content Databases --> Choose the Web Application with the offending database --> Select the database

Under Search Server if you have a search server selected like "HHVHSRV1"  change it to "Select one..." and hit OK.

Basically I didn't need the content from that site indexed so I excluded it from being acknowledged by the search server and thus it didn't reach out for it creating the error.

I was close to stopping the Windows SharePoint Services Search serivce in Operations. That would delete everything related to that service and you would need to re-config. It may be your best bet if you can suffer some down time and need that content indexed.

Hopefully some options :)

This is on a SBS2003 server which has side by side WSS 2.0 and 3.0 databases. This is required as SBS2003 is tightly integrated with WSS 2.0 and removing same is not wise or recommended. In any case I do want it indexed as it is our primary content database. Oddly enough. The original companyweb is in place to make SBS happy and provide the original featrues and services it provides.

I ran into this problem when I first setup the side by side install. I eventually deleted and recreated the WSS 3.0 database and the search started working. At this point that really isn't an option. I suppose I could create another content database and see if it can be found. Sadly this started when I approved a WSS SP inadvertently. I know better than to do that before researching the issues and work arounds to the SPs.

Thanks for the options:)

Sorry to say the problem still exists. I may be forced to delete the site and recreate it:(....the last thing I wanted to do and the primary reason why I posted on this site.

These are SBS 2008 specific, but will work:

http://msmvps.com/blogs/cgross/archive/2009/03/29/sharepoint-search-amp-event-id-2436-errors-in-sbs-2008.aspx

http://simultaneouspancakes.com/Lessons/2009/08/18/more-fun-with-sbs-2008-and-sharepoint-updates/

Philip

I tried something similar to the links, but I'll try again.

Thanks,
-peter

I tried the solutions provided by MPEC Sinc and it still doesn't work.  I think I might cancel my subscription to this service as it has not proved to be as helpful as I hoped. Like I said I'm 0 for 2 now. Thanks for your help,
Peter

Kewl! :)

Philip

Thanks again.  There isn't a good reason why the solution works, but it does.

-peter