hen trying to create a new folder in the ePDM vault, i get the error "New Folder" already exists. Does anyone know what could be causing this? There is no folder named "New Folder".
Are you sure that folder does not exist? Perhaps you simply do not have read access to the folder? Check in the administration tool to see if you can find it.
Yes, I'm sure it doesn't exist. When I right click in the vault view and select ->New->Folder, the default name Windows gives the folder is, "New Folder". I rename that to... in my case, "NPO", which all works fine for the first folder. So, for all appearances I have just created a new folder named "NPO", but then I attempt to create another folder parallel to that one by right clicking again and when Windows attempts to create the folder temporarily named "New Folder", I get a conflict that this folder already exists and it won't let me create any more folders at that level, because it thinks "New Folder" already exists, even though it is actually named "NPO". Really weird and a MAJOR issue. It is happening at all levels of the folder structure in that vault. Other vaults in the ePDM instance don't exhibit the same behavior. It is something particular to that vault.
What can you see when you also enable the local files? On top of your user on admin tool, right click, select "settings", go to "explorer" and from "File types to show" select "Show all files"
Maybe the New folder is local file? (Gray). But when you said it's on all levels, does your user have read&write -rights to the root folder of PDM (on windows side, not PDM)
Make sure you have all permissions to see folders/files in that state/workflow/etc. Right click where the file issue is, properties, deleted files. Destroy any files/folders with the same name. Then "work offline". Tools: Work Offline. Go to the folder you are trying to add it to. Delete the local cached folder/files with the same name (if it is empty and OK to delete). Then try to add after going back online. That works for me when I have those "file already exists" issues.
It is likely you have set the vault not to allow duplicate folder names (which is fine), and I assume you have already searched the vault for a folder named "New Folder" with the search tool.
This is an expansion of Jason Spansel's answer.
However, when you delete a file or folder it is not destroyed from the vault, so the name still exists in the vault, even if the delete function has moved the local file to your recycle bin.
To find if this is the case - log on to the vault as admin - go to top level vault folder - right click on folder and choose the deleted items folder, make sure to tick box at bottom for "include items in sub-folders".
- then you will see all files ever deleted but not destroyed - probably many more that you think and probably containing a deleted folder called "New Folder".
You can choose to destroy files permanently form this window, but be aware that if you are admin, all will be deleted permanently and may break other assemblies that use these files - it is better to get original user with limited user rights to destroy the files themselves.
If you are deleting files as a normal user like me, then perhaps you should hold the shift key down while pressing delete - this does delete and destroy in one step (just like windows explorer), but of course there is not going back - it is permanent delete, and the file and filename is gone from the database. We set our users up so that they can only delete and destroy if the file has not been into the release state so these users are protected from deleting files needed in customer releases of drawings.
Retrieving data ...