Search configuration issue in Valo Intranet installation
Last Updated on 2022-09-12 08:23:51 UTCSummary¶
Success
The issue is now solved via a fix provided by Microsoft!
While installing or updating Valo Intranet, you are likely to come across the following error:
DEBUG: Failed to execute Command:
Set-PnPSearchConfiguration -Path $Path -... , Error: Internal Server Error
This is currently seen across multiple tenants and one can reproduce this by exporting the existing search configuration (Get-PnPSearchConfiguration) in your own tenant and setting the same back using Set-PnPSearchConfiguration cmdlet.
We think that this incident is related to the following Microsoft issue: Some users may see errors and long wait times when searching through SharePoint Online and Microsoft Teams.
Latest updates¶
| Date (UTC) | Status |
|---|---|
| 2022-09-12 at 10:00 AM | Microsoft provided a fix for this issue. For more details, see Some users may see errors and long wait times when searching through SharePoint Online and Microsoft Teams. We can also confirm that the fix provided works! |
| 2022-08-31 at 2:30 PM | Created Microsoft support ticket and chat with Microsoft support agent. Conclusion that suspected issue is the one causing the problem. According to Microsoft, a fix should be delivered. |
| 2022-08-31 at 12:30 PM | Issue identified, reproduced, and search for workaround. |
Products affected¶
| Product name | Version | Comments |
|---|---|---|
| Valo Intranet | 4.0 | The issue was reported for version 4.0; but based on this functionality, version 3.1 might also be affected. |
Expected availability of fix¶
The problem seem to be related to the following Microsoft issue: Some users may see errors and long wait times when searching through SharePoint Online and Microsoft Teams. Hence, we expect Microsoft to solve it asap. However, we are investigating the root cause of the problem.
The issue is now solved via a fix provided by Microsoft!
Mitigation¶
The only workaround for now is allowing the installation/update to complete and then doing the mapping manually (please refer to the genesis-xx-XX file for the same).
While doing the mapping, if the corresponding crawled property is missing, then kindly make sure the corresponding Site Column is in use and has at least one item/document with that column filled.