Define Working Folder - Maybe

[Anonymous]

So, I have a user who has the working folder set and enforced as everyone else here, yet when she performs a Get on files, she gets the error that she's unable to update file references because they are in a different working folder. But to a path that is obviously not within the set working folder. Much along the very same lines as this article:

"Cannot fix reference" when trying to download files which are out of the workspace of the Vault pro...

Problem is, everything checks out as it should. The working directory is set as it has been.

I'm lost for possible fixes, but still actively looking.....anyone?

[Anonymous]

Here's a few screen shots:

How Vault is set for all including this user:

And the path generated when performing a Get:

But when this user performs a Get, this happens:

So my question is, if it's set to be enforced as it is, then what is overwriting it and how do I fix it?

[CGBenner]

@Anonymous 

When was this working folder set?  Before or after those files were originally checked in?  If they were generated under an older Inventor project, at the path you are seeing in the Get, and the Working Folder was (at that time) set to match... Vault still might try to perform the Get to that location.  Are you able to override or get past this in any way... to enforce the new location?

Could it be as easy as grabbing the files in $/Inventor Projects and moving them up to $/_Vault? Maybe test this with just one file and see if it gets you past this?

[Anonymous]

@CGBenner this has been the setting since I got here as far as I am aware.

This just started happening this morning it seems, but darn good point.

I have yet to find a way to override this, but no luck yet.

The problem with grabbing and moving the files as you suggested and I thought the very same thing at first, but my understanding is (and correct me if I'm wrong) that moving files outside of Vault Explorer can or will break links.

[ihayesjr]

This sounds like an environment variable issue on this users machine.

I recommend that you check there.

Also, delete her Vault xmls from her profile.

[CGBenner]

@Anonymous I was suggesting that you make the move inside Vault Client.  I assume the enforced Working Folder location is probably above the folder location I see in the images above?

But it is valid to think there might be lost references if this is an Assembly, if you move the .iam and the parts are still under the wrong location.

I am way out of practice in these situations, so take my advice with a grain of salt.  That's why I suggest doing a test move in Client.  Maybe start with just a part file and then try a Get to see what happens?  I've seen before where a combination of moving things around in Vault Client and making changes to enforced working folders can really make a mess if it isn't done thoughtfully and with a plan. 

EDIT:  Start with @ihayesjr advice first!  LOL

[Anonymous]

@ihayesjr @CGBenner , done....waiting on report back.