Internal Error: Invalid Solid Object Tag

[fgbrender]

Does anyone know what an "Invalid Solid Object Tag" could be? I have recieved it when creating a part family and when trying to deform a part in an assembly.

I couldn't get any useful information from the syslog and I searched GTAC for an answer but while there were issues posted regarding this, there were no solutions.

 

[JohnRBaker]

Try running a Part Cleanup with all the options set and that MIGHT help rid yourself of the problem. If that doesn't you'll probably have to call GTAC and open an IR to have them look at your model.

As for trying to figure out what is happening and which object is teh culprit, that's not easy without diagnostic tools.


John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[hudson888]

While we can't tell from you post glitches that are to do with features in your part are best fixed by doing a part cleanup. But if that doesn't work try re-ordering features in the model or rolling the feature list back and forth using make current feature sometimes you're with able to find the offending feature and other times the problems can be cleared when the system is able to re-evaluate the model successfully as occurs when you manipulate it in this way.

Best regards

Hudson

 

[fgbrender]

Thanks for the replies. I was afraid that those were the answers I'd get. I have run part cleanup a number of times. I also have searched GTAC and found similar problems reported but alas, not solutions posted.

What I really would like to know is "What is an invalid solid object tag?"

I know what many of the errors in NX are but I have never run across this one and not know what it means doesn't help me fix it.

Again, Thanks for your replies.

 

[hudson888]

Well it isn't as uncommon as we'd all like it to be. I think that it basically means that an entry in the list of objects that comprise the part file , in this case a solid object, has an error on it. Most of these seem to get caused when part of the file is basically corrupted with a bit of information that didn't get written properly due usually to memory errors somewhere in the model's past history. Usually they are fixable.

With the mode of error I would try using the assembly with the deformed part loaded as entire part. Check whether you can alter the deformation parameters. Then if that works we can work on whether you need to turn off partial loading or simple open the component fully as a manual step to make it go away. I suspect that if the parameter for deformation addresses an expression driving a sketch or something else that isn't fully loaded that might be the problem in a nutshell.

If I were going to make a broad recommendation about deformable parts then it would be that if you can create the deformable geometry without using a sketch then I would. This is simply because the deformable geometry as part of a parametric feature based solid may be more likely to be loaded even with partial loading turned on. If I'm wrong on this by all means let be know, but it is what I have been doing and I've had very few problems.

I have seen these errors several times and have had no cases where I could not find some way to fix the data. The most difficult may contain wave linked geometry, but you have made no indication that this is involved so I won't bore you with that.

If you're really stuck then I would start by making a copy of the file, and seeing whether you can delete objects starting with those you least need from the offending file. Do this in stages and test the results and you'll hopefully be able to reduce the file to a bare minimum such that the error object is no longer present.

Best Regards

Hudson