Forum Discussion
m_krone
Oct 15, 2019Brass Contributor
Sync cannot be initialized 0x80190194
I have one device which cannot be synced since 2 month. I am getting the message: Sync cannot be initialized 0x80190194 Any idea about this? Best regards, Miguel
- Jan 28, 2020
m_kroneI found a solution, hopefully this helps you
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseResourceManager\Tracked\[guid]
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments\[some guid which has the enrolment information]
- removed both reg paths above
- ran dsregcmd /leave
- reboot device
- ran AAD connect to provision device back into Azure AD
- device now Hybrid joined again and registration date is todays date and time / MDM set to none
- dsregcmd /status shows information is being pulled down, waiting for MDM URLs to populate
- Info button on settings / user accounts has now disappeared
- Rebooted device again after 10 minutes
- Upon reboot the MDM URLs now populated
- Event logs show device enrolled
- Info button now available and sync status is successful
- Intune policies applying
Thijs Lecomte
Oct 15, 2019Bronze Contributor
Is this a device you have access to?
- m_kroneOct 21, 2019Brass Contributor
Thijs Lecomte yes, sorry for the late response.
I also rejoined it already but its still not syncing.
Getting an evententry: MDM Session: OMA-DM client stopped with status: (Not found (404).).
- RyanWilsonJan 27, 2020Copper Contributor
m_kroneDid anyone get a resolution for this? I'm having same issue but no joy so far
Getting the same evententry: MDM Session: OMA-DM client stopped with status: (Not found (404).).
- m_kroneJan 27, 2020Brass Contributor