SABnzbd Forums

sander wrote: ↑November 19th, 2021, 3:25 am Do you think that additional info will provide things like "... because in use by Proces XYZ" (virusscanner use case), or "no rights to write file", or "disk not available" ... ?
Because that would indeed be useful.

Errno 13 can be caused by the high level error codes ERROR_ACCESS_DENIED and ERROR_SHARING_VIOLATION in Windows. As I understand it, ERROR_ACCESS_DENIED alone can be caused by any of these underlying Windows status codes:

STATUS_INVALID_LOCK_SEQUENCE 0xc000001e
STATUS_INVALID_VIEW_SIZE 0xc000001f
STATUS_ALREADY_COMMITTED 0xc0000021
STATUS_ACCESS_DENIED 0xc0000022
STATUS_PORT_CONNECTION_REFUSED 0xc0000041
STATUS_THREAD_IS_TERMINATING 0xc000004b
STATUS_DELETE_PENDING 0xc0000056
STATUS_FILE_IS_A_DIRECTORY 0xc00000ba
STATUS_FILE_RENAMED 0xc00000d5
STATUS_PROCESS_IS_TERMINATING 0xc000010a
STATUS_CANNOT_DELETE 0xc0000121
STATUS_FILE_DELETED 0xc0000123

Encrypting File System
STATUS_ENCRYPTION_FAILED 0xc000028a
STATUS_DECRYPTION_FAILED 0xc000028b
STATUS_NO_RECOVERY_POLICY 0xc000028d
STATUS_NO_EFS 0xc000028e
STATUS_WRONG_EFS 0xc000028f
STATUS_NO_USER_KEYS 0xc0000290

Hopefully it won't always be STATUS_ACCESS_DENIED.

So with some extra code we could maybe provide some more information?
That sounds like it's worth a try.
Sorry I missed this thread before.

Nox wrote: ↑November 19th, 2021, 6:19 am I will test my setup on Proxmox (another hypervisor) and on a windows computer without any hypervisor.

I did that now. The problem also occurs without any hypervisor, so it's not due ESXi & Promox.

Nox wrote: ↑November 26th, 2021, 11:23 am

Nox wrote: ↑November 19th, 2021, 6:19 am I will test my setup on Proxmox (another hypervisor) and on a windows computer without any hypervisor.

I did that now. The problem also occurs without any hypervisor, so it's not due ESXi & Promox.

Assuming we want to proceed ... how?

I have added printing of the error in a pull request on Github. You can download binaries for Windows here: https://github.com/sabnzbd/sabnzbd/acti ... 1512830592 (Requires Github account).

I would appreciate if you can test it and let us know what it says. There should be an info line which says Winerror:... after the normal error.

@nox and others in this thread: Puzzled's code with extra logging is in SAB 3.5.0 Beta2 (https://sabnzbd.org/downloads): "Print low-level Windows status error on IOError."
So can you install and verify? And post the extra logging when the Errno 13 occurs again.

I'm on vacation right now, I'll test and report when back.