Part changed on disk error after using Save as

[mtglass]

For some reason, and only on one of 3 tubes, I get a "part changed on disk" error the first time I save after executing a "save as". I have to close the file, then reopen it before I can do a regular save. It's a PIA. Any ideas how I can fix this issue? TIA

It does the same thing NX2 thru NX4, but only on one machine?

Mike

 

[DavidTolsma]

Are you saving this file on a remote storage or another machine for that matter? Sounds like your clock may be out of sync on that one machine.

-Dave

http://plmwiki.com

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

 

[mtglass]

You are right. The files are not saved locally, and the clocks are not in sync with the server. I'm 1 minute faster than box A, and 7 minutes behind box B, and neither of those has the same issue as mine (box C). I've also been told that they've tried rolling box C ahead 5 minutes and also back 5 minutes, and it still does the same thing.

 

[DavidTolsma]

Perhaps the network speed is causing some issues. What is your network speed to the server vs the other machines? Sounds like when you do a Save As it is recorded on the server as a future time.

I think there was a setting in the customer defaults for this but not behind NX right now to tell you for sure where it's located.



-Dave

http://plmwiki.com

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

 

[mtglass]

Slightly different devices and drivers but all 100Mbps...

 

[DavidTolsma]

actually do a traceroute or at least a ping test to see if there is a latency. Maybe a wrongly configured network card. Just trying to rule out variables at this point.

-Dave

http://plmwiki.com

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

 

[mtglass]

Server is actually 13 minutes behind, and Linux FYI. 2 Workstations are Windows 2000, and one is XP 64bit.

 

[DavidTolsma]

Try a search in the customer defaults for time

-Dave

http://plmwiki.com

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

 

[mtglass]

I'll check the network as you suggested, but what is the "customer defaults" you mentioned? Is that in a pull down menu, help, online or what?

 

[DavidTolsma]

File -> Utilities -> Customer Defaults

-Dave

http://plmwiki.com

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

 

[mtglass]

OK, So far I've updated the network device driver, NG. Installed and ran a repair utility from Dell - NG, sync'd the clock with the server and it's still NG. I tried saving to a different physical drive on the server, and that didn't work either. Pinging the server from any of the machines gives me the same result. I tested saving to a shared folder on another machine, and that worked! So it's between this machine and the server only. I saw what you meant under "customer defaults" But they are the same on all the machines, and the same even in NX4. How would I change the defaults to avoid this anyway? Thanks for you help.

 

[DavidTolsma]

I thought I remember seeing something regarding the ignore save new part message in the customer defaults, maybe just a dream.

Does these parts have WAVE or interpart expressions in them? Are they assemblies? If so, is the load interpart expressions delayed or not? Is the load options for assemblies set to fully load, etc...

Worst case is you create a new user on the machine and try the save as. If that fixes it, then the user settings is effecting it somehow.

-Dave

http://plmwiki.com

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

 

[hudson888]

Mike,

What networking protocol are you using between the server and workstations? Between Linux and NT/XP most people use Samba. I suspect that Samba may not prefer the same settings when using windows 2000 as per XP. Can we assume that the XP box is having the problems and the two that work are windows 2000. If so you may have to update you networking software it may predate XP64bit.

When XP was introduced there were problems with XP stations on regular NT/Win2000 based networks. If you are using a windows emulator, (like Samba) on your Linux machine, then it may be behaving like our windows servers did at the introduction of XP. Hopefully your IT guys keep you up to scratch with Windows updates, beyond that your networking protocol is the likely culprit. I am guessing at this one because this was a fair while ago, but since your talking Win2000 I guess you could be having a delayed occurrence of this sort of thing compared to some.

BTW in the past we used software other than Samba, whereby the networking was done by the Windows machines. We found that there were timing issues between machines with that technology. A couple of years have passed so newer versions may have improved. The issue was that the Windows machines were trying to emulate Unix by converting the file formats to and from the different protocols and passing data back and forth across the network. That's when we switched to Samba, because it makes Linux emulate windows without translating the files so to speak.

Also many versions of Linux if hooked up to the internet will set the correct time automatically on boot. Some utilities are available for Windows to keep the clocks correct. It is not usually strictly necessary to have all machines on a network strictly in exact sync.

Samba like Linux is open source (free), if you aren't familiar.

The error message you describe is not what I'm familiar with when wave links are the problem, rather you would see a modeling error dialog.

Last but not least change only one thing at a time as you try to improve the situation. I note also that most of what I suspect may be the problem has everything to do with anything but UG, so keep and eye out for other posters of this forum who may have some other ideas involving any UG settings that I'm unaware of.

Hope this helps

Good Luck

Husdon

 

[mtglass]

I'll pass along the info to IT, but I want to correct myself first. 1 box is 2000, 1 is xp64 and the one with issues is xp. I get this issue regardless if it's an assembly or not, or if it's wave linked or not. I think I'm headed in the right direction. If you come up with any more suggestions, let me know. Likewise, when I get it resolved, I'll post the fix here. Thanks again all.

Mike