Azure Synapse Pipeline: Status: TypeError: Cannot read properties of undefined (reading 'referenceName'), Possible reason: TypeError: Cannot read properties of undefined (reading 'referenceName')

Question

Hi,

one moment to the next my pipeline does not open.

I get the message: Status: TypeError: Cannot read properties of undefined (reading 'referenceName'), Possible reason: TypeError: Cannot read properties of undefined (reading 'referenceName').

I checked that all objects linked to in 'referenceName' do exist. And yes, they do.

I've tried going back to an earlier commit on the same branch to ensure that it was not caused by recent changes, but to no effect, i.e. even when I go back to an earlier commit the pipeline won't open.

I've seen that other people have had similar issues, but there does not seem to have been provided a solution... Seems like a recurring bug.

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

This issue often indicates a corruption or misconfiguration in the Synapse pipeline JSON file or its references. Here's a systematic approach to troubleshoot and resolve the issue:

1. Check Pipeline JSON for Corruption

• Export the pipeline JSON file using the Synapse Studio or check it in your repository.
• Look for missing or incorrectly configured properties, particularly those related to referenceName. Ensure:
  • All linked services, datasets, or other objects referred to by referenceName exist and are correctly named.
    • Syntax is valid, and there are no unclosed braces or commas.

2. Verify Linked Resources

• Open each linked service, dataset, or other resource referred to in the pipeline.
• Ensure they are not corrupted or missing any required properties.
• If possible, revalidate each linked service and dataset to ensure they are functioning correctly.

3. Check Synapse Logs

• Go to Monitor > Integration Runtimes or Pipeline Runs in Synapse Studio and look for logs related to the pipeline.
• Check for additional errors or warnings that might provide more context about the failure.

4. Test in a New Pipeline

• Create a new pipeline and try to replicate a minimal version of the functionality from the problematic pipeline.
• Add objects incrementally to identify which specific object or step triggers the issue.

5. Clear Synapse Studio Cache

• Browser cache can sometimes cause unexpected issues with Synapse Studio. Clear your browser cache or open Synapse Studio in an incognito window.

6. Restore from a Backup

• If you have version control enabled for your Synapse workspace, compare the current version of the pipeline JSON with earlier commits.
• Revert to a known good state and republish the workspace.

7. Sync and Publish

• If working with feature branches or multiple environments:
  • Ensure the branch is fully synced with the publish branch.
    • Publish all changes to the Synapse workspace to ensure consistency.

Potential Workaround

If the pipeline remains inaccessible:

1. Download the pipeline JSON from your repository or workspace.
2. Manually review and fix any issues in the JSON file.
3. Delete the problematic pipeline in Synapse Studio.
4. Recreate the pipeline by importing the fixed JSON.

If none of the above steps resolve the issue, and it appears to be a bug, consider raising a support ticket with Azure.

Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.