[BUG] Set-PnPSearchConfiguration: Internal Server Error. Executing with search import files that were working 2 weeks ago

[benjacernuda]

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.

We are using PnP.PowerShell 1.11.0. Same version 2 weeks ago when this was working

We have tried this workaround but still having the error
#1328

Thanks for your help

Ben

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?

• [ x] Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

[gautamdsheth]

hi @benjacernuda , thanks for raising the issue.
The error is coming from the server side.

Ran into this myself, we raised the issue with Microsoft support.
They acknowledged the issue and will rollout a fix for it.

Got this reply from MS Support.

Will close the issue here as we can't do anything about it here. Will just have to wait for the fix to be rolled out globally. Keep checking for you health center in admin portal for updates.

[benjacernuda]

Many thanks Gautam

[benjacernuda]

hi @gautamdsheth,

It seems that in all our environments the Search advisory has been fixed (Status: Service Restored Saturday September the 3rd) but we are still getting the same Internal Server Error trying to import search properties using Set-PnPSearchConfiguration. Not sure if you are experiencing the same problem.

Many thanks!

Ben