Forum Discussion
WH is not displaying Stored procedure
Hi Team,
I’m facing a serious issue in our Fabric development workspace and need assistance understanding the root cause and resolution.
Our Fabric Warehouse has suddenly started behaving unexpectedly:
- The Warehouse is not displaying any of our stored procedures (SPs), even though they were previously available and actively being used by our pipelines.
- As a result, pipelines that depend on these SPs are now failing.
- The error we are seeing is:
Operation on target Lookup Flag Update failed:
ErrorCode=SqlFailedToConnect
Message: Cannot connect to SQL Database.
Login failed for user ''. Reason: Authentication was successful, but the database was not found or the user has insufficient permissions to connect.
Additionally, we noticed something very unusual:
- My colleague is able to see two Warehouses appearing together in what seems like a single context/view.This is happening with one user only.
- When I check it on SSMS I am able to see those SPs but not in UI.
- ADF pipeline runs successfully pointing to that SP but fabric pipeline is failing
- The stored procedures are showing under this other Warehouse, which was never actually used by our pipelines.
- This is creating confusion around whether there has been some metadata mapping issue, Warehouse reference issue, or backend inconsistency.
This is currently happening in our development workspace, but my major concern is understanding how to recover from this if the same issue occurs in production, since it would directly impact business pipelines.
Hi sshetty014,
Thank you for reaching out to Microsoft Fabric Community.
Thank you Srisakthi for the prompt response.
Thank you for the response. Since the stored procedures are visible and executable from ssms and the adf pipeline is also working successfully, this shows that the SPs are still present and accessible in the warehouse backend.
Looks like the issue is specific to the fabric warehouse UI or fabric pipeline connection metadata rather than the issue with the stored procedures. Please try below following steps:
- Recreate the OAuth2 connection used in the fabric pipeline.
- Try to rebind the Lookup activity to the warehouse again.
- Republish the pipeline.
If the issue continues even after recreating the connection and rebinding the warehouse, please open a Microsoft support ticket for further backend investigation, because this can be related to backend metadata inconsistency in the fabric workspace.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar Chippa
7 Replies
- SrisakthiSuper User
Hi sshetty014 ,
Can you please cross verify the permissions once?
1. is your Fabric Pipeline uses any connection?
2. Is there any change in warehouse permission either at warehouse level or object level.
Regards,
Srisakthi
- sshetty014Frequent Visitor
hi Srisakthi
1. is your Fabric Pipeline uses any connection? Yes , as shown in below lookup activities , its pointing to a WH in another workspace
2. Is there any change in warehouse permission either at warehouse level or object level. -- Can you tell me what exactly i need to look for and where ?
- SrisakthiSuper User
Hi sshetty014 ,
For the other workspace how your pipeline is connecting . is it using Service Principal or OAuth? Can you try re-creating the connection once. Also make sure the Service Principal or OAuth has appropriate access the other workspace and its items, like contributor to the workspace.
Regards,
Srisakthi
- sshetty014Frequent Visitor
hi Srisakthi ,
hi ,
We are using OAuth2.0. I also checked with my admin , we havent changed any permission. And we are facing issue in the fabric warehouse UI because we are able to see the SPs when im connected with SSMS and also able to execute the SP in smms but not in Fabric UI.
- sshetty014Frequent Visitor
I am waiting for some solution here . Thanks in advance