Operating system
Windows
Joplin version
3.6.13
Desktop version info
Joplin 3.6.14 (prod, win32)
Device: win32, Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Client ID: a7271a7b5efd4f9e97bd4be582800445
Sync Version: 3
Profile Version: 49
Keychain Supported: Yes
Alternative instance ID: -
Sync target: Joplin Cloud
Editor: Rich Text
Revision: 7e2765a
Backup: 1.5.1
Easy Backlinks: 1.3.1
Freehand Drawing: 4.3.0
Hotfolder: 1.2.3
Joplin Calendar: 1.2.0
Joplin to Todoist: 1.0.1
What issue do you have?
When the app tries to do an automatic backup or I initiate one manually I get the following error.
Backup plugin
Error on folder creation: EPERM, Permission denied: \?\C:\Users\User\Backups\JoplinBackup\default\joplin_active_backup_job\profile '\?\C:\Users\User\Backups\JoplinBackup\default\joplin_active_backup_job\profile'
It worked ok when I initially started using the app a couple of weeks ago but this seems to have happened since I upgraded the app to the latest version, but I cant prove that,
Any idea what is causing this?
Same here (Error after latest update), and not sure what to do now.
JetGum
If I look in the folder where my backups are stored there is a folder called "JoplinBackup" in this folder is a folder called "default" and in here are all the individual folders containing the backup files.
When the backup fails in the "default" folder I can also see a folder called "joplin_active_backup_job".
If I delete this folder and rerun the backup it sometimes works, so you could try this, it wont affect any of the backup files.
I think the problem started not when I upgraded the Joplin App but when I moved my backup location to a folder that is also backed up to Google Drive, I think that it was previously in a folder that was not backed up to Google Drive, but I cant be sure of that.
I am going to move the backup folder out of the Google Drive location and see if this solves the problem, if it does then it looks as if the automatic Google Drive backup is interfering with the Joplin backup.
Once I have proved this I will escalate via GitHub as suggested in the _vg post.
_vg Thanks,
I think the problem started not when I upgraded the Joplin App but when I moved my backup location to a folder that is also backed up to Google Drive, I think that it was previously in a folder that was not backed up to Google Drive, but I cant be sure of that.
I am going to move the backup folder out of the Google Drive location and see if this solves the problem, if it does then it looks as if the automatic Google Drive backup is interfering with the Joplin backup.
Once I have proved this I will escalate via GitHub as you suggest.
@MartinC
thx, I checked the folders and found the folders as described by you.
Followed your instructions and deleted the "joplin_active_backup_job" folder. And it worked for me. problem solved.
PS: Unlike you, I did not change my sync process or file location. The problem just appeared after updating to the current Joplin version 3.6.14 (prod, win32) with Backup 1.5.1.