Link to home
Start Free TrialLog in
Avatar of matavai
matavaiFlag for New Zealand

asked on

Sharepoint Services 3 Search error

As with several other people who've logged calls, I'm also getting this Sharepoint error every five minutes.  The difference is I'm not using Sharepoint, I've never configured it, installed any certificates, or even done a search.   The error started back in March but I can't think of anything major I did around that time to upset it.

Event Type:      Error
Event Source:      Windows SharePoint Services 3 Search
Event Category:      Gatherer
Event ID:      2424
User:            N/A
Computer:      [servername]
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application 'Search', Catalog 'index file on the search server Search'


We're running Windows Server 2008.  I followed the instructions in this link http://support.microsoft.com/default.aspx/kb/927012 but the only user account I have t use is the administrator account, & that hasn't helped.  Any other ideas, in plain english, for someone who has no idea about Sharepoint Services & doesn't need to.
Avatar of QPR
QPR
Flag of New Zealand image

Looks like an incremental indexing job every 5 minutes.
If you aren't using sharepoint - have you looked under windows services for a sharepoint search service and disabled it?
Avatar of matavai

ASKER

I've tried stopping the Sharepoint Search service previously, but even though I set it to Manual, it still restarted itself quite quickly.  What's the difference between stopping the service & disabling it, the disable doesn't appear to actually stop it?
ASKER CERTIFIED SOLUTION
Avatar of QPR
QPR
Flag of New Zealand image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of matavai

ASKER

Oops, turns out disabling the Hardware Profile doesn't help, but disabling the Startup Type appears to have, it hasn't re-started for 30 minutes now.  I'd like to know why it suddenly started running in the first place, but more important is that it stays stopped.
If it was manual the. It would have been started if a process required it. If set to disabled then it won't start no matter what
*then it would*
Avatar of matavai

ASKER

Thanks QPR, service hasn't restarted 6 hours later, no more errors, yay!