Share via

SharePoint Subscription Edition search service application does not create crawled properties for custom site columns

Sergiu 41 Reputation points
2024-07-06T14:04:02.19+00:00

I installed SharePoint Subscription Edition on Windows Server 2022.

The Frontend and application servers are running on Windows Server 2022 and the Search servers on Windows Server 2019 (due to an issue on 2022).

I created the search service application and indexed a web application with a site collection with custom content types and custom site columns. After the full crawl is done, the crawled properties corresponding to the custom columns are not created.

Just to be clear, there is content with these custom columns and values in them.

I tried with custom columns deployed via a .wsp solution but also with custom columns and content type created via the browser in the site settings page.

I checked in the search SQL database in the crawledproperties table and the properties are not there either.

What could be the cause for this? How can I trace the issue?

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,298 questions
SharePoint
SharePoint
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
10,301 questions
SharePoint Development
SharePoint Development
SharePoint: A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.Development: The process of researching, productizing, and refining new or existing technologies.
2,809 questions
Accepted answer
  1. Haoyan Xue_MSFT 22,466 Reputation points Microsoft Vendor
    2024-07-08T05:59:54.2966667+00:00

    Hi @Sergiu ,

    Thank you for posting in this community.

    To troubleshoot the issue, you can start by checking the crawl logs to see if there are any errors related to the custom columns.

    To view the crawl log

    1. Verify that the user account that is performing this procedure is an administrator of the Search service application, or has Read permissions to it.
    2. In Central Administration, under Application Management, click Manage service applications.
    3. On the Service Applications page, click the Search service application.
    4. On the Search Administration page, in the Quick Launch, in the Diagnostics section, click Crawl Log.
    5. On the Crawl Log - Content Source page, click the view that you want.

    You can also check the search service application logs for any errors or warnings. Additionally, you can try resetting the search index and performing a full crawl again to see if that resolves the issue.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sergiu 41 Reputation points
    2024-07-10T10:42:00.9233333+00:00

    I eventually found the solution to my issue by changing the role of the server from "Search" to "Application with Search".

    I did see some errors in the event log about missing custom assemblies, although there was no error reported in the crawl log.It seems the custom solutions were not deployed on the server with the role Search. After changing the role to Application with Search, the solution was also deployed there.

    0 comments