cancel
Showing results for 
Search instead for 
Did you mean: 

TREX - rfc issues connecting to ECP system - MDG

Former Member
0 Kudos

Hello All,

We have an issue where our MDG consultant is trying to create a connector in ESH_COCKPIT, but it gives an error saying "error while preparing".

So we checked the logs of the job and it fails with error as " RFC failure"

We have checked the RFC "TREX_TGP" in SM59 of ECP and also in TREXAdmin , its working fine.

Now, we tried to look for logs and TREX logs says as below -

usr/sap/TGP/TRX70/trx70tgp/trace # tail -20 TrexIndexServer_trx70tgp.37003.000.trc


[139657946474240] 2014-03-05 11:53:38.125 e join_eval JoinEvaluator.cpp(01527) : showIndex failed for esh:ecp100~ecp100~mdg_business_partner~%e9dc0710 rc=2007

[139657946474240] 2014-03-05 11:53:38.149 e join_eval JoinEvaluator.cpp(01527) : showIndex failed for esh:ecp100~ecp100~mdg_business_partner~%e9dc0710 rc=2007

[139657938081536] 2014-03-05 12:45:08.830 e join_eval JoinEvaluator.cpp(01527) : showIndex failed for esh:ecp100~ecp100~mdg_business_partner~%e9dc0710 rc=2007

[139657938081536] 2014-03-05 12:45:08.831 e join_eval JoinEvaluator.cpp(01527) : showIndex failed for esh:ecp100~ecp100~mdg_business_partner~%e9dc0710 rc=2007

Attached is the screenshot of the error.

Any suggestions here will be highly appreciated.

Cheers, SG

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

In connectivity tab for trexadmin transaction, check if both RFC and ICM connection test results are fine.

Also, see if implementing the follwoing note helps you.

 

SAP Note 1764978 - Error when activating ESH connectors without ODP

Best Regards,
Anita

Former Member
0 Kudos

Bang on !! Anita your solution worked like charm.

SAP Note 1764978 solved the problem, I am happy our SAP community have such great experts who can help in resolving issues without even having a look at system.


I am marking this thread as closed now.


Cheers, SG



Answers (2)

Answers (2)

bxiv
Active Contributor
0 Kudos

Have you verified the default Trex RFC in the ECP system?

Tx se38 > ESH_ADM_SET_TREX_DESTINATION

I assume this is valid as the rest of your indexes would break without it.

Perhaps a user filtered trace on ECP to see what the connector is attempting to access, as the system user ID may be having an auth issue?

Former Member
0 Kudos

Hi Billy,

Yes, I checked that report ESH_ADM_SET_TREX_DESTINATION and executed it for RFC TREX_TGP but still same issue.

Not sure how to create this user filter and trace, please suggest how to apply this filter ?

Regards, Shobhit

bxiv
Active Contributor
0 Kudos

In ECP go to tx st05, you should only need RFC Trace but the others can't hurt just provide more logs.

Now click on "Activate Trace with Filter" and it will allow you to select a user ID, I would start with the account that is being used in the web UI of esh_cockpit along with the ID used for Trex to talk to ECP.  You may need to run 2 traces when trying to prepare the index to catch what ECP might have an issue with.

JPReyes
Active Contributor
0 Kudos

Hi SG,

Have you tried to upgrade the TREX revision?... this showIndex issues are usually bugs fixed on subsequent revision (Trex SP's).

You could also open an OSS note for this.

Regards, Juan

Former Member
0 Kudos

Hi Juan,

I thought so about it, but then its working perfectly fine in DEV and QA.

Its the Prod we are facing the issue.

Also our version is - 7.10.56.00

Regards, SG

Sriram2009
Active Contributor
Former Member
0 Kudos

Hi Sriram,

Thanks for your reply but our hostname is not more than 14 characters.

Hence note doesn't apply to us, also the length of the hostname is same as in DEV and QAS so I am certain this is not the issue in our case.

Any further suggestions ?

Regards, Shobhit