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

The Metadata service is not installed

Feb 1, 2012 at 3:16 PM

I'm getting following issue while installing SharePoint 2010 on Windows 2008 R2.
This environment has one SP Machine which is connecting to a SQL Cluster.

Have tried many things but no luck.

- Verified credentials
- Verified DCOM permission
- Verified Network Connectivity
- Uninstalled and installed SharePoint completely including IIS with server restart

Would appreciate any help.

Part of log looks like this :

 - Provisioning Managed Metadata Service Application
 - Starting Managed Metadata Service:
 - Managed Metadata Service already started.
 - Creating Metadata Service Application...
New-SPMetadataServiceApplication : The Metadata service is not installed.
At C:\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1334 char:71
+                 $MetaDataServiceApp = New-SPMetadataServiceApplication <<<< 
-Name $MetadataServiceName -ApplicationPool $ApplicationPool -DatabaseName $Met
aDataDB -AdministratorAccount $FarmAcct -FullAccessAccount $FarmAcct
    + CategoryInfo          : InvalidData: (Microsoft.Share...MetadataService:
   SPCmdletNewMetadataService) [New-SPMetadataServiceApplication], InvalidOpe 
    + FullyQualifiedErrorId : Microsoft.SharePoint.Taxonomy.Cmdlet.SPCmdletNew
 - Failed to create Metadata Service Application
At C:\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1335 char:37
+                 If (-not $?) { Throw <<<<  " - Failed to create Metadata Serv
ice Application" }
    + CategoryInfo          : OperationStopped: ( - Failed to Applica
   tion:String) [], RuntimeException
    + FullyQualifiedErrorId :  - Failed to create Metadata Service Application
 - Script aborted!
 - Error provisioning the Managed Metadata Service Application

Feb 3, 2012 at 1:19 AM

Hi Paul, this issue is a first for this forum (and for the Internet too, it seems)... What happens if you try to create a new Managed Metadata service app from the UI (Central Administration)?

In any case I don't think the problem is with AutoSPInstaller, but rather something corrupt or non-standard (permissions, group policy restriction, installation files bad, etc.) - especially since you mentioned you installed 2 other farms with no problem.

Do the ULS logs shed any more light on the problem?