SCTV
Sat May 10 09:06:00 CDT 2008
i'll try to run the stsadm -o osearch -action stop
Warning: The Office SharePoint Server Search service that was enabled on
this s
rver will be uninstalled and all index files for all SSPs will be deleted.
Are you sure you want to permanently delete all data in the index for all
SSPs?
[y/n]
and say yes to that question..
but after that nothing happen.. the command prompt still waiting
they don't said the stsadm success stopping or not...
what happen it is?
"Lem@community.nospam" wrote:
> Shortly after posting I found this article and was able to successfully
> change the satus from "stopping" to the start button being active again on
> this site:
>
>
http://msmvps.com/blogs/obts/archive/2006/12/11/412402.aspx
>
> I will update as soon as I am able to start my indexes and run the crawl
> schedules with success.
>
> "Lem@community.nospam" wrote:
>
> > Thanks for the responses,
> >
> > I have attempted to stop these services by:
> > 1st. stopping and restarting the office search and windows sharepoint
> > search services using services.msc
> > 2nd. stopping (status still says stopping) services under the central
> > admin services page
> > 3rd. I reset the indexes without a problem
> >
> > So now I am on the main central administration page trying to figure out how
> > to make the stopping status turn into the start button to retry indexing and
> > crawling.
> >
> > So my question is 1 how to use the stsadm tool to make the stop complete and
> > 2 if there is another way to make the stop complete could either of you point
> > me in the right direction on how to do that?
> >
> > I haven't tried stsadm because I failed to locate documentation on how to
> > use the command line tool.
> >
> >
> > Thanks for all your help John and Frederik.
> >
> > "Frederik Munster" wrote:
> >
> > > We had the same problem. We did a reset of the idexes, and then we stopped
> > > and started the office sharepoint search services .
> > >
> > > then we waited a few minutes and the crawl started automatically
> > >
> > > "John Timney (MVP)" wrote:
> > >
> > > > Go stop it from stsadm and then do a reset on the indexes from central
> > > > admin - see if that helps.
> > > >
> > > > Regards
> > > >
> > > > John Timney (MVP)
> > > >
http://www.johntimney.com
> > > >
http://www.johntimney.com/blog
> > > >
> > > >
> > > > <Lem@community.nospam> wrote in message
> > > > news:6EDDB760-C9D5-4ECD-8AD3-33561F2862EE@microsoft.com...
> > > > > Hi all,
> > > > >
> > > > > I am having trouble with my moss server, the crawls are setup to crawl
> > > > > with
> > > > > incremental and full crawl log settings but all of a sudden the server
> > > > > does
> > > > > not crawl anymore. There are no details in the crawl logs, I havent
> > > > > noticed
> > > > > anything in the event viewer.
> > > > >
> > > > > When I try to manually start/stop a crawl the status freezes. if i select
> > > > > stop it will say stopping for hours and when I select start it still
> > > > > displays
> > > > > stopping in the search settings.
> > > > >
> > > > > I have no clue where to start because there are no leads.
> > > > >
> > > > > Please let me know if anyone can help me troubleshoot this nightmare.
> > > >
> > > >
> > > >