• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 584
  • Last Modified:

unable to start WSS 3.0 Search service

unable to start WSS 3.0 Search Service.    receive error message:  "Could not access the Search service configuration database".  

from the Event Viewer:  
Event Type:  Error
Event Source:  Windows SharePoint Services 3 Search
Event Category:  Gatherer
Event ID: 10034
Date:  4/6/2010
Time:  2:02:17 PM
User:  N/A
Could not access the Search service configuration database.
Context: Application '86f369e8-ddea-4c9a-836a-806c2f4befb6'
Details:  The filename or extension is too long.  (0x800700ce)

  • 3
1 Solution
Can you elaborate your environment. are you suing dedicated Db for your SharePoint environment.

This problem is caused by the server names in use being too long. It is no good trying to change the name of the database server to be the Netbios name (rather than FQDN) within the Windows SharePoint Services Search Service configuration, you need to change the name of the server registered to perform the Search service.

Before doing this please ensure you take a full backup of your MOSS site collections (if you have any, in my case I didn't as it was a clean install):

stsadm.exe -o backup -url <http://hostname> -filename backup.dat

After the backup perform the following steps to register your search (perhaps also WFE/Index) server using stsadm.exe to invoke the "renameserver" command option.

Open a command prompt window and navigate to the folder where stsadm.exe sits. Normally "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN".

Use the renameserver command as follows, replacing and with the new and old names of your server:

stsadm -o renameserver -newservername -oldservername
c3iitsupportAuthor Commented:
to be clear, on the SP server we run the command to change the DB server name, correct?

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now