SharePoint and Me

The ramblings of Craig Porter, Another SharePoint Consultant

  • Facebook

  • Useful Links

This Server is not the indexer of this search application

Posted by Craig Porter on 25 June, 2009

I ran into the ‘This server is not the indexer of this search application’ problem recently while trying to build a MOSS development environment.  This is the first time I’ve encountered this issue and I’ve built a lot of SharePoint environments in my time so I was understandably stumped.

The first thing I checked was MS KB923896 …
http://support.microsoft.com/default.aspx/kb/923896
… but this wasn’t relevant as the SQL installation was on the same server. I then tried rebuilding the environment only to encounter the same issue. I was, by this point, pulling my hair out. Then I stumbled upon a post on sharepointblogs.com by Ariel …
http://www.sharepointblogs.com/forums/p/13449/25768.aspx (4th post down)
… which seemed to make more sense with regards to my situation.

Ariel’s post indicated that the issue was that the farm was set up using the FQDN instead of the NETBIOS name. This looked like a possible solution as my farm was indeed using the FQDN so I attempted to follow the instructions listed by Ariel but ran into a few problems. The first problem I encountered was that I could not update the objects table (sql below) of the SharePoint_Config database as this caused a violation of a foreign key constraint. Hmmm …

Use SharePoint_Config

UPDATE Objects Set Name='YOURSERVERSNETBIOSNAME'
WHERE Id=(SELECT Id FROM Objects WHERE Name='YOURSERVERSFQDN')

Then, I checked the objects table of the SharePoint_Config database for both the NETBIOS and FQDN using the following query:


SELECT *
FROM objects
WHERE name
IN ('YOURSERVERSNETBIOSNAME', ' 'YOURSERVERSFQDN')

This returned two rows. I checked the properties column XML of each and noticed that the m_ServerRole property of the netbios row was set to invalid while the m_ServerRole property of the FQDN row was set to Application.


<object type="Microsoft.SharePoint.Administration.SPServer,
                    Microsoft.SharePoint,
                    Version=12.0.0.0, Culture=neutral,
                    PublicKeyToken=71e9bce111e9429c">
<fld type="Microsoft.SharePoint.Administration.SPServerRole,
               Microsoft.SharePoint,
               Version=12.0.0.0, Culture=neutral,
               PublicKeyToken=71e9bce111e9429c"
               name="m_ServerRole">Invalid</fld>

I then deleted the NETBIOS entry from the objects table using the query below

DECLARE @return_value int
EXEC @return_value = [dbo].[proc_dropObject]
@Id = 'ID_OF_ ROW_CONTAINING_NETBIOS_ENTRY'

SELECT 'Return Value' = @return_value
GO

This worked and the invalid NETBIOS row entry was gone. I was then able to run Ariels suggested query which essentially alters your farms configuration to use the NETBIOS name instead of the FQDN.

Use SharePoint_Config

UPDATE Objects Set Name='YOURSERVERSNETBIOSNAME'
WHERE Id=(SELECT Id FROM Objects WHERE Name='YOURSERVERSFQDN')

I then tried to start the WSS Search Service again and ….


… IT WORKED !!!!

Advertisements

3 Responses to “This Server is not the indexer of this search application”

  1. macromedia said

    Hmm. Is it true? 🙂

  2. bhagvan said

    yes it works it is a problem with the fqdn … i did not have to delete the objects as such

  3. Anantha RishiKesan said

    Yes you are right. Even i had the problem, then i ininstalled and installed it using the computer name and it worked

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: