rurikon

Afternote: These managed properties don't appear in the Central Administration at all, not even "half done" so that the mapping is missing. They are just not created at all.

That command gives nothing. Also this gives nothing, even though there are some built-in properties with the string "Keywords" in them (like ows_q_TEXT_SeoKeywords and SharePoint:BestBetKeywords): ``` Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication 'Search Service...

Another interesting find: I added the mappings manually (again because we have to move forward with the project), and now DSC doesn't complain and Get-SPEnterpriseSearchMetadataCrawledProperty finds the properties. We have...

I noticed my mistake and checked with -like later, but I thought I'd debug a bit further before commenting more :) I did install a later CU, but our two...

Ok, so an update on this. In short: SharePoint continues to behave very weirdly and inconsistently. First of all, I installed the March 2021 CU. It looks like this one...

The problems in Farm 2 turned out to be a broken solution. I exorcised it and now it works the same way as Farm 1. So apparently Get-SPEnterpriseSearchMetadataCrawledProperty doesn't work...

If I can make a suggestion, maybe this configuration might work better if it created the managed property anyway, even when it can't find the crawled property to map to...

I'm not sure if this is related, but I noticed problems with database rights when creating the search service in SharePoint 2019. I have deleted Search Service Application many times...