MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS search crawler problems

  Asked By: Alexandria    Date: Aug 30    Category: MOSS    Views: 1838

The London heat wave caused disruption at our datacentre and the MOSS 2007 database Server (SQL 2005) switched off during a crawl of a large file store.

Since then the file store crawl hasn't stopped and CAN'T be stopped!
When I try to stop/pause the crawl it times out :(

I've rebooted the servers (2 Web servers, 1 SSP server and 1 DB) but it still continues to run.


When I check file store logs, it's not actually crawling anything, it's in some sort of sorry state. SQL Server is spewing out loads of SQL dumps like:

SQLDump46312.log (extract below)

Is there a way to kill the index job on the Index server?

(Steve from Combined did state that there is a bug in MOSS2007 using
SQL Server 2005.)

Extract from SQLDump46312.log:

External dump process returned no errors.

10:31:25.32 Server Error: 17310, Severity: 20, State:

10:31:25.32 Server A user request from the session
with SPID
56 generated a fatal exception. SQL Server is terminating this
Contact Product Support Services with the dump produced in the log
10:31:25.70 spid56 Using 'dbghelp.dll' version '4.0.5'

10:31:25.75 spid56 ***Stack Dump being sent to
Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump46311.txt

10:31:25.75 spid56 SqlDumpExceptionHandler: Process 56
generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL
Server is
terminating this process.



4 Answers Found

Answer #1    Answered By: Renee Murray     Answered On: Aug 30

What about you try to stop the Timer Service and kill the Windows SharePoint Services Service Process?

Answer #2    Answered By: Harshini Raju     Answered On: Aug 30

Wouldn't rebooting all servers stop the timer service/ all services?

I'm looking for a specific job that would terminate the
indexing/crawling process that continues to run even after a reboot.

Where would this job information reside, a text file on the SSP
server, a SQL server job.....?

any ideas anyone?

Answer #3    Answered By: Christop Mcfadden     Answered On: Aug 30

Try to reset the index and see if that will help you out. Resetting the index is what you do when you think your index file is corrupted. Depending on the size of your index, it may take several hours to reset it.

Answer #4    Answered By: Gopal Jamakhandi     Answered On: Aug 30

I am experiencng the same problem but when is issue the
"stsadm -o osearch -action stop" command to re-idex; my server dumps.

Didn't find what you were looking for? Find more on MOSS search crawler problems Or get search suggestion and latest updates.