SharePoint University

I installed sharepoint 2003 for a company and I did configure it myself, but somethig funny happend that I never saw it before :

 Search works fine for the main portal site,I can even get search results for all subsites within the search results of main site.

but when I go to any subsite and search for a word that I'm sure it exists in that site, I always get nothig, no results.

As I said if I search for that word in parent site (main portal site) I can get the result and it indicates that the word was found in that particular subsite.

what is happening to my portal site?I'm confused.

BTW I installed SPS SPK 2.0 and WSS 2.0 SPK 2.0 and I have .NET 2.0 installed on my server.SQL2K is installed On another Machine and works fine.
I'm suspecious to Microsoft Search Service On SQL Server Machine,Because WSS Uses Microsoft Search Service for searching WSS Sites.

Can anybody help?

Have you set up the index to crawl the other sites?  It's been quite a while since I set up the indexing/crawling, but I know I have my sites indexed under the "other content sources" .  SPS search and WSS search are 2 different animals and use 2 different search methods. 

ferretwoman is correct in that the indexing and searching for SPS 2.0 and WSS 2.0 are different.

However, you don't need to set up crawling to search on WSS 2.0 sites. The indexing is done via SQL indexes for WSS 2.0 sites. So, you need to make sure full-text indexing is enabled for your SQL databases (you can also check to make sure the indexes are created via SQL Enterprise Manager) and also ensure the "Built-in Administrators" group has not been removed from the SQL Server access list. For some reason, removing this entry will disable the searching feature (if memory serves me correctly)

BTW, do NOT use ASP.NET 2.0 on your SharePoint IIS virtual servers. See SharePoint Portal Server 2003 must use ASP.NET 1.1

dear dggcoop

About ASP .NET 2.0, I Have to tolerate it .because of other apps installed on this server.

I resolved .NET 2.0 problem by installing SPS SPK2.0 and WSS SPK 2.0 but I agree with you that having .NET 2.0 on sps 2003 server is not recomended.

You said :

"ensure the "Built-in Administrators" group has not been removed from the SQL Server access list"

Do you mean that SQL server user that I use for Microsoft SQL Server Service and Microsoft Search Service should be a member of Administrators Group on SQL server Machine?

Because Now this User is not a Local admin on that server and it's only a memebr of "System Administrators" on SQL Server.

I have the same problem here. Dggcoop did u solve the problem already?

 

 

abbasnaderi:

I resolved .NET 2.0 problem by installing SPS SPK2.0 and WSS SPK 2.0 but I agree with you that having .NET 2.0 on sps 2003 server is not recomended.

Just to be clear, installing Service Pack 2 for the SharePoint products does NOT resolve the issue with ASP.NET 2.0. The quote from the Microsoft link I provided above says "For Web applications that are running SharePoint Portal Server 2003 Service Pack 2 or an earlier version of SharePoint Portal Server 2003, the ASP.NET version that is indicated on the Properties page must be 1.1.x."
But, you can avoid the issue by selecting ASP.NET 1.1.x for just the IIS virtual server that SharePoint is using. You can have ASP.NET 2.0 installed on the same server and function properly.

abbasnaderi:

Do you mean that SQL server user that I use for Microsoft SQL Server Service and Microsoft Search Service should be a member of Administrators Group on SQL server Machine?

What I meant was that BUILTIN\Administrators needs to be left in the Security\Logins (SQL2000 location) for the server. If this entry in the Logins listing is removed, in my experience, Full-text indexing does not work.

thanx a lot dear dggcoop

It worked fine and you rescued me from a real disaster.

Except that for security reasons,i did not add BUILTIN\Administrators to sql server logins.Instead,I added "NT AUTHORITY\LocalService" to sql server logins and made it a member of "System Administrators".

Then I rebuild full text catalog on [PortalName]_SITE db and BINGO!! Search worked fine.

Again,Thank you very much.