Part family invalid names after upgrade

[Kirsten]

We just upgraded from NX2 to NX5.0.3 and are (still) using Teamcenter Engineering V9.1.3.8. When we try to update part, create part, or even just save family, we get this error:

Ivalid member name. The following member names are invalid
4485001-001
o-ring-Parker-5-180

(These are two of the names that fail. There are no trailing spaces, so that's not the problem. They are nearly identical in format to members that had been created before the upgrade.)

So here's what I've found so far:
1) Everything works fine if I'm running a native session with the same template part
2) If I change the letters to uppercase I get no errors, as long as there are no other invalid members
3) I cannot update part, create part, or even save family if any member is invalid--even if a valid row is the only one highlighted.
4) The ones that list as invalid are items that have never been created before in Teamcenter.

Any ideas?

 

[hudson888]

Check in the load options, for allow substitution to be ON.

Were you running Teamcenter before the updgrade? Same version, same settings?

Are you now opening assemblies via PSE or out of your UG session?

Can you create an empty item master out of teamcenter for these names?

I'm no teamcenter expert and may not be able to analyze your problem, and this isn't a heavily teamcenter oriented forum, but the above information should help better diagnose what ails you. Also I would report it back through your PLM support office, if something worked in the past then you ought to expect that there is some ongoing support.

Best Regards

Hudson

 

[DavidTolsma]

There is an option to enforce all naming is correct in the customer defaults. Quick workaround that may work.

Teamcenter naming rules? are you using them? is it enforced?



-Dave Tolsma
Tolsnet LLC

http://groups.google.com/group/NX_CAX/

http://groups.google.com/group/plm-exchange/

 

[Kirsten]

"Check in the load options, for allow substitution to be ON."
It was OFF, now is ON. No change.

"Were you running Teamcenter before the updgrade? Same version, same settings?"
Yes, they say nothing changed and we've been running this version for a few years.

"Are you now opening assemblies via PSE or out of your UG session?"
UG session.

"Can you create an empty item master out of teamcenter for these names?"
Yes.

I'm pretty sure we don't have enforced naming rules. The ugii_env setting "#UGII_OPTION=" for case is commented out. Besides, they swear nothing in TC has changed and the parts can be created with those names as long as it's not through a part family.

Those are good tests! Why didn't I think of all that? Thanks, Hudson & David.
Another test I tried is to add component to an assembly through NX rather than creating using the spreadsheet. Alas, still invalid. It even fails on John Baker's hardware names, such as: hex_mch_scr_5-16_x_1
The syslog says: Part Families: Encountered legacy part family template with no pre-allocated handles for its member - hex_mch_scr_5-16_x_1

I'll go to GTAC.

 

[hudson888]

Yes, do go to GTAC with it, because you've ruled out most of the causes you had any control over.

Try opening the assemblies via the PSE checking that they're not locked "precise", see if that doesn't help to be able to substitute the filenames.

I've done some work with some guys using Teamcenter 10, and NX-5. I needed to export the part I'm working on so that I could take it away to finish of a few things, we get similar error messages in native for some of the files and we don't know why. The difference for us is that it still works in teamcenter so we can get around the problem.

Please let us know what you find. I'm keen to guess whether the version of teamcenter or the change to NX-5 is what's behind these problems.

Best Regards

Hudson