NX7.5 Error when multiple users access same assembly
NX7.5 Error when multiple users access same assembly
(OP)
We keep getting an error message of "file not found" when trying to save a file in Native that is open by another user.
Has anyone else here run into this problem and/or know of a solution?
Has anyone else here run into this problem and/or know of a solution?





RE: NX7.5 Error when multiple users access same assembly
RE: NX7.5 Error when multiple users access same assembly
For example:
Person 1 working in file XXX which contains file YYY.
Person 2 working in file YYY saves file YYY.
Now person 1 is unable to save file XXX.
Does that make more sense?
And again this is in a Native environment.
Thanks for any help you can provide.
RE: NX7.5 Error when multiple users access same assembly
What is the exact error message you see when trying to save the file (there are several different warnings or error messages that may appear)?
RE: NX7.5 Error when multiple users access same assembly
AFAIK, the owner of the file is irrelevent if security settings aren't utilized.
"Good to know you got shoes to wear when you find the floor." - Robert Hunter
RE: NX7.5 Error when multiple users access same assembly
The suggestion for 'save workpart only' is also a good one.
I asked about the exact error message because I have seen messages similar to "save operation failed: XXX was saved but YYY was not". Be sure to read the fine print, the 'error' may not be as bad as it first appears.
The obvious answer here is some PLM solution, with Teamcenter as the primary choice. I assume you are looking for a low cost/free solution? I have heard of at least 1 free PLM system, but the setup sounded tricky and I'm unsure if anyone was offering support.
The system I was working on had all of the shared files on a linux server and we used Webmin to change the file permissions (take ownership) as necessary. Only the owner of the file could save it.
RE: NX7.5 Error when multiple users access same assembly
Anthony Galante

Senior Support Engineer
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.4.4, Beta NX8.0.0.23
RE: NX7.5 Error when multiple users access same assembly
I've attached a .pdf showing the error.
First error 1 appears (file in use by another process) when person 2 tries to save file YYY as in example above.
Then error 2 (file not found) appears after person 1 close out the file without saving and person 1 tries to save again.
Thanks again for all your help.
http://f
RE: NX7.5 Error when multiple users access same assembly
I'll just say thats the situation we are stuck with at the moment.
I will try the update mentioned above and see if that helps us out also.
Thanks again to all.
RE: NX7.5 Error when multiple users access same assembly
Anthony Galante

Senior Support Engineer
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.4.4, Beta NX8.0.0.23
RE: NX7.5 Error when multiple users access same assembly
Reopen YYY in assembly XXX and then XXX should save.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: NX7.5 Error when multiple users access same assembly
RE: NX7.5 Error when multiple users access same assembly
They are only open. There is not a new version of either file saved.
Part YYY is only opened by person 1 because its a component of the top level layout (XXX). We often open the layout just to see interfaces between subassemblies. So there would be no need to save XXX at that point. But simply having it open prevents others from saving their subassemblies.
RE: NX7.5 Error when multiple users access same assembly
Update to NX7.5.4 on all your systems. Then test again. If you still have the error report it to GTAC because it is not fixed in your case. If my memory serves it to do with facet loading and was the problem first appeared in NX7.5.2.
Anthony Galante

Senior Support Engineer
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.4.4, Beta NX8.0.0.23
RE: NX7.5 Error when multiple users access same assembly
I'm working on getting the updates rolled out for us to verify that it solves our problem.
I was just adding clarity for those that where still questioning the errors.
I will post back after the updates.
Thanks again for your help.