Skip to main content
12-Amethyst
August 29, 2024
Question

Odd NX assy navigator behavior with Windchill

  • August 29, 2024
  • 1 reply
  • 2556 views

Version: Windchill 12.0

 

Use Case: NX 2206 Users will open a large, top level assembly as "structure only", then expand 1 or 2 sub-assemblies, and the assembly navigator will jump to display a different sub-assembly, and NX becomes essentially useless.


Description:

User opens a large top level assembly, using "structure only" in NX.  Then the user will expand 1 or 2 sub-assemblies, and the Assembly Navigator will change to list a different sub-assembly, and the NX session becomes essentially useless.  You can click on things, but navigating the assemblies or parts, is non-functional.  Sometimes a fatal, or other error follows.

 

Top level assembly is just under 30gigs, and it is all in the local workspace.  Loading "structure only" should only be loading a minimal amount of data into the NX session.

 

Everything functions as you would expect, if you run an NX session disconnected from WGM.  I've done this by running a second NX session, which fails to connect to Windchill.  Then do the same load, and assembly expansion in both sessions at the same time.

 

Also, load time is about 10X faster, when not connected to WGM.

 

In this image, you can see that the NX session connected to WGM is showing one part number in the tab, but a different part number in the Assembly Navigator.  Compared to the stand alone NX session, which shows the matching tab and navigator column.  NX session connected to WGM also experienced a Fatal error.

Dave_K_1-1724938419622.png

Dave_K_2-1724938504553.png

We are looking for any insight on how to solve this issue, as it is limiting, and slowing our productivity.

 

1 reply

17-Peridot
August 30, 2024

@Dave_K 

 

The c0000005 error (when I had it popping up a few times 2 years ago) had to do with the registry being somehow corrupt. It was a difficult thing to reproduce but essentially boiled down to a stuck WFS service that had to be force uninstalled/removed with a Microsoft uninstall utility. I had a ticket with PTC on this and the recommendation was to:

- reinstall after the registry cleanup

- delete the %Appdata%/Local/Siemens folder

- run WGM as admin to first connect NX to it

- run per usual and hope for the best

 

Large assemblies will always run way slower in a stand-alone session than when connected to the WGM. Do you have any anti-virus software running? This may help: https://www.ptc.com/en/support/article/CS50545

We also have some other monitoring software that I had to exclude NX (ugraf.exe) and WGM (uwgm_client.exe) from to help the slow loads along. Our assemblies are in the 7GB range and with load_options.def file set to partially load + anti virus exclusions we got down to about 4-5 minutes instead of 15 without. 

 

There is a known "feature" in WGM that will cause major slowdowns too that has to do with mass reporting. Do you have mass reported from NX (NX_Mass via MassPropMass and MassPropRollupMass) to Windchill with the MSP:Mass mapping PTC suggests? https://support.ptc.com/help/windchill/plus/r12.1.2.0/en/index.html#page/Windchill_Help_Center/WWGMforNX/WWGMNXAdminConfigMappingwithUnits.html# doesn't point out that if there are modeling errors in NX that NX happily resolves - they seem to trigger mass calculations on the Windchill side for the number of errors that exist. Specifically: if you have pk_topol errors showing up in your syslog, you can go from a 30second load/save to 15-20 minutes. 

In NX if you do "Examine Geometry", "Feature replay" and "Part cleanup" it may help at least identify this. But there isn't a fix yet on Windchill not triggering a save even when you don't want one. The only thing I was able to do was remove the MSP:Mass mapping for NX_Mass until there's a fix in some newer version of WGM. 

 

 

Dave_K12-AmethystAuthor
12-Amethyst
September 3, 2024

@Dobi   I'm not a Windchill admin, so can you tell me where I would direct our admin, to turn this off?  "The only thing I was able to do was remove the MSP:Mass mapping for NX_Mass until there's a fix in some newer version of WGM. "

17-Peridot
September 3, 2024

@Dave_K  You want to go Site/Utilities/Type and Attribute Management. There, find the EPM Document item (under Manage types). Depending on how you have the system set you may have a Mass attribute at the top level or a level down (CAD Document). If you created any CAD document subtypes that inherit that value go to the parent.

 

In my case, MSP:Mass was defined at the CAD Document level:

Dobi_0-1725377865669.png

 

This was in the details of the attribute:

Dobi_1-1725377925458.png

 

Delete that line and save. 

 

That will have the consequence of your NX mass no longer reporting to Windchill. For us, this was preferred over a 15-20 minute save.