SharePoint Services 3 Search event errors after applying certificate on a SBS2008 server

It seems that changing the search accounts, creates a problem with installing SharePoint updates like SP2. So before changing the search accounts read this article!

After installing a ssl certificate on a SBS 2008 server you get 2 different SharePoint Services 3 Search event errors.

Event ID: 2424
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again

Event ID: 2436
The start address cannot be crawled.
Context: Application ‘Search inde file on the search server’, Catalog ‘Search’
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled. (0x80041205)

Solution: Got this solution from my brother, thanx for that:

First we have to create 2 service accounts: SPSearch and SPContent

  1. On your SBS, open Active Directory Users & Computers (Start –> Administrative Tools –> Active Directory Users & Computers.
  2. Within ADU&C, navigate to the Organizational Unit where you want to create the new user accounts.
  3. Right-click on the OU and select New –> User
  4. On the first page of the new user window, enter the following info:
    o First Name: SPSearch
    o Last Name:
    o Username: spsearch
  5. Click Next.
  6. Enter a strong password for the new account.
  7. Uncheck the option “User must change password at next login”
  8. Check the option “User cannot change password”
  9. Check the option “Password never expires”
  10. Click Next
  11. Click Finish.
  12. Repeat steps 3-11, using “SPContent” instead of “SPSearch” in step 4

We do not have to worry about granting any access or permissions to the two new accounts we created.
After the accounts have been created, close Active Directory Users & Computers, then open SharePoint Central Administration (Start –> Administrative Tools –> SharePoint 3.0 Central Administration).

  1. When SharePoint 3.0 Central Administration opens, go to the Operations tab.
  2. Click on the “Services on Server” link
  3. In the Action column, click the link to Stop the “Windows SharePoint Services Search” service.
    o You will receive a warning that stopping the search service will remove existing indices. Click OK to acknowledge the warning.
  4. When you return to the SharePoint Central Administration Operations tab, the Windows SharePoint Search Service will show as stopped. Click the link to Start the Windows SharePoint Services Search service. This will open the Search service configuration page.
  5. In the Service Account section, select the “Configurable” option
    o. For a username, enter \SPSearch (where is your AD domain).
    o. For a password, enter the strong password you assigned to the SPSearch account.
  1. In the Content Access Account section, select the “Configurable” option
    o. For a username, enter \SPContent (where is your AD domain)
    o. For a password, enter the strong password you assigned to the SPContent account.
  2. In the Search Database section, change the database name by appending and underscore 1 (“_1”) to the database name.
    o By default, the database name should be WSS_Search_[SERVERNAME], so we’re changing it to WSS_Search_[SERVERNAME]_1.
    o Changing the name is necessary because the default database name already exists with search data. If we attempted to use the default database name, SharePoint would throw an error that the database contains user-defined schema and cannot be used. By changing the search database name on this configuration page, SharePoint Central Administration will create a new database using this name and configure search to use this new database. Since the new database is empty, we won’t encounter any errors.
  1. Accept the remaining defaults and click the OK button.

After clicking OK, the settings should be applied and you should return to the “Services on Server” page in SharePoint Central Administration, and the Windows SharePoint Services Search” service should be listed as started.

Close SharePoint Central Administration and open the Services MMC (Start –> Administrative Tools –> Services). Restart the Windows SharePoint Services Search service. Verify that the Windows SharePoint Services Search service is configured to login with the SPSearch account you created.

And as last we have to create the following registry key:
[HKLM\System\CurrentControlSet\Control\Lsa] “DisableLoopbackCheck”=dword:00000001

Posted in Blog, SBS 2008 by ronnypot at October 26th, 2010.
Tags: , ,

2 Responses to “SharePoint Services 3 Search event errors after applying certificate on a SBS2008 server”

  1. Susan says:

    I’m concerned about the changing of the search accounts.


    If the account is anything other than Local Service….

    Changing away from Local service will cause the server to have issues with future updates of SharePoint.

  2. ronnypot says:

    Hi Susan,

    I have never seen a problem after doing this. Have you got any information about what kind of errors could occur?

Leave a Reply

Sharing Buttons by Linksku