can you please provide a screenshot of the sync-internals page for this machine (potentially covering any personal IDs in the top section.

Please see attached for chrome:\\sync-internals screen shot.

Deleted: syncinternalsbroken.png 382 KB

	syncinternalsbroken.png 382 KB View Download

At least in this screenshot it seems like it's all good now? Maybe chrome was not restarted when the policy was turned on when you observed the connection not attempted error. It talks from server btw but when local sync mode is on it is really only an in memory transaction that happens between the frontend and the backend code of Chrome that gets written to the file on disk.

Well, compare that screen shot to a working client.  The broken user has several bookmarks, yet the total entries seem to be 0 for everything.

Deleted: syncinternalsworking.png 139 KB

	syncinternalsworking.png 139 KB View Download

Right! I was looking at the various status flags and they are basically the same. Seems like some sync related state is incorrectly preserved when turning on the roaming profile feature after Chrome has been syncing with the regular sync server.

Thanks for clarifying I will look into that and see if I can offer you a quick workaround while the underlying issue is being fixed.

any update?

Just wondering if you found anything?

Hi, sorry we haven't had a chance to figure out what is going wrong with this client. Btw have you been updating Chrome since then. There have been some general  changes and fixes to the Roaming profiles feature lately and your issue might have been fixed by that?

One thing that I can suggest is locally on the affected machine to clear the two policies from the registry. Start Chrome without them - make sure Sync has been disabled and then restore them and see if this makes Chrome to start syncing. Alternatively if the profile contains all data that the user has you can try to delete the profile.pb file from the roaming location and let Chrome restore it from the local profile.

I am still seeing inconsistencies.  We have google enterprise support, do I log a case there (how?) or do I keep working with you?

Filing the case there will be beneficial as it will establish a good secure channel to let us request information that will be helpful to diagnose this issue.
How this is done I can't tell you, unfortunately, but I hope you should have some contact that you can call/mail that should be able to aid you. Cite this bug number to avoid having to describe the issue again once more.

Support case #17765516 has been filed. Is there additional information that should be passed from there? Or should a separate bug be filed?

Royans, can you start a mail thread with me and the customer so that I can request some follow up information there and/or grant me access to the support case if it offers means to communicate.

Any update on this?

Thanks
Zach

On Mon, Jan 7, 2019, 2:41 AM pastarm… via monorail <
monorail+v2.58893057@chromium.org wrote:

I just notice that the person I directed my request to is not on the CC list so most probably he missed it. I resent my request in a direct email to them.

Any update on this?

Thanks,
Zach

On Tue, Jan 15, 2019, 2:36 AM pastarm… via monorail <
monorail+v2.58893057@chromium.org wrote:

Still waiting for the case info to reach me. Pinged the thread again today.