Reg: Trex conectivity error

Former Member — Sat, 27 Aug 2011 06:27:28 GMT

Dear Experts,

Here we installed the trex in ecc ehp5 system, we able to test rfc between trex but we are unable to connect the t.code ESH_COCKPIT while conecting this follwing error message we are geting kindly hepl me on this.

Error while processing your query

What has happened?

The URL call https://ke5server:/sap/bc/webdynpro/sap/esh_admin_ui_component was terminated because of an error.

Note

The following error text was processed in system EED : Die URL enthält keine vollständige Domainangabe (ke5server statt ke5server.).

The error occurred on the application server KE5SERVER_EED_02 and in the work process 6 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: CHECK of program CX_FQDN=======================CP

Method: STARTUP_CHECKS of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP

Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP

Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP

Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

What can I do?

If the termination type is RABAX_STATE, you will find more information on the cause of termination in system EED in transaction ST22.

If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server KE5SERVER_EED_02 in transaction SM21.

If the termination type is ERROR_MESSAGE_STATE, you cansearch for further information in the trace file for the work process 6 in transaction ST11 on the application server. KE5SERVER_EED_02 . You may also need to analyze the trace files of other work processes.

If you do not yet have a user ID, contact your system adminmistrator.

Error Code: ICF-IE-https -c: 100 -u: ABAPER -l: E -s: EED -i: KE5SERVER_EED_02 -w: 6 -d: 20110827 -t: 112304 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION -X: 005056B000091ED0B48E1A84C06C0C9C_005056B000091ED0B48E1A84BB8A0C9C_1 -x: D470D0E00326F1668C9C005056B00009

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

Re: Reg: Trex conectivity error

BGarcia — Sun, 28 Aug 2011 09:32:53 GMT

Hi Rkishorejak,

Check that you assign the TREX rfc to ESH application, using report ESH_ADM_SET_TREX_DESTINATION.

If the problem wasn't here, check if your system is configured correcty to launch BSP and Webdynpro applications. Is that by checking to the link you provided, it seems a little strange to me:

https://ke5server:/sap/bc/webdynpro/sap/esh_admin_ui_component

Normally, the links are builted with the following syntax: http://<host>:<port>/.

In your case, seems the host is missing the parent domain, and you have no port associated, and therefore, is not a FQDN (full qualified domain). Maybe this is an issue for your system administrations to analyse, and check if this is the error reason.

Kind regards,

Garcia

Edited by: Bruno Garcia on Aug 28, 2011 10:33 AM

topic Re: Reg: Trex conectivity error in Application Development and Automation Discussions

Reg: Trex conectivity error

Re: Reg: Trex conectivity error