: To resolve the issue, follow these steps: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity\O365Integration\Settings\ The address is written to the following registry key on the server: The issue occurs due to a web exception when the Bec Web Service API tries to reach out to the remote endpoint for provisioning purpose. However, when we attempt to browse that URL (provisioning web service) in a browser, it may fail with the following exception:Īdditionally, when we attempt to do a telnet test to this remote server through the port 443, it fails: We can see the provisioning endpoint that the wizard is trying to reach, by running the command: > : Unable to connect to the remote server -> : No connection could be made because the target machine actively refused it 157.56.55.77:443 See InnerException, if present, for more details. This is often caused by an incorrect address or SOAP action. SharedServiceHost-EmailProviderServiceConfig.log,īecWebServiceAdapter: Connect to BECWS failed due to known exception : : There was no endpoint listening at In the C:\ProgramData\Microsoft\Windows Server\Logs\
The Integrate with Microsoft Office 365 wizard may fail to complete with the following error: We have found a new issue with Windows Server Essentials Dashboard integration wizard with Microsoft Office 365. First published on TechNet on Mar 14, 2018
