Hi,
I've been tasked to look at a problem with Searching in our WSS 3.0 environment. The server was upgraded from WSS 2.0, to WSS 3.0 and the databases are now running on SQL 2005. Search is not working in the Sharepoint sites, no results are returned.
In the SQL DB, a catalog exists for the content database, but there are no objects (columns, fields etc) in this catalog, so it is obviously useless. Right-clicking the catalog show that it currently contains 0 items.
The servers are configured in a farm. Only one of the servers is running the Sharepoint Services Search service. I don't know what these are, and I don't know if it's relevant, but we don't have any SSP's configured.
Any help getting our search working, or advice on how to rebuild the indexes would be much appreciated.
Thx
Mick
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I've just found a Microsoft article that says 'Windows SharePoint Services 3.0 does not include the shared services functionality'. Our catalog (ix_content) in our content DB does not have any objects defined in it, so there isn't anything for it to index. Is there a default set of columns that should be part of this index, or is it everything, or different for every installation?
I have a feeling that an index that is not comprised of any DB objects is unlikely to be much use.
M
Hi lambch0p,
I found the following articles in a microsoft link,
http://technet2.microsoft.
7ccbb9a891fd1033.mspx?mfr=
http://technet2.microsoft.
Hope its helpful,
Regards,
Shailaja Kumar
Business Accounts
Answer for Membership
by: NGPSoft1Posted on 2007-04-11 at 09:05:24ID: 18890818
Have you set up a crawl schedule?
Not sure about WSS 3.0, but in Office SharePoint Server 2007, you must configure a Shared Service Provider in order to crawl the sites and content sources. Without configuring the SSP, there is no way you can get search results because you can only configure a crawl on the Search Settings page of the SSP page.
The Windows SharePoint Services Search only allows you to search the Help feature, and you must set it up on every server where you want the search enabled.
I'm not sure if it's the same for WSS 3.0. Note that searching across site collections is not supported in WSS 3.0.