Re: Site full text not functioing
- From: v-warnw@xxxxxxxxxxxxxxxxxxxx (Warner Wang [MSFT])
- Date: Thu, 01 Jun 2006 01:58:54 GMT
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi Bob,
\par
\par Thank you for your response. I am sorry for giving you the incorrect link, this web is unavailable due to customer feedback and update.
\par
\par Regarding your issue, the full text search is working for SPS, but full text search is not working for WSS. So these are actually different. For WSS, we use SQL Full Text search. In SPS, we use our own index and searching.
\par
\par Since you enabled the full text search option in WSS, we would expect to see a full text catalog in the WSS Content database.
\par
\par The Full Text Indexing option in Microsoft SQL Server 2000 is used in conjunction with Windows Sharepoint Services to provide the functionality of searching through documents and other items such as pictures in your Sharepoint content databases.
\par
\par The majority of issues involved with the inability to activate this service is due to permissions issues. Please use the following method to troubleshoot this issue.
\par
\par 1. Change the SQL Startup account to another domain account with administrator privileges as a quick test. If MSSearch works, then find out which permissions on the original account are causing the problem by going through the rest of the steps below. You can change the SQL Server Startup account by going to Start>>Settings>>Control Panel>>Administrative Tools>>Services. Then find the MSSQLSERVER item if it is a default instance or MSSQL$instance_name. Right click on the service and go to properties. Click on the Log On tab and ensure you have a domain administrator listed as the Log On account.
\par
\par 2. Navigate to the D:\\MSSQL7\\FTDATA\\ folder via Windows Explorer.
\par
\par Check the read/write/create/delete permission settings for the SQL Startup Account and BUILTIN\\System account. Try writing a text file to that folder, and reading that text file. Make sure the SQL Startup Account defined in step 1 has read/write permissions to this folder.
\par
\par 3. Try to "repopulate all catalogs" for the broken Full Text catalogs by going to Enterprise Manager>>Databases>>(WSS Content database)>>Full-Text Catalogs. Right click on the Full Text Catlog listed in that window and hit "Start Full Population".
\par
\par a. Take note of the error path that pops up in the error. Send in the complete error description if an issue results in doing this.
\par b. Find out if the SQL Server account has permissions to that folder if the error message indicates a folder on the hard drive. If it does not have permissions, give the account Full Control permissions to that folder.
\par c. One way to test SQL Permissions is to run a query from xp_cmdshell such as xp_cmdshell 'dir D:\\MSSQL7\\FTDATA\\path' to see if errors occur, which would indicate file level permissions errors.
\par
\par 4. Look at the error message from this attempt to repopulate all catalogs to find the corresponding gatherer log file. Examine that gatherer log with the record of the problem. (These are located in here for example: D:\\MSSQL7\\FTDATA\\SQLServer\\GatherLogs\\SQL0001100005.2.gthr). Send support the error message if you are unable to ascertain what is is saying.
\par
\par 5. Verify the domain account SQL Server starts with has following rights in AD:
\par - Log On Locally
\par - Log On as a Batch
\par - Log on as service
\par - Act as part of operating system
\par - Access this computer from the Network
\par - Replace a process level token
\par - Increase quotas
\par
\par 6. Check registry permissions by going to Start > Run > Regedt32
\par
\par Look at this key, and the subkeys for HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Search\\1.0\\Gather\\SQLServer
\par
\par Make sure Local System and the SQL Startup Account have read/write permissions.
\par
\par 7. Check that the BUILTIN\\Administrators group is a login group in SQL Enterprise Manager Security>>Logins
\par
\par If the above account is missing recreate it by adding a SQL login with the BUILTIN\\Administrators name. Verify database access after this account has been created, you should notice that the BUILTIN\\Administrators account will be given db_owner privledges to every database after it has been created.
\par
\par 8. Sometimes when permissions are a problem and we have no other option, you can try third party tools from http://www.sysinternals.com/
\par
\par Filemon watches for disk file activity. You could filter Filemon to watch on the D drive for the include string *FTData* as MSSearch parse all the files in a directory called FTData. Search for ACC DENIED messages which would indicate that access is denied.
\par
\par Regmon watches for registry activity and can show Access Denied (Shown as ACC DENIED) related errors there. If these items occur enter Regedt32 as in step 6 and correct the permissions issue.
\par
\par If you have anything unclear about this issue, please feel free to let me know. Thank you!
\par
\par Thanks & Regards,
\par
\par Warner Wang
\par MCSE 2000&MCDBA
\par Microsoft Online Partner Support
\par
\par Get Secure! - www.microsoft.com/security
\par ======================================================
\par PLEASE NOTE: The partner managed newsgroups are provided to assist with break/fix issues and simple how to questions.
\par ?
\par \tab We also love to hear your product feedback!
\par \tab Let us know what you think by posting
\par \tab\tab from the web interface: Partner Feedback
\par \tab\tab from your newsreader: microsoft.private.directaccess.partnerfeedback.
\par \tab We look forward to hearing from you!
\par ======================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others
\par may learn and benefit from this issue.
\par ======================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par ======================================================
\par
\par }
- Follow-Ups:
- Re: Site full text not functioing
- From: Warner Wang [MSFT]
- Re: Site full text not functioing
- Prev by Date: Re: Cannot get to Central Administration
- Next by Date: Sharepoint 2007 64bit only ?
- Previous by thread: Re: Cannot get to Central Administration
- Next by thread: Re: Site full text not functioing
- Index(es):
Relevant Pages
|