Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Art Saffran

Essentials Dashboard cannot connect to microsoft online services

Client server running Essentials 2012 R2. In the Server Dashboard, I am not able to connect to Office 365. This problem occurs intermittently.

When I select Change Office 365 administrator account to troubleshoot, I get the following error: "Cannot connect to Microsoft online services. Make sure that the computer is connected to the Internet and try again."

Steps taken:

  1. Restarted the server
  2. Tried different password: I get an error telling me the username or password is incorrect. This seems to indicate that the server is able to connect to Office 365 services and is "told" of a password error.
  3. In Powershell, entered the following: Test-NetConnection -ComputerName watchdog.servicebus.windows.net -Port 9350 (Found this on a site with information about checking connection to Azure services. This test passes.

In the past I had to disable Office 365 integration and set it up again with the wizard. This forced users to create a new password...disruptive. It worked for a while then stopped again. Recently it was not working but after trying to change the Office 365 administrator account it suddenly connected. Now it's not working again.

Are there log files I can review to see where this is failing?

No updates are waiting to install on the server so it's up to date.

Thanks.

--Art

asked03/13/2018 02:03
14777 views
Add Comment
Last Activity 03/21/2019 12:19

1 Answer(s)

  • Mariette Knap

    Microsoft MVP

    Hello Art,

    Pls, confirm that in C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log you find this error:

    BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://bws902-relay.microsoftonline.com/ProvisioningWebservice.svc?Redir=1098557810&Time=636356539931802459 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused

    If that is the case open regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity\O365Integration. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity\O365Integration\Settings locate BecEndPointAddress key and delete that. Now reboot the server and try again.

    Essentials Dashboard cannot connect to microsoft online services

    answered 03/13/2018 16:51
    Add Comment
    Stig Jarle Bu

    Hi,

    Have fixed this on some Essentials 2012 R2 servers now.  Experienced this after WindowsUpdate in mars this year. 
    But have one Essentials 2012 (Not R2) with identical problem - could the BecEndPointAddress also cause the same problem here -?   

    From SharedServiceHost-O365ProviderServiceConfig.log:

    [13736] 180503.092052.3156: ProviderFramework: Information: [0] : PfErrorHandler: IGNORING WCF internal exception: (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (IOException) The read operation failed, see inner exception. ==> (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (SocketException) An existing connection was forcibly closed by the remote host
    [15092] 180503.092053.5467: BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://provisioningapi-s1-db3a.microsoftonline.com/ProvisioningWebservice.svc?Redir=1629536777&Time=636337722250919995 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 134.170.172.141:443

    Regards
    -- Stig Jarle --

    Mariette Knap

    Microsoft MVP

    Hello Stig Jarle,

    It looks like the same issue so why don't you try it? Make sure you export that registry hive before making any changes so you can always go back.

    replied 05/03/2018 08:35
    Stig Jarle Bu

    Thanks - I will give it a shoot - and report back in a couple of days ;)

    - Stig Jarle - 

    replied 05/03/2018 08:39
    Wouter Nouwens

    Although we are one year further, perhaps this will help. My problem was solved by first manually installing the Password Change Notification Service, then restart the server. After that, the Office 365 Integration Wizard (on W2012R2 Essentials) worked flawlessly.

    In some way, the Wizard cannot install the service.

    So, just go to C:\Program Files\Windows Server\Bin\PCNS\Password Change Notification Service.msi 

    replied 03/21/2019 12:06
    Mariette Knap

    Microsoft MVP

    Thanks Wouter! This is very helpful.

    replied 03/21/2019 12:19
    Reply
    replied 05/03/2018 08:31
Add an Answer