SQL Data Sync not running automatically according schedule

Question

Hello community,

All my 5 sync groups are configured to run automatically the sync process (following different sync schedules from 10 seconds to 1 minute), but since friday September 9th at 11:30 AM CST, they stop run automatically.

Before it happended...
I tried to create a SQL Elastic job in order to run a SQL Sentence once a day, I tried it 3 times with no success, so very probably it messed up my SyncDB configuration.

Once I realized about the issue, I started the research, I ran the DB Health Check powerswell script saying that DB was ok, no issues, but I got several warnings,

WARNING: DataSync_admin CONTROL on SCHEMA dss IS MISSING!
WARNING: DataSync_admin CONTROL on SCHEMA TaskHosting IS MISSING!
WARNING: DataSync_executor EXECUTE on SCHEMA dss IS MISSING!
WARNING: DataSync_executor EXECUTE on SCHEMA TaskHosting IS MISSING!
WARNING: DataSync_executor SELECT on SCHEMA dss IS MISSING!
WARNING: DataSync_executor SELECT on SCHEMA TaskHosting IS MISSING!
WARNING: DataSync_reader SELECT on SCHEMA dss IS MISSING!
WARNING: DataSync_reader SELECT on SCHEMA TaskHosting IS MISSING!
DataSync_admin CREATE FUNCTION on DATABASE exists
DataSync_admin CREATE PROCEDURE on DATABASE exists
DataSync_admin CREATE TABLE on DATABASE exists
DataSync_admin CREATE TYPE on DATABASE exists
DataSync_admin CREATE VIEW on DATABASE exists
DataSync_admin VIEW DATABASE STATE on DATABASE exists
WARNING: ##MS_SyncAccount## CONNECT on DATABASE IS MISSING!

I added back the permissions highlighted as warning, but I was not able to create the ##MS_SyncAccount## (I didnt found any information how to do it)

WARNING: ##MS_SyncAccount## CONNECT on DATABASE IS MISSING!

Current condition...

1) Jobs can run manually without issue, clicking the sync button from the UI.

2) I tried to remove and create a sync group in order to fix my seetings, but during the step to pull the Tables from the Central-HUB Db is not working, no tables are being displayed, so I lost one of my sync groups.

I wanted to avoid create my sync groups from scratch for the next reasons...

1) Those considerered many tables (~10) per sync groups with different conflict resolution
2) Those considered a lot of data.
3) Nodes continue operating, this is Production.

I hope you can guide me about this issue, I feel frustration not being able to found sustantial information from Internet about this issue.

Answer 1

@ShaktiSingh-MSFT

Thanks for the suggestion, but removing everything and starting from scratch is not a solution to me is precisely what I want to avoid.

Any additional suggestion to try?

Best Regards,

Answer 2

It was partially fixed by support Team, I just need to drop and create again some sync groups.