Error when processing your request

[Former Member]

Error when processing your request

What has happened?

The URL http://vinay:8000/sap/bc/webdynpro/sap/zfirst_web was not called due to an error.

Note

 The following error text was processed in the system NSP : Die URL enthält keine vollständige Domainangabe (vinay statt vinay.).

 The error occurred on the application server vinay_NSP_00 and in the work process 0 .

 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 was RABAX_STATE, then you can find more information on the cause of the termination in the system NSP in transaction ST22.

 If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server vinay_NSP_00 in transaction SM21.

 If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server vinay_NSP_00 . In some situations, 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 administrator.

Error code: ICF-IE-http -c: 001 -u: BCUSER -l: E -s: NSP -i: vinay_NSP_00 -w: 0 -d: 20090622 -t: 074756 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

[thomas_jung]

This is the Fully Qualified Domain Name Check (FQDN). Try searching the forum in the future before posting. This is an extremely common question and has been discussed in the forum and is documented in the online help extensively.

Here is the link from the online help:

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm

[Former Member]

500 connection out

error -5

version 7000

component icm

module icothr.c

line 2698

server nsp_vinay_00

detail connection to the partner is time out after 60 sec

[thomas_jung]

This new error message you have posted is a time out. The ICM times out after 60 seconds by default. If you have gotten past your FQDN error, then you are actually running an application for the first time. Most likely the loads have to generate. Be patient. You might experience several time outs before all the framework and applications loads get generated. Not uncommon, especially if running on relatively slow hardware.

[Former Member]

thanks for reply.......is any way to come out of this error or approximate how much try i have to do

[thomas_jung]

Retry a few times. You can check the process overview as well to see what is happening in the backend work process. How many times have you tried the application?

[Former Member]

7 to 8 time i had try but same error

[amy_king]

Hi Thomas,

I realize this is a rather old discussion, but I wonder if you know whether running transaction SGEN to generate the loads for either all web dynpros or just a particular transport containing a custom web dynpro would resolve the slow response time and timeout. After a customer message with SAP, this was their suggestion, however our Basis team is skeptical that this will have the desired effect. We noticed the issue when moving from development to QA so we won't know if this is the solution until we try it in production upon go-live.

Cheers,

Amy