I am trying to integrate our Office 365 with a newly installed instance of Windows Server Essentials 2012 R2.

When i run the integration wizard in the Windows server essentials dashboard and supply my username and password for my Office 365 admin account, the wizard runs for a very long time, and returns "An unknown error occurred. Make sure that the computer is connected to the internet, and the try again. If you continue to to experience, restart the server and then try again".

I have tried to restart the server several times and reinstalling the server from scratch, but the error still appears.

When i try to integrate the server with another, separate trial Office 365 tenant, I am able to integrate, but when I try to integrate with this Office 365 tenant, the wizard always returns this error. This leads me to think that there is a problem with this specific Office 365 tenant. 

We need this integration to work, and hope that you will be able to help us fix this error and get the integration with our server to work.

Hi,

Regarding the current issue, since its an Office 365 integration issue, I suggest youd better ask in the Office 365 forum. We will get a better assistance there. Thanks for your understanding.

http://community.office365.com/en-us/forums/default.aspx

Best Regards,

Andy Qi

Are there any major differences between the account that works and the one that doesn't?

Are you able to check the OIM logs in \programdata\microsoft\windows server\logs\ ?

I contacted Office 365 support regarding this issue, and they directed me to Microsoft professional support (https://support.microsoft.com/getsupport/hostpage.aspx?tenant=ClassicCommercial&locale=en-us&supportregion=en-us&ln=en-us&pesid=14203&sd=gn&oaspworkflow=start_1.0.0.0&wf=0&ccsid=635281359173124226).

Thought i'd try to see if anyone here could help before i submitted a ticket to them.

No, the only significant difference is that the trial account (that works) doesn't have as much data (accounts, domains, etc.). All test accounts here are E3-accounts.

The one that don't work has about 25 accounts, and I have migrated our onsite Exchange server and Sharepoint libraries to it. The accounts are a mix of E1 for nonprofits and E3 for nonprofits-accounts, based on the individual user's need for software.

This is what the latest entries in the OIMGettingStartedWizard.log says:

[5420] 140217.133612.9696: General: Initializing...C:\Windows\System32\Essentials\OIMGettingStartedWizard.exe
[6252] 140217.133613.7352: PfBinding: Information: [0] : Adding service dns identity [SERVER] in proxy endpoint.
[7940] 140217.133614.0165: PfBinding: Information: [0] : Adding service dns identity [SERVER] in proxy endpoint.
[3588] 140217.133614.2196: PfBinding: Information: [0] : Adding service dns identity [SERVER] in proxy endpoint.
[6680] 140217.133635.2825: GettingStartedWizard: Start O365 service
[6680] 140217.133635.3294: WssgCommon: Information: [0] : WseEmailSvc is already in the desired state.
[4268] 140217.134136.4603: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
[4268] 140217.134136.4603: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
[8156] 140217.134136.4759: GettingStartedWizard: error page exception : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeException: Failed to invoke <ActivateAAD>b__c ---> System.TimeoutException: ActivateAAD:0ea995af-7596-4fa6-aa82-36cfcef1dfa0 gets timeout.
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ObjectModelBaseExtended`1.SyncWrapper[T](Action`1 act)
   at Microsoft.WindowsServerSolutions.O365Integration.OIMWizards.GettingStartedWizard.<>c__DisplayClass8.<BeginStartO365Service>b__5(O365Manager o365Man)
   at Microsoft.WindowsServerSolutions.O365Integration.OIMWizards.GettingStartedWizard.<>c__DisplayClasse.<BeginConfigure>b__d(Object state)
[5420] 140217.134149.4606: GettingStartedWizard: RebootOrRestartDashboardIfNecessary with restart flag is False

Windows Server Office 365 Integration Service fails
http://jaytongarnett.blogspot.com/2013/03/windows-server-office-365-integration.html   Is the Password Synchronization Service enabled and started.  (Though I'm still not sure why one O365 account would work and the would not).  
--
Merv Porter
=========================

And can you post up the OIM logs please?

https://msmvps.com/blogs/bradley/archive/2013/04/16/key-windows-2012-essentials-log-files.aspx

I think we'll need more than just a sn

"The one that don't work has about 25 accounts, and I have migrated our onsite Exchange server and Sharepoint libraries to it. "

SharePoint.  Is that English language?

I've posted the entire log here: http://1drv.ms/1cSrGut

The standard language of our Sharepoint Online instance is Norwegian.

I think that may prove to be the issue.

Why don't we get this in front of the product group.  Mariussa can you email me your phone number so I can get a free support case set up for you?  email susan-at-msmvps.com (change the -at- to @)

Do you know why that may be the issue?

We're guessing based on the fact that you can itegrate it with an account with no prepopulated data but can't with one that does.  Like I said, how about we go for getting a better root cause answer by a free support case?

Thanks. I've sent you an email, but i've already submitted the case to Microsoft support. They have not been able to solve it yet.

Microsoft support is working on my case now. I will post here when I know more.

The bug is in Essentials.  Office 365 folks wouldn't be able to help. 

Symptom:

              Dashboard crashes if we enable O365 Add-ins

             

              Cause:

              SharePoint Libraries

              Issue occurs with an non-English O365 account which has
              been moved from Wave 14 to Wave 15
             

              If we try to integrate this account with the Server 2012
              R2 Essentials, due to SharePoint Libraries, the dashboard
              starts to crash.
             

             

              Earlier Workaround provided: Rename the
              SharePointLibraryTabPage.addin file, so that the
              SharePoint Libraries are not attempted to load.

             

              Resolution:

              In O365 Portal

              Under Team Site, Title for this website was empty causing
              the failure in loading SharePoint Libraries.

             

              Add some Title to the Site: In this case(Firm name)
             

             

              Dashboard is no longer crashes

             

              Additional Information:

              NA

Windows Server 2012 R2 Essentials dashboard crashes if SharePoint site title is empty:
http://support.microsoft.com/kb/2930172

Did you ever get a resolution?  I have a similar issue 

No, Microsoft was unable to solve the problem.

I have the same issue. This worked when running O365 Integration to a brand new trial account from Essentials 2012, but I just built out a clean install of Essentials 2012 R2, set up a different brand-new trial O365 account, and I get the exact same behavior as described above (Times out after a few minutes, recommends to restart computer).

I've used several trial accounts, and several re-installations of 2012 R2 Essentials (fully patched) and always the same behavior. I don't have any foreign language sharepoint sites; I'm really very interested if anyone has been able to get a clean install of 2012 R2 Essentials integrated with a trial of O365 lately?

---------------------------------------------------------
[4776] 140426.140815.0468: General: Initializing...C:\Windows\System32\Essentials\OIMGettingStartedWizard.exe
[7128] 140426.140815.8126: PfBinding: Information: [0] : Adding service dns identity [RIBO-DC1] in proxy endpoint.
[7136] 140426.140816.0939: PfBinding: Information: [0] : Adding service dns identity [RIBO-DC1] in proxy endpoint.
[7136] 140426.140816.2657: PfBinding: Information: [0] : Adding service dns identity [RIBO-DC1] in proxy endpoint.
[7116] 140426.140833.4126: GettingStartedWizard: Start O365 service
[7116] 140426.140833.4450: WssgCommon: Information: [0] : WseEmailSvc is already in the desired state.
[888] 140426.141334.9357: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
[888] 140426.141334.9357: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
[7128] 140426.141334.9357: GettingStartedWizard: Stop O365 service
[7128] 140426.141335.2482: GettingStartedWizard: error page exception : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeException: Failed to invoke <ActivateAAD>b__c ---> System.TimeoutException: ActivateAAD:536872b0-26fa-4b80-845e-910a4d26a994 gets timeout.
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ObjectModelBaseExtended`1.SyncWrapper[T](Action`1 act)
   at Microsoft.WindowsServerSolutions.O365Integration.OIMWizards.GettingStartedWizard.<>c__DisplayClass8.<BeginStartO365Service>b__5(O365Manager o365Man)
   at Microsoft.WindowsServerSolutions.O365Integration.OIMWizards.GettingStartedWizard.<>c__DisplayClasse.<BeginConfigure>b__d(Object state)
[4776] 140426.141335.2671: GettingStartedWizard: Stop O365 service

I'll open a support request with Microsoft at this point, but I felt compelled to reply here with a 'me too!'.

• Edited by Greg2468 Saturday, April 26, 2014 9:38 PM

Greg --  I have the exact same issue.  Fresh install of Essentials 2012 R2 and a brand new Office 365 trial account.

I happen to have a Essentials 2012 Install (non-R2), and it works fine from there, no timeout issue.  Seems to me that this must be an Essentials R2 issue.

Really interested if anyone comes up with a solution here.

Problem solved for me.

I'm just create a new bibliotheque test  on my SharePoint site on office 365.

And.... Integration with my Essential 2012 R2 , Go on.

I do not know if this is or if it is a windows update that has solved my problem. But now it works.
Good luck.
sorry for my bad English

After beating my head against the wall on this for an embarrassingly long time... I decided to call O365 support for a separate issue I was having with the sharepoint features of my trial account. I could resolve "O365rootname-public.sharepoint.com" just fine, but not "MyCustomDomainName-public.sharepoint.com".

The tech started walking through the DNS zone record configurations and I was quite annoyed thinking this would be a waste of time, but to my amazement (and I was almost speechless) after some tweaks and about 30 minutes for replication... it worked - fixed my sharepoint naming resolution issue AND the O365 integration issue. (Explains the 'timeout' from above... the integration wizard couldn't get to where it was trying to find (apparently a webservice on your appropriate sharepoint.com server that it's routing through DNS).

If this sounds like your issue; Try the following: (Please note: Your O365RootName is the *.onmicrosoft.com name they set you up with initially).

Ping "0365rootname.sharepoint.com" and grab the IP that comes back from that.
Log into your domain registrar to update DNS for your domain.
Delete the existing A record from the DNS Zone file and create a new one (Host=@ points to the IP that responds when you ping 0365rootname.sharepoint.com).
The second adjustment was to delete the WWW CName Alias.. and create a new one pointing to "O365rootname.sharepoint.com"
Give it an hour or two to replicate... and try again, should go through within seconds.
I'm so relieved... this was definitely obnoxious, but I'm pretty stoked with net result.

• Edited by Greg2468 Wednesday, April 30, 2014 11:48 PM
• Proposed as answer by Greg2468 Wednesday, April 30, 2014 11:51 PM

But I don't want to change where my www.domainname.com points to.

I just changed the IP address of  @ to point to the IP address of mydomain.sharepoint.com and was able to integrate Server 20102 R2 Essentials and Office 365.

Thank you so much!!!!

Hello,

I've recently had this problem and I'm posting my solution as it took me an age to  resolve:

After checking through the log files (C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log) I found the following:

Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: The remote server returned an error: (404) Not Found. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.WebClient.DownloadFile(Uri address, String fileName)
   at Microsoft.WindowsServerSolutions.O365Integration.SharePointManagementUtils.InstallCSOM()

I resolved the error by installing the 'SharePoint Server 2013 Client Components SDK' which contains the CSOM modules.  See here: http://www.microsoft.com/en-gb/download/details.aspx?id=35585

Once this had been installed the Integration wizard worked correctly.

• Proposed as answer by Jamie_Wilson546 11 hours 53 minutes ago

Hello,

I've recently had this problem and I'm posting my solution as it took me an age to  resolve:

After checking through the log files (C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log) I found the following:

Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: The remote server returned an error: (404) Not Found. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.WebClient.DownloadFile(Uri address, String fileName)
   at Microsoft.WindowsServerSolutions.O365Integration.SharePointManagementUtils.InstallCSOM()

I resolved the error by installing the 'SharePoint Server 2013 Client Components SDK' which contains the CSOM modules.  See here: http://www.microsoft.com/en-gb/download/details.aspx?id=35585

Once this had been installed the Integration wizard worked correctly.

• Proposed as answer by Jamie_Wilson546 Friday, April 24, 2015 7:09 PM

Working Perfectly, 

Thank you!

Thank you David,

Great fix, but why is it a bug in the first place, i have install 3 of these in the the last 5 weeks two went of with out a hitch but the last one had this issue, installing the above Components fixed the issue. Come on Microsoft fix these problems, so people are not spending so much time looking for solutions to issues that sholdn't be there in the first place.

Is there a resolution for this issue? I am having the exact same problem as Greg but I cannot find a resolution any where. My C:\ProgramData\Microsoft\Windows Server\Logs\OIMGettingStartedWizard.log shows the exact same results (except for the ActivateAAD GUID). As far as I can tell, I am not having any networking issues that would cause a timeout.

This solved my exact same issue as well. Thanks! Shame on Microsoft for not documenting this prerequisite.

I realize this is coming along quite late, but for us, we resolved the issue by replacing the PCNS.zip file and folder located under C:\Program Files\Windows Server\bin

Here is our thread with more info on it, if anyone is still having this issue.

https://social.technet.microsoft.com/Forums/exchange/en-US/dba06f4f-1011-4de3-946b-2a39718c2cc0/windows-server-2012-essentials-r2-and-office-365-integration?forum=winserveressentials

What worked for me was to (1) rename the existing PCNS folder to PCNSXXX, and the existing PCNS.zip file to PCNSXXX.zip, (2) download the PCNS.zip file that was provided in the link earlier in this thread and store it into the same folder c:\program files\windows server\bin, but do NOT try to unzip it, and (3) rerun the O365 Integration Wizard from the dashboard.

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

Are these all Dell preinstalled or any system?