A newer version of this part is available since it was loaded in the session.

[ChaseWichert]

NX 7.5.5.4

Can someone explain to me why a file on my desktop, when I go to save it would be newer than than the one I currently have open in NX? It hasn't been changed while it has been open in NX but yet there is no possible way to save anything that I have done? This is becoming a big deal. Why doesn't NX lock files when they are open like every other software in the world (not sure if that is true but I have never run into this problem except for NX). I can't even 'save as', are you kidding me? Is there ANY way around this that will keep my parametric model in tact? And why does it happen? Also Export Part doesn't work.

Thanks,
Chase

 

[JohnRBaker]

I assume that you have more than one user accessing files from a common server, correct?

If this is the way that you're going to be working with NX then perhaps you need to invest in at least a minimum level of managed mode using the basic capabilities of Teamcenter. Please contact Siemens PLM or your local distributor to learn more about the options available to you and your organization.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[Toost]

Do you have some kind of backup system running ?
I think NX simply compares the date & time of the loaded file to the file in the session and if the date/ time is newer of the loaded file, then "beep".
You should be able to do a "Save As" when this message appears, if not, you should check if your session crashed for some other reason.

The good thing about the "non-locked" files is that if your session crashes -whatever, the file on disk is not affected.
I have seen quite a few Word-Powerpoint-Excel-etc files over the years that got corrupted when the program crashed.


Regards,
Tomas

 

[ChaseWichert]

I have no backup system running, I looked at the date modified, and it is the same exact file, I even opened the file up in another session of nx to look at the part history and they are exactly the same. No one has access to my desktop so no one else is modifying the files. This has happened more often than it should, once or twice, okay, but this is like the 10th time in a year. And why am I unable to save as when this error occurs? As far as I can tell it is impossible to save my file. If it is fully loaded into NX why can't I save it? It exists uncorrupted in memory, but yet I can't save it. I am looking at it, that is the most frustrating part.

 

[deedub777]

I had a similar problem many years ago and (long story short) there was an automated backup running that marked my files archived (or read only, can't remember). This may give you something to look into?

 

[ChaseWichert]

I will look into it about the backup thing. I don't believe that we have something like that on our computers. We have encryption software, but I was having this error before the encryption software was installed.

 

[looslib]

Is there a copy of that file somewhere that you may have stored at one time and then loaded that one?

BTW, if you really mean the files is on your Windows Desktop and you use roaming profiles, you are killing system performance. The file could be on some other computer's desktop as well as on a server that stores the roaming profiles. Storing files directly on the desktop is a very bad practice. Put them in a folder under My Documents and use a shortcut on your desktop if you MUST have it there for reference.



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

Ben Loosli

 

[ChaseWichert]

There is only one copy of the file. And one NX Session. The part history nor the modified date of the file show any signs of change. Also I am not sure when you mean by roaming profiles, but I don't believe we use roaming profiles. When I log onto someone else's computer none of my settings or anything follows, it is computer specific.