Forum Discussion
Assistance Needed: Kernel Connection Timeout in VS Code with Microsoft Fabric
Hello Community,
I'm new to using Microsoft Fabric and am encountering a challenge that I hope some of you might be able to assist me with. I've been trying to run a Jupyter notebook in Visual Studio Code, but I keep running into a kernel connection timeout issue.
Here’s what I see when I try to start the notebook:
```
Failed to start the Kernel.
Unable to start Kernel 'fabric-synapse-runtime-1-1 (Python 3.10.10)' due to a connection timeout.
```
I've attached a screenshot of the error for reference.
What I've tried so far:
- Ensuring that the Conda environment is correctly set up and activated.
- Checking that the IPython kernel is installed and up to date.
- Uninstalling VS Code and reinstall all the extensions.
Despite these efforts, I'm still facing the timeout error. Could anyone provide some guidance on what might be causing this and how to resolve it? Any insights or suggestions would be greatly appreciated, especially from those familiar with Synapse and Fabric on VS Code.
Thank you so much for your time and help!
- Anonymous2 years ago
Hi Anonymous ,
Thank you so much for your help. I have raised a support ticket for this issue. Ticket Number is 2403130040001992. - Anonymous2 years ago
Hi Anonymous
The issue in your case is the session is starting very slowly. Can you please add the JupyterLaunch Timeout like this:
Default timeout is 60000 ms (1 minutes). Set the Default timeout to 10 mins (i.e) 600000ms. After setting the timeout you can connect to the cluster successfully.
Hope this helps. Please let me know if you have any further queries.
9 Replies
- AnonymousNot applicable
Hi Anonymous
Thanks for using Fabric Community.
Can you please check if the spark version in your notebook is also set to runtime 1.1 version?
Thanks.- AnonymousNot applicable
Hi Anonymous ,
Yes the spark version in my notebook is also set to runtime 1.1 version. I'm able to run this notebook in the UI but not locally in vscode.
Thank you.- AnonymousNot applicable
Hi Anonymous
Thanks for the details.
At this time, we are reaching out to the internal team to get some help on this. We will update you once we hear back from them.
Thanks