cancel
Showing results for 
Search instead for 
Did you mean: 

"A folder with the same name already exists"

Elio_C
Level 6

Hi,

I had an associate get the "A folder with the same name already exists" when trying to delete an item from their local Vault Cache.

I followed https://www-secure.symantec.com/connect/forums/error-when-deleting-itemsfolders-virtual-vault and renamed the Deleted Items folder and hey presto everything works.

Anyone understand what is happening and why would the rename helps?

Thanks,

(EV10.0.4, v10.0.4 Add-in, Windows 7, Outlook 2013 which is very different than the original post so this issue doesn't appear to be version specfic)

1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified

I've seen people created Deleted Items folder themselves or move the \deleted items folder from somewhere else, and its not being picked up as the true \Deleted Items folder (the icon looks like a regular folder, not a trash basket)

so that when you delete the item, Outlook doesn't see that it has a proper deleted items folder, tries to create one, and thats when the mapi collission comes around

Really though you'd have to look back through the client logs to find when the \Deleted items folder was created, but client logs only stick around for 5 days

https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

2 REPLIES 2

JesusWept3
Level 6
Partner Accredited Certified

I've seen people created Deleted Items folder themselves or move the \deleted items folder from somewhere else, and its not being picked up as the true \Deleted Items folder (the icon looks like a regular folder, not a trash basket)

so that when you delete the item, Outlook doesn't see that it has a proper deleted items folder, tries to create one, and thats when the mapi collission comes around

Really though you'd have to look back through the client logs to find when the \Deleted items folder was created, but client logs only stick around for 5 days

https://www.linkedin.com/in/alex-allen-turl-07370146

Elio_C
Level 6

Sounds plausible to me and makes perfect sense too, we have seen a huge amount of old PST/NSF/other archive imports so we are bound to get some "incorrect" folders.

Verified using "http://EVSERVER/EnterpriseVault/GetArchiveFolderHierarchy.aspx?archiveid=" and as noted renaming the folder to NOT "Deleted Items" fixes the issue.

True Deleted Items Folder (FolderIcon=4)
  <Folder FolderIcon="4" ExistsInMbx="0" IsDeletable="1" Deleted="0" IsManaged="0" FolderName="Deleted Items" VaultEntryId="xxxx" />
Fake Deleted Items Folder (FolderIcon=0)
  <Folder FolderIcon="0" ExistsInMbx="0" IsDeletable="1" Deleted="0" IsManaged="0" FolderName="Deleted Items" VaultEntryId="xxxx">