Sean Wallbridge
Ok, this week alone, I’ve run into two different scenarios, where I’ve gotten Application Event ID 2424 errors, when WSS Search is attempting to perform a search/catalog update.
Symptoms:
- Search returns no results, but no errors either, in WSS – simply that no results were found, when there definitely should be something there.
- Event ID 2424 and the error (along the lines of) 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’
Solutions (for me (this week, 2 different issues/2 different fixes)
- On one install, it was a brand new WSS site. All configured, all tuned, everything cool but missing SP1. Soon as I applied it and rebooted, my search started working – Whoopee! Happy.
- On the other install, it was a little more complicated but ultimately made perfect sense. My WSS server was on a private IP network (192.168.5.x). The URL I assigned it, instead of setting up a local web application and extending it (what I really should have done), actually resolved to the public IP of the site (67.44.44.x). Therefore, when search attempted to run, it itself was unable to *visit* the website, in order to search it. The quick fix was to resolve the IP’s internally by modifying the local hosts file. The real solution will be to rebuild the sites (backup/restore collection) to local web applications, that are extended for public access.
I’ll add more solutions, when/if I come across them. Hope this helps someone, somewhere.