I use ipynb notebook in VS Code
Today I started to get an error: Failed to start the Kernel. PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\Users\UserName\.ipython\profile_default\history.sqlite' -> 'C:\Users\UserName\.ipython\profile_default\history-corrupt.sqlite'. View Jupyter log for further details.
I got it in any notebook I tried to run
I tried: restarting the PC, deleting 'history.sqlite' (threre is also 'history.sqlite-journal' file in the same folder, that couldn't be deleted even after the reboot)
Tried to run handle on these files, but didn't find any processes that use them
Didn't help so far. Don't remember changing any system settings
I use ipynb notebook in VS Code
Today I started to get an error: Failed to start the Kernel. PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\Users\UserName\.ipython\profile_default\history.sqlite' -> 'C:\Users\UserName\.ipython\profile_default\history-corrupt.sqlite'. View Jupyter log for further details.
I got it in any notebook I tried to run
I tried: restarting the PC, deleting 'history.sqlite' (threre is also 'history.sqlite-journal' file in the same folder, that couldn't be deleted even after the reboot)
Tried to run handle on these files, but didn't find any processes that use them
Didn't help so far. Don't remember changing any system settings
Share Improve this question edited Mar 28 at 8:51 Diana asked Mar 27 at 16:43 DianaDiana 992 silver badges7 bronze badges 1- 1 That is ipython, and not python as your post's title references. Did you try getting that corrupt file out of there? See this comment for where some efforts resulted in kernel working again in case where didn't care about the history database. Also looks similar to here – Wayne Commented Mar 27 at 20:20
1 Answer
Reset to default 0Resolved by:
- rebooting, going to the folder before starting anything else, deleting that 'history.sqlite-journal' file (was allowed this time)
But cannot be sure if that was exactly what helped, maybe just the second reboot itself