I've never seen some like this before
I login as Admin
A file is not referenced to any file
All users close SW
Tried to move a file and kept getting error mesg
I've never seen some like this before
I login as Admin
A file is not referenced to any file
All users close SW
Tried to move a file and kept getting error mesg
Tested this on my system, if I have an assembly on another machine checked out and I move a part that's a component of it I get the same error. In this case you're moving a drawing which theoretically "contains" the part file, but in EPDM the reference can be treated as cyclical. The drawing contains the part but the part also contains the drawing, that's what makes drawings get marked as references in transitions, etc. So I'd say it's telling the truth and the 156368 sldprt file is checked out on another computer.
Another possibility is you somehow created an external reference in your part that references something from the drawing, but I'd have no idea how you did that...
In this case you're moving a drawing which theoretically "contains" the part file, but in EPDM the reference can be treated as cyclical. The drawing contains the part but the part also contains the drawing, that's what makes drawings get marked as references in transitions, etc
One of my engineer moved the 2D dwg to the Recycle folder (ok) but had trouble to move its part. I tried to login as admin and move the part and got the same error msg. I believe as long as the file is not checkout by any user, I can move it freely withing the Vault
I'd say it's telling the truth and the 156368 sldprt file is checked out on another computer.
I've asked all users to close their SW before moving the part and I double checked to make sure noone owns the file
possibility is you somehow created an external reference in your part
I double checked the part and there is no ref. file
Hi,
Try Undo Check Out - on Folder / Project- (from any computer, it is possible as Admin).
If does not help try - Unlocker. I usually so resolve this issue.
If the reason interests - that the reasons can be much, both local, and network.
Probably it is simpler to resolve this issue, than to establish the reason.
The hung-up notifications, tasks, add-ins, conditions, etc. can be the reasons.
Look at Log-s. Problems with SNL or with the rights of users are possible.
Of course, at the same time loss of some last modifications is possible - it is possible to look at history.
If necessary, in the history it is possible to make rollback or to save in other file.
Does the Where Used for the file show it as being used in a checked out assembly somewhere?