Recently while configuring the Export to Data Lake service, we observed the initial sync status being stuck for one of the tables at Not started.
Manage tables option also was not working
All changes for existing tables are temporarily paused when we are in the process of exporting data for new table(s). We will resume writing changes for existing table(s) after we complete exporting data for new table(s) to the Azure data lake.
As it was seemed to be stuck forever, we tried Unlinking the data lake and linking it back.
We left the Delete data lake file system unchecked.
Created a New link to data lake with the same storage account.
We would get the below error à
An error occurred: Container: dataverse-pmaurya105-unqdc8ed1c1df824188bbe2225de96f0 already existed with files for storage account: saazuredatalakecrm. Please clean dataverse-pmaurya105-unqdc8ed1c1df824188bbe2225de96f0
Basically, if we are using the same storage account for linking, we need to first delete or clean the container.
We cleaned the container.
And tried again.
This time it worked
Here we can check the Delete data lake file system option while Unlinking the data lake
This will perform the same step – deleting the files within the container.
If that doesn’t work or is not feasible, we should raise Microsoft Support Ticket.
Check other posts on Azure Data Lake and Dynamics 365 –
Hope it helps..
4 thoughts on “Fixed – Initial sync status – Not Started – Azure Synapse Link / Export to Data Lake”
Hi Nishant, do you experience that entities stopped syncing after a few days? The initial sync was successful.
Do not remember the team mentioning it. Id check with them
The main question I have is prior to the unlink/relink is what happens to the tables, configuration etc. when that is performed? Does anything need to be re-built after the relink?