Cancel
Showing results for 
Search instead for 
Did you mean: 

Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom

Hello TC experts!

 

I am testing asynchronous JT creation using 2 Tier environment.

 

There is only one request in the 'Dispatcher Request Administration Console' with state 'TERMINAL'.

 

The dispatcher client log shows failure as:

 

2019-02-28 06:32:48,823 ERROR - Failure processing request: U292712eec5c77c2d22f6x
java.lang.Exception: Translation request missing primary object.
at com.teamcenter.ets.request.TranslationRequest.refreshPriAndSecObjs(TranslationRequest.java:1244)
at com.teamcenter.ets.extract.Extractor.processRequest(Extractor.java:389)
at com.teamcenter.ets.extract.Extractor.start(Extractor.java:320)
at com.teamcenter.ets.extract.Extractor.<init>(Extractor.java:266)
at com.teamcenter.ets.ServiceMode.startService(ServiceMode.java:67)
at com.teamcenter.ets.ServiceMode.main(ServiceMode.java:256)

 

Can someone point how to fix this translation failure?

Please let me know if there is any additional information required.

7 REPLIES 7

Re: Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom
I'd need a few more details here - are you refering to NX using the nxtransdirect translator?

Re: Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom

Hi @MarkusK ,

 

I'd need a few more details here - are you refering to NX using the nxtransdirect translator?

Yes.

Re: Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom
does that happen with every part you save or just some parts?
if you take a look at the DispatcherRequest object after submitting this nxtransdirect, you should see that it has the ItemRevision as the Primary and Secondary Object - so an empty Primary Object is unusual... (just create a query for DispatcherRequest objects and then run the query and view the properties of one such object)
Do you have modified the rule tree so that the revision is not visible for the dcproxy user for some reason? (READ DENY?)

Re: Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom

Hi @MarkusK ,

 

Thanks again for all your attention.

 

does that happen with every part you save or just some parts?

It is happening for every part/assembly that I save from NX.
Just to ensure I reconfigured dispatcher setup from scratch and it is again failing with same error.

 

if you take a look at the DispatcherRequest object after submitting this nxtransdirect, you should see that it has the ItemRevision as the Primary and Secondary Object - so an empty Primary Object is unusual... (just create a query for DispatcherRequest objects and then run the query and view the properties of one such object)


NX_Dispatcher.png

 

Do you have modified the rule tree so that the revision is not visible for the dcproxy user for some reason? (READ DENY?)

No. But how to check it ?

In access manager, Do I need to check settings of any ACL(s) for correct access of item revision/primary object?

Re: Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom

@MarkusK , Any suggestions ?

Re: Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom

User 'dcproxy' was missing from projects. I have added it to the respective project(s), now translation is completing without any error/issue.

Re: Dispatcher failure - Asynchronous JT creation

Siemens Phenom Siemens Phenom
Siemens Phenom
Hi Ganesh,
sorry, I don't read the community on that regular base (the reason for the late answer)...
I am glad you ironed it out!
Regards,
Markus