Internnal Error: Null tag not allowed 1

[HallandStavert]

Within Part Navigator, I used "Make Current Feature"... sometime later I went to "Make Current Feature" the last Modle Feature in my list of features within the Part Navigator. I keep getting an Internal Error: Null tag not allowed. I can't even delete any feature that's not active.


The feature in model navigator is a Wave geometry linked curve.

Has anyone come across such occurence?


Thanks,

Paul Perry
Hall & Stavert

pperry@hytorq.com

 

[hudson888]

Paul,

This has happened before to me on NX-3 what version are you running? Without confidently saying that this is a bug at the very least your model may be corrupt. Even saying corrupt is not to infer that the file is damaged but that something in the data is scrambled for sure often only slightly and usually we have been able to rescue most of what we started with.

To begin with try running a part cleanup, you may as well turn on most of the options, but the part structure is the likely culprit. If it won't complete that task you may have more serious problems than you or I will be able to fix. It is best to know this sooner rather than later.

In cases like yours hopefully you have no saved your part with the current feature being just behind where you get stuck. What I usually do is to put the feature list into timestamp order and make a feature just a few above where you got stuck as the current feature. Then you should attempt to make current feature back to the last one in the model. Go back and forth until you can isolate the feature or features in the list that are affected. Basically if the feature where you had trouble was 100 features before the end then you should still be able to go back and forward by 99 features, or 98 etc.., but if you can't even go back one feature then you are in a fair bit of trouble, but keep trying from the other end, read below.

The other way you can go is to attack from below where you go several features earlier than where you got stuck and make a feature current. Then update going forward one, two or just a few features at a time to find a point where the problem happens.

Sometimes after doing this you find that the system refuses to jump one feature forward, but then succeeds in jumping past the affected feature by several steps. Who knows why, but once the problem passed it seldom re-occurs in the same manner.

Once you find the problem geometry then you may be able to delete it either from the feature list or by simply deleting the object from the model. If other things are associative to that feature or object, either you cop the damage and fix it later or you attempt to edit their parameters to get them working again.

Sometimes just tracking up and down the feature list with making different feature current will fix these kind of problems with little or no real explanation. Other times you'll have to decide how much you want to lose.

If you're working in teamcenter the system keeps your last four recent saves of the latest working file. Otherwise you would go to your backups in cases where the damage is too bad.

The most occasions where I have had these kind of problems is by exporting selected geometry from one file to another rather than importing the whole file. In principle the former is neater because if you select a solid to export then the system will carry with it all the objects, curves sketches, sheets etc used to build it and strip out what you don't need. We found that we couldn't always trust this to work properly. This was working between native and teamcenter in NX-3, and teamcenter was the rationale for our actions but not the culprit. We now recommend that users import the whole file and selectively delete unwanted objects to clean up.

Hope this helps

Best regards

Hudson