Error code 920007 ?

[Ehaviv]

Hi

when importing assembly to tc
l got error code 920007.

can someone help or guess
what's that mean.

Thank you.

 

[Toost]

I have no clue but,
Did you try Google ?
if not, try this :

https://www.google.se/search?ei=XRY.....0...1c.1.64.psy-ab..0.1.71....0.FJuWjHPyMPc

I.e Search for
"error code 920007 siemens"
or
"error code 920007 siemens NX"

I think there is replies with the info you are looking for.


Regards,
Tomas

 

[Ehaviv]

I'm Thank you for the link.

 

[Ehaviv]

When i checked file names.

I see that one of the component parts
have a square bracket [ in its name
and I suspect that cause the error.

do someone can help me in what characters
are not allowed in nx manager mode.

because in navie mode that ok [ in part name.

Thank you.

 

[NutAce]

When you are running NX in managed mode the naming is determined and governed by Teamcenter (or whatever PDM/PLM database you are using).
Your database admin should be able to tell you what the naming rules are for your database. Usually the db admin set up these rules.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX11 / TC11

 

[Ehaviv]

Ronald Thank you.

Maybe there exist a default/general setup.
and the admin can live it unchanged
or change it.

 

[NutAce]

Maybe there exist a default/general setup.

There is...
No naming rules out of the box (except for the rapid start install maybe), which basically means everything would be allowed.
It might be that your admin didn't allow for the [ to be used as it can be used to delimiter a set in the rules itself.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX11 / TC11

 

[Ehaviv]

Thank you very much.

 

[Ehaviv]

Hi
I found this in the Internet but
I don't know its source.


4/8/2004 T. Parker Item/Part Name Rules Restrictions Due to the following restrictions dictated by the CAD and Teamcenter software, users must follow these guidelines. 1. All Item/Part names must be entered in all UPPER CASE characters. 2. All Item/Part names must be a maximum of 32 characters in length. 3. Do NOT use any of the following characters in Item Names. ! @ # $ % ^ & * . , ' : ; ` ~ \ + / { } [ ] ( ) = | < > ? ". While the software will accept some of these characters, they WILL cause problems when trying to generate plots, DXF, IGS, and other files. 4. Since the commonly used “/” character is not allowed, all fractional values will be represented by the first three digits of their decimal equivalent. ½ will become 500, 1-1/2 becomes 1-500 etc. 5. Do NOT use spaces in Item Names, use the “_” underscore character to separate words, and use the “-“ hyphen character to string terms together. Teamcenter has a maximum length limit of 32 characters for an Item Name. This is fairly restrictive, but should suffice if we use the space wisely. 1. The item name is NOT a sentence or phrase, its primary purpose is to help CAD users locate data. 2. When possible spell it out. If 32 characters are room enough to fully spell out the name, DO. 3. Do not use generic names like drawing1, project2, junk, etc. Never accept the default name for items such as Drawing1, Part1. 4. Item names should start with a key noun like FLANGE, ADAPTER, TUBE, or the common device name 3Q120, MI62. Device names must be added to the list of approved abbreviations and acronyms. 5. A list of approved abbreviations and acronyms for Fermilab devices will be maintained at TPACROifind-web.pl . This list will include functionality for users to submit additional names to the list. 6. Avoid relative terms in Item names, i.e. new, old, and temp. 7. Do NOT use punctuation characters in an Item Name. 8. Do NOT use drafting special characters in an Item Name. 9. Do NOT confuse the Item Name with the Title/Description, which is an 80character field that should fully describe the Item. There are no character restrictions in this field which is also all UPPER CASE.

 

[Ehaviv]

This say maximum 32 character name length.

I checked in it in ower company to be 30 character.

Is the admin can set it to any number.

 

[Ehaviv]

In my case this error caused by a square
bracket character in one of the parts names. and nx say this.

ERROR: (920007) - Teamcenter Error: Invalid Tag %1$s - the requested object does
not exist

If the error massage was to say :
“unsllowed character in a part name”

I'l quickly will notice what's wrong.

 

[Toost]

I regularly see people naming their files using , what i consider, weird characters...
last week i saw a file where a diameter sign was included in the Item ID ,Teamcenter.
and another file with two "+" signs in the item id.


I have some difficulties understanding this,
Do these people speak like that also ?
"Hello mr salesman, i would like to look at this 44plussign2diametersignundersscoreplussign847diametersign".


Regards,
Tomas

 

[Bleaker]

Note that the cited document is from 2004. In the 14 years NX and TC have dramatically improved their object naming flexibility, expanding the allowed character range to almost everything Unicode has to offer. Unfortunately, I was unable to find any kind of documentation on that. My best result was an NX error message telling me that the symbols @ * ! ? : < > | ` are disallowed in many objects (but not in, say, TC ITemIDs).

This is why, when I have to deal with file names or object IDs, I go full-on paranoid and use names like ﷼̸̻̅Ы̸͆ͅ{̴͙̃[̴͖͝(̶̯͛@̵̭̽^̸̖͂°̵̧͝~̵̗͂'̶̪̍µ̷͓͝+̵̬̒§̶̮̀$̴͉̓#̷͙͛=̵̠̓&̵̻̓;̶̙̒€̷̠̂)̴̹̌,̷̝̋]̷̜̈́}̵̞̓汚̴̥͌れ̴͉̓の̸̐͜た̸̭͌わ̷̥̈ご̶̺̈́と̸̔͜ǜ̸͍ö̶̢͝�̷͖̎ä̶̹̈́ß̸̋͜р̸̥̓о̷̖́ḛ̸̕s̵͔̾h̵̤͑Å̴͔̀r̷̠̕е̶̗͛‽̸̯͐.prt to test my code and see if NX or TC can take the punishment...

 

[Ehaviv]

Hi Bleaker and thank you.

Can you give me a clue how you test
your code.
is it in vb

 

[Toost]

People should be forced to run unix for at least 6 months, then they will stay away from weird characters...

 

[Bleaker]

@Ehaviv: It's not a "proper" test I guess - whenever I have any kind input strings for names in my (NXOpen) code, I pre-fill them with monstrosities like the one I posted above on the first run, then gradually cut them down until they stop crashing.

@Tomas: Eh, I've had more problems with software/APIs still struggling to implement this brand new thing called "Unicode" they've invented just yesterday...