When I'm trying to add a table in an existing synapse link, my new table in waiting for snapshot state for long, after I check the log, I got the error message.Error 22724 severity 16 Error occurred while exporting initial snapshot to landing zone.

@Vignesh K

I understand you're encountering Error 22724, Severity 16: "Error occurred while exporting initial snapshot to landing zone" when adding a new table to an existing Azure Synapse Link. This error typically indicates a failure during the initial snapshot export process, where data from the source database is transferred to the landing zone (usually Azure Data Lake Storage Gen2).

To troubleshoot this issue, please follow the steps below:

Check Snapshot State - Run the following query on your source SQL database to monitor the status of the snapshot process for the table:

SELECT table_group_id, table_id, state, version, snapshot_phase, 
       snapshot_current_phase_time, snapshot_retry_count, snapshot_start_time,
       snapshot_end_time, snapshot_row_count 
FROM changefeed.change_feed_tables;

Pay special attention to the snapshot_phase and snapshot_retry_count columns to determine if the snapshot is still running or if it has encountered repeated failures.

Review Error Logs - Retrieve detailed error information from the following dynamic management view:

SELECT * FROM sys.dm_change_feed_errors;

This will provide insights into any specific errors that occurred during the snapshot process.

Based on the information gathered:

Verify Storage Account Permissions - Ensure that the Synapse workspace's managed identity has the required Storage Blob Data Contributor role assigned at the container or filesystem level of the storage account.

Check Network Configurations - Confirm that there are no firewall rules or network configurations preventing access to the storage account. If using private endpoints or service endpoints, ensure they're correctly configured.

Validate Table Schema - Review the table schema to ensure it doesn't contain unsupported features such as computed columns, unsupported data types, or lacks a primary key.

Monitor for Transient Issues - Occasionally, transient issues in the Azure infrastructure can lead to snapshot export failures. Retry the operation after some time. If the problem persists, consider restarting the Synapse Link or recreating it.

For more details refer: Troubleshoot: Azure Synapse Link for SQL initial snapshot issues

Get started with Azure Synapse Link for SQL Server 2022

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues. 

Hi,I have tried all the methods you listed above, but they are not working. However, if I stop and restart the specific link, it starts working.

If the issue persists due to the firewall or schema, it should throw an error even when restarting the link, correct?

Hi,I have tried all the methods you listed above, but they are not working. However, if I stop and restart the specific link, it starts working.

If the issue persists due to the firewall or schema, it should throw an error even when restarting the link, correct?

After the link started, I tried to add another table while the link is in running state. Again error.

@Vignesh K

Thank you for the update and for confirming that restarting the Synapse Link temporarily resolves the issue.

You're absolutely right if the root cause were related to firewall restrictions or unsupported schema, restarting the link should not bypass the error. The fact that restarting the link enables the snapshot to succeed points to a transient or internal state issue within the link process itself, rather than a persistent configuration problem.

This behavior suggests one of the following:

1. Sometimes, when a new table is added while the link is actively running, the snapshot engine may fail to initialize the process cleanly, especially if there's already an ongoing operation or internal queue delay.
2. Restarting the link clears out these stale states, allowing the snapshot process to resume successfully.

Before adding new tables, try stopping the link, then adding the new table, and finally starting the link again. This helps avoid mid-operation conflicts.

According to this documentation: https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-events-and-errors-22000-to-22999?view=sql-server-ver16 Reference: https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-error-severities?view=sql-server-ver16

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.