Category Archives: SharePoint Installation

Windows SharePoint Services Search – Required on Farm, not running

We had this problem using MOSS 2007 SP2 when we first installed SharePoint. We tried starting it with an administrators account as well as changing the Indexing schedule with no luck. What we ended up doing was detaching the WSS_Search_<your server name> database and taking it offline in SQL, then when we went back in to Central Administration – Operations – Services on Server and selected Start next to that service, we put in a new database since it will give you an Unknown Error if you try to use the same name, and it started fine.

Leave a comment

Posted by on July 26, 2010 in SharePoint Installation


Configuration Failed on MOSS 2007 SP2

We were trying to apply Service Pack 2 to our MOSS 2007 installation. Once we installed the service pack we tried to run the config wizard and it would get to task 5 and the configuration would fail. Then we would get the following events in the Event Viewer:

Event ID: 100

Source: SharePoint Products and Technologies Configuration Wizard


Configuration of SharePoint Products and Technologies failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_7_20_2010_8_9_2_615_239088506.log, fix the problem, and run this configuration wizard again.

Event ID: 104

Source: SharePoint Products and Technologies Configuration Wizard


Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstanceInConfigDB(Boolean provisionTheServiceInstanceToo, String serviceInstanceRegistryKeyName, Object sharepointServiceObject)

at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstances(Boolean provisionTheServiceInstancesToo, String serviceRegistryKeyName, Object sharepointServiceObject)

at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo)

at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run()

at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Event ID: 2426

Source: Windows SharePoint Services 3 Search


Advise Status Change failed. The system is probably low on resources. Free up resources and restart the service.

Context: Application ‘Search’, Catalog ‘index file on the search server Search’



Event ID: 10029

Source: Windows SharePoint Services 3 Search


Error backing up registry hive to the configuration database.

Context: Application ‘Search index file on the search server’


Access is denied. (0x80070005)

Event ID: 10030

Source: Windows SharePoint Services 3 Search


Error importing registry hive from the configuration database and into the registry.

Context: Application ‘e1daee80-85f6-4538-9358-59e286d2c897’


Access is denied. (0x80070005)

Event ID: 6066

Source: Office SharePoint Server


Couldn’t Register with Load Balancer: Unable to connect to the remote server

Event ID: 6102

Source: Office SharePoint Server


LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server

All of these were caused by one registry key:

HK_local_machine\software\microsoft\shared tools\web server extensions\12.0\wss\services\

 Under that key, find the service that it was failing on and delete that key. In our case it was Windows SharePoint Services Search. We backed up that registry key and then deleted it. We reran the configuration wizard and it worked.

I hope this helps!!

Leave a comment

Posted by on July 22, 2010 in SharePoint Installation


Installing MOSS 2007 (x86)

This post relates to installing Microsoft Office SharePoint Server (MOSS) 2007 in a secured environment with the following network setup:

  • Two server setup using Server 2003 – One web front end to run all MOSS services and one SQL server
  • SQL Server 2005 – Maintains all databases for MOSS installation

If you need to know the software/hardware requirements check that out here

In order to begin your MOSS installation you should have all critical updates applied and configure the server to be a Web server by enabling Internet Information Services (IIS) 6.0, including:

  • Common Files
  • WWW
  • SMTP ( Only if you’re going to be using e-mail services within SharePoint for notifications or so that SharePoint can accept and archive incoming email)

By default, on new installations, the server is set to use IIS 6.0 worker process isolation mode. If you upgraded from IIS 5.0 on Server 2000 Run WWW in IIS 5.0 isolation mode is enabled and must be changed to IIS 6.0 worker process isolation mode.

Also before installing MOSS you must have .NET Framework 3.0 installed and be sure that ASP.NET 2.0 is enabled. I recommend taking that one step further and updating to .NET Framework 3.5 SP1 since it’s a little trickier if you start out with 3.0 and want to upgrade later.

To enable ASP.NET v2.0.50727, open the Web service extension in the IIS snap-in on the Microsoft Management Console (MMC). If ASP.NET 2.0 is installed on the computer before IIS is enabled, you must enable ASP.NET 2.0 by running the command aspnet_regiis -i.

Next you need to have your SharePoint accounts set up. This varies depending on what you want out of your accounts. If you’re looking for security but higher management I recommend multiple accounts to run the different SharePoint services but a lot of users tend to lean towards having one administrative account to run everything. It is easier to manage that way but a LOT less secure. You can use as many or as few accounts as you’d like but the more you use the more confusing it gets when setting up permissions individually. Using Microsoft’s recommended way, you could end up with up to 13 accounts but after speaking with them personally it is just as safe to consolidate this to 4 or 5 accounts.

My accounts setup was as follows:

  • SQL service account – This account is used as the service account for the following SQL Server services (MSSQLSERVER,SQLSERVERAGENT)
  • Admin service account – This account is used to run the MOSS 2007 install, the SharePoint Products and Technologies Configuration Wizard, the psconfig command-line tool and the stsadm command-line tool
  • Search service account – This account is used as the service account for the Office SharePoint Server Search service
  • Application Pool service account – The user account that the worker process that service the application pool use as their process identity
  • Shared Services Provider service account – This account is used to manage all Shared Service Provider services

Once you have created your accounts whether using my setup or your own, ensure that the admin account used to run your installation is a member of the local administrators group on all SharePoint servers in your farm. This account must also have the securityadmin and dbcreator SQL Server security roles applied on the database server. You also need to ensure your SQL service account has the securityadmin, dbcreator and db_ownerSQL Server security roles applied on the database server. For more information on permissions that should be applied manually click here. For setup purposes these are all you need.

You are now ready to begin your MOSS 2007 installation:

  • Run Officeserver.exe
  • Enter your product key and click Continue

SharePoint key

  • On the Read the Microsoft Software License Terms page, review the terms (yeah right), select the I accept the terms of this agreement check box, and then click Continue

License Terms

  • On the Choose the installation you want page, click Advanced (If you want to run a basic setup with the default settings choose Basic)

Installation Type

  • On the Server Type tab, for this installation we’ll click Complete (If you would like to change the installation directory click the File Location tab and change it there)

Server Type and File Location

  • When Setup finishes, a dialog box appears telling you that you must complete the configuration of your server. Make sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.
  • Click Close to start the configuration wizard.

The SharePoint Products and Technologies Configuration Wizard is used to configure MOSS 2007. It also allows you to install and configure the configuration database (unless pre-created), install the MOSS 2007 services and install SharePoint Central Administration. Use the following instructions to run the SharePoint Products and Technologies Configuration Wizard:

  • On the Welcome to SharePoint Products and Technologies page, click Next

Configuration Wizard

  • Click Yes in the warning dialog box that appears notifying you that some services might need to be restarted during configuration.
  • On the Connect to a server farm page, do one of the following:

Since this is the first front-end server that you are configuring in your server farm, click No, I want to create a new server farm, and then click Next. If you are joining a server to your farm click Yes, I want to connect to an existing server farm

Connect to a server farm

  • On the Specify Configuration Database Settings dialog box, in Database server, type the name of the computer that is running SQL Server (ex \\servername)
  • If you have not pre-created your databases and this is the first server that you are configuring in your server farm, type a name for your configuration database in Database name, or use the default database name. (If you are going to have multiple SharePoint servers using your SQL Server it is best practice to name it something unique)

Configuration Database Settings

  • In Username, type the username of the account used to connect the the computer running SQL Server. In this case we’re using the SQL Server service account. (be sure to type the username in the format DOMAIN\username)
  • In Password, type the user’s password and click Next
  • On the Configure SharePoint Central Administration Web Application page, select the Specify port numbercheck box and type a port number if you want the SharePoint Central Administration Web application to use a specific port or leave the Specify port number check box unchecked if you want to use a random port

Configure Central Admin

  • On the Configure Security Settings portion of this page choose whether you’re going to use the default NTLM authentication or Kerberos. Kerberosrequires additional steps and are not covered in this particular post but will be in a future post focused specifically on Kerberos. Once selected, click Next
  • On the Completing the SharePoint Products and Technologies Wizard page, click Next
  • On the Configuration Successful page, click Finish

This is assuming the configuration completes successfully. There are many common issues that occur during initial setup and configuration that are not covered in this post. I will post information on SharePoint Common Issues soon.

At this point your new Central Administration page should open automatically. If you are prompted for a username and password you may need to add the SharePoint Central Administration site to the list of trusted sites and configure user authentication settings in your browser.

**Important notes**

Before moving forward with configuring SharePoint, creating sites etc. Be sure to install all needed Service Packs and updates beforehand. Installing updates to SharePoint can be tricky but here are a few helpful tips:

  • Always apply updates to Windows SharePoint Services (WSS) and then apply updates to MOSS
  • Apply service packs before any infrastructure or security updates
  • If you have multiple updates to apply you can install all of them with or without running the configuration wizard until you’ve finished installing them and then complete it by running the configuration wizard
  • Always make a good backup of all databases and of your SharePoint servers if possible before applying ANY updates!!!!
Leave a comment

Posted by on May 8, 2009 in SharePoint Installation