Vault duplicates folders - Help!!!!

[Anonymous]

OK, I'm starting a new thread due to this issue coming up under another thread on a different matter and feel it needs it's own.

Here's the original thread for the back story so I don't have to rehash everything:

http://forums.autodesk.com/t5/vault-forum/default-inventor-project-filer-error/td-p/6817772

So here I am today and I now have at least 2 systems this is happening on, possibly more, just haven't had the chance to verify such.

But in a nutshell, what's happening is if a user performs a "Get" on a file that is already located in Vault, it not only duplicates the folder structure (which is what it's supposed to do), but it recreates the folder structure that is already in place on the users HD.

For example (and as you'll see in the screen shots in the above link), their working folder is set and enforced to: C:/VaultWork

But when they perform a "Get" for a file that's in Vault it creates: C:/VaultWork/VaultWork/"job folder".

It recreates the "VaultWork" folder for some odd reason.

Now, let me add to that that this morning I attempted this on a different machine and performed a "Check Out" on a file, not only did it create the extra "VaultWork" folder, and the subfolder for the job, but it NEVER brought down the file. It just created the folder the file is in in Vault.

WTH?

I've tried everything that was suggested in the above link and contacted some of my very knowledgeable Vault people and we are all stumped.

Never seen anything like this in all the years I've been using Vault.

So at the moment I'm doing a complete reinstall.

Can someone from Adesk chime in and help me on this?

[Anonymous]

Oh it gets even better.

Since everything seems to work fine on my station and my admin log in, I logged in as Admin on a users station and performed a "Check Out" on a file, then checked it right back in. In the "Check In" dialogue box it showed the folder structure as it "should" be (VaultWork/"job folder").

So for a moment I thought, "great! looks like it's a user id issue", but nope.

Checking the local HD, it created the folder structure of "C:/VaultWork/VaultWork/"job folder" again.

So here's my question, if the dialogue box shows the file was placed on the HD in the correct location upon checking it back into Vault, why in the world does it actually locate it somewhere else (aka the extra "VaultWork" folder)?

[Rob67ert]

Hi,

What do you have on the virtual Folder in you ipj file?

Do you use only one ipj file that the users get form the Vault?

[Anonymous]

Robert,

Thanks for the reply.

Always use just one .ipj file, makes things a whole lot easier for everyone.

Here's a screen shot of the .ipj settings:

[Rob67ert]

Well some do use many ipj's 🙂
Change you vault Options form $/VaultWork to $
I had the same problem ones.

[Anonymous]

---

@Rob67ert wrote:
Well some do use many ipj's 🙂

NOOOOOOOOOOOOOOOOOOO......LOL. I've had some very spirited & heated, yet friendly "discussions" with Adesk on multiple vs single .ipj files.

Change you vault Options form $/VaultWork to $
I had the same problem ones.

I was told to do such at first (always had the .ipj down one level from root without issues - until now) and locating it root caused a whole 'nother ball of wax, so I moved it back one level down.

But thanks to a former co-worker who's on the boards here (take a bow Mark), I think we've stumbled on the issue, just not sure why or how it happened.

RMB on the details of the working folder I got the duplicated "VaultWork" folder listed (sorry, the screen shot was after the change)

I then went in and unchecked the "Enforce working folder" option and the "Enforce project file" options.

Mind you, these values never changed, these were just as you see them here. Anyways, once I unchecked these, I changed the "Working folder" back to as you see it in the above screen shot. Not sure why it would change, but I'm hoping that's all it was.

I'm now going to test this on the users station and I'll report back the results....fingers crossed.

[Anonymous]

SUCCESS!!!!!!

Not sure why the working folder would be set to the double directory as it was (even stranger, it was set to the double directory on my station, but worked fine), but once I went around to each users station and changed the working folder to what it's supposed to be and set the enforcement again, all seems to be working fine.

Props go out to my friend and former co-worker, Mark Flayler (but I'm taking credit for the solution here....LOL....;)

[mflayler]

Happy to help. 🙂

[Anonymous]

Ugh...my joy was short lived.

As soon as the user, including myself, logs out of their Vault session and logs back in:

The Working Folder resets back to the doubled folder structure.

[Anonymous]

OK, for whatever reason Vault seems to be going back to the Default folder location at each new session. For whatever reason that folder is the aforementioned "C:/VaultWork/VaultWork" folder. No idea where or how that was created but either way, how in the world do I STOP Vault from resetting back to this folder at each login? Remember, I have the Working folder Enforced to the C:/VaultWork folder. Where  is the override that is ignoring that enforce setting?

[Anonymous · Accepted solution]

Fixed!!!! Again.

Stupid mistake on my part as usual, I was thinking one folder too few. My "VaultWork" folder under the root, should be named "Designs" (or the like).

So far, so good, whether I start a new session or not.

Again, Thanks to Mark Flayler for getting me on a webex to resolve this.

[Anonymous]

Hi Mark

The default folders have been renamed but the issue persists. Something else amiss?