Forum Discussion
Fabric Notebook Error - AzureNotebookRef has been disposed
- Anonymous8 months ago
Hi pei2705ying ,
Thank you for reaching out to the Microsoft Fabric Community Forum and thank you for confirming that the Fabric capacity is active.
Since the issue persists across all notebooks, the behavior is more likely related to the notebook runtime environment or the workspace configuration rather than the capacity itself. To isolate the cause, please try creating a new blank notebook in the same workspace and check whether it opens successfully. If it fails with the same message, this points to a workspace-level issue.
Additionally, please test whether notebooks open correctly in another workspace to determine if the problem is isolated or tenant-wide. You may also review the Notebook Runtime Sessions under Monitor → Sessions to see if any sessions are stuck in a Starting or Failed state, as this can prevent new notebook environments from initializing. Lastly, ensure that the workspace is correctly assigned to the active capacity. Could you confirm whether a new notebook opens, whether notebooks work in other workspaces, and whether other users in your tenant are experiencing the same behavior?
Thank you.
- Anonymous7 months ago
Hi pei2705ying ,
We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.Thank you.
Hi pei2705ying ,
Thank you for reaching out to the Microsoft Fabric Community Forum and thank you for confirming that the Fabric capacity is active.
Since the issue persists across all notebooks, the behavior is more likely related to the notebook runtime environment or the workspace configuration rather than the capacity itself. To isolate the cause, please try creating a new blank notebook in the same workspace and check whether it opens successfully. If it fails with the same message, this points to a workspace-level issue.
Additionally, please test whether notebooks open correctly in another workspace to determine if the problem is isolated or tenant-wide. You may also review the Notebook Runtime Sessions under Monitor → Sessions to see if any sessions are stuck in a Starting or Failed state, as this can prevent new notebook environments from initializing. Lastly, ensure that the workspace is correctly assigned to the active capacity. Could you confirm whether a new notebook opens, whether notebooks work in other workspaces, and whether other users in your tenant are experiencing the same behavior?
Thank you.