Error during installation - DB

Feb 28, 2011 at 8:31 PM

Hello everyone !


I have a little issue when using AutoSPInstaller.

My config :

- Windows 7 (64bits)

- Sharepoint standalone installation OK without configuration wizard.

- Config.xml OK

- I already installed SQL Server 2008 R2 with Windows Auth.

Here is my XML configuration 






And the error (I launched the script as an administrator. I am logged as an admin).

- Checking farm membership for MORGAN-PC in "SharePoint_ConfidDB"...

- Attempting to join farm on "SharePoint_ConfidDB"...
- No existing farm found.
- Creating config database "SharePoint_ConfidDB"...
New-SPConfigurationDatabase : MORGAN-PC\spfarm
Au niveau de C:\Users\Morgan\Desktop\SP2010\AutoSPInstaller\AutoSPInstallerFunc
tions.ps1 : 489 Caractère : 32
+                 New-SPConfigurationDatabase <<<< –DatabaseName "$configDB" –
DatabaseServer "$DBServer" –AdministrationContentDatabaseName "$CentralAdminCon
tentDB" –Passphrase $SecPhrase –FarmCredentials $farmCredential
   + CategoryInfo         : InvalidData: (Microsoft.Share...urationDatabase:
   SPCmdletNewSPConfigurationDatabase) [New-SPConfigurationDatabase], Win32Ex
   + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPCon


Au niveau de C:\Users\Morgan\Desktop\SP2010\AutoSPInstaller\AutoSPInstallerFunc

tions.ps1 : 490 Caractère : 27

+                 If (-not $?) {throw <<<< }

   + CategoryInfo         : OperationStopped: (:) [], RuntimeException

   + FullyQualifiedErrorId : ScriptHalted


Is someone have an idea ?

thanks a lot !

Mar 1, 2011 at 2:07 PM
Edited Mar 1, 2011 at 2:07 PM

Just had the same error. 

- in the configfile the password for the SPfarm account is not set. Also, make sure this account has a password. (Line 14 of AutoSPInstallerInput.xml)

- DatabaseServerName is incorrect.


You do not have SQL 2008 SP2 or SQL 2008 R2. Check for the minimum requirements:


Sep 12, 2011 at 9:18 AM

Hi everyone,

I am encountering the same issue on my SP2010 installation:

I am trying to setup SP2010 with SP1 on a Win 2008 R2 SP1 VM with SQL 2008 R2 SP1 already set up. the machine is also a DC if it makes a difference (I am setting up a single server SP farm setup)

This is my AutoSPInstallerInput.xml content:

        <!-- 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="true" />
            <ClaimsToWindowsTokenService Start="true" />
            <SearchQueryAndSiteSettingsService Start="true" />
            <SMTP Install="false" />
            <OutgoingEmail Configure="false">
        <!-- 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 this 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">
            <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 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"
                                name="Portal Home"
                                description="Portal Home Site"
        <WebApplication type="MySiteHost"
                        name="MySite Host"
                <SiteCollection siteUrl="http://localhost:8080"
                                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
             specify the SyncConnectionAccount credentials and the script will attempt to create a default Sync connection using the new Add-SPProfileSyncConnection cmdlet -->
        <UserProfileServiceApp Provision="true"
                               Name="User Profile Service Application"
                               ProxyName="User Profile Service Application"
                               SyncConnectionAccountPassword="pass" >
        <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 Enterprise Search Application Pool" Account="DOMAIN\setupAdmin" Password="pass" />
                        <Server Name="localhost" />
                        <Server Name="localhost" />
                        <Server Name="localhost" />
                        <Server Name="localhost" />
                        <ApplicationPool Name="SharePoint Enterprise Search Application Pool" Account="DOMAIN\setupAdmin" />
                    <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="true"
                       Name="Excel Services Application"
        <VisioService Provision="true"
                      Name="Visio Graphics Service"
                      ProxyName="Visio Graphics Service"
        <AccessService Provision="true"
                       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="true"
        <ExcelService Provision="true"
                      Name="Excel Calculation Services"
                      ProxyName="Excel Calculation Services">
        <WordViewingService Provision="true"
                            Name="Word Viewing Service"
                            ProxyName="Word Viewing Service">
        <PowerPointService Provision="true"
                           Name="PowerPoint Service Application"
                           ProxyName="PowerPoint Service Application">
    <!-- Install the Adobe PDF iFilter and configure the search indexer to use it. This also adds the proper icon for .pdf files in SharePoint. -->
    <AdobePDFIndexingAndIcon 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" />



I took care that my user's password does not contain any characters other than letters and numbers, but whenever I set the <DBServer> value in my AutoSPInstallerInput.xml to blank (<DBServer><DBServer>) I get the following error:

- Validating user accounts and passwords...
- Account "DOMAIN\spFarmAcc"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Install based on:
- C:\Scripts\SP2010\AutoSPInstaller\\AutoSPInstallerInput.xml
- Environment: Dev
- Version: 2.5.3
- Disabling Loopback Check...
- Disabling IE Enhanced Security...
- Setting services Spooler, AudioSrv and TabletInputService to Manual...
- Spooler is already stopped and set Manual, no action required.
- AudioSrv is already stopped and set Manual, no action required.
- TabletInputService is already stopped and set Manual, no action required.
- Setting unused services WerSvc to Disabled...
- WerSvc is already stopped and disabled, no action required.
- Finished disabling services.
- Not changing CRL check behavior.
- SP2010 prerequisites appear be already installed - skipping install.
- SP2010 binaries appear to be already installed - skipping installation.
- Office Web Apps binaries appear to be already installed - skipping install.
- No language packs found in C:\Scripts\SP2010\LanguagePacks, skipping.
- Currently installed languages:
- English (United States)
- Adding DOMAIN\spFarmAcc to local Administrators (only for install)...
- DOMAIN\spFarmAcc is already an Administrator.
- Loading SharePoint Powershell Snapin
- Checking farm membership for SP2010 in "ConfigDB"...

- Attempting to join farm on "ConfigDB"...
Script aborted!


Exception             : System.Management.Automation.ParameterBindingValidation

                       Exception: Cannot validate argument on parameter 'Datab

                      aseServer'. The argument is null or empty. Supply an ar

                       gument that is not null or empty and then try the comma

                       nd again. ---> System.Management.Automation.ValidationM

                        etadataException: The argument is null or empty. Supply

                         an argument that is not null or empty and then try the

                         command again.

                           at System.Management.Automation.ValidateNotNullOrEmp

                       tyAttribute.Validate(Object arguments, EngineIntrinsics


                           at System.Management.Automation.ParameterBinderBase.

                       BindParameter(CommandParameterInternal parameter, Compi

                       ledCommandParameter parameterMetadata, ParameterBinding

                       Flags flags)

                           --- End of inner exception stack trace ---

                         at System.Management.Automation.ParameterBinderBase.

                       BindParameter(CommandParameterInternal parameter, Compi

                       ledCommandParameter parameterMetadata, ParameterBinding

                       Flags flags)

                         at System.Management.Automation.CmdletParameterBinde

                       rController.BindParameter(CommandParameterInternal argu

                       ment, MergedCompiledCommandParameter parameter, Paramet

                      erBindingFlags flags)

                           at System.Management.Automation.CmdletParameterBinde

                       rController.BindParameter(UInt32 parameterSets, Command

                       ParameterInternal argument, MergedCompiledCommandParame

                       ter parameter, ParameterBindingFlags flags)

                           at System.Management.Automation.CmdletParameterBinde

                       rController.BindParameters(UInt32 parameterSets, Collec

                        tion`1 arguments, CommandMetadata commandMetadata)

                           at System.Management.Automation.CmdletParameterBinde


                       ction`1 arguments)

                           at System.Management.Automation.CmdletParameterBinde

                       rController.BindCommandLineParameters(Collection`1 argu


                           at System.Management.Automation.CommandProcessor.Bin

                       dCommandLineParameters(CommandParameterInternal[] param


                           at System.Management.Automation.CommandProcessor.Pre

                      pare(CommandParameterInternal[] parameters)

                           at System.Management.Automation.CommandProcessorBase

                       .DoPrepare(CommandParameterInternal[] parameters)

                           at System.Management.Automation.Internal.PipelinePro

                       cessor.Start(Boolean incomingStream)

                           at System.Management.Automation.Internal.PipelinePro

                       cessor.SynchronousExecuteEnumerate(Object input, Hashta

                      ble errorResults, Boolean enumerate)

TargetObject         :

CategoryInfo         : InvalidData: (:) [Connect-SPConfigurationDatabase], Par


FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.SharePoint.P


ErrorDetails         :

InvocationInfo       : System.Management.Automation.InvocationInfo

PipelineIterationInfo : {}

PSMessageDetails     :


HOWEVER, If I change it to localhost, it is not treated in the same manner - the servername SP2010 is used instead of localhost and I receive an SQL connection error:

| Automated SP2010 install script |
| Started on: 09/12/2011 01:17:31 |
- Validating user accounts and passwords...
- Account "DOMAIN\spFarmAcc"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Account "DOMAIN\setupAdmin"...Verified.
- Testing access to SQL server/instance/alias: SP2010
- Trying to connect to "SP2010"...Fail
Script aborted!
- Connection Error. Check server name, port, firewall.


The same connection issue also happens with SP2010 as the DBServer, even though I have registered it as a server name in the SQL management studio.

I would really appreciate some help figuring this out as it is really holding me back...


Sep 12, 2011 at 10:53 AM

Looking at what I just posted, I think I will probably not get any replies since it is way too messy, so long story short:

Installing SP2010 SP1 on Win2008R2 SP1 with SQL2008R2 pre-installed. machine name SP2010 and it is a DC.

When I set the DBServer property in the input xml file to blank  I get the error:


                       Exception: Cannot validate argument on parameter 'Datab

                      aseServer'. The argument is null or empty

Even though in the input file it states that it will see blank as localhost...

If I try to put localhost or SP2010 in there I get a connection failure error.

If I try to put . or "" in there, I get the original InvalidData: (Microsoft.Share...urationDatabase: error as in the original post of this thread.

so, if anyone has any ideas I would love to hear them...


Sep 12, 2011 at 11:43 AM
Edited Sep 12, 2011 at 11:44 AM

I am assuming you are using the default instance on a SQL Server with NETBIOS name "SP2010" listening on the default port "1433". if this is the case, change this as follows:

            <!-- 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="" />


so, in a sense the issue is in the value of DBInstance. 

Sep 12, 2011 at 12:27 PM

managed a workaraound by running the new-spconfigurationdatabase cmdlet manually in powershell and supplying the machine's IP.

I have a few more installations ahead of me so I will still need it to work from the script...

Thanks for your help

Sep 13, 2011 at 11:38 AM

Thanks for your help josephsaad, however it is not working for me when I use SP2010 as the DBServer name.

I am using the 3695 port for central administration, if that makes any difference:

      <CentralAdmin Provision="true">

I read in a post somewhere that supplying localhost,(local) or '.' as the dbservername can result in a "Invalid name - loopback address" error, so I tried changing it to the machine's IP in the input.xml but it still failed...

When I run the command by hand with the IP it succeeds however, so I am guessing the script has a problem receiving an IP as a parameter...

If anyone has any idea how i can overcome this issue so my installation can be truly user-free I would be eternally in your debt :)


Sep 13, 2011 at 4:06 PM

this script is tested with the use of a domain accounts and yes you need to replace each "instance" of the domain with the NetBIOS name for the Domain.

It may appear to me that you are using local accounts and that you didn't change the "Domain\" to the necessary Domain name.

this script is not meant for a Windows 7 installation. I'd suggest that you try something like instead.

Sep 13, 2011 at 4:50 PM

Ok, thanks for your quick reply.

What about the customization mentioned here: ?

Would that allow me to simply change each DOMAIN instance to %DOMAIN% in the xml file and then the userdomain environment variable will be picked up in each different Domain Controller I run this on?

I am not installing it on Win7, but on Win2008R2 (DC) with SQL2008R2 pre-installed (Installing a single-server farm).

I am having an issue with the configDB setup, specifically the DB Server name: When I supply localhost I receive an error for invalid data (If I try to run the New-SPConfigurationDatabase cmdlet manually I receive a "Address invalid or loopback" error")

I managed to workaround it by using the machine's IP and manually creating the configDB but afterwards the Sharepoint server name is the IP and I believe it may be causing me other configuration problems down the line (As the script runs further, I get the SandboxedCode Service not started issue...)

Any ideas would be greatly appreciated...


Sep 15, 2011 at 3:23 PM

I don't think the customization for %Domain% is implemented in the mainstream releases yet.

General comments that may not directly help you with that error:

Ideally, SharePoint shouldn't be installed on the Server that is running the Domain controller. The script adds farm account to "Local administrator group" and DC doesn't have a "Local Admin Group", so unsure how will that behave.

It is also not recommended to install SQL on a domain controller, but SQL Server itself needs to be joining the domain. You will typically see a warning trying to install SQL.

before I even run autospinstaller, you need to configure the setup account (the one used to login to the SharePoint Server - hopefully not a domain admin) to have login on SQL Server, and member of the dbcreator and securityadmin fixed server roles on SQL Service . After this is done, you'll need to test the connectivity between SharePoint and SQL via creating a .udl file . Once this is successful, I use the information in the UDL connection into the xml input file for autoSPInstaller.

Using IP's or FQDN's for SQL isn't a good idea in general for SharePoint, you need to either NetBIOS names if you are using default instance of SQL or better to use SQL aliase. AutoSpinstaller creates a SQL alias if you let it do so, but you can also test it using cliconfg.exe utility.

Sep 15, 2011 at 3:34 PM

Managed to get it working, and let me tell you - It is a thing of beauty :) I must applaud the creators of this useful script - it has saved me a lot of time spent painstakingly trying to get SP2010 configured...

I understand the risks involved in this kind of AIO Single server installation, but since it is a demonstration machine and not in production I am willing to bend the MS rules a bit...

I implemented the %DOMAIN% customization in the script and it is working perfectly - I now believe all of my initial issues with DB connectivity were due to the incorrect username syntax (DOMAIN\user instead of %DOMAIN%\user)

A bit off-topic question: Does anyone know of an AUTOInstaller for MS Project Server 2010 and for FAST Search Server? need to install those as well and would be nice to automate it as well...

Thanks for all your help!

Sep 26, 2011 at 8:55 PM

Not sure about Project Server but for FAST, check this out: