none
I cannot integrate Office 365 with Server 2012R2

    Question

  • Initially, I had integrated Office 365 with Server 2012R2 so we could sync the passwords. This worked fine until recently. In the Windows Server Essentials Dashboard, all online accounts were shown as 'unknown', and when I tried to import online users (or do anything that required the online services) I got an error saying: "Cannot connect to Microsoft online services".

    So, I thought I could remove the integration, and try to re-integrate it again. I removed the Azure Active Directory, and Office 365 integration. Which worked fine. However, when I want to integrate with Office 365 again, I get the error I used to get. To integrate Office 365, I took the following steps:

    -Open the Windows Server Essentials Dashboard

    -In Home, under Services, I went to "Integrate with Microsoft Office 365", and clicked on "Integrate with Microsoft Office 365".

    -In the wizard I checked "I already have a subscription" and clicked next.

    -I entered a valid user name/password combination and clicked next.

    -I checked that I understand that the password policy will be set to strong and clicked next.

    -Then a progress bar appears for a short while, and then I get the "Cannot connect to Microsoft online services" error again.

    Does anybody know how I can resolve this?

    • Moved by AnnaWYModerator Wednesday, June 03, 2015 2:40 AM move from general
    Wednesday, May 06, 2015 12:01 PM

All replies

  • Hi Sefture,

    I recommend you can use Microsoft Online Services Module for powershell to test the connection issue of the Online service.

    To use Microsoft Online Services Module, we need to Install the Microsoft Online Services Sign-In assistant and the Windows Azure Active Directory (Azure AD) module on server, for more detailed steps, you can follow this article:

    Getting Started with Office 365 and PowerShell

    Then you need to input the user account and passwors to connect the online service:

    $cred=Get-Credential
    
    Connect-MsolService -Credential $CREd

    And the screenshoot is for your reference:

    If you connect to the online service, the cmdlet will encounter the error information, and you can troubleshoot the issue based on the error, and go through these articles:

    You can't connect to Office 365, Azure, or Intune by using the Azure Active Directory Module for Windows PowerShell

    If there is anything else regarding this issue, please feel free to post back.

    Best Regards,

    Anna Wang


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    • Edited by AnnaWYModerator Friday, May 08, 2015 12:53 PM
    • Proposed as answer by AnnaWYModerator Wednesday, May 20, 2015 11:56 AM
    • Marked as answer by AnnaWYModerator Thursday, May 21, 2015 8:21 AM
    • Unmarked as answer by Seftur Tuesday, June 02, 2015 9:53 AM
    Friday, May 08, 2015 12:53 PM
    Moderator
  • I did this, but in powershell it works fine. I can connect without a problem, and get the list of users. However, when I use the wizard in the Windows Server Essentials Dashboard, I still get the error.
    Tuesday, June 02, 2015 9:15 AM
  • Hi Sefture,

    In this case I would like to suggest you can collect the related error and logs to help us to troubleshoot.

    Please go to the Event Viewer and the failure in the file C:\programdata\Microsoft\Windows Server\Logs\OIMGettingStartedWizard.log.

    Please also check if you encountered the issue described in this article:

    Windows Server 2012 Essentials/R2 Essentials may fail to integrate with Microsoft Office 365

    If there is anything else regarding this issue, please feel free to post back.

    Best Regards,

    Anna Wang


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Tuesday, June 02, 2015 9:57 AM
    Moderator
  • I have looked at the issue in the article, but I'm having a different issue.

    I also tried to enable the integration using powershell, which gave me the following error:

    Enable-O365Integration : Call Bec web service <ListUsers>b__19() failed with generic communication issue
    At line:1 char:1
    + Enable-O365Integration
    + ~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Enable-O365Integration], O365ConfigureException
        + FullyQualifiedErrorId : InvalidInvoke,Microsoft.WindowsServerSolutions.O365Integration.EnableO365IntegrationPSCmdlet

    And the log contains the following:

    18256] 150602.113950.6903: General: Initializing...C:\Windows\System32\Essentials\OIMGettingStartedWizard.exe
    [17728] 150602.113951.3622: PfBinding: Information: [0] : Adding service dns identity [MV1] in proxy endpoint.
    [8552] 150602.113951.6591: PfBinding: Information: [0] : Adding service dns identity [MV1] in proxy endpoint.
    [18272] 150602.113952.1903: PfBinding: Information: [0] : Adding service dns identity [MV1] in proxy endpoint.
    [17728] 150602.114004.4862: GettingStartedWizard: Start O365 service
    [17728] 150602.114004.5018: WssgCommon: Information: [0] : WseEmailSvc is already in the desired state.
    [14124] 150602.114007.6581: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [14124] 150602.114007.6581: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [17728] 150602.114007.6737: GettingStartedWizard: Stop O365 service
    [17728] 150602.114007.9862: GettingStartedWizard: Activate O365 with Error Communication returned.
    [17728] 150602.114007.9862: GettingStartedWizard: Activate O365 with Error Communication returned.
    [17728] 150602.114008.0018: GettingStartedWizard: error page exception : O365ConfigurationFault = Communication
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Call Bec web service <ListUsers>b__19() failed with generic communication issue
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.ListUsers()
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.verifyAdminAccount(IO365ServiceAdapter adapter, String adminUserName, SecureString adminPassword)
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider.<>c__DisplayClassd9.<InvokeOperationWrapperAsync>b__d8()
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
    [18256] 150602.114008.0331: OIMUtils: GetO365ConfigurationErrorMessage for Communication
    [18256] 150602.114008.0331: GettingStartedWizard: Stop O365 service
    [18256] 150602.115712.0954: GettingStartedWizard: RebootOrRestartDashboardIfNecessary with restart flag is False



    • Edited by Seftur Tuesday, June 02, 2015 10:57 AM
    Tuesday, June 02, 2015 10:56 AM
  • Hi Seftur

    I am having the same issue as you. Did you ever find a solution?

    Sunday, January 03, 2016 12:29 AM
  • We are also having the same problem, office 365 integration, broke down from the dashboard, without any configuration changes as far as I can see.

    So my best bet is that an update broke the itnegration, or microsoft changed a backend setting that causes the problem.

    Do anybody have any fix yet?



    Best regards Jonas Akrouh Larsen
    IT-Consultant
    http://www.techbiz.dk

    Tuesday, January 05, 2016 9:09 AM
  • FYI: I have opened a case with Office 365 two weeks ago and it is now escalated to a specialized team. I have migrated from SBS 2011 to Windows Server 2012 R2 Datacenter + Essentials Experience role. The migration went just fine, no problems. Just the O365 integration wizard fails. But it is really strange because when I try to integrate with another O365 tenant it works just fine. I have captured traffic with Wireshark to see at what point it fails, Microsoft has these logs.

    Snippet from the log:

    [788] 160212.143522.5565: BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.ServiceModel.FaultException`1[Microsoft.Online.Administration.WebService.InvalidHeaderException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.Online.Administration.WebService.InvalidHeaderException).
    [788] 160212.143522.5719: UpdateMSOSecurityGroupDataTask: Failed to run UpdateMSOSecurityGroupDataTask: O365ConfigurationFault = Communication
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Connect to BECWS failed.
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.Connect()
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.get_Client()
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.<>c__DisplayClass70.<ListSecurityGroups>b__69(ListGroupsRequest r)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebServiceWithRetry[TRequest,TResponse](Func`2 func, TRequest request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.ListSecurityGroups()
       at Microsoft.WindowsServerSolutions.O365Integration.MSOSecurityGroupManager.CleanUpMSOSecurityGroupData()
       at Microsoft.WindowsServerSolutions.O365Integration.UpdateMSOSecurityGroupDataTask.Run().


    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook

    Friday, February 12, 2016 6:03 PM
  • Just got an email this morning that they are still working on a solution for this issue but they did not give an ETA. As a solution I should use Azure AD Connect but that is not what I want.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook

    Wednesday, March 09, 2016 3:00 PM
  • Anybody who has this issue please contact me at mariette at server-essentials dot com

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook

    Monday, March 21, 2016 1:06 PM
  • From O365 support I have now opened a case with Professional Support.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook

    Monday, April 04, 2016 2:42 PM
  • FYI: The last word on this issue is that it is a known issue, it is a design error. The Product Group is aware of the problem and working on a resolution. If you encounter similar problems you may refer to REG:116040413914419 Platform Support or Office 365 Ticket #30126-4719980.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook

    Tuesday, April 05, 2016 1:55 PM
  • I am having the same issues.  Any help would be greatly appreciated.  Thank you.
    Wednesday, October 12, 2016 12:15 PM
  • Almost daily I get emails from users with the same problem as described in this thread. Yesterday I tried to fix a similar issue on a client in New York. It seems that almost all of those problematic servers have one thing in common and that is they have a O365 subscription on E3 Enterprise or used to have that in the past but now they have Office 365 Business Premium. Pls, respond to this thread with more information on your O365 subscription. Please, also mention if your server was migrated from an older SBS and please also state how you migrated Exchange data if any?

    For Microsoft: The error "BecWebServiceAdapter: Connect to BECWS failed due to known exception" seems to be key to this issue. I have ran Wireshark to analyze the response of the server behind BECWS and the error is thrown by that service. IMHO the problem is NOT on the Windows Server 2012 R2 Essentials of customers but the problem is at your site. I have reported this error in January of this year and after working with several support professionals from O365 and Platform support I got the message that 'it is a known issue and we are working on this'. It has been 10 months until now and I get emails about every day people asking me if I know a solution to this.

    Microsoft, we cannot go on like this. It is unforgivable and unacceptable that you do not act.


    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook | Migrations done the easy way

    Check out the latest tutorial How to migrate Windows Server 2012 R2 (Essentials) to Windows Server 2016 (Essentials)

    Wednesday, October 12, 2016 12:40 PM
  • There were no problems for 3 years but now I have the exact same issue after planned Office365 admin password change. The Dashboard can detect the wrong credentials but it tells me to check my internet connection with the right ones . Connection is OK with PowerShell Office365 module. The problem in  OIMGettingStartedWizard is:

    [29412] 161012.232002.9888: GettingStartedWizard: Start O365 service
    [1864] 161012.232017.8646: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [1864] 161012.232017.8646: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [15356] 161012.232017.8646: GettingStartedWizard: Activate O365 with Error Communication returned.
    [15356] 161012.232017.8646: GettingStartedWizard: Activate O365 with Error Communication returned.
    [15356] 161012.232017.8646: GettingStartedWizard: error page exception : O365ConfigurationFault = Communication
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Call Bec web service <ListUsers>b__18() failed with generic communication issue
       в Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
       в Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.ListUsers()
       в Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.verifyAdminAccount(IO365ServiceAdapter adapter, String adminUserName, SecureString adminPassword)
       в Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
       в Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider.<>c__DisplayClassd9.<InvokeOperationWrapperAsync>b__d8()
       в Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
    [19640] 161012.232017.8802: OIMUtils: GetO365ConfigurationErrorMessage for Communication
    [19640] 161012.232024.4118: GettingStartedWizard: RebootOrRestartDashboardIfNecessary with restart flag is False


    • Edited by clicker71 Wednesday, October 12, 2016 2:56 PM
    Wednesday, October 12, 2016 2:55 PM
  • Just got this resolved on my server.  Microsoft has a hotfix for the issue which they are supposed to be releasing in the next few days.  In the mean time open a support ticket here - https://support.microsoft.com/en-us/assistedsupportproducts (if you don't have a support contract with MS then pay for a single incident and then request a refund if the issue is known like it was in my case).

    Wednesday, October 12, 2016 6:35 PM
  • Hi!

    I have a same issue from couple of days. I did try to resolve with Microsoft Office 365 tech Support form the Office 365 web admin surface.

    They said, there is no issue on their side, and there is no hotfix for that.

    Can you upload to somewhere this hotfix?

    or at least give me some reference for this hotfix?

    Thank You!

    Here is my configwizard.log

    [8212] 161014.132915.6128: General: Initializing...C:\Windows\System32\Essentials\ConfigWizard.exe
    [11476] 161014.132916.1440: PfBinding: Information: [0] : Adding service dns identity [RASHI] in proxy endpoint.
    [11924] 161014.132916.3784: PfBinding: Information: [0] : Adding service dns identity [RASHI] in proxy endpoint.
    [5972] 161014.132916.5034: PfBinding: Information: [0] : Adding service dns identity [RASHI] in proxy endpoint.
    [3784] 161014.132952.0567: GettingStartedWizard: Start O365 service
    [3784] 161014.132952.0567: WssgCommon: Information: [0] : WseEmailSvc is already in the desired state.
    [13588] 161014.132955.8225: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [13588] 161014.132955.8225: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [6964] 161014.132955.8225: GettingStartedWizard: Stop O365 service
    [6964] 161014.132958.0257: GettingStartedWizard: Activate O365 with Error Communication returned.
    [6964] 161014.132958.0257: GettingStartedWizard: Activate O365 with Error Communication returned.
    [6964] 161014.132958.0257: GettingStartedWizard: error page exception : O365ConfigurationFault = Communication
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException:

    Call Bec web service <ListUsers>b__18() failed with generic communication issue
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.ListUsers()
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.verifyAdminAccount(IO365ServiceAdapter adapter, String adminUserName, SecureString adminPassword)
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider.<>c__DisplayClassd9.<InvokeOperationWrapperAsync>b__d8()
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
    [8212] 161014.132958.0413: OIMUtils: GetO365ConfigurationErrorMessage for Communication
    [8212] 161014.132958.0569: GettingStartedWizard: Stop O365 service
    [8212] 161014.133006.9323: GettingStartedWizard: RebootOrRestartDashboardIfNecessary with restart flag is False

    With the Azure powershell scripts, everything just work fine.

    This is not some idiot certification issue? Maybe they generated a new certifications, but they forgot to push down

    Friday, October 14, 2016 11:37 AM
  • You have to call platform support and refer to this thread.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook | Migrations done the easy way

    Check out the latest tutorial How to migrate Windows Server 2012 R2 (Essentials) to Windows Server 2016 (Essentials)

    Friday, October 14, 2016 3:52 PM
  • Can someone share this hotfix please?
    Sunday, October 16, 2016 8:06 PM
  • For the love of god someone please share the hotfix!!
    Monday, October 17, 2016 4:37 AM
  • Call them and you will get the hot fix. Sharing is likely to be not legal.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook | Migrations done the easy way

    Check out the latest tutorial How to migrate Windows Server 2012 R2 (Essentials) to Windows Server 2016 (Essentials)

    Monday, October 17, 2016 7:05 AM
  • What?

    Share a hotfix for a well known, long running issue?

    are You kidding?

    The problem here, I called them!

    The platform is Office 365!

    We pay a lot of money for this service, and far as I know, this module is developed by the same team!

    Until last week everything is working fine.

    They did some changes, and now its not working!

    and most annoying this line in the log:

    Call Bec web service <ListUsers>b__18() failed with generic communication issue

    Thank You Mr. programmer, who did a really useful log..

    What is mean generic? How I can get a userlist with Powershell, if I have generic communication issue?

    No!

    Microsoft should come out with hotfix. Right now!

    You know what is illegal? To sell a platform with feature witch is not working....

    Monday, October 17, 2016 7:23 AM
  • Having the same problem on my server.
    Occured 3-4 days ago.
    Impossible to solve this over the phone with Microsoft.
    Really don't want to pay 499USD for a support request on this.

    Agree: Microsoft should come out with hotfix. Right now!

    Monday, October 17, 2016 9:07 AM
  • Would anybody tell me the Microsoft Hotfix KB number for this issue? If I know the KB numer the MS phone support guys can email it.
    Monday, October 17, 2016 10:28 AM
  • KB-wedontcareyouyoujusthavetopay

    this is the right KB number for this :) at the moment.

    Patch Tuesday maybe?

    Monday, October 17, 2016 11:19 AM
  • The hot fix that has been given to some customers requires you to install a non signed hot fix. That is something you should only do if you have no other options or you cannot wait for some more days. I do have some customers who suffer from this issue but I have decided to hold back the hot fix because those servers ran just fine without O365 integration.

    You have lived without the hot fix and with the bug for some time now, just wait a little longer until it has been fully tested and released to the public.

    Microsoft does care about the customers but sometimes fixing problems is not as easy as you have hoped for.

    No, I don't work for Microsoft but I do very well know that software is never without bugs or problems.


    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook | Migrations done the easy way

    Check out the latest tutorial How to migrate Windows Server 2012 R2 (Essentials) to Windows Server 2016 (Essentials)



    Monday, October 17, 2016 1:31 PM
  • KB319240 solved the issue for me. This included a fix for Office 365 connection with Server Essentials 2012 R2 due to an insufficent output buffer.

    More information at: 

    https://support.microsoft.com/en-us/kb/3192404 and 

    https://support.microsoft.com/en-us/help/24717/windows-8-1-windows-server-2012-r2-update-history

    Thursday, October 20, 2016 2:26 PM
  • That is good news. Now we can only hope that Microsoft fixes the same issue in Windows Server Essentials 2016 also.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook | Migrations done the easy way

    Check out the latest tutorial How to migrate Windows Server 2012 R2 (Essentials) to Windows Server 2016 (Essentials)

    Thursday, October 20, 2016 2:59 PM
  • sweet jesus thank you for the hotfix xxxxxxxxxxxx
    Friday, October 21, 2016 1:21 AM
  • Just got rid of "Internet connectivity" error but a new problem I suddenly got for today. Now it says "Invalid username or password" while trying to login with administrative account through the server Dashboard.

    I have no problem getting user list in Powershel with the same credentials. I am very confused.

    Monday, November 07, 2016 11:08 AM
  • Mariëtte,

    Do you know if you've heard from anyone else having this issue presently? I have a Server 2012 Essentials that stopped integrating with Office 365 after the October 2016 update rollup. It's odd because it fixed the issue for most people, but broke ours.

    Thanks!

    Friday, November 18, 2016 2:32 PM
  • Hi Jared, I think you will need to open a support request for this as we agreed per our email discussion.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Twitter | Facebook | Migrations done the easy way

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, November 18, 2016 6:42 PM
  • I have similar problem with my Server 2012 essentials (not R2). Connection was working for a while, but in early December I found that it is no longer working. Now I am trying to restore integration and nothing work. There is a part of log file. I think this error come from their server. Any suggestions?

    [7340] 170112.233759.7245: : Log has been continued from C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-O365ProviderServiceConfig.log
    [7340] 170112.233759.7245: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
    [7340] 170112.233759.7402: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistration]
    [7340] 170112.233759.7402: ProviderFramework: Information: [0] : Address: [net.tcp://127.0.0.1:65532//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistration]
    [7340] 170112.233759.7402: ProviderFramework: Information: [0] : Binding: []
    [7340] 170112.233759.7402: ProviderFramework: Information: [0] : Identifier: []
    [7340] 170112.233759.7402: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowLocalAccessOnly]
    [7340] 170112.233759.7402: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
    [7340] 170112.233759.7402: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [7340] 170112.233759.7714: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [11448] 170112.233759.8808: ProviderFramework: Information: [0] : _OnConnected called.
    [7340] 170112.233759.8808: ProviderFramework: Information: [0] : ConnectAsync was able to connect synchronously to the provider registry.
    [7340] 170112.233759.8964: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [IProvider], binding = [CustomBinding], EndpointAddress = [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider/Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider], AllowedConnectionType = [AllowLocalAccessOnly], EndpointCredentialType = [None]
    [7340] 170112.233759.8964: ProviderFramework: Information: [0] : AddServiceEndpoint type=[IProvider], binding=[System.ServiceModel.Channels.CustomBinding], address=[net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider/Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider]
    [7340] 170112.233759.8964: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [IO365Provider], binding = [CustomBinding], EndpointAddress = [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider/Microsoft.WindowsServerSolutions.O365Integration.IO365Provider], AllowedConnectionType = [AllowLocalAccessOnly], EndpointCredentialType = [User]
    [7340] 170112.233759.8964: ProviderFramework: Information: [0] : AddServiceEndpoint type=[IO365Provider], binding=[System.ServiceModel.Channels.CustomBinding], address=[net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider/Microsoft.WindowsServerSolutions.O365Integration.IO365Provider]
    [7340] 170112.233759.8964: ProviderFramework: Information: [0] : _ConfigureServiceHostDefaults()
    [7340] 170112.233759.9433: ProviderFramework: Information: [0] : Opening servicehost
    [7340] 170112.233800.0058: ProviderFramework: Information: [0] : Registering providers to PRS.
    [7340] 170112.233800.0058: ProviderFramework: Information: [0] : Registering Contract=[Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider], Address=[net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider/Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider], EndpointBehavior=[AllowLocalAccessOnly, None], impersonation=[Identification]
    [7340] 170112.233800.0214: ProviderFramework: Information: [0] : Registering Contract=[Microsoft.WindowsServerSolutions.O365Integration.IO365Provider], Address=[net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider/Microsoft.WindowsServerSolutions.O365Integration.IO365Provider], EndpointBehavior=[AllowLocalAccessOnly, User], impersonation=[Identification]
    [7340] 170112.233800.0214: ProviderFramework: Information: [0] : ProviderRegistryProxy: Beginning connection attempt.
    [7340] 170112.233800.0214: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
    [8792] 170112.233800.0370: ProviderFramework: Information: [0] : _OnConnected called.
    [7340] 170112.233800.0370: ProviderFramework: Information: [0] : ConnectAsync was able to connect synchronously to the provider registry.
    [7340] 170112.233800.0370: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [IProvider], binding = [CustomBinding], EndpointAddress = [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ClientProvider/Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider], AllowedConnectionType = [AllowLocalAccessOnly], EndpointCredentialType = [None]
    [7340] 170112.233800.0370: ProviderFramework: Information: [0] : AddServiceEndpoint type=[IProvider], binding=[System.ServiceModel.Channels.CustomBinding], address=[net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ClientProvider/Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider]
    [7340] 170112.233800.0370: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [IO365ClientProvider], binding = [CustomBinding], EndpointAddress = [net.tcp://factory:6602/Microsoft.WindowsServerSolutions.O365Integration.O365ClientProvider/Microsoft.WindowsServerSolutions.O365Integration.IO365ClientProvider], AllowedConnectionType = [AllowRemoteAccess], EndpointCredentialType = [User]
    [7340] 170112.233800.0370: ProviderFramework: Information: [0] : AddServiceEndpoint type=[IO365ClientProvider], binding=[System.ServiceModel.Channels.CustomBinding], address=[net.tcp://factory:6602/Microsoft.WindowsServerSolutions.O365Integration.O365ClientProvider/Microsoft.WindowsServerSolutions.O365Integration.IO365ClientProvider]
    [7340] 170112.233800.0370: ProviderFramework: Information: [0] : _ConfigureServiceHostDefaults()
    [7340] 170112.233800.0370: ProviderFramework: Information: [0] : Opening servicehost
    [7340] 170112.233800.0527: ProviderFramework: Information: [0] : Registering providers to PRS.
    [7340] 170112.233800.0527: ProviderFramework: Information: [0] : Registering Contract=[Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider], Address=[net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.O365Integration.O365ClientProvider/Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProvider], EndpointBehavior=[AllowLocalAccessOnly, None], impersonation=[Identification]
    [7340] 170112.233800.0527: ProviderFramework: Information: [0] : Registering Contract=[Microsoft.WindowsServerSolutions.O365Integration.IO365ClientProvider], Address=[net.tcp://factory:6602/Microsoft.WindowsServerSolutions.O365Integration.O365ClientProvider/Microsoft.WindowsServerSolutions.O365Integration.IO365ClientProvider], EndpointBehavior=[AllowRemoteAccess, User], impersonation=[Identification]
    [7340] 170112.233800.0527: ProviderFramework: Information: [0] : OnStart: service "O365ProviderSvc" ProviderServiceBase.OnStart finished. (ExitCode 0)
    [7340] 170112.233800.0996: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StartTasks called
    [7340] 170112.233800.1933: O365Integration:BackgroundTaskBase: Starting UpdateDomainTask
    [7340] 170112.233800.1933: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
    [7340] 170112.233800.1933: O365Integration:BackgroundTaskBase: Starting UpdateSharepointAddressTask
    [7340] 170112.233800.1933: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
    [7340] 170112.233800.1933: O365Integration:BackgroundTaskBase: Starting UpdateO365IntegrationDataTask
    [7340] 170112.233800.2089: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
    [11448] 170112.233800.2402: ProviderFramework: Information: [0] : (current thread: 0x2cb8): PfSynchronizationContext not needed.
    [11448] 170112.233800.2402: ProviderFramework: Information: [0] : (current thread: 0x2cb8): PfSynchronizationContext not needed.
    [11448] 170112.233801.6940: BecWebServiceAdapter: BEC web service is updated, need to update proxy code.
    [16372] 170112.233802.6178: BecWebServiceAdapter: Call Bec web service <ListUsers>b__15() failed: System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.
       --- End of inner exception stack trace ---
    Server stack trace:
       at System.ServiceModel.Channels.HttpInput.ThrowMaxReceivedMessageSizeExceeded()
       at System.ServiceModel.Channels.HttpInput.ReadBufferedMessage(Stream inputStream)
       at System.ServiceModel.Channels.HttpInput.ParseIncomingMessage(HttpRequestMessage httpRequestMessage, Exception& requestException)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at IProvisioningWebService.NavigateUserResults(NavigateUserResultsRequest request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.<ListUsers>b__15(NavigateUserResultsRequest r)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebServiceWithRetry[TRequest,TResponse](Func`2 func, TRequest request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
    [16372] 170112.233802.6178: UpdateO365IntegrationDataTask: Failed to get all users : O365ConfigurationFault = Communication
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Call Bec web service <ListUsers>b__15() failed with generic communication issue
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.ListUsers()
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.QueryAllOnlineUsers()
       at Microsoft.WindowsServerSolutions.O365Integration.UpdateO365IntegrationDataTask.Run()
    [8792] 170112.233802.6490: ProviderFramework: Information: [0] : Register to listen to ProviderRegistryConnectionMgmt connected event.
    [8792] 170112.233802.6490: ProviderFramework: Information: [0] : ProviderRegistryProxy: Beginning connection attempt.

    Thursday, January 12, 2017 11:37 PM
  • Hi Alexander,

    Microsoft is planning on releasing a fix for Essentials. If you wish, you can send in a support ticket (paid service) to Microsoft and get the hot fix. I received that exact hot fix and it resolved that exact problem for me. They'll be releasing the update sometime this month from what I gathered.

    Jared

    Friday, January 13, 2017 2:09 PM
  • Hi Jared

    Do you know the hotfix number? Please let me know as I have a user suffering from this issue.

    Thanks


    The call me nostradumbass

    Sunday, January 22, 2017 4:15 AM
  • Hi Ryrager,

    They installed hot fix KB3216737. It appears to be unavailable to the general public still.

    Jared

    Monday, January 23, 2017 2:14 PM
  • Hi Jared,

    Any news about this hotfix? I am very interested.

    Many thanks in advance.

    Best regards.

    Mehdi

    Tuesday, February 14, 2017 8:23 AM
  • Hi Mehdi,

    All I know is that the hot fix did resolve our issue and the problem has not resurfaced. As far as the status of the KB hotfix, I'm not sure. I haven't heard anything additional from Microsoft since they tested it on my server. You'll probably need to contact MS support and reference the KB I mentioned above to see if you can get it.

    Jared

    Tuesday, February 14, 2017 2:06 PM
  • Can Share ?
    Monday, February 20, 2017 6:37 PM
  • Hi Jared,

    I finally opened a ticket to MS support and they gave me quickly the same KB, and it's work fine.

    Thank you.

    Mehdi

    Tuesday, February 21, 2017 1:33 PM
  • Hi 2Dman,

    You will need to send Microsoft a support ticket to get the KB hot fix until it is released as a general update. Microsoft does not allow sharing the download publicly.

    Jared

    Tuesday, February 21, 2017 1:59 PM
  • Just had the same problem here. Paid microsoft for single-instance support, they installed the hotfix referenced above and refunded the charge for the support instance.
    Friday, April 28, 2017 10:15 AM
  • Hello together, i have the same issue but on windows 2012 essentials without r2. Does anybody know, if the paid microsoft support have a solution for the first essentials 2012 server?
    • Edited by isi-bizi Wednesday, June 07, 2017 10:14 AM
    Wednesday, June 07, 2017 10:13 AM
  • I have seen this particular symptom for different reasons and causes.

    And Microsoft has released the Hotfixes according to the logs:

    C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-O365ProviderServiceConfig.log

    So please try to re-produce the issue and upload the logs mentioned above.

    Wednesday, June 07, 2017 11:10 AM
  • Yes, this issue affects the non-R2 version; that's the one I had fixed by product support.
    Wednesday, June 21, 2017 10:03 AM
  • Mariëtte,

    Any update regarding this problem on Windows Server Essentials 2016?

    Just installed it and i am getting the same problem.

    Tuesday, November 07, 2017 10:48 PM
  • I have been dealing with this on 2 other 2012R2 servers and have't had any luck. Why can't MS just release the patch? There are many others having this same issue and no resolution. I saw the response from MS was to install 2012R2 or 2016. But I am having this issue on a 2012R2 server and I heard 2016 has the same issue. Come on is this a joke?
    Monday, December 04, 2017 6:17 AM
  • See if this is the issue nailing you

    PROBLEM: Unable to integrate Dashboard with 0365

     

    RESOLUTION: 

     

    Under C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log :

     

    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

     

    >> Launch the registry editor console and took backup of the following key:

     

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity\O365Integration

     

    >>Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity\O365Integration\Settings

     

    >> Delete the BecEndPointAddress key

     

    Tried integrating with 0365

    Successful.

     

    >>Needs to manually connect all the Dashboard users to their respective Office 365 mailboxes

    Tuesday, December 05, 2017 9:05 PM