Can't Save the NX5 part !

[jerry1423]

I have a part open in NX5 and I can't save it !

The file was accidently deleted by someone else, but thank goodness I have it open ... I should be able to save it (back in the good old days I could), but I can't.

Does anybody know what the problem is?

 

[JohnRBaker]

Try doing a 'Save As' and enter a different name.


John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[jerry1423]

I tried to rename it and then save again, but I get the following error:

The following part failed to save causing the overall operation to fail.
While saving oldpartname.prt : newpartname.prt File not found

I was able to salvage the part from a back-up a few days again (yesterdays back-up did not work) so it should be OK, but I still would like to find out what the problem is because I have seen it before.

 

[MSPBenson]

In my experience deleting a file you have open is a real bummer. You pull the rug from under UG's feet.
It seems to need the original file to save or save as.
The only option I can see is to export the whole part out to a new one as I don't think it would need the original file present to perform that operation.


Mark Benson
Aerodynamic Model Designer

 

[hudson888]

Jerry,

I am pretty certain that I have seen the same thing happen in earlier versions of NX. If you delete or rename a file while it is opened for editing then you can't save your data because the version on disk has changed (or disappeared) in the meantime. The trouble is that I couldn't reproduce the problem and that raises more questions for me than your initial post did. If it behaves differently from one version to the next or under different circumstances then I'm really quite curious as to the cause.

One thing I was able to find out is that office applications lock files for editing so that Windows won't allow you to rename or delete them while they're open for editing. I wonder why NX does not do the same?

curiouser and curiouser

Hudson

 

[realmagicracer]

Yeah! I've noticed that bug in NX 5.0.0.25. Sometimes I couldn't save the file.
When I've ugrated to 5.0.2 it doesn't apear... yet!

 

[ValBarber]

Same thing just happend to me yesterday, try this to resave the file, if you still have the file place it back where it used to be, same folder. I know this works for sure. Also you can attempt to create a dumb file save it with the same name as it used to be and same folder. This should work. Let me know!

 

[DavidTolsma]

I'm assuming it was fully loaded, Then doing a save or save-as should work. What version of NX5 are you using? sounds like a bug.

-Dave Tolsma
Tolsnet LLC

http://groups.google.com/group/NX_CAX/

http://groups.google.com/group/plm-exchange/

 

[Dave K]

"One thing I was able to find out is that office applications lock files for editing so that Windows won't allow you to rename or delete them while they're open for editing. I wonder why NX does not do the same?"

That is a feature I would like to see. Usually more than one of us is working on a project, so we could have the same assy open. It never fails that someone will accidentally hit "save" instead of "save work part only", and save a component someone else is working on.

I suppose Team Center, or some other PDM tool would work, but we don't need that with MS Office

-Dave

-Dave
Everything should be designed as simple as possible, but not simpler.

 

[DavidTolsma]

Pros and Cons to not having a lock on the file when it is being edited. For one thing if I opened the file(NX4) in NX5, it would be modified. Now the lock would be in place. This would potentially lock everyone from the ability to load the file in the assembly, since everyone will open the old file in the new file and essentially do a refile.

This is probably the same for overriding expressions, and any thing else that would mark the file as modified.

If you want to do this without a PDM, I would look into O/S locking the file. More administrative work. A cheap PDM system made of folders, and everyone copies the file they are working on into their sandbox, and all other files are readonly in the O/S.

-Dave Tolsma
Tolsnet LLC

http://groups.google.com/group/NX_CAX/

http://groups.google.com/group/plm-exchange/

 

[hudson888]

Dave,

Yes this has been mentioned before. Under Windows running in Native mode you can set up file permissions using "creator owner" which will effectively make most of the problems that you're likely to encounter go away. In other words unless you chose to delete you own files from under yourself then you're pretty much safe.

Teamcenter also locks the files in session. Which of itself tells you that in all likelihood it won't be fixed in native while it is evidently preferable to sell you teamcenter.

Best Regards

Hudson

 

[DavidTolsma]

Teamcenter locks the file from others saving, but they are free to modify. In Native you would be locked from even modifying if NX was to hold the lock on the file. That is one good reason for not locking files.

-Dave Tolsma
Tolsnet LLC

http://groups.google.com/group/NX_CAX/

http://groups.google.com/group/plm-exchange/

 

[hudson888]

Dave,

Not sure what you mean. Isn't to modify effectively pointless if you can't save? Also if you are using workflow in teamcenter and have ownership not just check in or out then only the owner should be able to do anything.

If I'm misunderstanding you then what modification would you wish to perform that you don't care to save? Is just for deformable parts and the like?

Regards

Hudson

 

[DavidTolsma]

Modify but can't save isn't always pointless. Many times components are modified without the user intending to by deformation (like you mentioned), opening in a newer version of NX, overriding expressions, Links load different versions of the components.

It is all sloppy, but it does happen a lot. I'm an advocate of refiling the parts when you run a new version of NX. So that all files are the same version. This would get rid of the new version of NX marking as modified. But depends on how the business decides to control the assembly structure it can happen a lot. The annoying warning message stating failed to save is from doing a Save All modified, which where modified.

Workflow in Teamcenter can be anything you want, Modify the ACL and the permissions can be opened or closed, anything you want.

Nothing should go through workflow if it is checked out.

-Dave Tolsma
Tolsnet LLC

http://groups.google.com/group/NX_CAX/

http://groups.google.com/group/plm-exchange/

 

[hudson888]

Thanks Dave,

Yes that all makes sense those modifications happen what we call "in session".

About nothing going through workflow of it is checked out. My understanding is that you may need to check it in create a workflow to assign it to, assign it and then you can allow the locks to set and unset themselves automatically, but nobody other than the item master owner will be able to lock those files. No more of the refesh locks stuff. In my experience refresh locks doesn't seem to work well most of the time. Using workflow enforces a bit more discipline, and takes to getting used to, but if you're having trouble with other users getting locks on your files it is certainly the way to go.

Best regards

Hudson