Tuesday, November 25, 2014

Migrate Managed Metadata Service to SharePoint 2013 error

Migrate Managed Metadata Service to SharePoint 2013 error


Managed Metadata Service connection i currently not availible
The Managed Metadata Service connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.
And in the ULS logs:
Failed to get term store for proxy ‘Managed Metadata Service Application Proxy’. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at Microsoft.SharePoint.Taxonomy.Internal.XmlDataReader.GetDateTime(String name)     at Microsoft.SharePoint.Taxonomy.Internal.SharedTermStore.Initialize(IDataReader dataReader, Guid termStoreIdValue, Boolean fromPersistedData)     at Microsoft.SharePoint.Taxonomy.Internal.SharedTermStore..ctor(IDataReader dataReader, Guid termStoreId, Boolean fromPersistedData)     at Microsoft.SharePoint.Taxonomy.Internal.DataAccessManager.GetTermStoreData(MetadataWebServiceApplicationProxy sharedServiceProxy, Boolean& partitionCreated) b195739c-8011-5023-8da3-f7cd968a5d80
The steps I did to get the error above:
  • Restore Managed Metadata Service database in the new SharePoint 2013 environment using SQL Server Management Studio
  • Used powershell to create new Managed Metadata Service application: (where -DatebaseName ‘Managed Metadata Service’ is my restored database.)
    New-SPServiceApplicationPool -Name 'ManagedMetadataServiceApplicationWebAppPool' -Account 'SP2013Services'
    $applicationPool = Get-SPServiceApplicationPool -Identity 'ManagedMetadataServiceApplicationWebAppPool'
    $mms = New-SPMetadataServiceApplication -Name 'Temp Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'Managed Metadata Service'
    New-SPMetadataServiceApplicationProxy -Name 'Managed Metadata Service Application Proxy' -ServiceApplication $mms -DefaultProxyGroup
  • Open Central Administration -> Application Management -> Manage Service Applications -> Manage Metadata Service Application -> Error!
The solution
  • Make sure you have started Managed Metadata Web Service in Central Administration -> System Settings -> Manage services on server
  • Make sure the account you used in the script above and that the farm account have appropiate rights on database intended for migration (default db owner)
  • Detach database in SQL Server Management Studio
  • Using Central Administration, remove the Managed Metadata Service Application (and associated data – do not forget to detach database before or it will be removed!)
  • Re-create Manage Metadata Service Application with a new database:
    $applicationPool = Get-SPServiceApplicationPool -Identity 'ManagedMetadataServiceApplicationWebAppPool'
    $mms = New-SPMetadataServiceApplication -Name 'Temp Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'New Managed Metadata Service'
    New-SPMetadataServiceApplicationProxy -Name 'Managed Metadata Service Application Proxy' -ServiceApplication $mms -DefaultProxyGroup
  • Verfiy that the term store management tool page is now working
  • Change database of the Managed Metadata Service application to your database intended for migration:
    Set-SPMetadataServiceApplication -Identity $mms -DatabaseName 'Managed Metadata Service'
  • Run iisreset
  • Verfiy that the term store management tool page is now working and that you can see terms from your old environment

Monday, November 24, 2014

SharePoint Edit Links (Drag and Drop Navigation) option missing

SharePoint Edit Links (Drag and Drop Navigation) option missing

f you’ve been using SharePoint 2013 you may have noticed the new ability to edit global navigation and quick launch navigation on the fly and to use drag and drop capabilities to create new links. This ability is provided via the ‘EDIT LINKS’ option in both the global navigation and quick launch navigation controls:
 image
However, you may notice that this ability is not available on all webs. This is because the SharePoint navigation provider limits this function to webs that have been created from a specific list of web templates:
  • Team Site – STS#0
  • My Site Host – SPSSITEHOST#0
  • SharePoint Portal Server Personal Space – SPSPERS#0
  • Storage And Social SharePoint Portal Server Personal Space – SPSPERS#2
  • Storage Only SharePoint Portal Server Personal Space – SPSPERS#3
  • Social Only SharePoint Portal Server Personal Space – SPSPERS#4
  • Empty SharePoint Portal Server Personal Space – SPSPERS#5
  • Project Site – PROJECTSITE#0

Friday, November 21, 2014

Design Manager Bug

Design Manager Bug 


Ran into an interesting little bug this past week with SharePoint 2013 Design Manager master pages. After having a friend recreate the issue on her VM, I contacted the Microsoft product team and confirmed this is an issue they hope to solve with a future update. Essentially, if you create a master page with the Design Manager, whether a minimal master or one that has been converted from HTML and CSS, the Site Contents > Add an app page will not allow you to add apps or lists to your site. This issue also impact the out of the box Oslo master page. Here is what you should see when you go to the Add an App page:


image
With this bug you end up never seeing the Apps you can add section. Sometimes you will see the “Working on it…” message and other times you will just see the Noteworthy apps.
The key to fixing this problem is to make sure your master page includes: DeltaPlaceHolderLeftNavBar, PlaceHolderLeftNavBar, DeltaPlaceHolderPageTitleInTitleArea, and PlaceHolderPageTitleInTitleArea and that each of them is not set to Visible=False. To do this in an HTML master page with Design Manager you would add the following snippets:

<!--SPM:<SharePoint:AjaxDelta id="DeltaPlaceHolderLeftNavBar" BlockElement="true" runat="server">-->
<!--SPM:<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server">-->
<!--SPM:</asp:ContentPlaceHolder>-->
<!--SPM:</SharePoint:AjaxDelta>-->
<!--SPM:<SharePoint:AjaxDelta id="DeltaPlaceHolderPageTitleInTitleArea" runat="server">-->
<!--SPM:<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server">-->
<!--SPM:</asp:ContentPlaceHolder>-->
<!--SPM:</SharePoint:AjaxDelta>-->
With these lines in place, the Apps you can add should show up again. Note, if you aren’t making a Design Manager HTML master page you will still want to ensure these controls (without the DM comments) are included somewhere in your master page and not marked as Visible=False.


Sharepoint Designer 2013, XSLT List View Options ribbon option is not showing

Sharepoint Designer 2013, XSLT List View Options ribbon option is not showing I have an ordinary Wiki Page, also tried making an Article...