Re: Search services not available

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}{\f1\fmodern\fprq6\fcharset134 \'cb\'ce\'cc\'e5;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hello Dave,
\par
\par It seems there is some problems during the start process, we may try to stop the search service with stsadm, and start it again, to see if this will help:
\par
\par 1. Open a command prompt window on the server, and change directory to Program Files\\Common Files\\Microsoft Shared\\web server extensions\\12\\BIN.
\par 2. Type
\par
\par stsadm -o spsearch \f1\endash action list
\par
\par This will output the current association of content databases to search servers.
\par
\par 3. Type
\par
\par stsadm -o spsearch -action stop
\par
\par This stops the Windows SharePoint Services Search service (this action throws away the search index).
\par
\par If you encounter a problem or error, do the following:
\par
\par Type
\par
\par net stop sptimerv3
\par net stop spsearch
\par
\par If the service does not stop, do the following:
\par
\par 1.Open a command prompt window, and type
\par
\par run tasklist /svc
\par
\par 2.Find "SPSearch" in the output and note the process ID <pid>.
\par
\par 3.At the command prompt, type
\par
\par run taskkill /f /pid <pid>
\par
\par 4.\lang1033 A\lang2052 t the command prompt, type
\par
\par stsadm -o spsearch -action stop
\par
\par net start sptimerv3
\par
\par \lang1033 After all about steps, we have stoped the search service on the server, and then we can start it in "Central Administration > Operations > Services on Server "
\par
\par or with stsadm.exe
\par
\par stsadm -o spsearch -action start -farmserviceaccount DoMAIN\\name -farmservicepassword password -databaseserver searchdatabaseserver -databasename WSS_Search_NewDB\lang2052
\par \f0
\par Sincerely,
\par
\par Luke Zhang
\par
\par Microsoft Online Community Support
\par ==================================================
\par Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notifications.
\par
\par Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx.
\par ==================================================
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par
\par }

Relevant Pages

  • Re: Search services not available
    ... I stopped the service using STSADM, and then used it again to ... stsadm -o spsearch -action stop ... This stops the Windows SharePoint Services Search service (this action ... Microsoft Online Community Support ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Error after running search service. Logging error every minute...
    ... stsadm -o osearch -action start ... sharepoint search service on all the servers but no luck. ... Application Server Administration job failed for service instance ...
    (microsoft.public.sharepoint.portalserver)