on 03-06-2014 10:13 AM
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Could you check this SAP Note 1906329 - TREX 710: Connectors can not be created - error during deserialization
Regards
Ram
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.