"Multiple Errors: DoPhysicalFiles - Access to the path is denied. " when deleting files. What permission shall I use?

Hi community,

I want to delete some orphaned files in the File Vault. We don´t use the "delete automatically" variable. I am able to discover the affected files in the file vault.

But when I try to delete one orphaned file manually in the File ItemType I get the following error message:

Multiple Errors: DoPhysicalFiles - Access to the path is denied. -

I assume I have add an additional permission to the Vault-folder structure in the File vault. But which one shall I use?

I remember I added one additional permission in the past on my old MS Server 2012. But I didn´t use the setting on my new 2022 instance. I assume I used "IIS_USRS" or similar in the past. But I never knew if this was the "correct" permission to use.

Does anyone know the "official" solution for this one? 

Thanks and best regards!

Angela

Parents
  • Hi community,

    after an eternity I finally build a PowerScript to repair the wrong permissions. 

    The issue itself was trivial and caused by moving the Vault Server to a new Server instance. For previous files, the permissions weren´t set correctly and only new files used the correct Vault AppPool permission.

    So the permissions are correct now I can can cleanup the orphaned files. But I run into a new problem. Some years ago we had a few minor stability problems with the server, so in rare cases file uploads failed. I can literally tell the 3 days in 2019 where File Upload didn´t work as expected. In this case, users simple reuploaded the files and everything was fine.

    But the previous invalid file uploads now lead to problems when I want to cleanup this orphaned files automatically. The files appear in the "Files" database table, but do not physically exist in the file vault. When I want to remove the files, I get an "DoPhysicalFiles [..] (500) Internal Server Error" error message. 

    A possible fix is to rebuild the missing Vault folder with a fake file. But doing this for a unknown amount of files (I expect 50..) is a bit painful when doing it manually.

    Does anyone know a simple way to check, if a file listed in the "File" database  exists physically in the File Vault? I know that previous users have build something like this already and I would be happy if I don´t have to start from the scratch :D

    Thanks for any help!

    Angela

Reply
  • Hi community,

    after an eternity I finally build a PowerScript to repair the wrong permissions. 

    The issue itself was trivial and caused by moving the Vault Server to a new Server instance. For previous files, the permissions weren´t set correctly and only new files used the correct Vault AppPool permission.

    So the permissions are correct now I can can cleanup the orphaned files. But I run into a new problem. Some years ago we had a few minor stability problems with the server, so in rare cases file uploads failed. I can literally tell the 3 days in 2019 where File Upload didn´t work as expected. In this case, users simple reuploaded the files and everything was fine.

    But the previous invalid file uploads now lead to problems when I want to cleanup this orphaned files automatically. The files appear in the "Files" database table, but do not physically exist in the file vault. When I want to remove the files, I get an "DoPhysicalFiles [..] (500) Internal Server Error" error message. 

    A possible fix is to rebuild the missing Vault folder with a fake file. But doing this for a unknown amount of files (I expect 50..) is a bit painful when doing it manually.

    Does anyone know a simple way to check, if a file listed in the "File" database  exists physically in the File Vault? I know that previous users have build something like this already and I would be happy if I don´t have to start from the scratch :D

    Thanks for any help!

    Angela

Children
No Data