I am struggling with an problem since for about one week. Now it`s time to ask you.
Following error message appears and turns the script to be halted:
-------------------------------------------------------------------------------
- Script halted!
- Provisioning Managed Metadata Service Application
- Managed Account CUSTOMER\SVC_SP2010_SERVICE CUSTOMER\SVC_SP2010_FARM not found
At C:\install\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1346 char:41
+ If ($managedAccountGen -eq $null) { Throw " - Managed Account $($spservice.u ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: ( - Managed Acco..._FARM not found:String) [], RuntimeException
+ FullyQualifiedErrorId : - Managed Account CUSTOMERE\SVC_SP2010_SERVICE CUSTOMER\SVC_SP2010_FARM not found
-------------------------------------------------------------------------------
My InputFile looks as following:
<?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. -->
<Configuration Environment="Dev" Version="3.2">
<!-- 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>
<!-- Set <PauseAfterInstall> to true in order to pause the script after the SharePoint binaries are installed.
Useful for running the binary install simultaneously on multiple servers but stopping short of the farm config (which can cause conflicts if running on multiple servers at once) -->
<PauseAfterInstall>false</PauseAfterInstall>
<!-- Set RemoteInstall Enable="true" to attempt a centralized, remote install & config of your entire farm -->
<RemoteInstall Enable="false">
<!-- ParallelInstall controls whether SharePoint binary file installs are triggered simultaneously on all servers in the farm during a remote install. Can speed things up considerably (unless of course all your VMs are running on the same host, sharing I/O resources etc.!) -->
<ParallelInstall>false</ParallelInstall>
</RemoteInstall>
<!-- AutoAdminLogon tells the script to place values in the registry that allow automatic logon with the install account credentials (only), should the installation proces require reboot(s).
In combination with the RunOnce entry, it gives a better unattended experience (as there can be several reboots now with SharePoint 2013).
Only the dedicated install account is supported; you can enter its password below. Note that it will be stored in PLAIN TEXT, both here and in the registry so be sure to change it afterwards (or disable the account).
Otherwise, you can leave the password blank in order to be prompted at run-time (though it will still be stored in plain text in the registry, at least until the server is rebooted once more after the install. -->
<AutoAdminLogon Enable="true" Password="PaSSwoRD" />
<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>true</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>PaSSPHrase!</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="true">
<Username>CUSTOMER\SVC_SP2010_FARM</Username>
<Password>PaSSwoRD</Password>
<Email></Email>
</Account>
<!-- Which server(s) to provision CentralAdmin on. Specify "true" or a list of servers -->
<CentralAdmin Provision="true">
<Database>CUSTOMER_SP2013_AdminContent</Database>
<Port>7777</Port>
<UseSSL>false</UseSSL>
</CentralAdmin>
<Database>
<!-- If you are creating an alias (recommended!), <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>SQL_ALIAS</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="true"
DBInstance="SERVER9005\SQL_ALIAS"
DBPort="1434" />
<!-- 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>CUSTOMER_SP2013</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" />
<SMTP Install="false" />
<OutgoingEmail Configure="false">
<SMTPServer></SMTPServer>
<EmailAddress></EmailAddress>
<ReplyToEmail></ReplyToEmail>
</OutgoingEmail>
</Services>
Part1
Comments: ** Comment from web user: AndreOL **
Following error message appears and turns the script to be halted:
-------------------------------------------------------------------------------
- Script halted!
- Provisioning Managed Metadata Service Application
- Managed Account CUSTOMER\SVC_SP2010_SERVICE CUSTOMER\SVC_SP2010_FARM not found
At C:\install\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1346 char:41
+ If ($managedAccountGen -eq $null) { Throw " - Managed Account $($spservice.u ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: ( - Managed Acco..._FARM not found:String) [], RuntimeException
+ FullyQualifiedErrorId : - Managed Account CUSTOMERE\SVC_SP2010_SERVICE CUSTOMER\SVC_SP2010_FARM not found
-------------------------------------------------------------------------------
My InputFile looks as following:
<?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. -->
<Configuration Environment="Dev" Version="3.2">
<!-- 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>
<!-- Set <PauseAfterInstall> to true in order to pause the script after the SharePoint binaries are installed.
Useful for running the binary install simultaneously on multiple servers but stopping short of the farm config (which can cause conflicts if running on multiple servers at once) -->
<PauseAfterInstall>false</PauseAfterInstall>
<!-- Set RemoteInstall Enable="true" to attempt a centralized, remote install & config of your entire farm -->
<RemoteInstall Enable="false">
<!-- ParallelInstall controls whether SharePoint binary file installs are triggered simultaneously on all servers in the farm during a remote install. Can speed things up considerably (unless of course all your VMs are running on the same host, sharing I/O resources etc.!) -->
<ParallelInstall>false</ParallelInstall>
</RemoteInstall>
<!-- AutoAdminLogon tells the script to place values in the registry that allow automatic logon with the install account credentials (only), should the installation proces require reboot(s).
In combination with the RunOnce entry, it gives a better unattended experience (as there can be several reboots now with SharePoint 2013).
Only the dedicated install account is supported; you can enter its password below. Note that it will be stored in PLAIN TEXT, both here and in the registry so be sure to change it afterwards (or disable the account).
Otherwise, you can leave the password blank in order to be prompted at run-time (though it will still be stored in plain text in the registry, at least until the server is rebooted once more after the install. -->
<AutoAdminLogon Enable="true" Password="PaSSwoRD" />
<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>true</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>PaSSPHrase!</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="true">
<Username>CUSTOMER\SVC_SP2010_FARM</Username>
<Password>PaSSwoRD</Password>
<Email></Email>
</Account>
<!-- Which server(s) to provision CentralAdmin on. Specify "true" or a list of servers -->
<CentralAdmin Provision="true">
<Database>CUSTOMER_SP2013_AdminContent</Database>
<Port>7777</Port>
<UseSSL>false</UseSSL>
</CentralAdmin>
<Database>
<!-- If you are creating an alias (recommended!), <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>SQL_ALIAS</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="true"
DBInstance="SERVER9005\SQL_ALIAS"
DBPort="1434" />
<!-- 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>CUSTOMER_SP2013</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" />
<SMTP Install="false" />
<OutgoingEmail Configure="false">
<SMTPServer></SMTPServer>
<EmailAddress></EmailAddress>
<ReplyToEmail></ReplyToEmail>
</OutgoingEmail>
</Services>
Part1
Comments: ** Comment from web user: AndreOL **
Yes you are right! I deleted the part for the service Account! Do I am able to add some more Accounts if I want or isn't it possible?
BTW:Now it works fine :-)