This project has moved and is read-only. For the latest updates, please go here.

Error creating new farm configuration database

Apr 25, 2012 at 5:09 PM

Not that I'll be doing it wrong. I have given permissions to the respective accounts and I always get this error:


I have: Windows Server 2008 R2 y SQL Server 2008 R2

Apr 25, 2012 at 5:28 PM

There are several things that can cause this error. I've had it happen to me in the past and a few reasons for it are:

  • The farm passphrase does not comply with policy or has invalid characters.
  • The farm or setup account doesn't have permissions to SQL
  • The SQL Server name is wrong, is blocked via firewall
  • There is already a (incomplete) SharePoint_Config database.

If you can post your XML, that might help us troubleshoot the problem.

Apr 25, 2012 at 5:50 PM

thanks for your answer wahidsaleemi. Mi XML is:

<?xml version="1.0" ?>

<Configuration Environment="Dev" Version="2.5.7">
    <!-- The Environment attribute above appears at the top of the installation transcript. It does not affect the installation -->
    <!-- The Install section controls what modifications are made to the Windows OS prior to installation and how the SharePoint installation is run -->
        <!-- ConfigFile is the name of the file containing the unattended install settings for SharePoint's setup.exe
             You must put your product key in this file -->
        <!-- If true, the SharePoint prerequisite installer will install from the \SharePoint\PrerequisiteInstallerFiles folder.
             If false, the prerequisites will be downloaded during install. In order to use true you must obviously download all the prerequisites in advance.
             You can use a script like to quickly accomplish this -->
            <!-- Disables network loopback checks. This prevents the OS blocking access to your server under names other than its actual host name,
                 which SharePoint needs to do for WebDAV requests. -->
            <!-- Disables windows services that are running by default on Windows 2008 that are not used by SharePoint to conserve resources -->
            <!-- Switch off IE Enhanced Security configuration, so that your sites and Central Admin render properly in a browser on the server -->
            <!-- Switch off checking whether the code-signing certificates used to sign the SharePoint code have been revoked. This slows down the
                 start up time for SharePoint, particularly if the server cannot connect to the Internet to perform the revocation check. -->
    <!-- The Farm section contains basic farm-wide settings -->
        <!--Enter the passphase that will be used to join additional servers to the farm. This farm passphrase will also be used for the Secure Store service app-->
        <!-- The "Farm" account that will be used to run Central Administration and the timer service. If AddToLocalAdminsDuringSetup is true, it will be
             added to the server's local administrators group for the duration of the execution of the script. This is required for some steps, such as
             configuring the User Profile Synchronization service. If for some reason you need to leave the Farm account in the Administrators group after setup, set LeaveInLocalAdmins to true -->
        <Account AddToLocalAdminsDuringSetup="true" LeaveInLocalAdmins="false">
        <!-- Which server(s) to provision CentralAdmin on. Specify "true" or a list of servers -->
        <CentralAdmin Provision="true">
            <!-- If you are creating an alias, <DBServer> is actually the value of the SQL alias; otherwise it's the NetBIOS name of the SQL server or instance.
                 If you leave <DBServer> blank or specify localhost, script will assume the local server for SQL databases -->
            <!-- The script can create a SQL alias for you. Enter the DBInstance, and if you leave <DBPort> blank, script will assume default port value of 1433 -->
            <DBAlias Create="false"
                     DBPort="" />
            <!-- The DBPrefix is prepended to all database names. e.g. If you set this to TEST, your config DB will be TEST_ConfigDB.
                 If you set the prefix to localhost, script will prepend each database with the name of the server on which the script is run.
                 Leave this blank for no prefix.
                 NOTE: If you are installing a multi-server farm, it is recommended that you do not use localhost as services provisioned on different servers
                       will have different prefixes.
            <!-- The name of the farm configuration database -->
        <!-- The Services section configures the core service instances & components that are part of SharePoint Foundation -->
            <SandboxedCodeService Start="false" />
            <ClaimsToWindowsTokenService Start="false" />
            <SearchQueryAndSiteSettingsService Start="false" />
            <SMTP Install="false" />
            <OutgoingEmail Configure="true">
        <!-- The ManagedAccounts section configures all accounts that will be added to SharePoint as managed accounts. -->
            <!-- The CommonName values should remain unchanged; you can add additional managed accounts, but script expects certain static values for these 4 managed accounts.
                 If you are creating additional web applications, use a new account for each web application with a new common name, unless you are creating a large number
                 of web applications, in which case the additional memory consumption this requires outweighs the security benefits. -->
            <ManagedAccount CommonName="spservice">
            <ManagedAccount CommonName="portalapppool">
            <ManagedAccount CommonName="mysiteapppool">
                <username>DOMAIN\SPS CADERH</username>
            <ManagedAccount CommonName="searchservice">
        <!-- The object cache accounts are user accounts that are given FullControl and FullRead privileges on WebApplications so items can be cached by ASP.Net to improve performance.
             These accounts should not have any special Active Directory privileges other than Domain User membership -->
        <!-- The <Logging> section allows you to move various log files to another location / volume, per best practices and to control disk space usage on the (default) C: drive.
             It also allows you to specify some logging options, such as using NTFS compression for additional disk space savings.
             The <Path> for all log types will be created if it doesn't yet exist. However, the root (drive, e.g. D:) must obviously pre-exist - and on ALL servers in your farm. -->
            <IISLogs Compress="true">
                <!-- The default <Path> is $Env:SystemDrive\Inetpub\logs\LogFiles - enter another path (e.g. D:\IISLogs) or leave <Path> empty to use the default. -->
            <ULSLogs Compress="true">
                <!-- The default <LogLocation> is $Env:CommonProgramFiles\Microsoft Shared\Web Server Extensions\LOGS - enter another path (e.g. D:\Logs) or leave <LogLocation> empty to use the default. -->
                <!-- <LogDiskSpaceUsageGB> specifies the maximum amount of disk space (GB) to use. If you specify a value here, LogMaxDiskSpaceUsageEnabled will automatically be set to True.
                     Leave empty to use the default values (1000 GB, but with LogMaxDiskSpaceUsageEnabled set to False - so effectively NO restriction on disk space) -->
                <!-- <DaysToKeepLogs> specifies the time, in days, to retain diagnostic log files. Leave empty to use the default (14 days). -->
                <!-- <LogCutInterval> specifies the time, in minutes, before a new log file is generated. Leave empty to use the default (30 minutes). -->
            <UsageLogs Compress="true">
                <!-- The default <UsageLogDir> is $Env:CommonProgramFiles\Microsoft Shared\Web Server Extensions\LOGS - enter another path (e.g. D:\Logs) or leave <UsageLogDir> empty to use the default. -->
                <!-- <UsageLogMaxSpaceGB> must be between 1 and 20 GB. Leave empty to use the default (5 GB) -->
                <!-- <UsageLogCutTime> specifies the time, in minutes, of usage data collected per usage log file (acceptable values are between 1 and 1440, default 5). Leave empty to use the default. -->
    <!-- The WebApplications section configures the applications and sites that will be created. You can add additional <WebApplication> child tags to create extra web applications.
         The AddURLsToHOSTS flag will add all Alternate Access Mappings to the local server's HOSTS file and is useful if you are (for example):
         creating web apps whose URLs are not defined in DNS yet, a test farm, or if you are creating a DR farm, etc. -->
    <WebApplications AddURLsToHOSTS="false">
        <!-- Web application attributes are as follows:
            "Portal" is the primary site. Exactly one WebApplication should have this type. It is setup as a trusted file location
            for Excel services, and as the portal site connection for other site collections. The script also uses it internally
            when it requires the URL of an arbitrary site.
            "MySiteHost" is the host web application for mysites.
            Any additional web applications that you create should have a type of your own choice such as "Other"
        name: Name of the web application
        applicationPool: Application pool name
        applicationPoolAccount: DOMAIN\USERNAME of the account under which the application pool runs. This should be a managed account.
        url: URL of the root site collection in the application pool. Do not include the port number, but do set http/https correctly.
        port: Port on which the web application runs.
        databaseName: Name of the first content database.
        useClaims: false = disable claims based authentication. true = enable claims based authentication.
        useBasicAuthentication: false = only accept Kerberos/NTLM claims. true = also accept Basic authentication claims. Has no effect if useClaims is false.
        useOnlineWebPartCatalog: false = disable use of the online webpart gallery on the web application. true (default) enable it. -->
        <WebApplication type="Portal"
                        name="Portal Home"
                <ManagedPath relativeUrl="help" explicit="true" />
                <!-- You can specify multiple site collections within a web application.
                siteUrl: URL of the site collection. Include the port if it is non default for the protocol (80/443). Do not include default ports as this will make the script fail.
                owner: Site collection owner account.
                name: Name/title of the site collection.
                description: Description of the site collection.
                SearchUrl: URL of the search site. This may be in another web application / site collection.
                CustomTemplate: Set to true if a custom template is to be used.
                Template: Name of the template to use.
                LCID: Locale ID of the language pack to use for the site collection.
                Locale: Actual locale of the site for regional settings. e.g. for UK English you use the US English LCID of 1033 but the locale en-gb.
                        If omitted, the default locale of the LCID is used.
                Time24: If true, times are displayed using a 24 hour clock. If false, AM/PM is used. If omitted, the default for the LCID is applied. -->
                <SiteCollection siteUrl="http://localhost"
                                owner="DOMAIN\SPS CADERH"
                                name="Portal Home"
                                description="Portal Home Site"
        <WebApplication type="MySiteHost"
                        name="MySite Host"
                <SiteCollection siteUrl="http://localhost:8080"
                                owner="DOMAIN\SPS CADERH"
                                name="My Site Host"
                                description="My Site Host"
                <ManagedPath relativeUrl="personal" explicit="false"/>
                <ManagedPath relativeUrl="sites" delete="true" />
    <!-- The ServiceApps section configures service applications included in the standard SharePoint licence.
        Common Attributes:
        Provision: Whether/which servers to provision the service application on
        Name: Name of the application
        ProxyName: name of the application proxy -->
        <ManagedMetadataServiceApp Provision="true"
                                   Name="Managed Metadata Service"
                                   ProxyName="Managed Metadata Service">
        <!-- EnableNetBIOSDomainName should be set to true if the host portion of your DNS Domain name is different than your NetBIOS domain name.
             StartProfileSync should be set to true to configure the User Profile Synchronization Service. NOTE: If this is set to TRUE in a multi-server
             farm, you must run this script first on the machine that will run the profile synchronization service.
             If you are running SP2010 SP1, you can set CreateDefaultSyncConnection to true and specify the SyncConnectionAccount credentials;
             the script will attempt to create a default Sync connection using the new (although unsupported) Add-SPProfileSyncConnection cmdlet.
             NOTE: Add-SPProfileSyncConnection may be useful for experimental/non-production builds but as per it's UNSUPPORTED in on-premises deployments -->
        <UserProfileServiceApp Provision="true"
                               Name="User Profile Service Application"
                               ProxyName="User Profile Service Application"
                               SyncConnectionAccountPassword="" >
        <EnterpriseSearchService Provision="true"
                                 InternetIdentity="Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 6.0 Robot)"
                                 IndexLocation="C:\Program Files\Microsoft Office Servers\14.0\Data\Office Server\Applications"
                <EnterpriseSearchServiceApplication Name="Search Service Application"
                    <ApplicationPool Name="SharePoint Search Application Pool" Account="DOMAIN\SPS_CRAWL" Password="Amom504" />
                        <Server Name="localhost" />
                        <Server Name="localhost" />
                    <!-- You should specify all the servers you listed in QueryServers in the SearchQueryAndSiteSettingsServers node below as well -->
                        <Server Name="localhost" />
                    <!-- You can only run the AdminComponent on one server per Search Service App, so only list one server here -->
                        <Server Name="localhost" />
                        <ApplicationPool Name="SharePoint Search Application Pool" Account="DOMAIN\SPS_SEARCH" />
                    <Proxy Name="Search Service Application" Partitioned="false">
                        <ProxyGroup Name="Default" />
        <StateService Provision="true"
                      Name="State Service"
                      ProxyName="State Service">
        <WebAnalyticsService Provision="true"
                             Name="Web Analytics Service Application">
        <SPUsageService Provision="true"
                        Name="Usage and Health Data Collection">
        <SecureStoreService Provision="true"
                            Name="Secure Store Service"
                            ProxyName="Secure Store Service">
        <BusinessDataConnectivity Provision="false"
                                  Name="Business Data Connectivity Service"
                                  ProxyName="Business Data Connectivity Service">
        <WordAutomationService Provision="false"
                               Name="Word Automation Services"
                               ProxyName="Word Automation Services">
    <!-- The EnterpriseSeviceApps section configures services only available with an Enterprise licence.
         Common Attributes:
         UnattendedIDUser: DOMAIN\UserName of the unattended user account. This does not have to be SharePoint managed account, and the same account can be re-used for all services.
         UnattendedIDPassword: Password of the unattended user account. -->
        <ExcelServices Provision="false"
                       Name="Excel Services Application"
        <VisioService Provision="false"
                      Name="Visio Graphics Service"
                      ProxyName="Visio Graphics Service"
        <AccessService Provision="false"
                       Name="Access Services"
                       ProxyName="Access Services">
        <!-- If you choose to provision Performance Point Services, the user running the script must be in the sysadmin role of the SQL server whilst the script runs. This can be revoked afterwards. -->
        <PerformancePointService Provision="false"
                      Name="PerformancePoint Service"
                      ProxyName="PerformancePoint Service"
    <!-- The OfficeWebApps section controls the installation of Office Web Apps. Setting Install="true" requires the office web apps installation files to be present -->
    <OfficeWebApps Install="false"
        <ExcelService Provision="false"
                      Name="Excel Web App"
                      ProxyName="Excel Web App"
        <WordViewingService Provision="false"
                            Name="Word Viewing Service"
                            ProxyName="Word Viewing Service">
        <PowerPointService Provision="false"
                           Name="PowerPoint Service Application"
                           ProxyName="PowerPoint Service Application">
    <!-- The AdobePDF section can install the Adobe PDF iFilter and configure the search indexer to use it, plus add the proper icon for .pdf files in SharePoint.
         Also, we can configure SharePoint web app MIME type associations to allow direct opening of PDF files (instead of the default behavior of only allowing 'save as') -->
        <!-- The iFilter element supports a comma- or space-delimited list of server names on which to install the PDF iFilter. Useful if you want to selectively install ONLY on crawl servers, for example. -->
        <iFilter Install="false" />
        <!-- Both the Icon and MIMEType elements support only "true" or "false"; you probably would want the icon on all farm servers, and MIMEType is a web app-wide setting anyhow, not bound to specific servers -->
        <Icon Configure="true" />
        <MIMEType Configure="true"/>
    <!-- Install ForeFront Protection for SharePoint 2010.
         Configuration and licensing of ForeFront is performed by running its administration program from the Start Menu after installation. -->
    <ForeFront Install="false"
               ConfigFile="answerfile-ForeFront.xml" />

Apr 26, 2012 at 6:00 PM

run the UI configuration wizard, you should see a more meaningful error.

Apr 27, 2012 at 3:31 PM

Yes, you may get more information from the UI. One thing I noticed in your XML is that you are using an instance name (SRV-SHARE\SQLEXPRESS). I suggest creating an alias for this:

Finally, your passphrase has an underscore character and I'm not sure if that's causing the error but I'd try replacing it with one of these !, $, #, %.

Apr 27, 2012 at 6:00 PM

Thank you for your help. It solves the above problem, the problem was domain name and some words in the script (Administrators - Administradores) since my software is in Spanish. I have my other problem here is not whether it will therefore:

error 2

Apr 27, 2012 at 7:14 PM

Make sure the xml script will open in Internet Explorer. That looks like a syntax error and IE will tell pretty much what it is and where.

Apr 28, 2012 at 5:19 PM

Also around line 180, check the "owner" variable for the SiteCollection node.

Aug 1, 2013 at 12:15 PM
I just ran into the same problem. In this case my SQL machine was a 32 bit machine while the SP boxes were 64 bit.