Notice
Hi
I have executed the script to import search managed properties in the Search Schema. We have use the same file 2 weeks ago in different tenants and worked without any problems but now we are getting an Internal Server Error
This happens in all of our tenants.
There was an advisory in the Health Centre and we thought that the problem would be fixed when the service was restored (#2310) but that hasn't been the case. Is this still happening to you @gautamdsheth? The advisory is solved but we are still having the Internal Server Error
We are using PnP.PowerShell 1.11.0. With the same version the script worked some weeks ago.
We have tried this workaround but still having the error
#1328
Not sure if you have noticed this @wobba or you are aware of some recent changes in the Search schema
Many thanks for your help
Expected behavior
The script run without errors and at the end the search managed properties are created in the Search Schema
Actual behavior
Steps to reproduce behavior
Execute et-PnPSearchConfiguration with a import file that was working before
What is the version of the Cmdlet module you are running?
PnP.PowerShell 1.11.0.
Which operating system/environment are you running PnP PowerShell on?
Notice
Hi
I have executed the script to import search managed properties in the Search Schema. We have use the same file 2 weeks ago in different tenants and worked without any problems but now we are getting an Internal Server Error
This happens in all of our tenants.
There was an advisory in the Health Centre and we thought that the problem would be fixed when the service was restored (#2310) but that hasn't been the case. Is this still happening to you @gautamdsheth? The advisory is solved but we are still having the Internal Server Error
We are using PnP.PowerShell 1.11.0. With the same version the script worked some weeks ago.
We have tried this workaround but still having the error
#1328
Not sure if you have noticed this @wobba or you are aware of some recent changes in the Search schema
Many thanks for your help
Expected behavior
The script run without errors and at the end the search managed properties are created in the Search Schema
Actual behavior
Steps to reproduce behavior
Execute et-PnPSearchConfiguration with a import file that was working before
What is the version of the Cmdlet module you are running?
PnP.PowerShell 1.11.0.
Which operating system/environment are you running PnP PowerShell on?