The Windows Server Essentials Service cannot synchronize the user password to the online identity repository

Jesse Flintoff 236

Hi there.

Recently. I have the below error coming up on multiple 2016 essential servers when doing password changes via the Essentials Dashboards.

I can confirm that passwords are not syncing to 365.

I have tired disabling 365 integration. Then re enabling. Same issue.

Anyone else seen this issue?

STM 1 Reputation point

2021-07-23T08:32:27.86+00:00

... any news?
Franck Gravel 1 Reputation point

2021-07-26T21:36:36.637+00:00

Same here and My users are freaking out! please keep me updated
Manson DeGraw 1 Reputation point

2021-07-29T17:21:15.057+00:00

We are also having this same issue with all clients using Server 2016 Essentials 2016 standard with Essentials Role installed. Password sync to Office 365 stopped working recently. Have not checked clients with Server 2012 R2 Essentials but will check them. I seems very odd that creating a new user with sync to Office 365 and create the password correctly In process of opening a MS ticket.

Manson
Shawn P. Lemay 21 Reputation points

2021-07-31T17:48:50.98+00:00

So glad I found this thread, I was just about to open a case to Microsoft, as I have 3 sites now failing with this error. Hopefully, they get this fixed soon!
Phillip Fielding 1 Reputation point

2021-08-06T09:22:11.563+00:00

Like others, ive now got 4 different customers experiencing this issue.
this is the only thread ive managed to find with any information.
has there been any update on this?
MAC 1 Reputation point

2021-08-06T20:17:26.877+00:00

I am also experiencing this issue. Any update?
Zachary Sigamony 1 Reputation point

2021-09-27T17:53:04.68+00:00

I have a similar issue too with two of my clients on server 2016 essential
Zachary Sigamony 1 Reputation point

2021-09-27T17:53:13.49+00:00

I have a similar issue too with two of my clients on server 2016 essential
Ishtiaq 71 Reputation points

2021-10-08T14:00:25.907+00:00

Good news, Password synch is now working, although I've not yet heard it from Microsoft in response to our support ticket. Just tested on a couple of Client server and it works!
Lets hope its a permanent fix...

45 answers

joe mills 26 Reputation points

2021-09-14T15:20:40.807+00:00

You may want to investigate and try the following.... a good config file is also necessary if you are using any of the online services.

I have found a temporary "workaround" to quiet the Computer Monitoring alert. It is working successfully for me across all my servers. Unfortunately, I can't and won't guarantee success for everyone since I do NOT work for Microsoft and I don't have access to the same resources; so please PROCEED AT YOU OWN RISK! You fully assume all risk, responsibility, and liability with this workaround and it's installation. Please read and understand what this workaround does and PROCEED AT YOUR OWN RISK. I recommend you make sure you backup your server and data.

Some background........ Microsoft has created dozens and dozens of health definitions in Essentials that scan the server (and clients) for particular issues (such as firewall problems, disk space problems, server role configuration problems, etc., etc.). Within all of that, there’s actually a specific health definition that checks for updates to just the online services integration stuff in Essentials. The health definition runs every thirty minutes where it downloads the language-specific config file. The config file contains the version information for the online services integration (which hasn’t actually changed from version 1.0.0.0 in all the years that 2016 Essentials has been out), and that’s what’s checked in order to see if an update needs to be downloaded from Microsoft. Since the config file on the server is now corrupt due to a broken or missing link on the Microsoft backend, Essentials falls over when it attempts to read the version information from it and then it tosses up the “Computer Monitoring Error” health alert.

The Workaround... It's actually quite simple and can be easily reversed if Microsoft decides to fix the broken backend.

Use the Essentials "Restore Files or Folder" (NOT A Full Drive) wizard to REPLACE the "OnlineServicesConfigFile" contained within: ProgramData/Microsoft/Windows Server/Data/Cloud. You MUST use a backup from prior to the Microsoft failure on or about August 31, 2021. (I successfully restored my config file using backup from August 29, 2021.)

Quickly (before the next Health Alert Evaluation runs and overwrites the file) right click the config file, select properties and set the Attribute to READ ONLY. (This should prevent the config file from being overwritten with corrupted information again due to the missing or broken backend.)

The Computer Monitoring Error should clear when the next Health Assessment Runs, which is usually every 30 minutes.
Was this answer helpful?
Shawn P. Lemay 21 Reputation points

2021-09-15T15:18:41.943+00:00

@joe mills - The problem here is not the alert and being annoyed by it, it's that the Essential Server IS NOT syncing with the cloud any longer. So disabling the alert does not solve the problem.

Huw Pendry 51 Reputation points

2021-09-23T09:33:08.29+00:00

ok, so my Essentials server is just for development use and as it's not critical I only do limited backups, and don't have a copy of the file from before the corruption - doh!

Anyone have a good copy of OnlineServicesConfigFile-GB.xml they can post?

Huw Pendry 51 Reputation points

2021-10-08T07:51:48.437+00:00

aha - the file has magically restored itself. Presumably Microsoft has fixed the failing fwlink.
Made a backup copy just in case!

Linus Haake 31 Reputation points

2021-10-08T08:44:58.487+00:00

Issue seems to be resolved, I just changed the password of one of the test accounts and could log on with the new password in the cloud.

Ishtiaq 71 Reputation points

2021-10-08T14:01:51.523+00:00

same here
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Linus Haake 31 Reputation points

2021-09-15T15:43:12.873+00:00

Seems like it's taking just a bit more time... but only a bit!
I sometimes wonder how serious people take this...

*Dear Mr. Haake,
Thank you for your patience during the processing time.
You spoke to a colleague of mine on Friday and I just wanted to tell you briefly that I still expect feedback from our product group.
The issue still seems to be in progress and there is no official date until when it will be fixed.
Nevertheless, I write to the product group again, hopefully I will receive an answer.
Kind regards
Dragoș I****
Team Manager
Microsoft 365
For Microsoft Customer Service & Support
Working Hours: M-F 9:00 - 18:00 (GMT+2)
Feedback: [email protected]*
Was this answer helpful?
Shawn P. Lemay 21 Reputation points

2021-09-15T16:00:58.76+00:00

@Linus Haake - email them back and ask them if there would be any benefit if we all opened cases, to get this escalated and given more resources any faster???
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
joe mills 26 Reputation points

2021-09-15T15:50:36.65+00:00

The workaround does NOT disable the alerts. As I understand the problem, the server is checking to see if there have been any changes to the version information for the online services integrations stuff. To my knowledge the version information has NOT changed since 1.0.0.0. However, because their is a problem with the response from the Microsoft backend, the server thinks there has been a change and then overwrites the file with blanks or gibberish which then causes the other failures and alerts. Restoring the files and temporarily preventing them from being overwritten should restore the online services integration.
Was this answer helpful?
Shawn P. Lemay 21 Reputation points

2021-09-15T16:13:01.45+00:00

@joe mills BUT, does it actually fix the sync? Meaning a user changes their password on the server, does it push that change up to the cloud? If not, this "patch" really doesn't help us out much other than disables the alert. If it does, then awesome!!! I'll give it a test...
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
joe mills 26 Reputation points

2021-09-15T16:35:35.147+00:00

Unfortunately, I am not using the online O365 services so I can’t for sure that it will fix your problem. However, the config files contain fwlinks to O365, Azure, Intune, etc…. and I suspect your problem is because they are missing. Have you inspected the config files on your server? Are they intact or corrupt?
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Linus Haake 31 Reputation points

2021-09-15T18:00:40.68+00:00

I've tested it here, the content did not seem to be trash, at least from what I could see.
However, I've replaced the file from the backup (31st of May, since some folks meant that it already happened in June 21) and changed the password of a test-user, but it still does not seem to be updated for the related object in the tenant.
I will give it a while, but MS told me that the issue is not with the local server, but with some changes on Microsoft Graph (Azure).
Was this answer helpful?
Linus Haake 31 Reputation points

2021-09-15T19:57:34.357+00:00

Did not help at all, neither the issue is resolved by workaround, nor the error messages did not re-appear again after I've deleted them.
Trying to logon with the password changed before does also not work.

joe mills 26 Reputation points

2021-09-16T15:36:34.713+00:00

I am very sorry to hear that the workaround is not working in your particular situation. I find it odd that your config files are NOT being corrupted by the MS backend problem. I am curious if your Cloud folder also contains a "CloudServiceEnvironment-XX.xml" file and if it is not corrupt.

Linus Haake 31 Reputation points

2021-09-16T15:47:18.593+00:00

It exists but does not look corrupt at all.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

The Windows Server Essentials Service cannot synchronize the user password to the online identity repository

45 answers

Your answer