Microsoft Knowledge Base Email Alertz

(923896) - Describes an issue that occurs in Windows SharePoint Services 3.0 when you try to run the pre-scan upgrade tool from the command line. Provides a workaround.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 923896 - Last Review: May 28, 2009 - Revision: 2.0

Error message when you try to run the Windows SharePoint Services 3.0 SharePoint Products and Technologies Configuration Wizard from the command line: "This server is not the indexer of this search application"

SYMPTOMS

When you try to run the Microsoft Windows SharePoint Services 3.0 SharePoint Products and Technologies Configuration Wizard (Psconfig.exe) from the command line, you receive the following error message:
Failed to register SharePoint services

This server is not the indexer of this search application.

CAUSE

This issue occurs if the Windows SharePoint Services 3.0 database is hosted on a separate computer that is running Microsoft SQL Server. In this situation, the Windows SharePoint Services search logon account may not have the correct permission to access or to query the Windows SharePoint Services database on the computer that is running SQL Server.

WORKAROUND

To work around this issue, stop the Windows SharePoint Services Search service. Then, add a domain account that has permissions to access the computer that is running SQL Server. To do this, follow these steps:
  1. Use an account that has administrative permissions to log on to the computer that is running Windows SharePoint Services 3.0.
  2. Click Start, click Run, type cmd in the Open box, and then click OK.
  3. At the command prompt, move to the %programfiles%\common files\microsoft shared\web server extensions\12\bin folder.
  4. Type the following at the command prompt, and then press ENTER:
    stsadm -o spsearch -action stop
    This command stops and disables the Windows SharePoint Services Search service.
  5. Click Start, point to Administrative Tools, and then click Services.
  6. In the Services MMC snap-in, right-click Windows SharePoint Services Search, and then click Properties.
  7. In the Windows SharePoint Services Search Properties dialog box, click the Log On tab.
  8. Click This account, type the name of the domain account that has the correct permissions, type the password, and then type the password again in the Confirm password box.
  9. Click the General tab, click the list next to Startup type, and then click Automatic. Click Apply, click Start, and then click OK.

APPLIES TO
  • Microsoft Windows SharePoint Services 3.0
Keywords: 
kbtshoot kbexpertiseinter kbprb KB923896
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Steve Report As Irrelevant  
Written: 5/5/2008 11:24 AM
hmmmm, I tried this twice, still the same error

Karl Report As Irrelevant  
Written: 7/30/2008 3:57 AM
I also still have the same problem.

Mike Report As Irrelevant  
Written: 10/31/2008 1:07 PM
Same issues here as well. I have create and re-created the same and diffrent named databases. This is on the same server.

Rajesh.T Report As Irrelevant  
Written: 3/20/2009 6:41 AM
Even for me also the same problem...Its still not working.