Sharepoint Event ID 2424

I have a recurring error in my application log. Can anyone shed some light
as to the cause and correction that it requires?
I am running SBS2008 as a Guest OS on A Windows 2008 Standard Server with a
Hyper-V role. the Sbs server is allocated 4GB RAM and 2 CPUS.
thanks
m

Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 10/15/2009 4:00:41 PM
Event ID: 2424
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: SBSSERVER.server.local
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'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3 Search" />
<EventID Qualifiers="32768">2424</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-15T14:00:41.000Z" />
<EventRecordID>90331</EventRecordID>
<Channel>Application</Channel>
<Computer>SBSSERVER.server.local</Computer>
<Security />
</System>
<EventData>
<Data>

Context: Application 'Search', Catalog 'index file on the search server
Search'</Data>
</EventData>
</Event>

Hi Moshe,

I have exactly the same error message and a similar set up to you. Any help
in solving this would be appreciated.

Doug

"Moshe Raab" <> wrote in message
news:F3C65DCE-2038-4714-8F30-...
>I have a recurring error in my application log. Can anyone shed some light
>as to the cause and correction that it requires?
> I am running SBS2008 as a Guest OS on A Windows 2008 Standard Server with
> a Hyper-V role. the Sbs server is allocated 4GB RAM and 2 CPUS.
> thanks
> m
>
> Log Name: Application
> Source: Windows SharePoint Services 3 Search
> Date: 10/15/2009 4:00:41 PM
> Event ID: 2424
> Task Category: Gatherer
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: SBSSERVER.server.local
> 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'
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Windows SharePoint Services 3 Search" />
> <EventID Qualifiers="32768">2424</EventID>
> <Level>2</Level>
> <Task>3</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2009-10-15T14:00:41.000Z" />
> <EventRecordID>90331</EventRecordID>
> <Channel>Application</Channel>
> <Computer>SBSSERVER.server.local</Computer>
> <Security />
> </System>
> <EventData>
> <Data>
>
> Context: Application 'Search', Catalog 'index file on the search server
> Search'</Data>
> </EventData>
> </Event>

Hi,

Thanks for your post.

Based on research, 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.

For troubleshooting steps, please refer toKB927012 below:

Error message when you perform a search query after you upgrade to the release version of Microsoft Windows SharePoint Services 3.0: "Your search cannot be
completed because of a service error"
http://support.microsoft.com/kb/927012/en-us


Please have a try and hope this helps.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

================================================== ================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/...i/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/...i/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
================================================== ================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ================
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ================

I changed the account to an admin account. but now I am getting the
following error:


Log Name: Application
Source: Windows SharePoint Services 3
Date: 10/19/2009 1:45:10 PM
Event ID: 6398
Task Category: Timer
Level: Error
Keywords: Classic
User: N/A
Computer: SBSSERVER.server.local
Description:
The Execute method of job definition
Microsoft.SharePoint.Search.Administration.SPSearc hJobDefinition (ID
51e6fb53-ed1d-42b8-ad9c-44c9fda18619) threw an exception. More information
is included below.

The gatherer is shutting down.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3" />
<EventID Qualifiers="0">6398</EventID>
<Level>2</Level>
<Task>964</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-19T11:45:10.000Z" />
<EventRecordID>97890</EventRecordID>
<Channel>Application</Channel>
<Computer>SBSSERVER.server.local</Computer>
<Security />
</System>
<EventData>
<Data>Microsoft.SharePoint.Search.Administration.S PSearchJobDefinition</Data>
<Data>51e6fb53-ed1d-42b8-ad9c-44c9fda18619</Data>
<Data>The gatherer is shutting down. </Data>
</EventData>
</Event>



""Robbin Meng [MSFT]"" <v-> wrote in message
news:IgV$...
>
>
> Hi,
>
> Thanks for your post.
>
> Based on research, 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.
>
> For troubleshooting steps, please refer toKB927012 below:
>
> Error message when you perform a search query after you upgrade to the
> release version of Microsoft Windows SharePoint Services 3.0: "Your search
> cannot be
> completed because of a service error"
> http://support.microsoft.com/kb/927012/en-us
>
>
> Please have a try and hope this helps.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
> ================================================== ================
> Please post your SBS 2008 related questions to the SBS newsgroup on
> Connect website:
> https://connect.microsoft.com/sbs08/...i/default.aspx
>
> Please post your EBS related questions to the EBS newsgroup on Connect
> website:
> https://connect.microsoft.com/ebs08/...i/default.aspx
>
> If you want to use a newsreader other than a web forum to access these
> newsgroups,
> please refer to the following blog to apply NNTP password and configure a
> newsreader:
> http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
> ================================================== ================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ================================================== ================
>
>
>

Actually I saw a KB article that says that I need to add the user name with
the fully qualified network name, server\user
I did that but now I am still getting the original error (event id 2424)



"Moshe Raab" <> wrote in message
news:...
>I changed the account to an admin account. but now I am getting the
>following error:
>
>
> Log Name: Application
> Source: Windows SharePoint Services 3
> Date: 10/19/2009 1:45:10 PM
> Event ID: 6398
> Task Category: Timer
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: SBSSERVER.server.local
> Description:
> The Execute method of job definition
> Microsoft.SharePoint.Search.Administration.SPSearc hJobDefinition (ID
> 51e6fb53-ed1d-42b8-ad9c-44c9fda18619) threw an exception. More information
> is included below.
>
> The gatherer is shutting down.
> Event Xml:
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Windows SharePoint Services 3" />
> <EventID Qualifiers="0">6398</EventID>
> <Level>2</Level>
> <Task>964</Task>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2009-10-19T11:45:10.000Z" />
> <EventRecordID>97890</EventRecordID>
> <Channel>Application</Channel>
> <Computer>SBSSERVER.server.local</Computer>
> <Security />
> </System>
> <EventData>
>
> <Data>Microsoft.SharePoint.Search.Administration.S PSearchJobDefinition</Data>
> <Data>51e6fb53-ed1d-42b8-ad9c-44c9fda18619</Data>
> <Data>The gatherer is shutting down. </Data>
> </EventData>
> </Event>
>
>
>
> ""Robbin Meng [MSFT]"" <v-> wrote in message
> news:IgV$...
>>
>>
>> Hi,
>>
>> Thanks for your post.
>>
>> Based on research, 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.
>>
>> For troubleshooting steps, please refer toKB927012 below:
>>
>> Error message when you perform a search query after you upgrade to the
>> release version of Microsoft Windows SharePoint Services 3.0: "Your
>> search cannot be
>> completed because of a service error"
>> http://support.microsoft.com/kb/927012/en-us
>>
>>
>> Please have a try and hope this helps.
>>
>>
>> Best regards,
>> Robbin Meng(MSFT)
>> Microsoft Online Newsgroup Support
>>
>> ================================================== ================
>> Please post your SBS 2008 related questions to the SBS newsgroup on
>> Connect website:
>> https://connect.microsoft.com/sbs08/...i/default.aspx
>>
>> Please post your EBS related questions to the EBS newsgroup on Connect
>> website:
>> https://connect.microsoft.com/ebs08/...i/default.aspx
>>
>> If you want to use a newsreader other than a web forum to access these
>> newsgroups,
>> please refer to the following blog to apply NNTP password and configure a
>> newsreader:
>> http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
>> ================================================== ================
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> ================================================== ================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> ================================================== ================
>>
>>
>>
>

Hi Moshe,

Thanks for your reply.

Based on further research, to continue troubleshooting this issue, you may try one of the following methods to disable the authentication loopback check:

Method 1: Disable the loopback check
http://support.microsoft.com/kb/896861/en-us#letmefixit

Method 2: Disable the authentication loopback check
http://support.microsoft.com/kb/926642/en-us

Note You must restart the server for this change to take effect. By default, loopback check functionality is turned on in Windows Server 2003 SP1, and the
DisableLoopbackCheck registry entry is set to 0 (zero).

By the way, have you applied the latest WSS update SharePoint 3.0 SP2 (KB 953338) for your SBS 2008 server?


For more information, please refer to the below article:

FIX: You may be unable to manage IIS by using Server Manager if two threads access IIS at the same time
http://support.microsoft.com/kb/946517/en-us

SharePoint Search & Event ID 2436 errors in SBS 2008
http://msmvps.com/blogs/cgross/archi...-sbs-2008.aspx

Hope this helps.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

thank you for your reply.
first i did apply SharePoint 30.0 SP2 x64
second, i looked over the KB articles and they seem to address a login issue
(i already corrected that by including the FQN for the account).
I am still getting the original error:

Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 10/20/2009 1:50:02 PM
Event ID: 2424
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: SBSSERVER.biconix.local
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'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3 Search" />
<EventID Qualifiers="32768">2424</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-20T11:50:02.000Z" />
<EventRecordID>99898</EventRecordID>
<Channel>Application</Channel>
<Computer>SBSSERVER.biconix.local</Computer>
<Security />
</System>
<EventData>
<Data>

Context: Application 'Search', Catalog 'index file on the search server
Search'</Data>
</EventData>
</Event>ax


""Robbin Meng [MSFT]"" <v-> wrote in message
news:...
>
>
> Hi Moshe,
>
> Thanks for your reply.
>
> Based on further research, to continue troubleshooting this issue, you may
> try one of the following methods to disable the authentication loopback
> check:
>
> Method 1: Disable the loopback check
> http://support.microsoft.com/kb/896861/en-us#letmefixit
>
> Method 2: Disable the authentication loopback check
> http://support.microsoft.com/kb/926642/en-us
>
> Note You must restart the server for this change to take effect. By
> default, loopback check functionality is turned on in Windows Server 2003
> SP1, and the
> DisableLoopbackCheck registry entry is set to 0 (zero).
>
> By the way, have you applied the latest WSS update SharePoint 3.0 SP2 (KB
> 953338) for your SBS 2008 server?
>
>
> For more information, please refer to the below article:
>
> FIX: You may be unable to manage IIS by using Server Manager if two
> threads access IIS at the same time
> http://support.microsoft.com/kb/946517/en-us
>
> SharePoint Search & Event ID 2436 errors in SBS 2008
> http://msmvps.com/blogs/cgross/archi...-sbs-2008.aspx
>
> Hope this helps.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
>
>
>

Hello Moshe,

Thanks for posting back.

Regarding the Event 2424 error, as we discussed before, this 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.

So I would like to confirm if the event 2424 still occurs if we change the service account to non built-in account like domain administrator account?

Regarding the Event 6398 error, you may refer to the following steps to resolve it:

The Windows SharePoint Services search logon account may not have the correct permission to access or to query the Windows SharePoint Services database on the
computer that is running SQL Server. To work around this issue, stop the Windows SharePoint Services Search service. Then, add a domain account that has permissions to
access the computer that is running SQL Server. To do this, follow these steps:

1. Use an account that has administrative permissions to log on to the computer that is running Windows SharePoint Services 3.0.
2. Click Start, click Run, type cmd in the Open box, and then click OK.
3. At the command prompt, move to the %programfiles%\common files\microsoft shared\web server extensions\12\bin folder.
4. Type the following at the command prompt, and then press ENTER:

stsadm -o spsearch -action stop

This command stops and disables the Windows SharePoint Services Search service.
5. Click Start, point to Administrative Tools, and then click Services.
6. In the Services MMC snap-in, right-click Windows SharePoint Services Search, and then click Properties.
7. In the Windows SharePoint Services Search Properties dialog box, click the Log On tab.
8. Click This account, type the name of the domain account that has the correct permissions, type the password, and then type the password again in the Confirm
password box.
9. Click the General tab, click the list next to Startup type, and then click Automatic. Click Apply, click Start, and then click OK

Finally by the way, have you tried running SBS 2008 BPA? Please also have a try.

The Windows Small Business Server 2008 Best Practices Analyzer examines a server that is running Windows Small Business Server 2008 (Windows SBS) and presents a
list of information and errors that administrators should review.

Introducing the Windows Small Business Server 2008 Best Practices Analyzer
<http://technet.microsoft.com/en-us/library/dd145275.aspx>

Windows Small Business Server 2008 Best Practices Analyzer
<http://www.microsoft.com/downloads/details.aspx?FamilyId=86A1AA32-9814-484E-BD43-3E42AEC7F731&displaylang=en>

Hope this helps.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

================================================== ================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/...i/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/...i/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
================================================== ================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ================
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ================

this seems to solve the problem
thanks
m

""Robbin Meng [MSFT]"" <v-> wrote in message
news:...
>
> Hello Moshe,
>
> Thanks for posting back.
>
> Regarding the Event 2424 error, as we discussed before, this 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.
>
> So I would like to confirm if the event 2424 still occurs if we change the
> service account to non built-in account like domain administrator account?
>
> Regarding the Event 6398 error, you may refer to the following steps to
> resolve it:
>
> The Windows SharePoint Services search logon account may not have the
> correct permission to access or to query the Windows SharePoint Services
> database on the
> computer that is running SQL Server. To work around this issue, stop the
> Windows SharePoint Services Search service. Then, add a domain account
> that has permissions to
> access the computer that is running SQL Server. To do this, follow these
> steps:
>
> 1. Use an account that has administrative permissions to log on to the
> computer that is running Windows SharePoint Services 3.0.
> 2. Click Start, click Run, type cmd in the Open box, and then click OK.
> 3. At the command prompt, move to the %programfiles%\common
> files\microsoft shared\web server extensions\12\bin folder.
> 4. Type the following at the command prompt, and then press ENTER:
>
> stsadm -o spsearch -action stop
>
> This command stops and disables the Windows SharePoint Services Search
> service.
> 5. Click Start, point to Administrative Tools, and then click Services.
> 6. In the Services MMC snap-in, right-click Windows SharePoint Services
> Search, and then click Properties.
> 7. In the Windows SharePoint Services Search Properties dialog box, click
> the Log On tab.
> 8. Click This account, type the name of the domain account that has the
> correct permissions, type the password, and then type the password again
> in the Confirm
> password box.
> 9. Click the General tab, click the list next to Startup type, and then
> click Automatic. Click Apply, click Start, and then click OK
>
> Finally by the way, have you tried running SBS 2008 BPA? Please also have
> a try.
>
> The Windows Small Business Server 2008 Best Practices Analyzer examines a
> server that is running Windows Small Business Server 2008 (Windows SBS)
> and presents a
> list of information and errors that administrators should review.
>
> Introducing the Windows Small Business Server 2008 Best Practices Analyzer
> <http://technet.microsoft.com/en-us/library/dd145275.aspx>
>
> Windows Small Business Server 2008 Best Practices Analyzer
> <http://www.microsoft.com/downloads/details.aspx?FamilyId=86A1AA32-9814-484E-BD43-3E42AEC7F731&displaylang=en>
>
> Hope this helps.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
> ================================================== ================
> Please post your SBS 2008 related questions to the SBS newsgroup on
> Connect website:
> https://connect.microsoft.com/sbs08/...i/default.aspx
>
> Please post your EBS related questions to the EBS newsgroup on Connect
> website:
> https://connect.microsoft.com/ebs08/...i/default.aspx
>
> If you want to use a newsreader other than a web forum to access these
> newsgroups,
> please refer to the following blog to apply NNTP password and configure a
> newsreader:
> http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
> ================================================== ================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ================================================== ================
>
>
>

Hi Moshe,

Thanks for your feedback and glad to know the information was helpful. You are welcome.


Here are some SBS 2008 server articles just for your reference:

Managing Your Windows Small Business Server 2008 Network
<http://technet.microsoft.com/en-us/library/cc546017.aspx>

Downloadable documentation for Windows Small Business Server 2008
<http://technet.microsoft.com/en-us/library/cc707659.aspx>

SBS 2008 training links (revised)
http://msmvps.com/blogs/bradley/arch...s-revised.aspx

Windows Small Business Server 2008 Repair Guide
http://technet.microsoft.com/en-us/l...85(WS.10).aspx

The Official SBS Blog
<http://blogs.technet.com/sbs/default.aspx>


Again, thank you for posting in the SBS newsgroups. Please feel free to contact us again in the future.

Have a nice day!


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

================================================== ================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/...i/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/...i/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
================================================== ================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ================
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ================