![]() |
#1 |
Junior Member
![]() Posts: 2
Karma: 10
Join Date: Jul 2016
Device: Kobo Glo
|
![]()
I had the same error today. Managed to solve it by installing the newest available version of Python (which is used by Calibre). You can find the newest version of Python on their official website (link is for Windows users): https://www.python.org/downloads/windows/
(I did not uninstall/reinstall Calibre before updating Python so didn't have to reconfigure anything) Hope this helps some people who encounter this nasty python error ![]() Last edited by fiskie; 07-31-2016 at 06:34 AM. Reason: added line about not uninstalling first |
![]() |
![]() |
![]() |
#2 |
Ex-Helpdesk Junkie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Um, calibre does not require or make use of external Python installs, so I can assure you the fact that calibre started working again was purely a coincidence. Or you did something else which fixed it.
Especially if by "newest available version of python" you mean Python3! |
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Junior Member
![]() Posts: 2
Karma: 10
Join Date: Jul 2016
Device: Kobo Glo
|
Yeah, I found out you're right today. After a few restarts it generated the error again. What did however fix it for good, was setting the calibre temp environment variable to something else than the standard. I use C:\Windows\Temp now and it works like a charm!
I think reinstalling Python worked because it created the temp folder Calibre also uses (which I noticed was deleted after a Windows 10 reboot) Last edited by fiskie; 08-02-2016 at 03:52 PM. |
![]() |
![]() |
![]() |
#4 |
null operator (he/him)
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 21,725
Karma: 29711016
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
@fiskie - IIRC - the default location for CALIBRE_CONFIG_DIRECTORY (set internally) is %LOCALAPPDATA%\Temp
I question if calibre would even start if CALIBRE_CONFIG_DIRECTORY was set to C:\Windows\Temp. The C:\Windows\Temp directory is one of those 'off limits' directories even to read. If it is working then I suspect you or something must have changed the permissions of that directory. The factory set permissions for C:\Windows\Temp, C:\Windows\Prefetch etc are deliberately set that way to deter their use by users or applications. Moderator Notice I've put your issue into its own thread, please don't tack your issues onto someone else's thread unless you are solving their problems BR Last edited by BetterRed; 08-02-2016 at 05:20 PM. Reason: Add Moderator Message |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Windows Error | Tanys | Devices | 4 | 07-17-2016 04:39 AM |
Calibre error in Windows 8.1 | vinieux | Devices | 29 | 05-28-2016 04:20 AM |
Sigil 0.7.0 Error in Windows Xp | mont555 | Sigil | 5 | 02-23-2013 04:01 PM |
Windows error | jgray | Sony Reader | 4 | 10-01-2010 12:31 AM |
Runtime Error: Windows 7 | ZacWolf | Sigil | 16 | 01-07-2010 11:54 PM |