WSS 3.0 on SBS2003 event 2436 error after install WSS SP3

After installing SP3 for WSS 3.0 the search function no longer returned results and the 2436 errors started. The event log (sans server and DB name) follows, but I have tried the following:
Changing accounts under search service for content and search per (;en-us;927012) to read enabled users (same and different) for the content and search databases. Restarting the the service. Stopping and creating a new search database. Not to mention about 4 or 5 (blocked items, etc.) other suggested changes including AAM. So what do I try next? I can't help, but think this is something related to SP3 as it had been working some time (1+ years) and the installation is per MS recommendations for a parallel install of WSS 2 and 3 on SBS2003.

Event Type:      Warning
Event Source:      Windows SharePoint Services 3 Search
Event Category:      Gatherer
Event ID:      2436
Date:            5/12/2009
Time:            6:10:03 PM
User:            N/A
Computer:      XXXXXXX
The start address <sts3://XXXXX:1730/contentdbid={60864f21-6eda-4db0-a7fc-052c5797fedc}> cannot be crawled.

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

      The object was not found.   (0x80041201)

For more information, see Help and Support Center at
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ted BouskillSenior Software DeveloperCommented:
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.
pj_reidAuthor Commented:
Thanks - I tried that along with another related MS KB. Good thought though.
Ted BouskillSenior Software DeveloperCommented:
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:

So, we have to determine what the crawler or indexing account can't access the web service.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

pj_reidAuthor Commented:
Okay what would suggest next? I read the article, but I don't exactly see what to look at next.
Ted BouskillSenior Software DeveloperCommented:
Check your content scope, maybe we could try changing it to do a http search instead.
pj_reidAuthor Commented:
I'm knowledgable to the point of being dangerous. How do I check and/or change the content scope?
Ted BouskillSenior Software DeveloperCommented:
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.
pj_reidAuthor Commented:
Yes - I check that. It matches the site I want to search.
Ted BouskillSenior Software DeveloperCommented:
What are the settings for it?  Can you list them here?
pj_reidAuthor Commented:
Sorry for being slow. What do you mean by setting?
pj_reidAuthor Commented:
Are you refering to content databases under application management or sevices under operations on the WSS 3.0 central admin panel?
Ted BouskillSenior Software DeveloperCommented:
No I mean the content source settings.  You have to edit the content source to see them.
pj_reidAuthor Commented:
Database server  
SQL Server database name  

Database status  
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 :)
pj_reidAuthor Commented:
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:)
pj_reidAuthor Commented:
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.
pj_reidAuthor Commented:
I tried something similar to the links, but I'll try again.

pj_reidAuthor Commented:
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,
Philip ElderTechnical Architect - HA/Compute/StorageCommented:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Kewl! :)

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

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.