Saturday, August 25, 2007

WSS 3.0 Content Indexing: The update cannot be started

I noticed recently that I was getting an error in my Application Event log every time the WSS Search Service ran. That means an error every five minutes, which is a little disheartening. One option is to change the WSS index schedule so that the error only occurs once per day – but some might say that is avoiding the issue. Which I suppose is a fair point.

The error that was showing up in my Application Event Log was:

Event ID 2424
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'

I fixed this by going to Central Administration – Operations – Services on Server. I selected the Windows SharePoint Services Search entry. I then changed the Service Account username and password to match the Content Access Account details. Click OK on the bottom of the page and wait five minutes.

Once I saw that the error was no longer being logged I went back and set the Service Account back to its original username and password. Still no sign of the error. I also verified that WSS was indexing content again.

So a bit of a strange issue. It looks like some settings got messed up along the way and just need to be reset. I did notice that the error started to happen after some scheduled maintenance on the SQL Server. I'll have a word with the SQL Admin and see what he's been up to.

Monday, August 20, 2007

August 2007 User Group meeting

We have a jam-packed session this month. Brad Saide will be presenting on the Business Data Catalogue. Then Han Duong will cover customizing SharePoint themes. To top it off Jey Srikantha from K2 is returning to show us the K2 Blackpearl capabilities. This extends the out of the box workflows in and integrates directly with MOSS 2007.

This month's session is on Tuesday 21st at the Unique World offices in Haymarket. So come along, grab some beer & pizza and mingle with the local SharePointers. For more information go to