Solved

Sharepoint 2007 - Crawl stop working 4 weeks ago

Posted on 2011-09-30
16
829 Views
Last Modified: 2012-05-12
on the search setting I get this :
Propagation status: Query server not responding  Server4

I did restart all the servers, reset the crawl, restart a full crawl... not working again...

I have 4 server in farm, The Server4, I check on it and cannot see anything wrong... but again, my knowledge of sharepoint is limited.

thanks for your advise and help
0
Comment
Question by:altzar
  • 9
  • 6
16 Comments
 
LVL 14

Expert Comment

by:GeorgeGergues
ID: 36899576
That is very hard to debug
but I do reommend that you check the Crawl log and check that everything is crawled ok and you don't have Crawl Access issues for example.

If you want to debug the problem with index propagation , this should show more information under you windows application log.

Also you can run this stsadm command

from the command prompt at the Bin folder or if you have Bin folder on path .
stsadm -o osearch -action start


Read more about those commands here
http://technet.microsoft.com/en-us/library/cc262920%28office.12%29.aspx


Best of luck.
0
 
LVL 8

Expert Comment

by:nsyyoung
ID: 36904567
Do you have enough disk space?  

From http://support.microsoft.com/kb/925609:
This problem occurs because there is insufficient disk space.

RESOLUTION
To resolve this problem, perform one of the following actions: Reset the index....To resolve this problem, perform one of the following actions:
•Reset the index.
•Free some disk space. To do this, delete unnecessary content, or add another hard disk.
•Use the Stsadm.exe command-line tool to move the catalog.

See the kb link above for more info.

-n
0
 
LVL 1

Author Comment

by:altzar
ID: 36905036
there is enough free disk space. more than 50% free per drive minimum.

on the SQL, got 750 G free.

I ran the atsadm -o search -action start,  ( I forgot to do a list before to capture the initial state )
it gave me that the service started successfully, did a LIST after that, it was running on all server.

but on the server that the problem was reported ( SERVER4 ) , the log started to go crazy, same error occurring indefinitely,

0/03/2011 10:25:15.31       mssearch.exe (0x0824)                         0x0708      Search Server                       MS Search Propagation               0      Monitorable      Dumping error record [0]:   Source: Microsoft OLE DB Provider for SQL Server   HRESULT: 0x00040ecd   Code: 0   Description: Input dialect was ignored and command was processed using default dialect.

10/03/2011 10:25:15.31       mssearch.exe (0x0824)                         0x0708      Search Server Common                Exceptions                          0      Monitorable      <Exception><HR>0x80040e14</HR><eip>0139535E</eip><module>d:\office\source\search\ytrip\tripoli\propagation\propdatabase.cxx</module><line>138</line></Exception>

10/03/2011 10:25:15.31       mssearch.exe (0x0824)                         0x0708      Search Server                       MS Search Propagation               0      Monitorable      OLEDB: {? = call dbo.proc_MSS_PropagationQueryServerReportTaskReady(?,?,?,?,?)}, Application: (null), hr error=0x80040e14.


I check and the path on the D: does not exist... and it never did ( since the past 6 month ) .  not sure what to make of it.  I do not have this issue on the other server in the farm and they don't have the path .

0
Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

 
LVL 14

Expert Comment

by:GeorgeGergues
ID: 36905120
The search Database Log is running out of space

Can you check if the Log has a hard limit on growth set to a specific value ?


You might want to remove this limit for a while.

Best of luck
0
 
LVL 1

Author Comment

by:altzar
ID: 36905883
if I'm missing some space, is it normal that those logs entry only appear on only 1 of the farm server ?

I have 1 server setup as index

and 3 other setup as query ( it's on 1 of the query that I see those logs entry )

thansk
0
 
LVL 14

Expert Comment

by:GeorgeGergues
ID: 36905951
You will find a Database by the name
[ServerName_DB_Guid]

that would be the search database configured for the server.

check that DB and see if the log file (SQL LOG FILE ) is running out of free space

Steps
SQL manager Connect to SQL Server  >  Databases , - > Right click on your DB and Select Properties
and select the file (Log File ) and select properties ,that should show you if you are set with a limit File limit.

Best of luck
0
 
LVL 1

Author Comment

by:altzar
ID: 36906026
Sorry for my ignorance... something I think I did not catch...

all my servers are configure in 1 MOSS Farm, so when I look at the database, the server name is not include, it's more the Farm terminology.

so when I talk about the entry in the log, those are locally to server 4 ( inside the locally diagnostic Logging file of the server )

I have hard time relating those entry to one specific database on the SQL Server...

in my logic ( correct me if I'm wrong ), but if limit where reach on the SQL, should I get the same error on each server ? ( locally )

thanks

.. checking all the limits on each database....
0
 
LVL 1

Author Comment

by:altzar
ID: 36909789
on the database setting, no limits are reach, have more than 50% of disk space free

have 500G total on data volume, only use 220G ( with logs ), logs are set to 2T ( don't ask me why )
0
 
LVL 1

Author Comment

by:altzar
ID: 36909801
whan I plan to do , shutdown this server, then do a full crawl... see what happen.

other option, remove it from the farm and install a new one.

any other suggestion ?

thanks
0
 
LVL 14

Expert Comment

by:GeorgeGergues
ID: 36909976
I would not remove and add the Server to the farm ( that will cause more problems )

Try Running the Configuration wizard on the server and reboot it .
see if that generates any errors on your Server application log and System log
0
 
LVL 1

Author Comment

by:altzar
ID: 36910835
those are prod server, would you run the wizard during business hour ?

and I think I found the problem, some patch occure 1 day before the crawl break.
looking into that.
0
 
LVL 14

Expert Comment

by:GeorgeGergues
ID: 36910944
The wizard will cause an IIS RESET on the server where it is running.

be careful
you can do it off hours if you think it is safer.

0
 
LVL 1

Author Comment

by:altzar
ID: 36911312
I can reboot the server during day hour, I have an external load balancer ( unless the wizard start a iis reset on all the server )

I tought of something else, I could just turn off Searching on server4, then launch a full crawl. until I can point exacly the issue.
0
 
LVL 14

Accepted Solution

by:
GeorgeGergues earned 150 total points
ID: 36911456
It will do IISRESET on that particular server

Reboot / Stop crawl / Recrawl at own risk . this might take a long time.
0
 
LVL 1

Assisted Solution

by:altzar
altzar earned 0 total points
ID: 37007031
here is the conclusion, we are almost positive that the crawl stop working for 1 of the 2 reasons:

- the rules in the VIP was change.
- patch on server 4 was apply incorrectly.

here what solve our issues


1. stop server 4
2. stsadm -o osearch -action stop
3. Restart Office Sp server serach, and wss search in services.msc
4. stsadm -o osearch -action start -role indexquery
5. Assign indexer via "Shared Services Administration", drop-down for SSP>Edit Properties, and complete page, making sure to assign an indexer.
6. Wait for index propagation, 2-5 minutes, and then start full crawl at SSP Admin Page>Search Administration>Content Sources>Start full crawl with content source.
 
0
 
LVL 1

Author Closing Comment

by:altzar
ID: 37035268
started has a specific problem with a too large possibility source, we open a case with microsoft and found the solution after 1 week of investigation ( trial and error )
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I recently came across an issue with a MOSS 2007 deployment where access into some sub-sites were denied, even for the MOSS farm administrators. A bit of background to the setup of this MOSS farm; this was a three server setup, consisting of a fr…
I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get…
This Micro Tutorial will teach you how to censor certain areas of your screen. The example in this video will show a little boy's face being blurred. This will be demonstrated using Adobe Premiere Pro CS6.
This tutorial gives a high-level tour of the interface of Marketo (a marketing automation tool to help businesses track and engage prospective customers and drive them to purchase). You will see the main areas including Marketing Activities, Design …

778 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question