Forum Discussion
Memorable MemberAnother random spark failure in fabric on custom pool - No module named 'azure.core.exceptions'
Hi,
I have been troubleshooting this issue today, as I experienced it whilst running my custom packages in my custom Fabric environment. I ended up creating a new environment and testing in a notebook to see if the issues persisted, miraculously this actually resolved the issue. All the built-in libraries were the same, and my custom packages also work in this new environment.
Memorable MemberSounds like the fix is to update the version of azure-core library in Fabric. Odd that customers would be doing this independently of Microsoft's direction.
I hope it is still a supported configuration. We don't want to risk even more problems, and get even less support for our customized environment.
Did you find a solution to this? I have just had the exact same error, regarding the same package "notebookutils". Something must be happening with updates since we are both getting the same error within the same week.