Serious Error - old version could not be found...

[dan_butler_komatsu]

We often get a Serious Error that states:
"File C:\_Workspace\...partnumber.iam version 367 could not be located at the given parth nor at C:\_Workspace\...partnumber.0367.iam"

(Version 367 is only an example)

This error kills Inventor - we cannot save the assembly and must exit out of Inventor and bring it back up again. One person says that he lost several saves because of his error, at least on his top level assembly.

It is unclear to us what causes the problem, I have seen it happen when undoing a checkout from the Vault... or in our most recent case as of today, it was just changing the value of a constraint.

For some reason, Inventor tries to access the old version file -

Just wondering if anyone else is having this problem or if Autodesk is aware of it. I could not see it in the knowledge base.

See attached files

[Anonymous]

It is caused from doing a "get latest" from Vault Explorer with the files
open in IV.

You may have to ultimately delete the local file(s) and do an open from
Vault to get a proper working file back into your local workspace.

QBZ



wrote in message news:5247822@discussion.autodesk.com...
We often get a Serious Error that states:
"File C:\_Workspace\...partnumber.iam version 367 could not be located at
the given parth nor at C:\_Workspace\...partnumber.0367.iam"

(Version 367 is only an example)

This error kills Inventor - we cannot save the assembly and must exit out of
Inventor and bring it back up again. One person says that he lost several
saves because of his error, at least on his top level assembly.

It is unclear to us what causes the problem, I have seen it happe
n when undoing a checkout from the Vault... or in our most recent case as of
today, it was just changing the value of a constraint.

For some reason, Inventor tries to access the old version file -

Just wondering if anyone else is having this problem or if Autodesk is aware
of it. I could not see it in the knowledge base.

See attached files

[dan_butler_komatsu]

The user got the latest from the Vault at 5:30 AM today, and did not get the error until 10:45 or so. He did not get anything else out of the Vault between those times.

Could there also be another cause?

When the error occurs, we just exit out of IV and it works fine.

[Anonymous]

That almost makes sense. You mentioned "undo checkout".

If you did a "get latest" then undid the checkout, you would be missing a
version if the component was saved at some point.

If there is another "documented" cause, it would be good to know about it.

Is it possible that the component was perhaps checked out by another person
but the local file was overwritten somehow?

Stuff like this makes people who are trying to give Vault an honest try go
freakin ballistic.

QBZ


wrote in message news:5247858@discussion.autodesk.com...
The user got the latest from the Vault at 5:30 AM today, and did not get the
error until 10:45 or so. He did not get anything else out of the Vault
between those times.

Could there also be another cause?

When the error occurs, we just exit out of IV and it works fine.

[Anonymous]

I have seen this error, though very rare, and we don't use vault here. The
only thought I had was it might be a hiccup in the network connection at the
point of save. I really have no idea whatsoever though.

--
Do infants enjoy infancy as much as adults enjoy adultery?
-------------------------
IV 9 SP4 No extra Hotfixes
Win xp Pro SP2
Amd 3800 64 Bit
2 Gig Ram
Nvidia FX1000 7756driver
-------------------------
Corey Parks
Design Engineer
Metro Machine & Engineering Corp.
Eden Prairie, MN
cparks(A-T)metromachine(D-O-T)com

"Quinn Zander" wrote in message
news:5247874@discussion.autodesk.com...
That almost makes sense. You mentioned "undo checkout".

If you did a "get latest" then undid the checkout, you would be missing a
version if the component was saved at some point.

If there is another "documented" cause, it would be good to know about it.

Is it possible that the component was perhaps checked out by another person
but the local file was overwritten somehow?

Stuff like this makes people who are trying to give Vault an honest try go
freakin ballistic.

QBZ


wrote in message news:5247858@discussion.autodesk.com...
The user got the latest from the Vault at 5:30 AM today, and did not get the
error until 10:45 or so. He did not get anything else out of the Vault
between those times.

Could there also be another cause?

When the error occurs, we just exit out of IV and it works fine.

[Anonymous]

Was anybody else using (even if "just reading") the file in question?

Another possibility is that somehow the "Old Versions" folder is being deleted / modified from underneath the user who has the file checked out. Is your "local" copy of the vaulted file actually on a "networked" drive? If so, when another user opens the file in question and modifies / saves it (or manually deletes the Old Version folder / file) it could be deleting the version of the file the first user needs, particularly if you don't have your project set up for infinite old versions. Although you could still run into problems if somebody saves it from under you, causing a problem because the version you have open would no longer be the most current version.

I agree that it's all pretty convoluted, but this is just one of the many reasons why I think the "local" vault workspace should be an isolated area for each user. I like "C:\Vault" and make sure the local drive is not shared. Or for those paranoid about data loss, you could give each user a networked folder to which only they have write access. Personally I'd also give them sole read access with the exception of the administrator, but that's because I'm a fanatic about siloing checked out data - had too many bad experiences.

Good luck!

Glen

[Anonymous]

I had this happen the other day on a part I was trying something new out on. I saved the test part to the desktop (so i could do something that required it be saved, but i forget what). then it started giving me that error. I looked at the desktop and there was no OldVersions folder. At some point I think i had rmb on the file at the desktop to find the file size, and i *may* have done something odd to it by accident.

so, it happened to me with no network and no vault.

-barrett