Microsoft sent out an email saying that we have to run the script they provide, Update-FederatedHybridSearchForM365.ps1.
I'm running this on our dev farm to begin with, and I did have to run it a few times to get past some errors. However, it is stuck on this error:
EVO Successfully Registered as Trusted Token Issuer
Certificate was successfully retrieved.
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 1/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 2/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 3/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 4/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 5/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 6/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 7/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 8/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 9/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 10/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 11/12)
WARNING: The service principal 'c3959f3a-5ad4-4d2b-b1f0-bc70f9a5d0a1' credentials cannot be created right now, waiting
for proper Service Principal creation. Trying again (attempt 12/12)
Add-ServicePrincipalCredentials : An error occurred:
Microsoft.Online.Administration.Automation.MicrosoftOnlineException: Unable to complete this action. Try again later.
at Add-ServicePrincipalCredentials, E:\scripts\Update-FederatedHybridSearchForM365.ps1: line 226
at Set-S2SCertificateForSkill, E:\scripts\Update-FederatedHybridSearchForM365.ps1: line 212
at <ScriptBlock>, E:\scripts\Update-FederatedHybridSearchForM365.ps1: line 549
at <ScriptBlock>, <No file>: line 1
At E:\scripts\Update-FederatedHybridSearchForM365.ps1:212 char:9
- Add-ServicePrincipalCredentials $SkillAppId $StsCertB64 12
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
- FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Add-ServicePrincipalCredentials
It looks like something is not being created properly.
I ran this on the app server, I plan on running it on all on prem servers in our dev farm once it runs successfully.
It looks like an error in the script, which was provided by MS, so I'm hoping you can help fix it?