| Event Id | 2424 |
| Source | Windows SharePoint Services 3 Search |
| Description | The update cannot be started because the content sources cannot be accessed.Fix the errors and try the update again. |
| Event Information | According to Microsoft: Cause: This issue occurs when the service account for the Windows SharePoint Services Search service is configured to use the Network Service account. The search service account must not use a built-in account to access the Windows SharePoint Services 3.0 database. An example of a built-in account is the Local Service account or the Network Service account. Resolution : To resolve this issue, use a configurable account for the Search Service account. To do this, follow these steps: 1.Log on to the Windows SharePoint Services 3.0 server by using an account that has administrative permissions. 2.Click Start, point to Administrative Tools, and then clickSharePoint 3.0 Central Administration. 3.On the Central Administration page, click Operations. 4.Under Services on the Services on Server: ServerName page, click Windows SharePoint Services Search. 5.Next to Service Account on the Configure Windows SharePoint Services Search Service Settings on server: ServerName page, select Configurable. 6.Type a user account and password that has access to the Windows SharePoint Services 3.0 database, and then click OK. ------------------------------------------------------------------------------------------------- This information from some newsgroups may help you: These are the following steps to resolve this issue. 1.Log into Central Administration > Operations > Services on Server > click on Windows SharePoint Services Help Search. 2.You should now be in Configure Windows SharePoint Services Search Service Settings on server XXXXXX. 1.Update the "Service Account" to be the same account as the "Content Access Account". 2.Scroll to the bottom of the page and click OK. You can see just above the OK button the Indexing Schedule; by default, this is set to every 5 minutes which is why the application event log had an Event ID 2424 every 5 minutes. 3.I haven't taken the time to investigate whether you should just reset IIS or reboot the server once you've updated that account. In my case, I just rebooted the server. |
| Reference Links | Event ID 2424 from Source Windows SharePoint Services 3 Search |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.