Forum Discussion
Fabric Objects Not Loading/Erroring (Notebooks, Lakehouse Tables, Data Warehouse Tables...)
- 1 year ago
Thank you for the reply and feedback. We discovered that the issue was related to a change that was made to our internal DNS. The changes have been reverted and the functionality is back to normal.
Hi gwayne
I’m sorry to hear you’re experiencing these issues with Microsoft Fabric. It sounds quite frustrating, especially given the impact on your workflows. But it’s good to hear that you can create visual queries. This suggests that the core data services are operational, and the issues might be more related to the interface or specific configurations.
Here are some considerations that may help you troubleshoot and narrow down the issue while you wait for further guidance from Microsoft Support:
-
Browser and Cache: Clear your browser cache or try accessing Fabric service from a different browser or incognito mode. Browser-related issues can sometimes cause loading problems.
- Capacity: Do these issues occur in one particular Fabric capacity or in all the capacities that you have? Are these capacities paid F capacities or Fabric Trial capacities? Is it possible to move a workspace to another Fabric capacity to check whether it would go to work?
- Users: Do only specific users have these issues, or do all users have these issues? If only specific users have the issues, try removing their access to the workspace, then provide them with the access again.
-
Network and Permissions: Given the network-related error messages, double-check your network settings and permissions. Sometimes, network configurations or firewall settings can cause such issues. If possible, try accessing Fabric from a different computer or network environment to see if the results will be different.
I can't reproduce these issues, and I haven't found other users reporting them, so I suspect it may be related to some specific setup, or an issue that is happening in a specific environment. I recommend that you continue to contact the relevant Microsoft engineer of your ticket to check any progress or feedback. They may need to gather some information to troubleshoot from the background end. It may take some time. Thank you for your understanding.
Best Regards,
Jing
Community Support Team
- gwayne1 year agoFrequent Visitor
Thank you for the reply and feedback. We discovered that the issue was related to a change that was made to our internal DNS. The changes have been reverted and the functionality is back to normal.