Showing results for 
Search instead for 
Do you mean 
Reply
Solved! Go to solution

Problem renaming UGMASTER object

Hi guys,

 

I want to rename a UGMASTER in TEAMCENTER Rich Client but I get error like below.

 

 

I clicked on Edit Properties on the dataset, check it out, try to rename but this happens.

 

How can I solve it?

 

Thanks!

 

 

9 REPLIES

Re: Problem renaming UGMASTER object

This issue may encounter because failed to dataset for XML rendering.

 

Can you post RAC console log and tcserver*****.syslog ?

Re: Problem renaming UGMASTER object

[ Edited ]

Found the RAC log but not the other one.

 

Re: Problem renaming UGMASTER object

We need to have tcserver***.syslog to find exact cause of this issue.

Please look at Help->About Teamcenter for syslog location.

Re: Problem renaming UGMASTER object

[ Edited ]

You can find it attached.

 

Not to forget, This is Teamcenter Rapid Start V10.1.3 on a Windows Server 2008 R2 x64

 

Thank you!

Re: Problem renaming UGMASTER object

Syslog says as follows

 

"An invalid object instance tag is being used in conjunction with property %1$s." we never substituted argument 2 : rule_tag

 

 

Re: Problem renaming UGMASTER object

Yes but what does it mean?
This is an NX Part created by NX Integration. Is this normal? How can I fix that?
Solution
Solution
Accepted by topic author CemAlpay
‎08-26-2015 04:32 AM

Re: Problem renaming UGMASTER object

Can you perform following steps and post the result .

 

1. Select 'UGMaster' dataset and Click on summary tab.

2. Peform Check-out and modify the 'object name' on summary tab.

3. Peform the check-in .

Re: Problem renaming UGMASTER object

Thank you very much, that solved it.

How did you understand that this was the problem? The way to solve it I mean?

Or is this a general rule for changing dataset names?

Re: Problem renaming UGMASTER object

We can modify datasetname in different ways , like using summary tab / Viewer tab ..etc..

 

But you have some problem when do you perform 'edit properties' , so I still feel this problem releated to some rendering stylesheet.