Multible bugs: DoPhysicalFiles - Access to the path was denied. (translated version, english version may be differnt)Also my files are still available in the file vault! I even can open them when selecting them in the ItemType File. In my case, the delete problems are caused by security settings in the file vault itself. 1. Go to your file vault and search a file 3. Select the File -> right click -> Properties 4. Go to the
Securitytab 5. Take a look at the
Group or user namesbox A regular file where everything is ok will contain a "Aras Vault AppPool ASP.NET 4.0" in the Group or user names box A corrupted file doesn´t contain the "Aras Vault AppPool ASP.NET 4.0" user. Instead a local users (in my case it´s myself) is set. Maybe it´s possible to restore the security settings for the complete File Vault. I didn´t fix this yet as only a small number of files was affected. Hope this helps. Angela
When you have to use a URL, you propably have to chance the user credentials parameter in the Vault config to get direct access. Then your URL have to look somehow like this: myplm/.../vaultserver.aspx You can build your url string with the filename and id property of the File item.
Innovator inn = this.getInnovator(); string path ="E:\\Aras\\MyVault\\MyDB\\A\\06\\123348FBF4AB2A5B12B53EB0933B7\\MyFile.txt"; var x = File.Exists(path); return inn.newResult("File exists: "+x);
are you still doing PLM? I right now face the same issue that you had 5 years ago.
I get the same error message. Certain physical files have been removed from the Vault, but they still appear in the "File" table.
I would prefer to clean up the wrong entries in the "File" table, but don´t want to erase the data directly in SQL.
One idea I currently have is to rebuild the missing folder structures with fake files and then finally delete them again.
But I wonder if you have found a more elegant solution?
Thanks and best regards!
If anyone else knows a good solution to this one, please let me know!!!!!
Solved it! I didn´t skip the problematic files entries, but repaired them so I finally was able to delete them like regular files.