SharePoint 2010 Installations: Adding a second server to an existing SharePoint Server Farm

As many of you know, I’ve been working on building some hosted SharePoint 2010. I’m also trying to determine exactly what each service account needs rights/permissions to. I’ll have more on the specifics of the service accounts in an upcoming post, but the main service accounts I currently have are:

  1. Install account
  2. Farm account

The Install service account is what I use to run the SharePoint 2010 installation and configuration wizard.

The Farm service account is the account I use for app pools and database connectivity.

When you setup the configuration wizard this way, your configuration database is created by the farm account you specify, while the admin database is created with the install account. This doesn’t cause problems… until you try to connect a second SharePoint Server to the farm.

The Problems:

If you click the Retrieve Database names button you should get the following error:

Cannot find an existing configuration database located at the specified database server. Please choose a different database server.

If you type in the database name and click next, you should get the following error:

Failed to connect to the existing server farm located at the specified database server and database name. The database name is not a valid configuration database.

The Root Cause of The Problems:

The install service account you are using to run the configuration wizard on the second server has no rights to the configuration database that was created by the farm account during the first server install.

The Quick Fix

I went through to try and give minimal rights to allow the configuration wizard to pass, but only full rights works. To continue moving through the SharePoint 2010 configuration wizard, you must give the install service account db_owner rights/permissions.

2009-12-16T09:03:31+00:00 December 16th, 2009|


  1. Ardiseis October 4, 2011 at 4:32 am - Reply

    I am Having the same issue as listed above please see thread

    What service settings are you talking about in your post I am in a 2 server enviroment and the windows installer service runs as local system account how would I give it permission on the second server?

  2. rohan December 9, 2011 at 12:00 am - Reply

    Hello Chris,

    I have a query , I got an error while testing the MOSS 2007 CU updates on their test environment. I just need your expertise on this issue, it would be very helpful for me while troubleshooting further.

    Test Environment- Server – windows 2003, MOSS 2007 sp2, aug-2011 CU update

    WSS and MOSS patches(CU updates-2011-aug) were installed but the SharePoint Wizard failed. From our investigation, the configuration database is where the patching failed and the web server became disconnected to the farm. We tried to connect it back but the configuration database looks to have become corrupted.

    The error message is : Failed to connect to the existing server farm located at the specified database server and database name. The database name is not a valid configuration database.

  3. Tom Cox AA June 17, 2010 at 10:00 am - Reply

    This issue can also be caused by missing stored procs caused by using Sql Server Intregrated Services SSIS. Copy the Stored Procs to the DB and try again.

    God Bless You.

  4. December 25, 2012 at 1:22 am - Reply

    SharePoint 2010 Server Installations: Adding an existing configuration database to a SharePoint farm, ended up being a perfect blog title to give this article.
    Where exactly could I actually learn more pertaining to this?

Leave A Comment