Re: SQL 2000 Question
- From: "Jeff Teel" <jdteel@xxxxxxxxxxxx>
- Date: Tue, 19 Jul 2005 07:46:22 -0500
Hi Jerry
I wanted to follow up on the search problem that I was having with my
SharePoint web. I did install the Full-Text component on my SharePoint
instance but still was not able to get any search results. It was suggested
that I re-install SP4 on my SharePoint instance to see if that fixed the
problem. After doing that the Full-Text catalogs were built and I am now
able to get results from doing a search on all of my SharePoint webs.
Thank you for your patience and assistance for helping me with this issue.
Jeff
"Jerry zhao (MSFT)" <v-jerryz@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:cqCxS62iFHA.588@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Jeff,
>
> Thanks for your update.
>
> As for your scenario, I would like confirm that you have exactly followed
> the steps in the KB 837367.
>
> If all the steps you did are correct, I would suggest you try the
> following
> troubleshooting steps:
>
> 1. Please check if the Microsoft Search service account is a member of
> Administrator group of your SQL server computer. To do so, please follow
> these steps:
> a. Click Start and choose Run.
> b. Type "services.msc" (without quotation mark) and click OK.
> c. Locate the Microsoft Search service. Right click on this service and
> choose Properties.
> d. Choose "Log On" tab.
>
> 2. Check Index data folder permission:
> a. Open Windows Explorer and navigate to "<Drive>:\Program Files\Microsoft
> SQL Server\MSSQL$<instance_name>\FTDATA" folder.
> b. Right click on the folder and choose Properties.
> c. Choose "Security" tab and make sure the SQL startup account and
> BUILTIN\System account have full control of this folder.
>
> 3. Try to "repopulate all catalogs" for the Full Text catalogs by going to
> Enterprise Manager -> Databases -> <WSS Content database> -> Full-Text
> Catalogs. Right click on the Full Text Catalog listed in the right panel
> and hit "Start Full Population".
>
> 4. If the problem persists, please 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: <Drive>:\ Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\FTDATA
> \SQLServer$<instance_name>\GatherLogs\).
>
> 5. Verify the domain account SQL Server starts with has following rights
> in
> AD:
> - Log on locally
> - Log on as a batch
> - Log on as service
> - Act as part of operating system
> - Access this computer from the Network
> - Replace a process level token
> - Increase quotas
>
> 6. Check registry permissions by going to Start -> Run -> Regedit
>
> Locate the key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Gather\SQLServer. Right
> click and choose Permissions.
>
> Make sure Local System and the SQL Startup Account have read/write
> permissions.
>
> 7. Check that the BUILTIN\Administrators group is a login group in SQL
> Enterprise Manager -> SQL server Instance -> Security -> Logins.
>
> 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.
>
> For your information:
>
> Verify that SQL Server full-text searching is working correctly for your
> SharePoint sites
> http://office.microsoft.com/en-us/assistance/HA011602971033.aspx
>
> If you have any questions, please feel free to let me know. Thanks for
> your
> time, and I look forward to hearing from you.
>
> Best regards,
>
> Jerry Zhao (MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
.
- Follow-Ups:
- Re: SQL 2000 Question
- From: Jerry zhao (MSFT)
- Re: SQL 2000 Question
- References:
- SQL 2000 Question
- From: Jeff Teel
- RE: SQL 2000 Question
- From: Jerry zhao (MSFT)
- Re: SQL 2000 Question
- From: Jeff Teel
- Re: SQL 2000 Question
- From: Jerry zhao (MSFT)
- SQL 2000 Question
- Prev by Date: Re: SBS2003 SP1 error Exchange Server sp not installed
- Next by Date: RE: SBS2003 Remote Connection problems with Windows Media Center
- Previous by thread: Re: SQL 2000 Question
- Next by thread: Re: SQL 2000 Question
- Index(es):
Relevant Pages
|
Loading