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

Error provisioning the Managed Metadata Service Application


I've come across the following error while trying to install SP2013. Can anyone suggest what the issue might be?
Thanks in advance!
  • Provisioning Managed Metadata Service Application
  • Starting Managed Metadata Service:
  • Managed Metadata Service already started.
  • Creating Metadata Service Application...
    New-SPMetadataServiceApplication : The term 'New-SPMetadataServiceApplication'
    is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify
    that the path is correct and try again.
    At E:\Temp\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1569 char:39
  • $metaDataServiceApp = New-SPMetadataServiceApplication -Name
    $me ...
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : ObjectNotFound: (New-SPMetadataServiceApplicatio
      n:String) [], CommandNotFoundException
    • FullyQualifiedErrorId : CommandNotFoundException

  • Script halted!
  • Error provisioning the Managed Metadata Service Application


brianlala wrote Apr 18, 2013 at 5:06 AM

It almost looks like something went wrong with the SharePoint installation, or the PowerShell cmdlets for SharePoint didn't load. Have never seen the above error before.

If you have since resolved it, could you please close/resolve the issue here.


plip1978 wrote Apr 18, 2013 at 11:02 AM

thanks for replying. I wasn't sure if it occurred because I was installing SharePoint 2013 Foundation. I found that if I turned of the provisioning of the managed metadata service, the user profile service, the enterprise search service, excel, vision, access and performance point - then it would run to the end and complete the install.
Is this the behaviour you'd expect?

plip1978 wrote Apr 18, 2013 at 11:11 AM

Also, I'm not sure why, but the ALIAS didn't work. I had set up something like SERVER\INSTANCE, but all the databases were put into SERVER. Any ideas why this might have occurred?

plip1978 wrote Apr 18, 2013 at 3:37 PM

I've recreated everything for autospinstaller 3.86 (in terms of the xml file) and have asked it to provision all the services I said I had to turn off in the previous post.

I am currently running up against this error:

  • Done setting up managed paths at "http://RTMOSAIQSVR:80"
  • Granting CYMRU\vcc_sp_services rights to "Portal"...Done.
  • Creating Site Collection "http://RTMOSAIQSVR"...

WARNING: Template is not found and is not applied.

  • Script halted!
Exception : System.UnauthorizedAccessException: <nativehr>0x8007000
                    5</nativehr><nativestack></nativestack>Access denied.
                       at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedA
                    ccessException(UnauthorizedAccessException ex)
                    gApplicationId, String bstrUrl, Int32 lZone, Guid 
                    gSiteId, Guid gDatabaseId, String bstrDatabaseServer, 
                    String bstrDatabaseName, String bstrDatabaseUsername, 
                    String bstrDatabasePassword, String bstrTitle, String 
                    bstrDescription, UInt32 nLCID, String bstrOwnerLogin, 
                    String bstrOwnerUserKey, String bstrOwnerName, String 
                    bstrOwnerEmail, String bstrSecondaryContactLogin, 
                    String bstrSecondaryContactUserKey, String 
                    bstrSecondaryContactName, String 
                    bstrSecondaryContactEmail, Boolean bADAccountMode, 
                    Boolean bHostHeaderIsSiteName, Int32 
                    iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, 
                    Int32 iDatabaseVersionBuild, Int32 
                    iDatabaseVersionRevision, String bstrSiteSchemaVersion)
                       at Microsoft.SharePoint.Administration.SPSiteCollect
                    ion.Add(SPContentDatabase database, SPSiteSubscription 
                    siteSubscription, String siteUrl, String title, String 
                    description, UInt32 nLCID, Int32 compatibilityLevel, 
                    String webTemplate, String ownerLogin, String 
                    ownerName, String ownerEmail, String 
                    secondaryContactLogin, String secondaryContactName, 
                    String secondaryContactEmail, String quotaTemplate, 
                    String sscRootWebUrl, Boolean useHostHeaderAsSiteName, 
                    Boolean overrideCompatibilityRestriction)
                       at Microsoft.SharePoint.PowerShell.SPCmdletNewSite.C
                       at Microsoft.SharePoint.PowerShell.SPNewCmdletBase`1
                       at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessR
TargetObject : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
CategoryInfo : InvalidData:
                    [New-SPSite], UnauthorizedAccessException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, E:\Temp\SP\AutoSPInstaller\AutoSPInsta
                    llerFunctions.ps1: line 2111
                    at CreateWebApplications, E:\Temp\SP\AutoSPInstaller\Au
                    toSPInstallerFunctions.ps1: line 1966
                    at Setup-Farm, 
                    line 189
                    at <ScriptBlock>, 
                    line 357
                    at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}

PSMessageDetails :

This is my xml file:

<WebApplications AddURLsToHOSTS="true">
<WebApplication type="Portal" name="Portal" applicationPool="Portal" applicationPoolAccount="CYMRU\vcc_sp_portalapppool" url="http://localhost" port="80" UseHostHeader="false" AddURLToLocalIntranetZone="true" databaseName="Content_Portal" useClaims="true" useBasicAuthentication="false" useOnlineWebPartCatalog="false">
    <DBServer />
    <DBAlias Create="false" DBInstance="SERVER\INSTANCE" DBPort="" />
    <ManagedPath relativeUrl="help" explicit="true" />
    <SiteCollection siteUrl="http://localhost" HostNamedSiteCollection="false" Owner="DOMAIN\portalapppool" Name="Portal Home" Description="Portal Home Site" SearchUrl="http://localhost/search" CustomTemplate="false" Template="SPSPORTAL#0" LCID="1033" Locale="en-gb" Time24="false" />
<WebApplication type="MySiteHost" name="MySite Host" applicationPool="MySites" applicationPoolAccount="DOMAIN\profilesapppo" url="http://localhost" port="8080" UseHostHeader="true" AddURLToLocalIntranetZone="true" databaseName="Content_MySites" useClaims="true" useBasicAuthentication="false" useOnlineWebPartCatalog="false">
    <DBServer />
    <DBAlias Create="false" DBInstance="SERVER\INSTANCE" DBPort="" />
    <ManagedPath relativeUrl="personal" explicit="false" />
    <SiteCollection siteUrl="http://localhost:8080" HostNamedSiteCollection="false" Owner="DOMAIN\profilesapppo" Name="My Site Host" Description="My Site Host" SearchUrl="http://localhost/search" CustomTemplate="false" Template="SPSMSITEHOST#0" LCID="1033" Locale="en-gb" Time24="false" />


plip1978 wrote Apr 18, 2013 at 3:39 PM

Apologies for the strange formatting! And thanks in advance!

plip1978 wrote Apr 26, 2013 at 11:14 AM

I can't seem to close this issue.

bjorn80 wrote Dec 10, 2013 at 8:52 AM

GEtting the same error :-/

bjorn80 wrote Dec 10, 2013 at 9:05 AM

Found answer

added the contentapppool account and farm on the security tab with local acitivation and launch.