Search service errors in SPS2003 - Sharepoint

I will add that the SharePoint Timer Service is running in the same account
as the WSS Admin App Pool account on all of our servers, and that the
Oledb32.dll is at the correct version.

What may possibly help is the fact that one of the servers in this farm had
to be rebuilt some time back, and I believe the problems have been happening
since then.

"Share~a~pint" wrote:

> SharePoint Portal Server 2003 and wss 2.0 on a multi-server farm (Windows
> 2003 servers consisting of 2 search, 2 web and 1 index/job server, plus 1 SQL
> 2000 server).
>
> On one of the search servers, we have the following error:
> Event Type: Information
> Event Source: Microsoft SharePointPS Search Service
> Event Category: Search service
> Event ID: 7059
>
> Description:
> The propogation for the index cannot be accepted. The environment is missing
> critical files and the installation of the search service may be damaged.
> Reinstall the application. If the problem persists, contact Microsoft Product
> Support. Context: Application, 7b6fa026-30a4-4bc4-b1f8-0c9b6a7b9aa6
> Portal_Content Catalog
>
> We also have this error message on every server in the farm:
>
> Event Tpye: Error
> Event Source: Windows SharePoint Services 2.0
> Event Category: None
> Event ID: 1000
>
> Description: #50070: Unable to connect to the database SPS01_Config_db on
> (our sql server and instance). Check the database connection information and
> make sure that the database server is running.
>
> I've verified that the database server is running, and the account that
> should have access to it can in fact access the database. Has anyone had this
> combination of errors before? When it says "Reinstall the application", does
> that mean to just reinstall SharePoint 2003 on that server, or can I try to
> run the repair first?
>
> The sites are up and being served fine, and the search appears to be working
> on the sites, although the search index is not propogating to any of the
> other servers. In Central Administration, the propogation status is pending
> for all Portal_Content and Non_Portal_Content, and the Last Successful
> Propogation says "Not Built or Propogated" for all. We cannot force the
> propogation or stop it either.
>
> Any help or advice regarding what you would be checking in this was your
> environment would be appreciated.
>
> Thanks!