Script aborted (don't know where)

Jan 4, 2012 at 9:26 AM

Hello,

I'll add the whole log file, since I got no clue what wasn't working. I can access the central administration without any problems, everything seems working so far. Maybe you could again point out what is the problem here. Thanks in advance:

**********************
Start der Windows PowerShell-Aufzeichnung
Startzeit:    20120104094536
Benutzername: GOB\u4sadmin 
Computer:	 hostname (Microsoft Windows NT 6.1.7601 Service Pack 1) 
**********************
Die Aufzeichnung wurde gestartet. Die Ausgabedatei ist "C:\Users\u4sadmin\Deskt
op\AutoSPInstaller-2012-01-04_9-45.rtf".
-----------------------------------
| Automated SP2010 install script |
| Started on: 04.01.2012 09:23:50 |
-----------------------------------
--------------------------------------------------------------
 - Validating user accounts and passwords...
 - Account "gob\svc_sp_farm"...Verified.
 - Account "gob\svc_sp_svcapp"...Verified.
 - Account "gob\svc_sp_apppool"...Verified.
 - Account "gob\svc_sp_apppool"...Verified.
 - Account "gob\svc_sp_search"...Verified.
--------------------------------------------------------------
--------------------------------------------------------------
 - Testing access to SQL server/instance/alias: hostnamedb
 - Trying to connect to "hostnamedb"...Success
 - SQL Server version is: 10.50.1600.1
 - This instance of SQL Server is not clustered
 - Check if GOB\u4sadmin has dbcreator server role...Pass
 - Check if GOB\u4sadmin has securityadmin server role...Pass
--------------------------------------------------------------
 - Install based on: 
 - C:\SP2010\AutoSPInstaller\\AutoSPInstallerInput-hostname.xml 
 - Environment: Dev 
 - Version: 2.5.7
--------------------------------------------------------------
 - 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.
--------------------------------------------------------------
--------------------------------------------------------------
 - Configuring IIS logging...
 - C:\Inetpub\logs is already compressed.
--------------------------------------------------------------
--------------------------------------------------------------
 - SP2010 binaries appear to be already installed - skipping installation.
--------------------------------------------------------------
--------------------------------------------------------------
 - Installing SharePoint Language Packs:
 - Installing extracted language pack de-de....Done.
 - Language Pack installation complete.
 - Currently installed languages:
  - Englisch (USA)
--------------------------------------------------------------
--------------------------------------------------------------
 - Loading SharePoint Powershell Snapin
--------------------------------------------------------------
--------------------------------------------------------------
 - Checking farm membership for hostname in "hostnamedb_Config"...

 - Attempting to join farm on "hostnamedb_Config"...
 - No existing farm found.
 - Creating config database "hostnamedb_Config"...
 - Done creating configuration database for farm.
--------------------------------------------------------------
--------------------------------------------------------------
 - Configuring the SharePoint farm/server...
 - Installing Help Collection...
 - Securing Resources...
 - Installing Services...
 - Installing Features...
 - Creating Central Admin site...
 - Waiting for Central Admin site...Online
 - Installing Application Content...
 - Creating Version registry value (workaround for bug in PS-based install)
 - Getting version number... 14.0.0.6114
 - Done initial farm/server config.
--------------------------------------------------------------
--------------------------------------------------------------
 - Configuring SharePoint diagnostic (ULS) logging...
 - C:\SharePoint Logs doesn't exist; creating...
 - Setting SharePoint diagnostic (ULS) logging options:
  - DaysToKeepLogs: 14
  - LogMaxDiskSpaceUsageEnabled: False
  - LogDiskSpaceUsageGB: 1000
  - LogLocation: C:\SharePoint Logs
  - LogCutInterval: 30
 - Moving any contents in old location C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\ to C:\SharePoint Logs...
 - Compressing C:\SharePoint Logs and subfolders...
WARNUNG:  - Errors encountered compressing C:\SharePoint Logs, continuing...
--------------------------------------------------------------
--------------------------------------------------------------
 - Adding Managed Accounts
 - Creating local profile for gob\svc_sp_svcapp...Done.
 - Registering managed account gob\svc_sp_svcapp...
 - Creating local profile for gob\svc_sp_apppool...Done.
 - Registering managed account gob\svc_sp_apppool...
 - Creating local profile for gob\svc_sp_apppool...Done.
 - Managed account gob\svc_sp_apppool already exists.
 - Creating local profile for gob\svc_sp_search...Done.
 - Registering managed account gob\svc_sp_search...
 - Done Adding Managed Accounts
--------------------------------------------------------------
--------------------------------------------------------------
 - Creating web applications...
 - Creating Web App "hostname Home"
 - Setting up managed paths for "http://hostname:80"
 - Setting up explicit managed path "help" at "http://hostname:80"
 - Done setting up managed paths at "http://hostname:80"
 - Skipping creation of site "" - already provisioned.
--------------------------------------------------------------
 - Applying object cache accounts to "http://hostname:80"...
 - Done applying object cache accounts to "http://hostname:80"
 - Setting online webpart catalog access for "http://hostname:80"
--------------------------------------------------------------
--------------------------------------------------------------
--------------------------------------------------------------
--------------------------------------------------------------
--------------------------------------------------------------
--------------------------------------------------------------
 - Provisioning State Service Application...
 - Creating State Service Application Proxy...
 - Done creating State Service Application.
--------------------------------------------------------------
--------------------------------------------------------------
 - Configuring Usage Logging...
 - Moving any contents in old location  to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS...
 - Compressing C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS and subfolders...
WARNUNG:  - Errors encountered compressing C:\Program Files\Common 
Files\Microsoft Shared\Web Server Extensions\14\LOGS, continuing...
 - Done configuring usage logging.
--------------------------------------------------------------
--------------------------------------------------------------
 - Provisioning Secure Store Service Application...
 - Creating SharePoint Hosted Services Application Pool...
 - Starting Secure Store Service Instance...
 - Waiting for Secure Store service...Online
 - Creating Secure Store Service Application...
 - Creating Secure Store Service Application Proxy...
 - Done creating Secure Store Service Application.
 - Creating the Master Key...
 - Creating the Application Key...
 - Done creating/configuring Secure Store Service Application.
--------------------------------------------------------------
--------------------------------------------------------------
 - Applying service account gob\svc_sp_svcapp to service SPSearch4...
 - Done.
--------------------------------------------------------------
--------------------------------------------------------------
 - Applying service account gob\svc_sp_svcapp to service SPTraceV4...
 - Adding gob\svc_sp_svcapp to local Performance Monitor Users group...
 - gob\svc_sp_svcapp is already a member of Performance Monitor Users.
 - Adding gob\svc_sp_svcapp to local Performance Log Users group...
 - gob\svc_sp_svcapp is already a member of Performance Log Users.
 - Updating service account...
 - Restarting service SPTraceV4...
 - Done.
--------------------------------------------------------------
--------------------------------------------------------------
--------------------------------------------------------------
 - Script aborted!


Exception             : System.Management.Automation.ParameterBindingValidation
                        Exception: Das Argument kann nicht an den Parameter "St
                        ring" gebunden werden, da es NULL ist.
                           bei System.Management.Automation.ParameterBinderBase
                        .ValidateNullOrEmptyArgument(CommandParameterInternal p
                        arameter, CompiledCommandParameter parameterMetadata, T
                        ype argumentType, Object parameterValue, Boolean recurs
                        eIntoCollections)
                           bei System.Management.Automation.ParameterBinderBase
                        .BindParameter(CommandParameterInternal parameter, Comp
                        iledCommandParameter parameterMetadata, ParameterBindin
                        gFlags flags)
                           bei System.Management.Automation.CmdletParameterBind
                        erController.BindParameter(CommandParameterInternal arg
                        ument, MergedCompiledCommandParameter parameter, Parame
                        terBindingFlags flags)
                           bei System.Management.Automation.CmdletParameterBind
                        erController.BindParameter(UInt32 parameterSets, Comman
                        dParameterInternal argument, MergedCompiledCommandParam
                        eter parameter, ParameterBindingFlags flags)
                           bei System.Management.Automation.CmdletParameterBind
                        erController.BindParameters(UInt32 parameterSets, Colle
                        ction`1 arguments, CommandMetadata commandMetadata)
                           bei System.Management.Automation.CmdletParameterBind
                        erController.BindCommandLineParametersNoValidation(Coll
                        ection`1 arguments)
                           bei System.Management.Automation.CmdletParameterBind
                        erController.BindCommandLineParameters(Collection`1 arg
                        uments)
                           bei System.Management.Automation.CommandProcessor.Bi
                        ndCommandLineParameters(CommandParameterInternal[] para
                        meters)
                           bei System.Management.Automation.CommandProcessor.Pr
                        epare(CommandParameterInternal[] parameters)
                           bei System.Management.Automation.CommandProcessorBas
                        e.DoPrepare(CommandParameterInternal[] parameters)
                           bei System.Management.Automation.Internal.PipelinePr
                        ocessor.Start(Boolean incomingStream)
                           bei System.Management.Automation.Internal.PipelinePr
                        ocessor.SynchronousExecuteEnumerate(Object input, Hasht
                        able errorResults, Boolean enumerate)
TargetObject          : 
CategoryInfo          : InvalidData: (:) [ConvertTo-SecureString], ParameterBin
                        dingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsof
                        t.PowerShell.Commands.ConvertToSecureStringCommand
ErrorDetails          : 
InvocationInfo        : System.Management.Automation.InvocationInfo
PipelineIterationInfo : {}
PSMessageDetails      : 



-----------------------------------
| Automated SP2010 install script |
| Started on: 04.01.2012 09:23:50 |
| Aborted:    04.01.2012 09:52:59 |
-----------------------------------
**********************
Ende der Windows PowerShell-Aufzeichnung
Endzeit: 20120104095259
**********************

Jan 6, 2012 at 2:17 AM

Normally Enterprise Search installation/configuration would be next. Are you doing that or skipping it? Posting your Input XML file will help also.

Jan 9, 2012 at 9:30 AM
<!--?xml version="1.0" ?--> <!-- AutoSPInstaller Sample Configuration File General Instructions: 1. If you use the characters ' " < > & in your configuration (e.g. in passwords) you should encode them as follows: ' ' " " < < > > & & For example <Password>Fd"je&f</Password> should be written <Password>Fd"je&f</Password> 2. Configuration IS case sensitive. 3. Use a validator like http://www.w3schools.com/xml/xml_validator.asp to check the syntax of your file. 4. Any element that has a Provision="" attribute controls whether a particular component, site, or service is installed on a particular server. It can be set to either true to provision on every server on which the script is run, false to never provision, or to a list of computer names to provision the service only on the listed machines. This allows you to configure an entire multi-server farm with different servers fulfilling different roles using a single configuration file. e.g. <ExcelServices Provision="Server1 Server2"> would provision excel services only on Server1 and Server2. --> <!-- 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 -->

 

<?xml version="1.0" ?>
<!-- AutoSPInstaller Sample Configuration File
    General Instructions:
    1. If you use the characters ' " < > & in your configuration (e.g. in passwords) you should encode them as follows:

        '	&apos;
        "	&quot;
        <	&lt;
        >	&gt;
        &	&amp;
    
        For example <Password>Fd"je&f</Password> should be written <Password>Fd&quot;je&amp;f</Password>
    2. Configuration IS case sensitive.
    3. Use a validator like http://www.w3schools.com/xml/xml_validator.asp to check the syntax of your file.
    4. Any element that has a Provision="" attribute controls whether a particular component, site, or service is installed
       on a particular server. It can be set to either true to provision on every server on which the script is run,
       false to never provision, or to a list of computer names to provision the service only on the listed machines.
       This allows you to configure an entire multi-server farm with different servers fulfilling different roles
       using a single configuration file.
       e.g. <ExcelServices Provision="Server1 Server2"> would provision excel services only on Server1 and Server2. -->
<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 -->
    <Install>
        <!-- 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 -->
        <ConfigFile>config.xml</ConfigFile>
        <!-- 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 http://autospinstaller.codeplex.com/releases/view/44442 to quickly accomplish this -->
        <OfflineInstall>true</OfflineInstall>
        <Disable>
            <!-- 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. -->
            <LoopbackCheck>true</LoopbackCheck>
            <!-- Disables windows services that are running by default on Windows 2008 that are not used by SharePoint to conserve resources -->
            <UnusedServices>true</UnusedServices>
            <!-- Switch off IE Enhanced Security configuration, so that your sites and Central Admin render properly in a browser on the server -->
            <IEEnhancedSecurity>true</IEEnhancedSecurity>
            <!-- 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. -->
            <CertificateRevocationListCheck>false</CertificateRevocationListCheck>
        </Disable>
    </Install>
    <!-- The Farm section contains basic farm-wide settings -->
    <Farm>
        <!--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-->
        <Passphrase>Pa$$w0rd</Passphrase>
        <!-- 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">
            <Username>gob\svc_sp_farm</Username>
            <Password>Pa$$w0rd</Password>
            <Email>noreply@gob.de</Email>
        </Account>
        <!-- Which server(s) to provision CentralAdmin on. Specify "true" or a list of servers -->
        <CentralAdmin Provision="true">
            <Database>CentralAdministration</Database>
            <Port>20000</Port>
            <UseSSL>false</UseSSL>
        </CentralAdmin>
        <Database>
            <!-- 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 -->
            <DBServer>domaindb</DBServer>
            <!-- 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"
                     DBInstance="SERVER\INSTANCE"
                     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.
            -->
            <DBPrefix>domain</DBPrefix>
            <!-- The name of the farm configuration database -->
            <ConfigDB>Config</ConfigDB>
        </Database>
        <!-- The Services section configures the core service instances & components that are part of SharePoint Foundation -->
        <Services>
            <SandboxedCodeService Start="false" />
            <ClaimsToWindowsTokenService Start="false" />
            <SearchQueryAndSiteSettingsService Start="false" />
            <SMTP Install="true" />
            <OutgoingEmail Configure="true">
                <SMTPServer>192.168.1.1</SMTPServer>
                <EmailAddress>email@address.com</EmailAddress>
                <ReplyToEmail>email@address.de</ReplyToEmail>
            </OutgoingEmail>
        </Services>
        <!-- The ManagedAccounts section configures all accounts that will be added to SharePoint as managed accounts. -->
        <ManagedAccounts>
            <!-- 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">
                <username>gob\svc_sp_svcapp</username>
                <Password>Pa$$w0rd</Password>
            </ManagedAccount>
            <ManagedAccount CommonName="portalapppool">
                <username>gob\svc_sp_apppool</username>
                <Password>Pa$$w0rd</Password>
            </ManagedAccount>
            <ManagedAccount CommonName="mysiteapppool">
                <username>gob\svc_sp_apppool</username>
                <Password>Pa$$w0rd</Password>
            </ManagedAccount>
            <ManagedAccount CommonName="searchservice">
                <username>gob\svc_sp_search</username>
                <Password>Pa$$w0rd</Password>
            </ManagedAccount>
        </ManagedAccounts>
        <!-- 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 -->
        <ObjectCacheAccounts>
            <SuperUser>gob\svc_sp_farm</SuperUser>
            <SuperReader>gob\svc_sp_farm</SuperReader>
        </ObjectCacheAccounts>
        <!-- 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. -->
        <Logging>
            <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. -->
                <Path></Path>
            </IISLogs>
            <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. -->
                <LogLocation>C:\SharePoint Logs</LogLocation>
                <!-- <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) -->
                <LogDiskSpaceUsageGB></LogDiskSpaceUsageGB>
                <!-- <DaysToKeepLogs> specifies the time, in days, to retain diagnostic log files. Leave empty to use the default (14 days). -->
                <DaysToKeepLogs>14</DaysToKeepLogs>
                <!-- <LogCutInterval> specifies the time, in minutes, before a new log file is generated. Leave empty to use the default (30 minutes). -->
                <LogCutInterval></LogCutInterval>
            </ULSLogs>
            <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. -->
                <UsageLogDir></UsageLogDir>
                <!-- <UsageLogMaxSpaceGB> must be between 1 and 20 GB. Leave empty to use the default (5 GB) -->
                <UsageLogMaxSpaceGB></UsageLogMaxSpaceGB>
                <!-- <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. -->
                <UsageLogCutTime></UsageLogCutTime>
            </UsageLogs>
        </Logging>
    </Farm>
    <!-- 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:
        type:
            "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="unitop4sure"
                        applicationPool="domain Apppool"
                        applicationPoolAccount="gob\svc_sp_apppool"
                        url="http://domain"
                        port="80"
                        AddURLToLocalIntranetZone="true"
                        databaseName="Content"
                        useClaims="true"
                        useBasicAuthentication="false"
                        useOnlineWebPartCatalog="false">
            <ManagedPaths>
                <ManagedPath relativeUrl="help" explicit="true" />
            </ManagedPaths>
            <SiteCollections>
                <!-- 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\portalacc"
                                name="Portal Home"
                                description="Portal Home Site"
                                SearchUrl="http://localhost/search"
                                CustomTemplate="false"
                                Template="SPSPORTAL#0"
                                LCID="1033"
                                Locale="en-us"
                                Time24="false">
                </SiteCollection-->
            </SiteCollections>
        </WebApplication>
        <!--WebApplication type="MySiteHost"
                        name="MySite Host"
                        applicationPool="MySites"
                        applicationPoolAccount="DOMAIN\mysitesacc"
                        url="http://localhost"
                        port="8080"
                        AddURLToLocalIntranetZone="true"
                        databaseName="MySites_Content"
                        useClaims="false"
                        useBasicAuthentication="false"
                        useOnlineWebPartCatalog="false">
            <SiteCollections>
                <SiteCollection siteUrl="http://localhost:8080"
                                owner="DOMAIN\mysitesacc"
                                name="My Site Host"
                                description="My Site Host"
                                SearchUrl="http://localhost/search"
                                CustomTemplate="false"
                                Template="SPSMSITEHOST#0"
                                LCID="1033"
                                Locale="en-us"
                                Time24="false">
                </SiteCollection>
            </SiteCollections>
            <ManagedPaths>
                <ManagedPath relativeUrl="personal" explicit="false"/>
                <ManagedPath relativeUrl="sites" delete="true" />
            </ManagedPaths>
        </WebApplication-->
    </WebApplications>
    <!-- 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 -->
    <ServiceApps>
        <!--ManagedMetadataServiceApp Provision="true"
                                   Name="Managed Metadata Service"
                                   ProxyName="Managed Metadata Service">
            <Database>MetaData</Database>
        </ManagedMetadataServiceApp-->
        <!-- 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 http://www.harbar.net/archive/2011/07/12/332.aspx it's UNSUPPORTED in on-premises deployments -->
        <!--UserProfileServiceApp Provision="true"
                               Name="User Profile Service Application"
                               ProxyName="User Profile Service Application"
                               EnableNetBIOSDomainNames="false"
                               StartProfileSync="true"
                               CreateDefaultSyncConnection="false"
                               SyncConnectionAccount="DOMAIN\UPSync"
                               SyncConnectionAccountPassword="" >
            <ProfileDB>Profile</ProfileDB>
            <SyncDB>Sync</SyncDB>
            <SocialDB>Social</SocialDB>
        </UserProfileServiceApp-->
        <!--EnterpriseSearchService Provision="true"
                                 ContactEmail=""
                                 ConnectionTimeout="60"
                                 AcknowledgementTimeout="60"
                                 ProxyType="Default"
                                 IgnoreSSLWarnings="false"
                                 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"
                                 PerformanceLevel="PartlyReduced"
                                 Account="DOMAIN\SPSearch"
                                 Password=""
                                 ShareName="SearchIndex">
            <EnterpriseSearchServiceApplications>
                <EnterpriseSearchServiceApplication Name="Search Service Application"
                                                    DatabaseServer=""
                                                    DatabaseName="Search"
                                                    FailoverDatabaseServer=""
                                                    Partitioned="false"
                                                    Partitions="1"
                                                    SearchServiceApplicationType="Regular"
                                                    ContentAccessAccount="DOMAIN\SearchContentAccess"
                                                    ContentAccessAccountPassword="">
                    <ApplicationPool Name="SharePoint Search Application Pool" Account="DOMAIN\SPSearch" Password="" />
                    <CrawlServers>
                        <Server Name="localhost" />
                    </CrawlServers>
                    <QueryServers>
                        <Server Name="localhost" />
                    </QueryServers-->
                    <!-- You should specify all the servers you listed in QueryServers in the SearchQueryAndSiteSettingsServers node below as well -->
                    <!--SearchQueryAndSiteSettingsServers>
                        <Server Name="localhost" />
                    </SearchQueryAndSiteSettingsServers-->
                    <!-- You can only run the AdminComponent on one server per Search Service App, so only list one server here -->
                    <!--AdminComponent>
                        <Server Name="localhost" />
                        <ApplicationPool Name="SharePoint Search Application Pool" Account="DOMAIN\SPSearch" />
                    </AdminComponent>
                    <Proxy Name="Search Service Application" Partitioned="false">
                        <ProxyGroup Name="Default" />
                    </Proxy>
                </EnterpriseSearchServiceApplication>
            </EnterpriseSearchServiceApplications>
        </EnterpriseSearchService-->
        <StateService Provision="true"
                      Name="State Service"
                      ProxyName="State Service">
            <Database>StateServiceDB</Database>
        </StateService>
        <!--WebAnalyticsService Provision="true"
                             Name="Web Analytics Service Application">
            <ReportingDB>WebAnalyticsReportingDB</ReportingDB>
            <StagingDB>WebAnalyticsStagingDB</StagingDB>
        </WebAnalyticsService>
        <SPUsageService Provision="true"
                        Name="Usage and Health Data Collection">
            <Database>UsageAndHealthDB</Database>
        </SPUsageService-->
        <SecureStoreService Provision="true"
                            Name="Secure Store Service"
                            ProxyName="Secure Store Service">
            <Database>SecureStoreDB</Database>
        </SecureStoreService>
        <!--<BusinessDataConnectivity Provision="false"
                                  Name="Business Data Connectivity Service"
                                  ProxyName="Business Data Connectivity Service">
            <Database>BusinessDataCatalogDB</Database>
        </BusinessDataConnectivity>-->
        <!--WordAutomationService Provision="false"
                               Name="Word Automation Services"
                               ProxyName="Word Automation Services">
            <Database>WordAutomationDB</Database>
        </WordAutomationService-->
    </ServiceApps>
    <!-- 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.	-->
    <EnterpriseServiceApps>
        <!--ExcelServices Provision="false"
                       Name="Excel Services Application"
                       UnattendedIDUser="DOMAIN\ExcelUser"
                       UnattendedIDPassword="">
        </ExcelServices>
        <VisioService Provision="false"
                      Name="Visio Graphics Service"
                      ProxyName="Visio Graphics Service"
                      UnattendedIDUser="DOMAIN\VisioUser"
                      UnattendedIDPassword="">
        </VisioService>
        <AccessService Provision="false"
                       Name="Access Services"
                       ProxyName="Access Services">
        </AccessService-->
        <!-- 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"
                      UnattendedIDUser="DOMAIN\PerfPointUser"
                      UnattendedIDPassword="">
            <Database>PerformancePointDB</Database>
        </PerformancePointService-->
    </EnterpriseServiceApps>
    <!-- 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"
                   ConfigFile="config-OWA.xml">
        <ExcelService Provision="false"
                      Name="Excel Web App"
                      ProxyName="Excel Web App"
                      UnattendedIDUser="DOMAIN\ExcelUser"
                      UnattendedIDPassword="">
        </ExcelService>
        <WordViewingService Provision="false"
                            Name="Word Viewing Service"
                            ProxyName="Word Viewing Service">
        </WordViewingService>
        <PowerPointService Provision="false"
                           Name="PowerPoint Service Application"
                           ProxyName="PowerPoint Service Application">
        </PowerPointService>
    </OfficeWebApps>
    <!-- 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') -->
    <AdobePDF>
        <!-- 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="true" />
        <!-- 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"/>
    </AdobePDF>
    <!-- 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" />
</Configuration>

 

 

<!--<BusinessDataConnectivity Provision="false" Name="Business Data Connectivity Service" ProxyName="Business Data Connectivity Service"> <Database>BusinessDataCatalogDB</Database> </BusinessDataConnectivity>--> <!--WordAutomationService Provision="false" Name="Word Automation Services" ProxyName="Word Automation Services"> <Database>WordAutomationDB</Database> </WordAutomationService--> <!-- 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" UnattendedIDUser="DOMAIN\ExcelUser" UnattendedIDPassword=""> </ExcelServices> <VisioService Provision="false" Name="Visio Graphics Service" ProxyName="Visio Graphics Service" UnattendedIDUser="DOMAIN\VisioUser" UnattendedIDPassword=""> </VisioService> <AccessService Provision="false" Name="Access Services" ProxyName="Access Services"> </AccessService--> <!-- 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" UnattendedIDUser="DOMAIN\PerfPointUser" UnattendedIDPassword=""> <Database>PerformancePointDB</Database> </PerformancePointService--> <!-- The OfficeWebApps section controls the installation of Office Web Apps. Setting Install="true" requires the office web apps installation files to be present --> <!-- 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. --> <!-- 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 --> <!-- Install ForeFront Protection for SharePoint 2010. Configuration and licensing of ForeFront is performed by running its administration program from the Start Menu after installation. -->
Jan 9, 2012 at 4:33 PM

I am running into what I think is the same or similar issue.  Generic config file (just filled in the accounts, farm passpharse, and changed the URLs for the portal site and my sites).

 I am getting the following error (also, the Central Admin site will not load -- I get a 404 error):

--------------------------------------------------------------
- Provisioning Enterprise Search...
--------------------------------------------------------------
- Script aborted!

 

Exception             : System.Management.Automation.ParameterBindingValidation

                       Exception: Cannot bind argument to parameter 'String' b

                       ecause it is an empty string.

                           at System.Management.Automation.ParameterBinderBase.

                        ValidateNullOrEmptyArgument(CommandParameterInternal pa

                       rameter, CompiledCommandParameter parameterMetadata, Ty

                       pe argumentType, Object parameterValue, Boolean recurse

                       IntoCollections)

                           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

                       rController.BindCommandLineParametersNoValidation(Colle

                       ction`1 arguments)

                           at System.Management.Automation.CmdletParameterBinde

                       rController.BindCommandLineParameters(Collection`1 argu

                       ments)

                          at System.Management.Automation.CommandProcessor.Bin

                       dCommandLineParameters(CommandParameterInternal[] param

                       eters)

                           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: (:) [ConvertTo-SecureString], ParameterBin

                       dingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,M

                       icrosoft.PowerShell.Commands.ConvertToSecureStringComma

                       nd

ErrorDetails         :

InvocationInfo       : System.Management.Automation.InvocationInfo

PipelineIterationInfo : {}

PSMessageDetails     :

Jan 9, 2012 at 4:40 PM

Don't comment the XML file the way you are doing. If you don't want to provision a particular service application, set the provision option to "false". The PowerShell script is still trying to read the XML and doesn't find the node which is the likely cause of the error you are facing.

Same for other nodes such as "Site collections", but in this case for each web app, there should be at least one Site Collection node.