After spending a lot of time trying to figure out how to enable Windows SharePoint Search service in my WSS 3.0 SharePoint Portal I finally figured out how to do the same. Here is step by step guide for the same:
Check whether SQL Full Text Search is installed or not if not install it and configure it.
If SQL Full Text is installed the check whether your WSS search services is installed and working..
To verify go to "Central Administration --> Operations --> Services on Server" of your SharePoint portal.
You should find Windows SharePoint Services Search listed under services. If not then follow the following steps to enable it:
a. Open a command prompt with admin privileges.
b. Change folder location to: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
Here you will find the an .exe file named "psconfig.exe"
c. Run this exe file through cmd with following parameters
psconfig.exe -cmd services -install
This command will install Search Services on your SharePoint Server.
To configure your Search Services from the same location as above run following command:
stsadm -o spsearch -action -farmserviceaccount [WSS service account] -farmservicepassword [Account Password]
This command will set service account for your WSS Search Services.
To add an existing WSS 3.0 site to Search Service run command given below:
Stsadm -o spsearch -action attachcontentdatabase -databasename <content database name> [-databaseserver <server\instance>] [-searchserver <search server name>]
Here databasename is your spsite content database name. databaseserver and searchserver are optional. When left out the search service takes default search server and and default database server names.
Below are mdsn links for more information about both utilities:
For psconfig
http://msdn.microsoft.com/en-us/library/cc288944(v=office.12).aspx
For stsadm spsearch command
http://technet.microsoft.com/en-us/library/cc288507(office.12).aspx
For full list of stsadm commands
http://technet.microsoft.com/en-us/library/cc288507(office.12).aspx
No comments:
Post a Comment