Managed Metadata Service Application – The Default Term Store for this site cannot be identified.


One of the common issues that you face if you try to create a Managed Metadata Service application manually from Manage Service Application.  Although creating it manually is no different than creating it using Farm configuration wizard but Farm configuration Wizard does something that we did not get done automatically.

Amazingly the behavior is same in SharePoint 2013 as well.  If you try to use Managed Metadata Column or Create Term Set from Site Collection and try to put Terms you receive the following error.

"The default term store for this site cannot be identified."

Follow this step if you want to reproduce this.

Click on Document or Go to Shared Documents in SharePoint 2010 Team Site.

Click on Library Ribbon and Choose Create Column

Enter RequestTypes as Title and Choose Managed Metadata Column
You can select an existing term set from Term Store or click Customize your Term set that will make the terms not visible in the Enterprise keywords in the Term Store but term set will still be available at Term Store Level.

Let’s Fix it.

Go to Central Administration à Manage Service Application à Now Select the Row of Manage Metadata Service Application Proxy and click Properties

Now the Option Dialog will appear

You have to choose the 2nd Option.

Now Go back to Library and Close the Create Column Dialog and Try to create the Column Again.

Now Click on Edit Using Term Set Manager
Click OK. You will see that Create Button of the Create Column Dialog is pressed behind the scene and now a dialog is open that will allow you to add Request Types. The dialog was bit different in 2007 as it was a small Windows Type Dialog but here in 2013 it is more like Term Set Editor.
Now Let’s add few Terms
Now Close the Dialog

now Let’s edit properties of one of document in library

 

 

You can also select by typing the first character. To see all Click the Icon next to Request Types Text Box.

Now you can select Existing or event add a new Request Type

 

 

Simply click on Add New Item and then go on and add few. You can only select 1 because column settings does not allow multiple selection. 2010 UI for this screen was pretty confusing and Add new Item Link was hard to notice but now its pretty clear J

Here is what it will look like when you


SharePoint 2010 Pre-Population powershell script


I was trying to do some bulk upload Test using Powershell and found the below link to pre-populate SharePoint with some Test Data.  I tried to make it work but there were few bugs. The actual script writtne by ArianNevjestic is still available at http://blogs.technet.com/b/anevjes/archive/2010/03/01/sharepoint-2010-pre-population-powershell-script.aspx

Note that this is not my Script.  I have made some changes and putting the updated one here.

Set-ExecutionPolicy Unrestricted

#USER Defined Variables

$siteCollTemplate = “STS#0″
$webAppProtocol =”http://”
$WebAppsToCreate = @(“extranet.contoso.com:80″,”www.contoso.com:80“)
$numSiteCollectionsPerWebApp =5
$OwnerAlias = “contoso\sp_admin”
$docLib = “AnalyticsReports”
$fileSource = “C:\Users\sp_admin\Desktop\UploadFiles”
$appPoolExt = “App_Pool”
# DO not edit anything beyond this line

function SPContentUpload {

#my document upload function to a sharepoint doc library.

param ([string]$urlDocLib,[string]$urlSPWeb,[string]$strDirPath)

$hshDocProps=@{“ContentType”=”Document“}
[void][System.Reflection.Assembly]::LoadWithPartialName(”Microsoft.SharePoint”)
$SPsite=new-object Microsoft.SharePoint.SPSite($urlDocLib)
$SPweb=$SPsite.openweb($urlSPWeb)

#loop through all the files in the source folder and add each file to the defined SharePoint doc library

dir $strDirPath | foreach-object {
               $bytes=get-content $_.fullname -encoding byte
               $arrbytes=[byte[]]$bytes
               $SPWeb.files.Add($($urlDocLib +$docLib) + “/” + $_.Name + [guid]::newGuid().tostring(),$arrbytes,$hshDocProps, $true)
 

}

$SPSite.Dispose()

}

#[guid]::newGuid().tostring()
$b=1

foreach ($webApp in $WebAppsToCreate) {
$Split=$webApp.split(“:”)
$webAppUrl=$Split[0]
$webAppPort =$Split[1]

Write-Host Web App Url $webAppUrl $webAppPort
$webAppUrlFull=”$webAppProtocol$webAppUrl”

$OwnerMA = Get-SPManagedAccount -Identity “Contoso\sp_admin”
New-SPWebApplication -Name $($webAppUrl + ” Web Application” + $b) –URL $webAppUrlFull -port $webAppPort -ApplicationPool “$($webAppUrl + “_app_Pool” + $b)” -ApplicationPoolAccount $OwnerAlias -DatabaseName $($webAppUrl + “_” + $webAppPort) -HostHeader $webAppUrl

Write-Host Web App Url $webAppUrlFull

#Create new content db

#New-SPContentDatabase $webAppUrl -WebApplication $webAppUrlFull
New-SPContentDatabase $($webAppUrl + “_” + $webAppPort + “_2”) -WebApplication $($webAppUrlFull + “:” + $webAppPort)

$b++

$fileSource = “C:\Users\sp_admin\Desktop\UploadFiles”
$i=1

do {
$siteCollPath = $($webAppUrlFull + “:” + $webAppPort + “/sites/” + $i)
$siteCollPath2 = $($webAppUrlFull + “:” + $webAppPort + “/sites/” + $i + “_”)

Write-Host Creating site collection $siteCollPath

#create site collection to go to unique content database
New-SPSite -url $siteCollPath -OwnerAlias $OwnerAlias -Name “Test Wiki content db_1_ $i” -Template $siteCollTemplate -ContentDatabase $($webAppUrl + “_” + $webAppPort)
#populate Doc lib for above site collection
SPContentUpload “$($webAppUrlFull + “:” + $webAppPort + “/sites/” + $i + “/”)” “” “$fileSource”
#create site collection to go to sep content database
New-SPSite -url $siteCollPath2 -OwnerAlias $OwnerAlias -Name “Test Wiki content db_2_$i” -Template $siteCollTemplate -ContentDatabase $($webAppUrl + “_” + $webAppPort + “_2”)

#populate Doc lib for above site collection
SPContentUpload “$($webAppUrlFull + “:” + $webAppPort + “/sites/” + $i + “_/”)” “” “$fileSource”

$i++
}
while ($i -le $numSiteCollectionsPerWebApp)
}

Couple of Tips: Make sure that you have access to your Source file Folder.   If UAC is on you will not have access to C Drive.

Do not copy paste the script from you PC to HyperV VM using write clipboard text.  Seems Like some words were replaced by special characters.

Follow a Document Library


image

Once you go visit a Document Library you will see a small STAR ICON in Share and Track Ribbon Group.  Clicking on that in case retuned the above error.  Another thing that I was trying to System Account so I switched my user on Windows 7. 

Seems Like I can not Follow the full Document Library.  But once you select a document the ribbon will get enabled and let you follow up.

image

The document I am following will be visible on my mysite.

image

Setting Up Managed Metadata Service Application SharePoint 2013


Here are some articles about creating this Service Application. Both with UI and PowerShell.  I like the first one.

http://www.lamber.info/post/2010/12/05/How-do-I-create-a-new-managed-metadata-service-application.aspx

I faced a small issue during setting up the MMS.

My Setup consists of

1 Front End Servers

1 Application Servers,

1 SQL Server 2012

1 Workflow Server

1 WAC Server

1 AD Server

All the setup has been done in least permissions with different service account.  I started the MMS Web service from Manage Service on Server Page.  Then went on to create MMS Service Application with least permission.  On Visiting the MMS Service Application page I saw the error. 

Message “The Managed Metadata Service ‘Managed Metadata Service Application’ is inaccessible.”

Event ID: 8080

Task Category Taxonomy

image

Another error in log was

 

Event ID: 8077

Message “There are no instances of Managed Web Service is started on any server in the farm. Ensure that at least one instance is started on an application server in the farm using the Services on Server Page in Central Administration.”

image

Solution:

Your SharePoint Admin Account or System Account that you are using to browse the Central Administration does not has access to service Application so

Go to Manage Service Applications Page

Select Managed Metadata Service Application Row

image

From Ribbon Click Permissions

Now Add your Admin account contoso\SP_Admin in my case.  Click Add and give him all 3 permissions and click OK.

image

Better to do an IISRESET

Now try to access it again.

image

It took me some time to get it back. 

Here are some guys talking about the same issue.

http://sharepointknowledgebase.blogspot.com/2012/09/the-managed-metadata-service-or.html

SharePoint 2013–The start address sps3://intranet.contoso.com cannot be crawled


 

I guess you might have seen this issue before so please try to remember the fix as well.  While configuring Search I find out that SharePoint 2013 Search gave me the following error on User Profile Crawling.

“Access is denied.  Verify that either the Default Content Access Account has permission to access this repository, or add a crawl rule to crawl this repository…”

To Fix it we have to add our Content Access Account to be able to Crawl the content.

To do so we will go to Manage Service Application.

image

Now Select the User Profile Service Application row and click Administrator.

image

Now Enter your content Access Account in the first text box and click Add.

image

Click OK.

Now run the Full Crawl again.

image

Now compare the Searchable Items

image

Now Just take a look at Amazing Search Results Page.

image

Here is Conversation Search

image

People Results

image

Video test the video results later.

Search Settings at Site Collection Level

image

For More information and idea about the Vision of Microsoft SharePoint Search please visit the Microsoft SharePoint Team Blog for Series of Articles on SharePoint Search.

http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=1030