Hello,
We have had this issue now for a couple years and don't know what is causing it. We are using vault pro with admin set single project file. A user can work for months using correct.ipj, then randomly at 10:42 they will notice the active project was been changed to some other temporary project location "c:\temp.....". Then it will happen to different users at different times. I cant seem to find any correlation to anything. I can only imagine that it is somehow triggered from the vault addin.
Has anyone else had any experience with this issue? We are inventor 1012 and vault 2012 pro.
Thanks,
Jeremy
This sounds like a question that would be better presented to the Vault forums, and I suspect there are clues in your Vault server logs. Is it always at the same time that this happens?
http://forums.autodesk.com/t5/Autodesk-Vault/bd-p/101
Chris Benner
Inventor Tube & Pipe, Vault Professional
Cad Tips Tricks & Workarounds | Twitter | LinkedIn
Autodesk University Classes:
Going With The Flow with Inventor Tube and Pipe | Increasing The Volume with Inventor Tube and Pipe | Power of the Autodesk Community | Getting to Know You | Inventor Styles & Standards |Managing Properties with Vault Professional | Vault Configuration | Vault - What is it & Why Do I Need It? | A Little Less Talk - Tube & Pipe Demo | Change Orders & Revisions - Vault, Inventor & AutoCAD | Authoring & Publishing Custom Content
Hi Chris,
I was a little torn which place to post the question. But I ended up placing it here because the problem I actully see is with inventor changing inventor project file with out notice.
There isn't any rhyme or reason that we can find. My only guess is that it might get changed when a user opens a file from vault sometimes. But that is a complete shot in the dark, as we only have a single project for the entire company. So there really isn't anything recorded in the logs about the project file, unless an admin changes the default(i am on guessing on this one) Otherwise, no error is presented to the user until they go and try to check their files back into the vault and the addin isn't active because the project file was changed to a non vault project.
Lets see, if I don't get any bites here, i'll move it over to the vault side 😉 If nothing there, I will say hello to the support guys again lol
Thanks,
Jeremy
I have seen something like this before. It usually manifests when I go to the projects editor and it will pop up a message saying that it can no longer find the project called C:\temp\8g0csh0opd\whatever.ipj. Clicking OK makes it not search for this project anymore (which never should have existed in the first place). Then it usually sets the project back to Default, and we have to switch it back to our vault project.
I have no idea what causes this to happen, and it doesn't happen very often so it is hard to pin it down.
Just wanted to add my voice to this chorus so you know you aren't alone.
-cwhetten
That is exactly what happens. And it has happened enough times that I have told everyone to check the project file before they come ask me for anything.
I just forget about it sometimes and spend 30 minutes trying to debug something remotely only to find that it was this stupid problem 🙂 Was just hoping someone had some easy fix to prevent it. Nobody understands the project file anyway and they get really pissy when it somehow is preventing them from finishing a job lol
Thanks for backup 🙂
On our vault setup I created one vault project file for all my users. Then you can enforce the this project file so its the only one vault uses.
To do this go into vault as an admin
Tools > Admin > Vault Settings > Working Folder > Define
Enforce your working folder and project file as shown in the picture
This sovled alot of my vault project file problems
Hope this helps
Cheers
Chris Rodway
Design Engineer
Sheffield, UK
HI Chris,
I tried to mention this in the original post, but I guess it didn't come out that way. We are set up this way also. It is a good practice, but we still have the problem.
Thanks,
Jeremy
If its enforce on the vault it should always use that project file, the only other thing ive done with the project file when we were having trouble is ive checked it out to me.
This means no one can move or edit it apart from me
When I enforced my project file and checked it out this stopped all our project file errors
Cheers
Chris Rodway
Design Engineer
Sheffield UK
Chris,
You are exactly right. We have it enforced and the project is locked down and released. Nobody has permission to touch the file except admins. Which makes the problem even more mysterious.
Well hopefully Autodesk will see this feed and come up with some answers becuase
your vault is setup correctly from what you've said
I wonder if network latency has any issues, where a request exceeds the time allocation and it switches to the default settings.