NX7.5 Error when multiple users access same assembly

[jrgrove]

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?

 

[cowski]

Who has ownership of the file? Only the owner can/should save the file.

 

[jrgrove]

Only one person is attempting to save, the second person just has the file open working in a subassembly.

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.

 

[cowski]

The question of file ownership remains. Even in a native environment, someone 'owns' each file. To see this information, open a file explorer window, open the folder of interest and change the view to 'details'. In the header row, right click and choose the 'owner' option (if it is not already checked).

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)?

 

[ewh]

While I have seen this problem the other way around (person 1 saving XXX, thus preventing person 2 from saving YYY), I have not yet come across your exact situation.
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." - [small]Robert Hunter[/small]

 

[cowski]

The owner of the file is irrelevent if the security settings aren't utilized.

This is a good point. I was thinking back to my time on 'native', but we did have access to the security settings. The system in place was easily defeated, but was still slightly better than a truly native setup.

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.

...know of a solution?

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.

 

[Arkance/PhoeNX]

Update to NX7.5.4. This may be the known bug, that was reported as fixed in the NX7.5.4 Maintenance Release.


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

 

[jrgrove]

The owner is a 3rd user who does not currently have the file open.

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://files.engineering.com/getfil...291-408b-8e42-edd44c119737&file=UG_Errors.pdf

 

[jrgrove]

Thanks cowski, the free plm option would basically be our only hope due to budget cuts/constraints. Even then it would be a stretch getting approved for the time get up and running.

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.

 

[Arkance/PhoeNX]

Those error messages fit the PRs that I have logged for my customers and have been reported as fixed in NX7.5.4. Try the update to see if it fixes it.

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

 

[looslib]

Person 1 cannot save XXX becasue there has been some change in memory to the YYY file that Person 2 saved. The system trys to save the XXX AND the YYY file, but it can't because YYY is newer.

Reopen YYY in assembly XXX and then XXX should save.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[cowski]

When you hit 'save', NX will try to save any parts you have open that have been modified. In this case it tries to save XXX and YYY; YYY fails because someone else has it open and has modified it. XXX is saved, but the overall save operation failed because it was not able to save all modified parts.

 

[jrgrove]

Neither file XXX nor YYY have been saved by person 1.

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.

 

[Arkance/PhoeNX]

i don't know why i bother posting if people don't read. The problem that jrgrove is experiencing is a known problem and is reportedly fixed in NX7.5.4. I had a customer who had the exact same error messages. I was able to replicate the problem on my systems. We logged it to GTAC and were told that it was fixed in NX7.5.4. I have since tested after the MR release and problem is gone.

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

 

[jrgrove]

Thank you namdaci45.

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.