Start a discussion

3006 views
11 replies

Server 2016 essentials - O365 Integration Error

Hello,

I am struggling to get this to work with one of my small customers. This is Server 2016 essentials, and is not Server 2012 R2, so I was wondering if you knew of any hiccups with integrating the online services? I am just trying to sync their O365 and Azure AD accounts with the essentials server.

So, I am getting this error now in the logs. I ended up reinstalling WSE 2016 all together. I can't seem to find the error in the SharedServiceHost-EmailProviderServiceConfig log anywhere online:

[5524] 170111.193636.7434: O365ManagementProvider(IO365Callback): QueryAllMSOSecurityGroups:61495a74-0e79-4715-9f7d-f4e37b6cbda1 failed due to O365ConfigurationFault = NotActivated Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Operation cannot be called if O365 is not activated on the box yet

When I got this error, I tried activating Office on the server, and associating it with the O365 global admin account.   Another thing I tried: I am able to add the Azure AD Powershell and run the MSOnline commands successfully. I thought I might try AD connect, but found that isn't supported in Server 2016 Essentials.  Has anyone seen this error before?

I will add that the business owner purchased these licenses about a month ago. They also use exchange online with these accounts.

Thanks, John

User User
Published 01/12/2017 13:36
Add Comment
Host

As of May 2018, there is another issue with Office 365 integration, read Start a discussion > Office 365 integration broken on Windows Server 2016 (Essentials Experience role)

replied 05/08/2018 15:32
Emil Khisamov

Hi John, did you get it resolved?

i'm having exactly same issue, with no luck fixing it.

replied 11/02/2017 03:50
User

I'll give that a try. Thank you for your time.

replied 01/12/2017 16:15
Mariette Knap
I would definitely try to enable the disabled users (set new password) and try to run the wizard again. If that does not work I would open a case. I have seen instances with multiple different subscriptions failing at integration.
replied 01/12/2017 16:09
User

Thanks Mariette,

So this business has exchange online licenses (6) as well as O365 business (4). There are also other users in the admin center that are unlicensed or blocked (old users). Do you think that would have anything to do with it?

It was just a thought. Thank you for all of your help. It is very much appreciated.

replied 01/12/2017 16:06
Mariette Knap

Hello John,

What I do not understand is this:

[8124] 170112.101616.7085: O365ManagementProvider(IO365Callback): QueryAllMailboxStatistics:d5651390-330f-409c-b685-52c262d888f2 failed due to O365ConfigurationFault = IncorrectCredential

Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: userName and password should not be empty

It looks like the wizard is querying the O365 mailboxes and found one without a Username and Password. Technically this could be possible but I have no idea how and why.

I would open a case with Office 365 support, to begin with, and if that does not work open a case at PSS. They will ask you for your credit card and charge you for it but when it is a bug they will refund also.

replied 01/12/2017 15:53
User

Attached is the log file. Thanks for looking at it!

replied 01/12/2017 15:35
Mariette Knap

OK, great. Can you do the following:

  1. Open Explorer on the server and type in the address bar %ProgramData% and hit enter,
  2. Rename the SharedServiceHost-EmailProviderServiceConfig.log to SharedServiceHost-EmailProviderServiceConfig.log.bak,
  3. Rerun the O365 integration wizard
  4. Go back to ProgramData and copy the SharedServiceHost-EmailProviderServiceConfig.log to your desktop and ZIP it.
  5. Attach the ZIP to your answer in this thread.

If you zip the contents of the logs they cannot be crawled by search engines.

replied 01/12/2017 15:09
User

Mariette,

Yes, I verified the server is up-to-date. Also, checked the option to "Give me updates for other Microsoft products when I update Windows."

replied 01/12/2017 14:48
Mariette Knap

Hello John, in 2012 R2 this issue was fixed with installing the latest cumulative updates. Is your server fully updated?

replied 01/12/2017 14:32
User

Good morning,

first of all sorry for my bad english. Thirtyfive years are gone as i learned it in school :-) This thread is quite old, but i think some users have still problems with integration of O365 to the Essentials dashboard.

I'm using a WSE 2016 for a couple of years as our DC. In the past the O365-Integration was working well. But when i enable the new security standards in my tenant (Azure Active Directory -> Properties -> Tenant properties -> Access management for Azure resources) the integration fails.

This is due to the MFA, which is part of the security standards. I think, the Essentials dashboard can't handle MFA. You can verify this via Powershell with "Enable-O365Integration". It doesn't work and you get a error message.

Few months ago i gave up and installed Azure AD Connect on a separate Server 2019 (member server of my AD). Now sync works very well. The AAD setup generates a new user in the tenant like "sync_server1_abcdefg@company.onmicrosoft.com". This user is member of the role "directorysynchronzationaccounts". I guess, that a member of this role doesn't need the MFA for access to the tenant.

I created a new account in my tenant and gave him membership to this a.m. role. When i use this account in the essentials dashboard the Azure AD integration works, but not the O365 integration. The user must have a "company.onmicrosoft.com" suffix. Otherwise it won't work. You can't give membership to the "directorysynchronzationaccounts"-role when creating this account, because you can't search for this role while creating the account. I guess the only way is to edit the AADConnect-Account, click on the role within these account and add the newly created account to this role.

I know...not really a solution, but perhaps my investigations will make the circle for searching for a solution a little bit smaller.

Best regards from Stuttgart, Germany

replied 07/29/2020 06:10
Last Activity 07/29/2020 06:10