iCloud Error "...Code=1 "Operation not permitted"

[Mr_Noodle]

Is the error in the logs the same?

[MarkusBe]

It is kind of the same, but with some more information I think:

2024-03-03 14:25:29.356 hazelworker[86379] B1v5y1mP8OL.pdf: Rule PDFs in Scaninput schieben matched.
2024-03-03 14:25:29.356 hazelworker[86379] DEBUG: Manual run. Forcing actions to be executed.
2024-03-03 14:25:29.369 hazelworker[86379] DEBUG: Error with direct copying /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS/B1v5y1mP8OL.pdf to location /Volumes/scaninput/B1v5y1mP8OL.pdf: Operation not permitted
2024-03-03 14:25:29.372 hazelworker[86379] DEBUG: Error copying /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS/B1v5y1mP8OL.pdf to /Volumes/scaninput/B1v5y1mP8OL.pdf for move operation: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
2024-03-03 14:25:29.372 hazelworker[86379] Error moving file from /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS/B1v5y1mP8OL.pdf to /Volumes/scaninput/B1v5y1mP8OL.pdf: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
2024-03-03 14:25:29.373 hazelworker[86379] [Error] Move failed: Could not move file B1v5y1mP8OL.pdf from folder /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS to folder /Volumes/scaninput/B1v5y1mP8OL.pdf.
2024-03-03 14:25:29.373 hazelworker[86379] DEBUG: Tapping error retry sequence
2024-03-03 14:25:29.373 hazelworker[86379] DEBUG: Writing out DB file for /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS to path: /Users/markusbe/Library/Application Support/Hazel/16777223-65277.hazeldb
2024-03-03 14:25:29.374 hazelworker[86379] DEBUG: Directory /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS processed in 0.223430 seconds
2024-03-03 14:25:29.374 86Z3GCJ4MF.com.noodlesoft.HazelHelper[32118] DEBUG: Checking events for path /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS, folder 00_EcoDMS
2024-03-03 14:25:29.374 hazelworker[86379] DEBUG: Sending metrics to scheduler. Next scheduled run: 2024-03-03 14:30:29.294
2024-03-03 14:25:29.374 hazelworker[86379] Done processing folder 00_EcoDMS
2024-03-03 14:25:29.375 86Z3GCJ4MF.com.noodlesoft.HazelHelper[32118] DEBUG: Received metrics for folder /Users/markusbe/Library/Mobile Documents/com~apple~CloudDocs/00_EcoDMS: {
directoryDepth = 0;
requestedSchedulingTime = "2024-03-03 13:30:29 +0000";
triggerPaths = "<NoodlePathSet: 0x600000bddee0>\n";
unavailablePaths = "{(\n)}";
}

[Mr_Noodle]

What version of Hazel are you running now?

[MarkusBe]

I am running Version 5.3b5

[Mr_Noodle]

Note that version 5.3.3 is the latest version.

[MarkusBe]

Hi MrNoodle,

I think I have the solution. I updated to version 5.3.3, but that didn't solve the problem.
In fact, it was an issue from my document management system ecodms. They are writing this:

Solution on the MAC
Open the terminal on your Mac
Execute the following command: defaults write com.apple.desktopservices DSDontWriteNetworkStores true
Restart your Mac or log out and then log in again.
The ".DS_Store files" are now only created on local disks.
(https://confluence.applord-gruppe.eu/ek ... t-abgeholt)

So far so good. But when moving the files to my ubuntu drive, another file will be created, the filename is the same, but it begins with "._". These files are hidden and my samba share had a "veto files" parameter:

veto files = /._*/.DS_Store/
delete veto files = yes

Samba is trying to delete the "._*" files as soon as they appear, and this is causing Hazel to stop the moving process - at least I THINK so. So my solution is to comment out the veto files in samba, restarted samba. In Hazel I inserted an additions shell script which is changing to the scaninput-folder "/Volumes/scaninput" and then deleting the "._*" files with "rm ._*".

With these changes everything SEEMS to be good right now...

Long way to solution - thank you for your efforts again! After all I think it wasn't a real Hazel problem, at least not only on Hazel side... I am not sure, why the moving process was interrupted. But who knows - it is working right now and I am happy! Thank you!

[Mr_Noodle]

A bit of an obscure issue but glad you have it figured out.