none
Windows Server 2012 Essentials R2 and Office 365 Integration

    Question

  • Hi


    I'm in the process of moving a client from SBS Server 2003 to 2012 Essentials R2 and as part of this I am setting up a POC for Office 365 so that they can test before purchasing.  I have generated a trial from our Partner portal and am currently trying to setup the Office 365 integration with this trial with no success.  The error message that I get is, There was an issue configuring the integration, make sure the computer is connected to the internet and then try again.


    The server is connected to the internet and I have validated that I can login with the tenant credentials to confirm that these are correct.  I haven't created any users within the tenant and the only user on the server is the Administrator account.  As this is a POC I haven't added their internet domain to the Office 365 tenant but I don't believe that this is required by default.

    I have tried the suggestions listed in other threads related to this issue with no success, I have also applied the hotfix that was recently released that appears to address these issues.  Any help on this would be appreciated.

    I have checked the log files and the following errors are in them:

    ConfigWizard

    [10740] 150519.195536.3531: General: Initializing...C:\Windows\System32\Essentials\ConfigWizard.exe
    [4632] 150519.195536.9937: PfBinding: Information: [0] : Adding service dns identity [XXXX] in proxy endpoint.
    [5684] 150519.195537.2593: PfBinding: Information: [0] : Adding service dns identity [XXXX] in proxy endpoint.
    [16304] 150519.195537.3999: PfBinding: Information: [0] : Adding service dns identity [XXXX] in proxy endpoint.
    [2344] 150519.195630.0888: GettingStartedWizard: Start O365 service
    [2344] 150519.195630.1044: WssgCommon: Information: [0] : WseEmailSvc is already in the desired state.
    [13756] 150519.195633.8701: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [13756] 150519.195633.8701: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [7276] 150519.195633.8701: GettingStartedWizard: Stop O365 service
    [7276] 150519.195634.2294: GettingStartedWizard: Activate O365 with Error Unexpected returned.
    [7276] 150519.195634.2294: GettingStartedWizard: Activate O365 with Error Unexpected returned.
    [7276] 150519.195634.2294: GettingStartedWizard: error page exception : O365ConfigurationFault = Unexpected
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Failed to activate password sync
       at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivatePasswordSync()
       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)
    [10740] 150519.195634.2451: GettingStartedWizard: Stop O365 service
    [10740] 150519.195752.3608: GettingStartedWizard: RebootOrRestartDashboardIfNecessary with restart flag is False


    SharedServiceHost-EmailProviderServiceConfig


    [8008] 150519.195631.8232: 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).
    [8008] 150519.195631.8232: UpdateMSOSecurityGroupDataTask: Failed to run UpdateMSOSecurityGroupDataTask: O365ConfigurationFault = Communication
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Connect to BECWS failed.


    [16104] 150519.195633.3232: DescriptionMapFromResource: failed to get ServiceDisplayName for INTUNE_O365
    [16104] 150519.195633.3388: DescriptionMapFromResource: failed to get ServiceDisplayName for OFFICE_BUSINESS
    [16104] 150519.195633.3388: SkusFromXML: failed to get SkuDisplayInfo for OFFICE_BUSINESS
    [16104] 150519.195633.3388: DescriptionMapFromResource: failed to get ServiceDisplayName for YAMMER_ENTERPRISE
    [16104] 150519.195633.3388: SkusFromXML: failed to get SkuDisplayInfo for YAMMER_ENTERPRISE
    [16104] 150519.195633.3388: DescriptionMapFromResource: failed to get ServiceDisplayName for EXCHANGE_S_STANDARD
    [16104] 150519.195633.3388: SkusFromXML: failed to get SkuDisplayInfo for MCOSTANDARD
    [1972] 150519.195633.4013: PasswordSyncManagementProvider(IPasswordSyncCallback): Activate:8e346f16-bace-40a3-b4e8-1780491d335a starts
    [1972] 150519.195633.7920: PasswordSyncManagementProvider(IPasswordSyncCallback): Activate:8e346f16-bace-40a3-b4e8-1780491d335a failed due to PwdSyncConfigurationFault = Unexpected


    [16104] 150519.195633.8232: O365ManagementCore: Failed to activate password sync: Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeException: Failed to invoke <Activate>b__11 ---> Microsoft.WindowsServerSolutions.PasswordSync.PwdSyncConfigurationException: Unable to extract the PCNS schema LDIF file.


    [16104] 150519.195633.8232: O365ManagementProvider(IO365Callback): ActivateAAD:58bc5cf4-ea2d-4f6e-ac8c-b1c955ada23d failed due to O365ConfigurationFault = Unexpected
    Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Failed to activate password sync


    Wednesday, May 20, 2015 9:11 AM

Answers

  • Ok, so the PCNS file was the correct fix for this issue.

    The steps are you navigate to the location GHUber7 mentioned, rename the old .ZIP file and the PCNS folder (do NOT delete them). The place the new .ZIP file into the same directory, unzip it then try to re-run the integration wizard with the FIRST Office 365 account that you created. I was trying it with a second account, that had Global Admin rights, but not Tenant Admin rights.

    Link to PCNS.zip

    I have uploaded the PCNS.zip file that the MS Support rep gave to me. Hop


    Friday, May 22, 2015 8:31 PM
  • I ended up resolving this issue by disabling IPV6 on my LAN adapter on the Essentials 2012 R2 Server.. it connected quickly after that.

    Jason

    Sunday, May 31, 2015 2:27 PM

All replies

  • I believe this may be a known issue with a corrupt PCNS.zip file.

    Do you have access to another Essentials server to copy one from?


    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+

    Thursday, May 21, 2015 11:34 AM
    Moderator
  • I've been working through this same issue. Brand new Server 2012 R2 Essentials install, but the Office 365 integration fails when I input our Admin credentials for Exchange Online. I've searched high and low and can not find any sort of answer.

    Here's my log file: http://pastebin.com/g54LR57e

    Anyone have any ideas?

    Thursday, May 21, 2015 3:48 PM
  • For anyone interested, I'm working with Dell on this issue, as well as the Server 2012 team. As soon as I get a resolution, I will post it for you. This has been a maddening issue to troubleshoot.

    What's interesting though, is that the wizard will tell me if I input the incorrect password for the O365 admin account, or if I use the @onmicrosoft domain instead. Weird, right? So the connection is there...but something on the server (Password Synchronization, I guess?) is not allowing the integration to complete.

    Friday, May 22, 2015 1:11 PM
  • We had one of these on the call last month and they said they were using the wrong account.  I have no clue how or what is the correct account but if you can think of any others you might try them

    Grey

    Friday, May 22, 2015 1:23 PM
    Moderator
  • Grey,

    Thanks for the tip. FWIW, I'm using our global administrator account for Office 365. When I use our "username@domain.onmicrosoft.com" username, it kicks back an error and says that is the incorrect account (rightly so since our domain name is the primary account there).


    • Edited by phefner Friday, May 22, 2015 2:11 PM clarification
    Friday, May 22, 2015 2:11 PM
  • Exact same problem here.  Brand new Server 2012 R2 Essentials install on Dell T320.

    I have tried three completely different Office 365 account/configurations and the error is exactly the same.

    Friday, May 22, 2015 2:27 PM
  • Ditto to above

    Dell T320 Server 2012 R2

    Same errors


    PS C:\Windows\system32> Enable-O365Integration
    cmdlet Enable-O365Integration at command pipeline position 1
    Supply values for the following parameters:
    O365AccountUPN: xxxxxx@xxxxxxxxx.com.au
    Password: ***********
    Enable-O365Integration : Failed to activate password sync
    At line:1 char:1
    + Enable-O365Integration
    + ~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Enable-O365Integration], O365ConfigureException
        + FullyQualifiedErrorId : InvalidInvoke,Microsoft.WindowsServerSolutions.O365Integration.EnableO365IntegrationPSCm

    I tried a Trial account and I setup a new account.

    One interesting thing is that SFC comes up with errors. I am going to trouble shoot these now.

    Also since we are all Dell people. Can I assume we all did the latest Dell driver updates? I used Dell command update 2!

    Friday, May 22, 2015 2:39 PM
  • Hi Robert,

    This solution worked for me. For others having this issue, I navigated to "C:\Program Files\Windows Server\Bin" on a working Essentials server and copied the "PCNS.zip" file from there to the Essentials sever experiencing the issue. After doing so, I was immediately able to activate the Office 365 Integration.

    Thanks,

    Greg

    • Proposed as answer by Nexxus Cloud Friday, May 22, 2015 9:10 PM
    Friday, May 22, 2015 4:03 PM
  • Ok, so the PCNS file was the correct fix for this issue.

    The steps are you navigate to the location GHUber7 mentioned, rename the old .ZIP file and the PCNS folder (do NOT delete them). The place the new .ZIP file into the same directory, unzip it then try to re-run the integration wizard with the FIRST Office 365 account that you created. I was trying it with a second account, that had Global Admin rights, but not Tenant Admin rights.

    Link to PCNS.zip

    I have uploaded the PCNS.zip file that the MS Support rep gave to me. Hop


    Friday, May 22, 2015 8:31 PM
  • So does the PCNS file get messed up if you use the wrong account?

    Grey

    Friday, May 22, 2015 9:03 PM
    Moderator
  • I just ran across this while configuring our 2012 Essentials R2 server with Office 365 and the file linked here downloaded properly and worked per the instructions. I also virus scanned the file before using it and it's all good from my end. Thanks for the fix, saved me calling tech support and waiting for an engineer.
    Friday, May 22, 2015 9:11 PM
  • I honestly don't know. Although I did use my first O365 account during the initial set up, and it still failed. I do know that after we replaced the PCNS folder/.ZIP file, that when I used a second Global Administrator account, the integration failed, but then I used the first account, and it went through. I guess the first O365 account you create is the main Tenant Admin, at least that's how the MS engineer explained it.

    I think the main issue is that the PCNS file is corrupt, possibly a bad image from the Dell warehouse. Either way, using the one in the link above, should resolve the issue. Just rename the old ones, copy the new one to the same location, extract it to the same location, then re-run the integration wizard on the dashboard.

    Friday, May 22, 2015 9:13 PM
  • You're very welcome! I'm glad I could help! I want to save people from the trouble I had to go through to get it fixed.
    Friday, May 22, 2015 9:21 PM
  • ARGH! Thank you Greg. I'd been bashing my head on and off for days on this one.
    Friday, May 22, 2015 9:38 PM
  • Yep worked for me also. 

    Thanks

    Saturday, May 23, 2015 12:36 AM
  • Thanks a lot! I search for many hours and tried many different things. This one finally solved the issue!
    Sunday, May 24, 2015 3:27 PM
  • tryed that file but that enable Microsoft Azure Active Directory will have Office 365 enable!!

    What is wrong

    Monday, May 25, 2015 12:38 PM
  • tryed that file but that enable Microsoft Azure Active Directory will have Office 365 enable!!

    What is wrong

    I'm not quite sure I understand. Are you saying that this enabled the Azure Active Directory service, but you want Office 365 enabled? Or that you want the Azure Active Directory service to work?
    Tuesday, May 26, 2015 2:31 PM
  • I'm having the same issue, Getting the msg

    "There was an issue configuring the integration.

    Make sure that the computer is connected to the internet, and then try again."

    This is on a Windows Server Essentials 2012 R2, on the initial Office 365 integration .

    I did the search for the PCNS.zip file and didn't find anything... Also looked in "C:\Program Files\Windows Server\Bin" and didn't see it...

    Any guidance appreciated,

    Jason

    Thursday, May 28, 2015 5:12 PM
  • If it is not there then you need to copy that file to that location and the wizard should work
    Friday, May 29, 2015 2:04 AM
  • what is the exact path?  should there PCNS directory in addition to the  "C:\Program Files\Windows Server\Bin" or is the PCNS.zip just in the BIN directory by itself?
    Friday, May 29, 2015 10:36 AM
  • Windows Server 2012 Essentials/R2 Essentials may fail to integrate with Microsoft Office 365 - The Windows Server Essentials and Small Business Server Blog - Site Home - TechNet Blogs:
    http://blogs.technet.com/b/sbs/archive/2015/05/29/windows-server-2012-essentials-r2-essentials-may-fail-to-integrate-with-microsoft-office-365.aspx

    • Proposed as answer by BhargavShukla Tuesday, June 9, 2015 4:30 AM
    Friday, May 29, 2015 5:01 PM
  • what is the exact path?  should there PCNS directory in addition to the  "C:\Program Files\Windows Server\Bin" or is the PCNS.zip just in the BIN directory by itself?
    Follow the link that Susan Bradley posted. It has the MSI file and ZIP files you need to do the job.
    Friday, May 29, 2015 8:56 PM
  • I went through the exact steps outlined in the link Susan Bradley posted, and no luck..  I also posted under that blog... 
    Saturday, May 30, 2015 12:09 PM
  • JC you have EXACTLY the same error messages?

    What's in your log files?

    Saturday, May 30, 2015 1:41 PM
  • I just made another attempt.. here is what I have in my log files..

    Seems as I'm getting a timeout, I've highlighted what I got from the log..  if anyone has any suggestions please let me know..

    Jason

    ConfigWizard

    --------------------------------------------------------
    [6836] 150531.073224.9332: General: Initializing...C:\Windows\System32\Essentials\ConfigWizard.exe
    [10504] 150531.073225.1981: PfBinding: Information: [0] : Adding service dns identity [] in proxy endpoint.
    [8012] 150531.073227.2719: PfBinding: Information: [0] : Adding service dns identity [] in proxy endpoint.
    [8012] 150531.073227.3500: PfBinding: Information: [0] : Adding service dns identity [] in proxy endpoint.
    [16544] 150531.073251.1380: GettingStartedWizard: Start O365 service
    [16544] 150531.073251.1380: WssgCommon: Information: [0] : WseEmailSvc is already in the desired state.
    [3824] 150531.073333.9842: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [3824] 150531.073333.9842: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
    [16544] 150531.073334.0006: GettingStartedWizard: Stop O365 service
    [16544] 150531.073334.1246: GettingStartedWizard: Activate O365 with Error Communication returned.
    [16544] 150531.073334.1246: GettingStartedWizard: Activate O365 with Error Communication returned.
    [16544] 150531.073334.1246: GettingStartedWizard: error page exception : 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.<ListUsers>b__18(ListUsersRequest 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.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)
    [6836] 150531.073334.1401: OIMUtils: GetO365ConfigurationErrorMessage for Communication
    [6836] 150531.073334.1401: GettingStartedWizard: Stop O365 service
    [6836] 150531.073404.0936: GettingStartedWizard: RebootOrRestartDashboardIfNecessary with restart flag is False

    SharedServiceHost-EmailProviderServiceConfig

    ---------------------------------------------------------
    [17116] 150531.073251.1850: SharedServiceHost: Information: [0] : ==========================================================
    [17116] 150531.073251.2004: SharedServiceHost: Information: [0] : "C:\Windows\System32\Essentials\SharedServiceHost.exe" C:\Windows\System32\Essentials\EmailProviderServiceConfig
    [17116] 150531.073251.2004: SharedServiceHost: Information: [0] : Loading service information from "C:\Windows\System32\Essentials\EmailProviderServiceConfig".
    [140] 150531.073251.2316: WinSrvEmailProviderSvc: Microsoft.WindowsServerSolutions.O365Integration.O365ManagementService, Wssg.O365Provider, Version=6.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 is created as hosted email service provider
    [140] 150531.073251.2316: WinSrvEmailProviderSvc: Microsoft.WindowsServerSolutions.PasswordSync.PwdSyncManagementService, Wssg.PasswordSyncProvider, Version=6.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 is created as hosted email service provider
    [140] 150531.073252.4628: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StartTasks called
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: Starting UpdateDomainTask
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: Starting UpdateSharepointAddressTask
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: Starting UpdateO365IntegrationDataTask
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: Starting UpdateCachedSkuInfoTask
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: Starting UpdateMSOSecurityGroupDataTask
    [140] 150531.073252.4628: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
    [140] 150531.073252.4785: PasswordSyncManagementCoreFactory: Creating PasswordSyncManagementCore instances
    [140] 150531.073252.5095: UpdateMSOSecurityGroupDataTask: Start UpdateMSOSecurityGroupDataTask
    [7076] 150531.073252.5719: MSOSecurityGroupManager: Sync queue is empty.
    [10796] 150531.073252.6186: O365ManagementProvider(IO365Callback): ActivateAAD:91189971-2198-4ecc-896b-cd6c4004d9a3 starts
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StopTasks called
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: Stopping UpdateDomainTask
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: Stopping UpdateSharepointAddressTask
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: Stopping UpdateO365IntegrationDataTask
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: Stopping UpdateCachedSkuInfoTask
    [10796] 150531.073252.6186: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [140] 150531.073252.6186: MSOSecurityGroupManager: Full sync task will start in 00:10:00 minutes.
    [14376] 150531.073254.2551: PfBinding: Information: [0] : Adding service dns identity [] in proxy endpoint.
    [140] 150531.073312.6904: BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.TimeoutException: The request channel timed out attempting to send after 00:00:20. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'https://provisioningapi.microsoftonline.com/provisioningwebservice.svc' has exceeded the allotted timeout of 00:00:19.9850000. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
       at System.Net.HttpWebRequest.GetRequestStream()
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       --- End of inner exception stack trace ---
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       --- End of inner exception stack trace ---

    Server stack trace:
       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.MsolConnect(Request request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.Connect()
    [140] 150531.073312.6904: 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().
    [140] 150531.073312.6904: UpdateMSOSecurityGroupDataTask: End UpdateMSOSecurityGroupDataTask
    [10796] 150531.073312.6904: O365Integration:BackgroundTaskBase: Stopping UpdateMSOSecurityGroupDataTask
    [10796] 150531.073312.6904: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [10796] 150531.073333.9687: BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.TimeoutException: The request channel timed out attempting to send after 00:00:20. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'https://provisioningapi.microsoftonline.com/provisioningwebservice.svc' has exceeded the allotted timeout of 00:00:20. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
       at System.Net.HttpWebRequest.GetRequestStream()
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       --- End of inner exception stack trace ---
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       --- End of inner exception stack trace ---

    Server stack trace:
       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.MsolConnect(Request request)
       at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.Connect()
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StartTasks called
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: Starting UpdateDomainTask
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: Starting UpdateSharepointAddressTask
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: Starting UpdateO365IntegrationDataTask
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: Starting UpdateCachedSkuInfoTask
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: Starting UpdateMSOSecurityGroupDataTask
    [10796] 150531.073333.9687: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
    [10796] 150531.073333.9687: O365ManagementProvider(IO365Callback): ActivateAAD:91189971-2198-4ecc-896b-cd6c4004d9a3 failed due to 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.<ListUsers>b__18(ListUsersRequest 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.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)
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StopTasks called
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: Stopping UpdateDomainTask
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: Stopping UpdateSharepointAddressTask
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: Stopping UpdateO365IntegrationDataTask
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: Stopping UpdateCachedSkuInfoTask
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: Stopping UpdateMSOSecurityGroupDataTask
    [12740] 150531.073334.0006: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [12740] 150531.073334.0622: O365ManagementProvider(IO365Callback): Channel_Closed called
    [12740] 150531.073334.0622: O365ManagementProvider(IO365Callback): Provider disconnected
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskManager: BackgroundTaskManager.Dispose called
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Stopping UpdateDomainTask
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Dispose for UpdateDomainTask called
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Stopping UpdateSharepointAddressTask
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Dispose for UpdateSharepointAddressTask called
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Stopping UpdateO365IntegrationDataTask
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Dispose for UpdateO365IntegrationDataTask called
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Stopping UpdateCachedSkuInfoTask
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Dispose for UpdateCachedSkuInfoTask called
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Stopping UpdateMSOSecurityGroupDataTask
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
    [17116] 150531.073334.1558: O365Integration:BackgroundTaskBase: Dispose for UpdateMSOSecurityGroupDataTask called
    [7076] 150531.073334.1558: MSOSecurityGroupManager: MSO Security Group Sync Worker Thread Stopped.
    [17116] 150531.073334.1713: SharedServiceHost: Information: [0] : Exiting with code 0
    [17116] 150531.073334.1713: SharedServiceHost: Information: [0] : ==========================================================

    I also tried via PS and got a similar result

    PS C:\Windows\system32> Enable-O365Integration

    cmdlet Enable-O365Integration at command pipeline position 1
    Supply values for the following parameters:
    O365AccountUPN: *****@*****.***
    Password: *****
    Enable-O365Integration : Connect to BECWS failed.
    At line:1 char:1
    + Enable-O365Integration
    + ~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Enable-O365Integration], O365ConfigureException
        + FullyQualifiedErrorId : InvalidInvoke,Microsoft.WindowsServerSolutions.O365Integration.EnableO365IntegrationPSCm

     

    • Edited by jcwhoffman Sunday, May 31, 2015 12:08 PM add addtl
    Sunday, May 31, 2015 11:56 AM
  • I ended up resolving this issue by disabling IPV6 on my LAN adapter on the Essentials 2012 R2 Server.. it connected quickly after that.

    Jason

    Sunday, May 31, 2015 2:27 PM
  • For me, it wasn't that it was "corrupt".  When the system creates the PCNS folder, it mistakenly puts in extra parent folders from the ZIP file.  All you have to do is go into the folder ...\PCNS\Password Change Notification Service\x64\, copy the contents, and paste it into the ...\PCNS\ folder.  Or you can grab it out of your existing PCNS.ZIP file.  Completely ridiculous problem from MS.
    Sunday, June 7, 2015 5:49 AM
  • Thanks chap, on site over the weekend doing an install and this saved me.

    Geoff

    Saturday, June 13, 2015 12:38 PM
  • While GHUber7 gave me the location it was useless without your file down load, thanks.

    Geoff

    Saturday, June 13, 2015 12:39 PM