Azure data sync error : Database re-provisioning failed with the exception

Burcu Belen 0 Reputation points
2023-03-11T13:49:23.5066667+00:00

Hi,

I constanttly getting same error and I couldn't solve this issue. Error:

Database re-provisioning failed with the exception "Provisioning did not succeed because associated hub might be busy with other provisioning work. Sync Service will retry provisioning during next sync. For more information, provide tracing ID ‘3ad26f86-a691-44e2-b272-1ec002071e9d’ to customer support."

I deleted data sync group and all tables and related views from database and recreated data sync group again. It didn't worked.

I closed all automatic sync which has same server. That didn't work either.

Before I get this error, I tried to change data types of columns manually in Azure SQL database related this data sync group. I am not sure this caused to this error or not. I need to fix this issue urgently.

Could you please help me?

Thanks.

Azure SQL Database
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. RahulRandive 10,486 Reputation points Volunteer Moderator
    2023-03-11T14:33:28.1933333+00:00

    Thanks for your question.

    To get the exact and meaningful error or to know root cause of an issue, you can run

    Azure SQL Data Sync Health Checker report

    This PowerShell script will check if all the metadata of a hub and member is in place and also validate the scopes against the information we have on the sync metadata database (among other validations). This script will not make any changes, will just validate data sync and user objects. It will also gather some useful information for faster troubleshooting.


  2. GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator
    2023-03-13T13:26:02.66+00:00

    @Burcu Belen This error is usually transient and comes when multiple scopes are being provisioned at once. It’s also possible that one of the sync groups failed in the middle of provisioning and did not clear up its state, Are you trying to do multiple provisioning at once? Please try with 1 Sync Group at once, if you are doing so.

    Otherwise, we will need to manually de-provision any stuck scope_status for that you need to raise a support case please let us know if you have any issues raising a support case.

    Regards

    Geetha


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.