We help IT Professionals succeed at work.

Sharepoint Search Indexing keeps failing

mgudites1
mgudites1 asked
on
The automatic daily indexing keeps!  I go to the "Manage Content Sources" area to see that it gets 7 seconds in, and fails.  (Last crawl duration say 00:00:07).  When I look at the logs, this is what I see (attached picture).  I'm not sure what the problem is though, all those documents seem to be relevant and functional.  

However, I can go in there and MANUALLY run it, and it works fine.  Any ideas?
Screenshot of error log
Comment
Watch Question

Justin SmithSr. System Engineer
Top Expert 2012

Commented:
How much drive space (check every drive) do you have available on your index server?  Have you tried resetting the index file?

Author

Commented:
We're using the all-on-one server solution.  Our server has 33GB free on the C drive, and 342GB free on the D drive.

I'm not sure how to reset the index file...meaning just clear the whole index out and start from scratch?
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
Yes.  Under the SSP - Search Administration, there is a link to "Reset Crawled Content".  

Depending on how much data you are crawling you might want to do this over a weekend or after hours.  Especially since everything is running on one  box.  

Are you on SP2 (MOSS & WSS)?

Author

Commented:
K, I will try that next.  Additionally, I noticed today that my Profile Import is stuck (can't seem to fix it...tried restarting services, no good).  I'll try doing the reset next.

Yes, SP2 on both.
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
anything in the application event logs?

Author

Commented:
Yes, many!
In addition to the ones below, there are messages about "insufficient memory," but I've never seen those before...this box has 12GB of RAM, and is not a very heavily trafficked server.  Task manager shows that 9 of those 12 GB are free.


1:
A user request from the session with SPID 51 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

2:
A database error occurred.

Source: Microsoft OLE DB Provider for SQL Server
Code: 0 occurred 1 time(s)
Description: Timeout expired

Context: Application 'd69123f4-6a42-4266-aec9-d01a55852c7e'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
Are the memory events related to MOSS?  Can you post a few specifically related to MOSS or WSS?

Author

Commented:
The exact message for the memory event is "There is insufficient system memory to run this query" and the source is the SQL database Sharepoint is running on.

The vast majority of the errors in here are of the "A user request from the session with SPID 51 generated a fatal exception" variety, and they also list SQL as the source.  Looks like they started occuring yesterday.

I'm wondering if it's just time to reboot this box.  It's been about 40 days.
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
never a bad idea
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
WHat is the status?

Author

Commented:
Still happening.  Can't figure out what's going on.

Author

Commented:
Stiiiiiiiiill happening :(

Author

Commented:
Still no resolution.

Author

Commented:
Guess it's hopeless
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
Do you have the latest service pack installed for SQL?

Author

Commented:
Yes, latest patches for SQL have been installed.
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
So how did you fix it?  Not surprised that a Symantec product caused issues in SharePoint.

Author

Commented:
It fixed the issue.