A community member has associated this post with a similar question:
Synapse Pipeline (Lineage) ingestion into Purview - Failed to report lineage to catalog
Only moderators can edit this content.
Synapse Pipeline (Lineage) ingestion into Purview - Failed to report lineage to catalog
Hi,
We created Purview specific pipelines in Synapse and it worked as expected in QA environment.
Last week, we migrated our code to production, and the lineage is not getting generated from the pipelines. We are getting "The catalog provided for lineage reporting cannot be connected, please check the catalog uri and network connection."
I verified all the permissions are intact in Synapse (Reader), Storage account (Storage Blob Data Reader), and I can see the connection is connected in Synapse -> Manage - > MS Purview.
Role-related commands were also executed
CREATE USER [purviewacc] FROM EXTERNAL PROVIDER
GO
EXEC sp_addrolemember 'db_datareader', [purviewacc]
GO
SELECT p.name AS UserName, r.name AS RoleName
FROM sys.database_principals p
LEFT JOIN sys.database_role_members rm ON p.principal_id = rm.member_principal_id
LEFT JOIN sys.database_principals r ON rm.role_principal_id = r.principal_id
WHERE p.authentication_type_desc = 'EXTERNAL'
ORDER BY p.name;
Can you please let me know what else could be the reason for not generating the lineage?
In addition to this, I can see the lineage of other pipelines which are generic but not for Purview specific.
Regards,
Hargopal