apple_cloud_notes_parser: Permission denied @ rb_file_s_rename
Hello! I did everything according to the instructions for windows (10), and get this error:
PS D:\apple_cloud_notes_parser-master> rake
D:/Ruby26-x64/bin/ruby.exe notes_cloud_ripper.rb --file NoteStore.sqlite
Starting Apple Notes Parser at Sat Feb 1 18:47:55 2020
Storing the results in ./output/2020_02_01-18_47_55
Created a new AppleBackup from single file: NoteStore.sqlite
Traceback (most recent call last):
8: from notes_cloud_ripper.rb:83:in `<main>'
7: from notes_cloud_ripper.rb:83:in `new'
6: from D:/apple_cloud_notes_parser-master/lib/AppleBackup.rb:86:in `initialize'
5: from D:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/fileutils-1.4.1/lib/fileutils.rb:539:in `mv'
4: from D:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/fileutils-1.4.1/lib/fileutils.rb:1586:in `fu_each_src_dest'
3: from D:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/fileutils-1.4.1/lib/fileutils.rb:1604:in `fu_each_src_dest0'
2: from D:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/fileutils-1.4.1/lib/fileutils.rb:1588:in `block in fu_each_src_dest'
1: from D:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/fileutils-1.4.1/lib/fileutils.rb:548:in `block in mv'
D:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/fileutils-1.4.1/lib/fileutils.rb:548:in `rename': Permission denied @ rb_file_s_rename - (./output/2020_02_01-18_47_55/test.sqlite, ./output/2020_02_01-18_47_55/NoteStore.sqlite) (Errno::EACCES)
rake aborted!
Command failed with status (1): [D:/Ruby26-x64/bin/ruby.exe notes_cloud_rip...]
D:/apple_cloud_notes_parser-master/Rakefile:7:in `block in <top (required)>'
Tasks: TOP => default => run
(See full trace by running task with --trace)
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (6 by maintainers)
If your database is running you should close it. I had the same error once, that’s how I fixed it
I ran the command line as admin user and tried it again and it resolved the issue.
Thanks for sharing this. The problem was Windows saw the file as “open” and wouldn’t rename it. I added a line to expressly close the database and it appears to work well now on Windows 10 Enterprise. Please try it out and let me know if it solves your problems.
Commit was 9e31faa8a7982e9ebd1ce389b07406ef1f4f8079