Forum Discussion
Advocate IUnexpected Data Refresh Failure and Query Execution from Wrong Snowflake Warehouse in Power BI
Community SupportHi sushovan93 ,
Thank you for reaching out to the Microsoft Community Forum.
Hi tayloramy , Thank you for your prompt responses.
Hi sushovan93 ,
Please try below things to fix the issue.
1. Please check that each Snowflake connection in the gateway is uniquely named and mapped to only one dataset. Avoid having multiple Snowflake connections in the same gateway unless absolutely necessary.
2. Fix the gateway logging issue to inspect the actual query routing and connection used. Enable verbose logging and check for MashupEngine and SnowflakeConnector logs.
3. Please check that the service user cannot switch roles or access other warehouses. Use session parameters to enforce role and warehouse.
ALTER USER SVC_A SET DEFAULT_ROLE = 'ROLE_A';
ALTER USER SVC_A SET DEFAULT_WAREHOUSE = 'WHS_XXX_Reporting';
4. Use query tags to trace execution. Use Snowflake’s Access History view to correlate user, role, warehouse, and query source.
5. Please try to refresh the dataset manually using Power BI Desktop with the same gateway to see if the issue reproduces.
6. Please clone the dataset and remove all but the problematic table. Test refresh behavior to isolate whether the issue is with the table/query or the dataset configuration.
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Advocate IHi v-dineshya
1. Gateway connection name is unique and those 2 uses seperate warehouse in the connection and only mapped to their related datasets.
2. For the fix of Gateway log I'm still working with MSFT.
3. the role assignment is already there, but I'll dauble check that again and thank you for suggestion on seeting the default warehouse. will try that.
4. the problem is it's happening intermitently. let say we have 24 api trigger refresh per day for the dataset and 1 or 2 of them are behaving like this and that also not in consecutive run. that's where our problem is if it was executing all the runs with the wrong warehouse we can definitely say there is something wrong with either gateway connection or dataset configuration but lets say 10 runs execute with WH_A and SVC_A then 1 in the middle is executing with WH_B and SVC_B then again next 2-3 runs are fine and aging in one of the run it exceutes with WH_B/SCV_B and after that it works fine again.
I'll try to test with that particular table now the in the gateway schedule and see the results.
- v-dineshya
Hi sushovan93 ,
Thank you for the update. As you mentioned in your previous response that, you are checking with Microsoft team to fix the Gateway log. please share the support ticket link or Service request number , it will help us to check the current status of the thread.
Regards,
Dinesh
- sushovan93
2509040040013333- this one's for the gateway logs.
Hi sushovan93 ,
I am also a member of CST team and since you have already submitted the ticket, the support team will handle the issue and resolve it soon.
Thank you for your patience.
Regards,
B Manikanteswara Reddy