It appears that the issue is tying the property to ows_taxid instead of ows_fieldname. I am missing a few Managed Properties, but will track that down via another forum post.
It appears that the issue is tying the property to ows_taxid instead of ows_fieldname. I am missing a few Managed Properties, but will track that down via another forum post.
I have exactly the same issue. I have re-mapped to the crawled property using just ows_fieldname but 24 hours later the refiners are still displaying GUIDs identical to yours. Did you get any further with this, please?
I just encountered the same issue on a client's SharePoint 2013 farm. And I also was able to fix it by removing the Crawled Property mappings that refererred to the ID's.
