PeteSp
Mechanical
- Oct 24, 2012
- 11
Hello everyone,
Just some upfront FYI...I am working with Teamcenter 8.3.3.4 and NX 8.0.3.4
About two months ago, I upped to NX 8 and since have been having much trouble opening certain asms and get the attached
errors/warnings.
Normally, the first step taken is launching the NX asm from TC with "All Components" load option. Some load perfectly fine with no issues whatsoever, and then we have the warning (see attachment). This is the initial crippler which stops all loading and prevents NX file from opening.
Next, I load "Stucture Only" and load each subassembly or component one by one. Eventually, one (or multiple) of the individual components I've attempted to load gets an error that reads:
"Error recovery completed for the following error:
An operation was attempted on an object needing a file root but lacking one".
So, it seems that must be the problem child...but when I open the problem child part on its own, it has no problem opening up just fine.
Has anyone experienced this? It is really stopping production from my engineering group and seems that it will not be solved as quickly as I need it to be. Any info is GREATLY appreciated!
Thanks!
Just some upfront FYI...I am working with Teamcenter 8.3.3.4 and NX 8.0.3.4
About two months ago, I upped to NX 8 and since have been having much trouble opening certain asms and get the attached
errors/warnings.
Normally, the first step taken is launching the NX asm from TC with "All Components" load option. Some load perfectly fine with no issues whatsoever, and then we have the warning (see attachment). This is the initial crippler which stops all loading and prevents NX file from opening.
Next, I load "Stucture Only" and load each subassembly or component one by one. Eventually, one (or multiple) of the individual components I've attempted to load gets an error that reads:
"Error recovery completed for the following error:
An operation was attempted on an object needing a file root but lacking one".
So, it seems that must be the problem child...but when I open the problem child part on its own, it has no problem opening up just fine.
Has anyone experienced this? It is really stopping production from my engineering group and seems that it will not be solved as quickly as I need it to be. Any info is GREATLY appreciated!
Thanks!