Cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Re: NX freezing with "Updating objects..." message

Valued Contributor
Valued Contributor
Back on topic, since switching to history-free mode did not help in another assembly. The older project.
I have the logs of a problematic and normal operation and those are exactly the same.
Opening it on another workstation (same spec hardware) it seems to work much faster, but the problem is still apparant.
- The logs are exactly the same.
- Subassemblies are fine, components are problematic.

Re: NX freezing with "Updating objects..." message

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

If it was Teamcenter, I'd blame a corrupt cache, but you don't say you use Teamcenter.

I believe load options are logged in the syslog, so it isn't that.

I am *assuming* both users/computers have full read access to the folders/files.

 

Could be the registry or user.mtx or... is corrupt?

 

With the user who has problems logged on:

- Exit all NX sessions

- Using regedit, rename the key HKEY_CURRENT_USER\Software\Unigraphics Solutions\NX\(your version)

to something else

- find where the user has their user.mtx file (typically C:\Users\(username)\AppData\Local\Siemens\(your version) - rename that folder as well

 

- Then try restarting NX & opening the assembly

 

Another option is see if the "bad" user's "temp" folder(s) have lots of files (100s or 1000s) - try deleting all of the files/folders in their temp folders (NOTE: have the user log off, then log back on, and DO NOT start any applications.  Clean up the folder using DOS commands so it keeps going when it encounters files it can't delete.  You really should NOT delete temp files while applications are running)  I have seen cases where cleaning up temp folders clears a problem.

 

Hope one (or more) suggestions helps...

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: NX freezing with "Updating objects..." message

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

How old are these model files? Have they ever been saved since you moved to NX 8.5? I ask because when NX opens a file saved on an older version, it 'converts' it to the new format behind the scenes. If these files are several versions old, you might consider using the 'refile_part' utility to bring them up to the NX 8.5 format; especially if you are using lightweight representations in the assembly.

 

Also, consider using 'ug_inspect' to scan for file corruption and use the 'examine geometry' command to look for any corrupt geometry within the part.

Re: NX freezing with "Updating objects..." message

Siemens Honored Contributor Siemens Honored Contributor
Siemens Honored Contributor

1) Assembly Load Options:

  • Load: All Components
  • Use Partial Loading - unchecked
  • Use Lightweight Representations - unchecked
  • Load Interpart Data - checked
  • Load Parents: All Levels

2) Load the assembly

3) Tools > Update > Update for External Change

4) Tools > Update > Interpart Update > Update All

5) Part Cleanup

  • Part: Work Part and Components
  • Moderate Cleanup Actions: Check all

6) Repeat steps 3 - 5

7) File > Save All

8) Reopen the assembly and repeat the steps that caused the session to update.

 

If this does not work, consider calling GTAC and sending your parts in for a thorough analysis.

Regards, Ben

Re: NX freezing with "Updating objects..." message

Valued Contributor
Valued Contributor

Unfortunately applying this did not solve the problem.

 

We are using native NX setups.

 

To clarify:

By older I mean like a year older, not as old as NX4.0 old Smiley Happy

Problem is within a particular assembly and its components, but sub-assemblies are fine.

This is within modeling, while in drafting its all good.

There is absolutely nothing special about this assembly, no links, no  expressions.

 

I guess GTAC it is.