I have seen this behavior before.
My conclusion was the folder is a locally cached copy of the folder the user had permissions to view using Windows but when entering through the EPDM interface causes EPDM to try to manage the viewing which throws the error.
Here is the reader's digest version of my current understanding on how the navigation works. Others may know significantly more about this so they can add to this if needed:
- When the user entered through "Windows Explorer", Windows explorer was managing the interface when the user clicked the old shortcut so whatever folder permissions the user has "in Windows" are active. This activity is not on EPDM's radar.
- When the user entered through EPDM (pasted the path into EPDM), the Windows explorer interface is taken over by EPDM so the user has a virtual interaction with the files and folders and navigation to the folder is not allowed since the folder no longer virtually exists.
Sort of like working offline...but not completely.
Hope this helps.