Saturday, December 08, 2007 4:49 AM
Can not start the search service. The event viewer on my Search server consistently reports the following error
Error executing service instance (un)provisioning job. Service instance: "Windows SharePoint Services Search"
(id "30aa4636-d364-48cc-8168-2d2744fab56) "WSS_Search on CL_SQ02CHC contains user defined schema.
Databases must be empty before they can be used. Delete all of the tables, stored procedures and other
objects or use a different database.
The other Error reported in event viewer,
An attempt to start/stop instance of service Windows SharePoint Services Help Search on server
AA02WPPUB did not succeed. Rerun the action via UI or command line on the specified server.
Additional information below.
WSS_Search on CL_SQ02CHC contains user-defined schema Databases must be empty before they can
be used. Delete all of the tables, stored procedures and other objects or use a different database.
I've used another database with the same results.
Within Central adminstration it consistently errors when trying to start the search service.
Any help would be appreciated.
Monday, January 21, 2008 3:39 PMim having the same problem did you find a solution for your problem?
Monday, January 21, 2008 6:10 PM
The only way that will solve your problem is to create a new empty search database.
Wednesday, March 12, 2008 11:41 PMCan anyone explain HOW to do this and what the problems with doing so might be?
Thursday, March 13, 2008 11:46 AM
In Central Admin under Operations -> Services on Server select the server that you want to run the WSS Search service. Click 'start' next to the service in the list and fill in the required accounts. To create a new DB enter a new name into the database name field and then click the start button at the bottom.
I've done this a couple of time with no ill effects.
- Proposed As Answer by Metaltark Wednesday, June 29, 2011 1:09 AM
Monday, April 28, 2008 5:58 PM
When I tried the steps above the database got created but did not show the service as started and gave the error message
Could not access the Search service configuration database
In the Windows event viewer there was an error message stating:
Could not access the Search service configuration database.
Context: Application '31f895f0-6487-4dce-8941-ed4e82d3a00c'
The filename or extension is too long. (0x800700ce)
any got any Ideas?
Wednesday, December 17, 2008 11:39 AMI have the same problem with my setup. The problem seem to appear when you during the installation say that it's a server in a farm you want to setup and still uses the local installation of a SQL-server. The real problem is tha tyou probally used FQDN when you named the SQL server in the setup. I'm still looking for a solution other the reinstall.
Wednesday, December 17, 2008 12:04 PMMoving to the Search forum
Wednesday, April 21, 2010 2:52 PMI'm also having this problem after attaching a server to an existing farm.
Friday, July 27, 2012 5:37 PM
Duncan, when you attach a server to an existing farm there are a few powershell commands that will help you migrate your search....
Wednesday, October 24, 2012 6:22 PMHas this ever been completed.