Monday, July 29, 2019

Installing Azure DevOps Server Search extension from Local Gallery

One of the mistakes that Azure DevOps Server Admins make is installing the Search extension from the Visual Studio Market Place. The Search extensions in Market Place are compatible only with Azure DevOps Service account. For Azure DevOps Server (i.e. OnPremises), the extension need to be installed from the Local Gallery page. This has been well-documented here.

In case you have already installed the incorrect extension, refer to the following sequence of steps to fix it:

NOTE: These steps are applicable for all TFS versions where Search is supported. Hence, replace \Azure DevOps Server 2019\ with the appropriate TFS version folder based on your current installation.

  • Uninstall the incorrect extensions for each of the collection where it's already installed. For that, follow the guidelines mentioned in this blog. It is important to get the database into a clean state before we can proceed with the extension install.
  • Go to the local gallery management page: http://<serverurl>/tfs/_gallery/manage and upload new extension.
  • Choose the VSIX package from \Program Files\Azure DevOps Server 2019\Tools\Deploy\TfsServicingFiles\Extensions for the correct entity (Code, WorkItem, WIKI) - 
    • "\Program Files\Azure DevOps Server 2019\Tools\Deploy\TfsServicingFiles\Extensions\Microsoft.TeamFoundation.Extension.Search.Web.Code.vsix"
    • "\Program Files\Azure DevOps Server 2019\Tools\Deploy\TfsServicingFiles\Extensions\Microsoft.TeamFoundation.Extension.Search.Web.WikiOnPremises.vsix"
    • "\Program Files\Azure DevOps Server 2019\Tools\Deploy\TfsServicingFiles\Extensions\Microsoft.TeamFoundation.Extension.Search.Web.WorkItemOnPremises.vsix"
  • Once the vsix package is uploaded, verify that the extension shows up in the local gallery page i.e. http://<serverurl>/tfs/_gallery
  • Install the specific extension for a collection from the local gallery.
Extension install triggers a re-indexing of that entity (Code, WorkItem, WIKI) for that collection. You may now monitor the indexing progress for that collection as mentioned in the blog here.

If the Search still does not work as expected post that, try the Repair-Search script for further troubleshooting and mitigation.


3 comments:

  1. First, awesome content! Second, we are running into a problem where the Wiki and WorkItem entities are not being indexed correctly (even when using the TriggerCollectionIndexing.ps1). Using some of your content to review the index, I noticed that in the tbl_JobHistory table, the ResultMessage shows that "Event 477738 completed with message 'BeginBulkIndex-AccountFaultIn: Indexing is disabled for this (TFSEntityId: b37add351f6648a2-877e-78fa-267dfe4, IndexingUnitType: Git_Repository, EntityType: Wiki, IndexingUnitId: 7361)." I've haven't been able to find anything online about how to enable this and I've tried to remove and the add the Wiki extension back and reran the TriggerCollectionIndexing.ps1 again with the same result. How would you recommend resolving this?

    ReplyDelete
  2. Thank you for your nice list of Web Development blog.
    DevOps Online Training

    ReplyDelete

Installing Azure DevOps Server Search extension from Local Gallery

One of the mistakes that Azure DevOps Server Admins make is installing the Search extension from the Visual Studio Market Place . The Sear...