Home

Build 75.0.137.0 says it can't sync

%3CLINGO-SUB%20id%3D%22lingo-sub-480006%22%20slang%3D%22en-US%22%3EBuild%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480006%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%2C%20after%20updating%20from%20build%2075.0.134.0%20to%2075.0.137.0%20(Edge%20Canary%2C%20of%20course)%2C%20my%20Microsoft%20account%20was%20signed%20out%20of%20the%20browser%2C%20and%20upon%20signing%20in%2C%20it%20seems%20to%20be%20unable%20to%20sync.%20The%20settings%20page%20says%20it's%20unable%20to%20connect%20to%20the%20sync%20server.%20Surely%20a%20minor%20speed%20bump%2C%20but%20I%20thought%20I%20should%20report%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480608%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480608%22%20slang%3D%22en-US%22%3EYeah%20have%20the%20exact%20same%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480610%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480610%22%20slang%3D%22en-US%22%3EI%20just%20needed%20to%20go%20back%20to%20settings%20and%20enable%20sync%20again%2C%20took%20me%202%20seconds.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480611%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480611%22%20slang%3D%22en-US%22%3EI%20tried%20that%20already.%20Tried%20signing%20out%20and%20back%20in.%20Restarted%20etc.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481482%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481482%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20chiming%20in%20to%20say%20that%20the%20issue%20persists%20on%2075.0.138.0.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481488%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481488%22%20slang%3D%22en-US%22%3E%3CP%3EI%20get%20the%20same%20error%20since%20the%20first%20public%20build%20of%20the%20Chromium-based%20Edge.%20Under%26nbsp%3B%3CA%20href%3D%22edge%3A%2F%2Fsync-internals%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eedge%3A%2F%2Fsync-internals%2F%3C%2FA%3E%26nbsp%3Bit%20shows%20the%20following%20error%20message%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EUnrecoverable%20error%20detected%20at%20OnEngineInitialized%40..%2F..%2Fcomponents%2Fsync%2Fdriver%2Fprofile_sync_service.cc%3A914%3A%20BackendInitialize%20failure%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481497%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481497%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F325834%22%20target%3D%22_blank%22%3E%40RedSign%3C%2FA%3E%26nbsp%3B%20Sorry%2C%20that%20situation%20does%20not%20exist%20here.%26nbsp%3B%20Syncing%20fine.%26nbsp%3B%20Using%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CDIV%3EMicrosoft%20Edge%20is%20up%20to%20date%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22secondary%22%3EVersion%2075.0.138.0%20(Official%20build)%20canary%20(64-bit)%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481499%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481499%22%20slang%3D%22en-US%22%3EYeah%20it%20doesn't%20seem%20to%20be%20widespread%20and%20must%20have%20something%20to%20do%20with%20my%20system%20configuration.%20Tried%20everything%20to%20get%20sync%20up%20and%20running%20in%20Edge%2075%20but%20no%20dice.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481712%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481712%22%20slang%3D%22en-US%22%3ESame%3A%20Unrecoverable%20error%20detected%20at%20OnEngineInitialized%40..%2F..%2Fcomponents%2Fsync%2Fdriver%2Fprofile_sync_service.cc%3A914%3A%20BackendInitialize%20failure%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-486699%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-486699%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20adding%20that%20the%20issue%20still%20persists%20in%2076.0.141%20in%20the%20Canary%20channel%20and%20has%20been%20introduced%20this%20week%20in%20the%20Dev%20channel%20with%2075.0.139.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-486741%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-486741%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20all%20who%20are%20having%20sync%20issues%3A%26nbsp%3B%20Sync%20problems%20of%20one%20sort%20and%20another%20seem%20to%20be%20relatively%20frequent%20with%20Edge%20Chromium%2C%20based%20on%20the%20number%20of%20theads%2Fcomments%20in%20recent%20days.%26nbsp%3B%20%26nbsp%3BPlease%20consider%20reporting%20this%20issue%20to%20Microsoft%20Edge%20Support%20(%3CA%20href%3D%22https%3A%2F%2Fmicrosoftedgesupport.microsoft.com%2Fhc%2Fen-us%2Frequests%2Fnew%3F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftedgesupport.microsoft.com%2Fhc%2Fen-us%2Frequests%2Fnew%3F%3C%2FA%3E)%2C%20which%20will%20collect%20your%20system%20information%20and%20might%20help%20Microsoft%20isolate%20and%20resolve%20the%20issue.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-557021%22%20slang%3D%22en-US%22%3ERe%3A%20Build%2075.0.137.0%20says%20it%20can't%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-557021%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20the%20same%20exact%20issue%20with%20the%20latest%20Dev%20version.%3C%2FP%3E%3C%2FLINGO-BODY%3E
indospot
Occasional Contributor

Hey everyone,

 

Today, after updating from build 75.0.134.0 to 75.0.137.0 (Edge Canary, of course), my Microsoft account was signed out of the browser, and upon signing in, it seems to be unable to sync. The settings page says it's unable to connect to the sync server. Surely a minor speed bump, but I thought I should report it.

 

Thanks!

11 Replies
Yeah have the exact same issue.
I just needed to go back to settings and enable sync again, took me 2 seconds.
I tried that already. Tried signing out and back in. Restarted etc.

Just chiming in to say that the issue persists on 75.0.138.0.

I get the same error since the first public build of the Chromium-based Edge. Under edge://sync-internals/ it shows the following error message: 

 

Unrecoverable error detected at OnEngineInitialized@../../components/sync/driver/profile_sync_service.cc:914: BackendInitialize failure

@RedSign  Sorry, that situation does not exist here.  Syncing fine.  Using 

Microsoft Edge is up to date
Version 75.0.138.0 (Official build) canary (64-bit)

 

Yeah it doesn't seem to be widespread and must have something to do with my system configuration. Tried everything to get sync up and running in Edge 75 but no dice.
Same: Unrecoverable error detected at OnEngineInitialized@../../components/sync/driver/profile_sync_service.cc:914: BackendInitialize failure

Just adding that the issue still persists in 76.0.141 in the Canary channel and has been introduced this week in the Dev channel with 75.0.139.

To all who are having sync issues:  Sync problems of one sort and another seem to be relatively frequent with Edge Chromium, based on the number of theads/comments in recent days.   Please consider reporting this issue to Microsoft Edge Support (https://microsoftedgesupport.microsoft.com/hc/en-us/requests/new?), which will collect your system information and might help Microsoft isolate and resolve the issue.  

Have the same exact issue with the latest Dev version.