topic Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File in Vault Forum

Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

Anonymous — Mon, 28 Sep 2020 22:05:39 GMT

I have a remote user who VPNs into our system to be able to generate and check in parts, assemblies and drawings for us.

Our support data (templates, design data, materials) are all located on a network drive folder and the Vault Project file points to this folder. My user has been given permissions on this folder. He can see and access this folder when using Windows Explorer. However, when he sets the Vault Project, it creates an empty duplicate of the folder within the folder and none of the pertinent information is available to him from within Inventor.

Does anyone have any ideas?

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

gandhey — Tue, 29 Sep 2020 03:33:45 GMT

Hello,

Can you provide the snap of the Vault project file with the folder information for templates, design data etc. ?

This sounds more like project file issue (Inventor related) than related to Vault.

Hi @johnsonshiue , any hint here please ?

Just to confirm :
You see the issue only for VPN user who sets this project ipj file in Inventor and not other users ?

Regards,

yogeshwar

(Vault team)

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

ihayesjr — Tue, 29 Sep 2020 13:49:04 GMT

The VPN user should use the Project File that is already in Vault or the one that is used by users on the network.

The most likely cause of the problem is the location the VPN user is saving the project file and the workspace mapping.

This could cause the problem the VPN user is experiencing.

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

Anonymous — Tue, 29 Sep 2020 14:03:18 GMT

Below is a clip of the project file...what ends happening for my VPN user when he sets the project is a duplicate folder gets created in the N:\Inventor Support Data folder called Inventor Support Data. That duplicate folder has an empty \MHC Templates folder and an empty \Design Data folder rather than referencing those folders that already exist with files in them a level up.

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

Anonymous — Tue, 29 Sep 2020 14:05:15 GMT

The VPN user is using the same project file as everyone else. I even had him get the .ipj again. I was able to watch the creation of the duplicate folder in realtime as he went through the process of setting the project file.

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

ihayesjr — Tue, 29 Sep 2020 14:21:17 GMT

Have the user open the Vault client and take a look at what they have set for the working folder inside of Vault. It could be different then what it should be. This is done by right-clicking on the Project Explorer($) and click Details.

Sorry, I am confusing issues. This doesn't have anything to do with the Vault working folder. I will have to see if someone from the Inventor team could help.

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

GunnarNilsson — Wed, 30 Sep 2020 07:01:55 GMT

Did you see those extra folders being created at drive N: at a computer at the office or directly on the vpn connected computer? What I'm getting at is maybe N: is mapped one folder down on the vpn computer compared to the computers at the office. That would cause this behaviour.

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

Anonymous — Mon, 05 Oct 2020 16:32:15 GMT

Interesting thought. I've bumped that question over to our IT service as they set up the mapping. I'll update as I find out more.

Re: Vault Basic Generating Duplicate Folder Structure when VPN User Sets Project File

Anonymous — Tue, 06 Oct 2020 16:26:29 GMT

Turns out this is exactly what the problem was. My user was mapped incorrectly. Once I was able to get IT to map him up a level, everything worked as it should.

Thanks for the assist.