It seems to work again, (It just worked for me).
Error in Office 365 Hybrid Configration Wizard - The root element does not exist
Hi,
I have an MS Exchange 2019 on premise server and would like to run the Hybrid Wizard. After successful login, the environment check starts. The Office 365 environment check does not work. The following is written in the log.
The wizard runs in German "Das Stammelement ist nicht vorhanden" means "The root element is not present"
Is there a way to reset the hybrid configuration?
Or to check it?
LogFile...
2024.07.09 12:55:16.726 10084 [Client=UX, Activity=Tenant Connection Validation, Thread=22] Erfolgreiche HTTP/S-Verbindung mit Host "outlook.office365.com" in 432 ms.
2024.07.09 12:55:16.828 10084 [Client=UX, Activity=Tenant Connection Validation, Thread=22] Verbindung mit "https://outlook.office365.com/powershell-liveid" wird hergestellt...
2024.07.09 12:55:16.934 10468 [Client=UX, Activity=Tenant Connection Validation, Thread=22] AdminApiEnabled: True
2024.07.09 12:55:17.382 ERROR 10085 [Client=UX, Activity=Tenant Connection Validation, Thread=22] Das Stammelement ist nicht vorhanden.
2024.07.09 12:55:17.383 10084 [Client=UX, Activity=Tenant Connection Validation, Thread=22] Das Stammelement ist nicht vorhanden.
2024.07.09 12:55:17.383 10275 [Client=UX, Activity=Tenant Connection Validation, Thread=22] FINISH Time=2014,0ms
2024.07.09 12:55:17.384 WARNING 10079 [Client=UX, Activity=Tenant Connection Validation, Thread=22] Das Stammelement ist nicht vorhanden.
Thanks
4 answers
Sort by: Most helpful
-
-
Joachim Mistlbacher 0 Reputation points
2024-07-10T09:05:58.1533333+00:00 Same error here. Looks like the URL https://outlook.office365.com/powershell-liveid has a malfunction. Error 500
I also can't migrate mailboxes from onprem to EXO. Can anybody confirm this?
-
Noah Ma-MSFT 2,725 Reputation points Microsoft Vendor
2024-07-10T10:03:52.2333333+00:00 Hi @Andre Musholt ,
Thank you for posting to Microsoft Community.
Based on your description, it could be related to the connection with Exchange Online.
You could try to change authentication method to Office 365 to see if it works.
Hope it helps.
-
Mick Jacobson 0 Reputation points
2024-07-10T14:14:01.0133333+00:00 Same error also here in a hybrid deployment with exchange 2016 and 2019 enviro. Running the HCW throws this error.