Wednesday, 30 May 2007

MOSS 2007 Installation - Could not access the Search service configuration database

I had some trouble configuring the Windows SharePoint Services Search Service during a MOSS 2007 installation. When starting the service I hit the following error message:

Could not access the Search service configuration database

In the Application Event log the following error was shown:

The filename or extension is too long. 0x800700ce

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

That should do it.

I am told that this command is safe to run as part of your configuration if necessary, although I would recommend you follow the setup procedure in the following site though to avoid it.


Peter J C said...

Thanks - That was most helpful & solved my problem.
I have posted the solution with credit to the MSDN forums.
So; now to fix the "Not Complete" message!
Thanks again.

Anonymous said...

Thank you so much! I scoured the net for help. Your solution seemed to work perfectly.

Anonymous said...

thanks for this! the fix worked perfectly, but what a silly issue... hard to believe we still live with these NETBIOS resolution issues years later.

ekeyser said...

yes netbios is lame. bizarre how ms keeps using non-scalable and inflexible methods.

Anonymous said...

Genius - That did it. Thanks