Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Problem in OSearch service on my index server

  Asked By: Garrett    Date: Dec 31    Category: MOSS    Views: 2452

I am beating my head against the wall. I am having a problem with the
OSearch service on my index server. It is in the STOPPING phase and has
been like that for the past three hours. I have done countless research
and have tried just about everything except for rebuilding the portal
which is NOT an option. Has anyone been successful in getting the
OSEARCH server to restart after it has hung. I have even stopped and
started the OSEARCH service via the UI and stsadm on both of the front
end web servers but the Index server will not do anything.

Please help! I don't know what to do at this point.

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Lonnie Cohen     Answered On: Dec 31

Are there any errors in the event log?

 
Answer #2    Answered By: Ruchir Satam     Answered On: Dec 31

Yes, I the default crawl account is locking out…which is the same service
account for OSearch.

But I cannot fix it because I cannot get the OSEARCH service to get out of the
stopping phase on the index server. Otherwise I would have ran the stsadm
commands to reset all the service accounts just to make sure but when I try to
do that I get an error message saying the service is being updated…by me…I
am running around in circles. All app pools and web sites are running. This is
so strange. Nothing has changed in this environment and then bam…search does
not work and service account locks out every 5 minutes.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6641
Date: 9/17/2010
Time: 2:14:30 PM
User: N/A
Computer: SERVERNAME
Description:
The SSP Timer Job Distribution List Import Job was not run.

Reason: The referenced account is currently locked out and may not be logged on
to

Technical Support Details:
System.ComponentModel.Win32Exception: The referenced account is currently locked
out and may not be logged on to
at
Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(St\
ring userDomainName, String password, LogonType logonType)
at
Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(St\
ring userDomainName, String password)
at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state)

 
Answer #3    Answered By: Anthony Rutledge     Answered On: Dec 31

I don't understand the OSEARCH service, but have you cycled OWSTIMER service?

 
Answer #4    Answered By: Heena Nagori     Answered On: Dec 31

I will give it a try..is that done by the command line?

 
Answer #5    Answered By: Aishwarya Karmarkar     Answered On: Dec 31

On the server:

Start-->Run¦ services.msc

Go down to Windows SharePoint Services Timer. Right-click and Restart.

Or,

Start-->Run... cmd.exe

Type or copy/paste: net stop sptimerv3 & net start sptimerv3

I added this to a .BAT file and I run it from a shortcut on my server's quick
launch.

 
Didn't find what you were looking for? Find more on Problem in OSearch service on my index server Or get search suggestion and latest updates.




Tagged: