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

Managed accounts not found

Oct 11, 2011 at 3:03 PM

Hi all,

I am done with the Installation for SharePoint 2010. during the configuration, it does not start Metadata service application and User Profile service application. I am getting the following error:-

 - Provisioning Managed Metadata Service Application
 - Managed Account  not found
At E:\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1124 char:46
+        If ($ManagedAccountGen -eq $NULL) { Throw <<<<  " - Managed Account $(
$spservice.username) not found" }
    + CategoryInfo          : OperationStopped: ( - Managed Account  not found
   :String) [], RuntimeException
    + FullyQualifiedErrorId :  - Managed Account  not found
 - Provisioning User Profile Service Application
 - Managed Account  not found
At E:\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1124 char:46
+        If ($ManagedAccountGen -eq $NULL) { Throw <<<<  " - Managed Account $(
$spservice.username) not found" }
    + CategoryInfo          : OperationStopped: ( - Managed Account  not found
   :String) [], RuntimeException
    + FullyQualifiedErrorId :  - Managed Account  not found
Press any key to exit...


Please let me know how to fix this ASAP. thanks


Oct 11, 2011 at 6:37 PM

Will need to see the full XML (without passwords). 

Oct 11, 2011 at 7:02 PM

HI JOseph,

 Please check the whole AutpspinstalletInput.xml file below:-----


<?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 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.3">
    <!-- The Environment attribute above appears at the top of the installation transcript. It does not affect the installation -->
    <!-- The Install section controls what modifications are made to the Windows OS prior to installation and how the SharePoint installation is run -->
        <!-- ConfigFile is the name of the file containing the unattended install settings for SharePoint's setup.exe
             You must put your product key in this file -->
        <!-- If true, the SharePoint prerequisite installer will install from the \SharePoint\PrerequisiteInstallerFiles folder.
             If false, the prerequisites will be downloaded during install. In order to use true you must obviously download all the prerequisites in advance.
             You can use a script like to quickly accomplish this -->
            <!-- Disables network loopback checks. This prevents the OS blocking access to your server under names other than its actual host name,
                 which SharePoint needs to do for WebDAV requests. -->
            <!-- Disables windows services that are running by default on Windows 2008 that are not used by SharePoint to conserve resources -->
            <!-- Switch off IE Enhanced Security configuration, so that your sites and Central Admin render properly in a browser on the server -->
            <!-- Switch off checking whether the code-signing certificates used to sign the SharePoint code have been revoked. This slows down the
                 start up time for SharePoint, particularly if the server cannot connect to the Internet to perform the revocation check. -->
    <!-- The Farm section contains basic farm-wide settings -->
        <!--Enter the passphase that will be used to join additional servers to the farm. This farm passphrase will also be used for the Secure Store service app-->
        <!-- The "Farm" account that will be used to run Central Administration and the timer service. If AddToLocalAdminsDuringSetup is true, it will be
             added to the server's local administrators group for the duration of the execution of the script. This is required for some steps, such as
             configuring the User Profile Synchronization service. If for some reason you need to leave the Farm account in the Administrators group after setup, set LeaveInLocalAdmins to true -->
        <Account AddToLocalAdminsDuringSetup="true" LeaveInLocalAdmins="false">
        <!-- Which server(s) to provision CentralAdmin on. Specify "true" or a list of servers -->
        <CentralAdmin Provision="true">
            <!-- If you are creating an alias, <DBServer> is actually the value of the SQL alias; otherwise it's the NetBIOS name of the SQL server or instance.
                 If you leave <DBServer> blank or specify localhost, script will assume the local server for SQL databases -->
            <!-- The script can create a SQL alias for you. Enter the DBInstance, and if you leave <DBPort> blank, script will assume default port value of 1433 -->
            <DBAlias Create="false"
                     DBPort="" />
            <!-- The DBPrefix is prepended to all database names. e.g. If you set this to TEST, your config DB will be TEST_ConfigDB.
                 If you set the prefix to localhost, script will prepend each database with the name of the server on which the script is run.
                 Leave this blank for no prefix.
                 NOTE: If you are installing a multi-server farm, it is recommended that you do not use localhost as services provisioned on different servers
                       will have different prefixes.
            <!-- The name of the farm configuration database -->
        <!-- The Services section configures the core service instances & components that are part of SharePoint Foundation -->
            <SandboxedCodeService Start="false" />
            <ClaimsToWindowsTokenService Start="false" />
            <SearchQueryAndSiteSettingsService Start="false" />
            <SMTP Install="false" />
            <OutgoingEmail Configure="true">
        <!-- The ManagedAccounts section configures all accounts that will be added to SharePoint as managed accounts. -->
            <!-- The CommonName values should remain unchanged; you can add additional managed accounts, but script expects certain static values for these 4 managed accounts.
                 If you are creating additional web applications, use a new account for each web application with a new common name, unless you are creating a large number
                 of web applications, in which case the additional memory consumption this requires outweighs the security benefits. -->
            <ManagedAccount CommonName="FarmAccount">
            <ManagedAccount CommonName="SpInstaller">
            <ManagedAccount CommonName="CAapppool">
            <ManagedAccount CommonName="PortalAppPool">
            <ManagedAccount CommonName="UpsAppPool">
 <ManagedAccount CommonName="MySiteAppPool">
   <ManagedAccount CommonName="MetadataAppPool">
     <ManagedAccount CommonName="BDCAppPool">
     <ManagedAccount CommonName="UPSyncronizationaccount">
        <!-- The object cache accounts are user accounts that are given FullControl and FullRead privileges on WebApplications so items can be cached by ASP.Net to improve performance.
             These accounts should not have any special Active Directory privileges other than Domain User membership -->
        <!-- The <Logging> section allows you to move various log files to another location / volume, per best practices and to control disk space usage on the (default) C: drive.
             It also allows you to specify some logging options, such as using NTFS compression for additional disk space savings.
             The <Path> for all log types will be created if it doesn't yet exist. However, the root (drive, e.g. D:) must obviously pre-exist - and on ALL servers in your farm. -->
            <IISLogs Compress="true">
                <!-- The default <Path> is $Env:SystemDrive\Inetpub\logs\LogFiles - enter another path (e.g. D:\IISLogs) or leave <Path> empty to use the default. -->
            <ULSLogs Compress="true">
                <!-- The default <LogLocation> is $Env:CommonProgramFiles\Microsoft Shared\Web Server Extensions\LOGS - enter another path (e.g. D:\Logs) or leave <LogLocation> empty to use the default. -->
                <!-- <LogDiskSpaceUsageGB> specifies the maximum amout of disk space (GB) to use. If you specify a value here, LogMaxDiskSpaceUsageEnabled will automatically be set to True.
                     Leave empty to use the default values (1000 GB, but with LogMaxDiskSpaceUsageEnabled set to False - so effectively NO restriction on disk space) -->
                <!-- <DaysToKeepLogs> specifies the time, in days, to retain diagnostic log files. Leave empty to use the default (14 days). -->
                <!-- <LogCutInterval> specifies the time, in minutes, before a new log file is generated. Leave empty to use the default (30 minutes). -->
            <UsageLogs Compress="true">
                <!-- The default <UsageLogDir> is $Env:CommonProgramFiles\Microsoft Shared\Web Server Extensions\LOGS - enter another path (e.g. D:\Logs) or leave <UsageLogDir> empty to use the default. -->
                <!-- <UsageLogMaxSpaceGB> must be between 1 and 20 GB. Leave empty to use the default (5 GB) -->
                <!-- <UsageLogCutTime> specifies the time, in minutes, of usage data collected per usage log file (acceptable values are between 1 and 1440, default 5). Leave empty to use the default. -->
    <!-- The WebApplications section configures the applications and sites that will be created. You can add additional <WebApplication> child tags to create extra web applications.
         The AddURLsToHOSTS flag will add all Alternate Access Mappings to the local server's HOSTS file and is useful if you are (for example):
         creating web apps whose URLs are not defined in DNS yet, a test farm, or if you are creating a DR farm, etc. -->
    <WebApplications AddURLsToHOSTS="false">
        <!-- Web application attributes are as follows:
            "Portal" is the primary site. Exactly one WebApplication should have this type. It is setup as a trusted file location
            for Excel services, and as the portal site connection for other site collections. The script also uses it internally
            when it requires the URL of an arbitrary site.
            "MySiteHost" is the host web application for mysites.
            Any additional web applications that you create should have a type of your own choice such as "Other"
        name: Name of the web application
        applicationPool: Application pool name
        applicationPoolAccount: DOMAIN\USERNAME of the account under which the application pool runs. This should be a managed account.
        url: URL of the root site collection in the application pool. Do not include the port number, but do set http/https correctly.
        port: Port on which the web application runs.
        databaseName: Name of the first content database.
        useClaims: false = disable claims based authentication. true = enable claims based authentication.
        useBasicAuthentication: false = only accept Kerberos/NTLM claims. true = also accept Basic authentication claims. Has no effect if useClaims is false.
        useOnlineWebPartCatalog: false = disable use of the online webpart gallery on the web application. true (default) enable it. -->
        <WebApplication type="Portal"
                        name="Portal Home"
                <ManagedPath relativeUrl="help" explicit="true" />
                <!-- You can specify multiple site collections within a web application.
                siteUrl: URL of the site collection. Include the port if it is non default for the protocol (80/443). Do not include default ports as this will make the script fail.
                owner: Name of owner
                name: Site Name
                description: About site
                SearchUrl: Localhost url for search
                CustomTemplate: Put false or true
                Template: Put custome template here
                LCID: Specify the number
                Locale: Language description
                        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://devserver-001"
                                description="Coda Site"
        <WebApplication type="MySiteHost"
                        name="MySite Host"
                <SiteCollection siteUrl="http://devserver-001: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="""" >
        <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="Testdomain\searchcontaccess" Password="""" />
                        <Server Name="devserver-001" />
                        <Server Name="devserver-001" />
                        <Server Name="devserver-001" />
                        <Server Name="devserver-001" />
                        <ApplicationPool Name="SharePoint Enterprise Search Application Pool" Account="Testdomain\Searchcontaccess" />
                    <Proxy Name="Search Service Application" Partitioned="false">
                        <ProxyGroup Name="Default" />
        <StateService Provision="false"
                      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="false"
                            Name="Secure Store Service"
                            ProxyName="Secure Store Service">
        <BusinessDataConnectivity Provision="false"
                                  Name="Business Data Connectivity Service"
                                  ProxyName="Business Data Connectivity Service">
        <WordAutomationService Provision="false"
                               Name="Word Automation Services"
                               ProxyName="Word Automation Services">
    <!-- The EnterpriseSeviceApps section configures services only available with an Enterprise licence.
         Common Attributes:
         UnattendedIDUser: DOMAIN\UserName of the unattended user account. This does not have to be SharePoint managed account, and the same account can be re-used for all services.
         UnattendedIDPassword: Password of the unattended user account.    -->
        <ExcelServices Provision="false"
                       Name="Excel Services Application"
        <VisioService Provision="false"
                      Name="Visio Graphics Service"
                      ProxyName="Visio Graphics Service"
        <AccessService Provision="false"
                       Name="Access Services"
                       ProxyName="Access Services">
        <!-- If you choose to provision Performance Point Services, the user running the script must be in the sysadmin role of the SQL server whilst the script runs. This can be revoked afterwards. -->
        <PerformancePointService Provision="false"
                      Name="PerformancePoint Service"
                      ProxyName="PerformancePoint Service"
    <!-- The OfficeWebApps section controls the installation of Office Web Apps. Setting Install="true" requires the office web apps installation files to be present -->
    <OfficeWebApps Install="false"
        <ExcelService Provision="false"
                      Name="Excel Calculation Services"
                      ProxyName="Excel Calculation Services">
        <WordViewingService Provision="false"
                            Name="Word Viewing Service"
                            ProxyName="Word Viewing Service">
        <PowerPointService Provision="false"
                           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" />

Oct 11, 2011 at 11:02 PM

AutoSPInstaller uses a generic service account for most of the services which seems to be missing from your list and this what is causing your error.

Stick with the template (don't remove the nodes or rename them which you seem to have done).

Few other notes:

Not all accounts need to be managed accounts. For example, the install account cannot be. Also, you cannot run CA under a different account than Farm admin. User Profile service cannot even use managed account and neither the sync connection.

The candidates for "Managed Accounts" are the App Pool Accounts and farm admin (in addition to the one that was deleted).

AutoSPInstaller implicilty add the farm account as a managed account, so you don't need to redefine it in the managed accounts. 

Oct 11, 2011 at 11:06 PM

This is what was deleted/renamed


<ManagedAccount CommonName="spservice"> <username>DOMAIN\spservice</username> <Password/> </ManagedAccount

You seem to have deleted the search one as well and you will be getting another error shortly as it seems you are trying provision Enterprise search as well as per the XML.

<ManagedAccount CommonName="searchservice"> <username>DOMAIN\SPsearch</username> <Password/> </ManagedAccount>

Stick with the template. Adding to it is fine, but not removing nodes or renaming them. 

Oct 13, 2011 at 2:30 PM

Hi Joseph,

 Thank you so much. This was my issue. i changed the service accounts in the input.xml file and that's  why i was getting "managed account not found". I really appreciate your time and efforts. It works like a charm now. Once again , thanks for your help.


Shaan Singh

Feb 9, 2012 at 10:29 AM

I got the same type of problem but in my case i wrote the domainname "". It could create managed accounts but it could´nt use them. Accounts not found when trying to create "Managed Metadata Service". I changed the domain name to "splab" and it worked as it should.



Sep 20, 2012 at 7:00 PM
hahnej wrote:

I got the same type of problem but in my case i wrote the domainname "". It could create managed accounts but it could´nt use them. Accounts not found when trying to create "Managed Metadata Service". I changed the domain name to "splab" and it worked as it should.



Thanks, Johan!

I had the same issue you did. It looks like AutoSPInstaller - or SharePoint - has an issue with using the FQDN. Using the shorter domain name fixed it for me too.