7.20 patch 421 standalone Web Disparcher redirect not working

[Former Member]

Hello,

I was hopping to find a solution posted here.  I am using standalone web Dispaterchers pointing to NW 7.30  backend.  Replacing our "working" DMZ SAP Web Dispatcher with a 7.20 patch 421 version. Just copied the old profile over and modified as needed.

sapwebdisp pf=<profile> -checkconfig ends with 0 errors and 0 warings!

I am not sure if this parameter is still supported:

icm/HTTP/redirect_0 = PREFIX=/, TO=/sap/public/bc/its/mimes/zcnp_disc/99/default.html

icm/HTTP/logging_0 = PREFIX=/, TO=/sap/public/bc/its/mimes/zcnp_disc/99/default.html, LOGFILE=access_log,MAXSIZEKB=5000, SWITCHTF=month, FILEWRAP=on

I can bring up https://<URL>.com/sap/admin

I get the old 500 Dispatching Error

Error -26

Version 7200

HTTP_ROUTE

http_route.c

3369

{0000000e}

no valid destination server available for '!ALL' rc-4

I am guessing this method of redirect has changed for this version.  it does tag to my URL the proper path of /sap/publlic/bc/its/mimes/z*.*

Trace leve 3 log results:

Thr 2404] *** ERROR => no valid destination server available for '!DIAGS' rc=4 {00000012} [http_route.c 3369]
[Thr 2404] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3393]
[Thr 2404] *** WARNING => original destination was '!DIAGS' [http_route.c 3396]
[Thr 2404] *** ERROR => no valid destination server available for '!ALL' rc=4 {00000012} [http_route.c 3369]
[Thr 2404] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3393]
[Thr 2404] *** WARNING => original destination was '!ALL' [http_route.c 3396]
[Thr 2404] *** ERROR => no valid destination server available for '!ALL' rc=4 {00000012} [http_route.c 3369]

[Thr 3596] *** ERROR => IcrAttachToServer('!DIAG') failed 4 [icrxx.c      3510]
[Thr 3596] *** ERROR => IcrAttachToServer('!DIAG') failed 4 [icrxx.c      3510]
[Thr 3596] *** ERROR => IcmConnClientRqCreate: No service for protocol HTTP started [icxxconn.c   2666]
[Thr 3596] *** ERROR => IcmConnClientRqCreate() failed (rc=-1) [icrxx.c      6938]
[Thr 3596] *** ERROR => IcmConnClientRqCreate: No service for protocol HTTP started [icxxconn.c   2666]
[Thr 3596] *** ERROR => IcmConnClientRqCreate() failed (rc=-1) [icrxx.c      6938]

Not sure where !DIAGS came from.  Must be some feature imbeded with Software Provisioning Manager 1.0

Regards,

Dan Mead

[Former Member · Accepted solution]

This issue was corrected by upgrading to kernel 426 which came out shortly after I patached the kernel to 421.  This issue is referenced in SAP 1845042 - Web dispatcher ping over https uses http server port.

Regards,

Dan Mead

[Former Member · Accepted solution]

Interesting, Thank you for providing the solution. Had you tried out as per my request a patch level prior to 421 (which introduces the error), would you have found out this error.

[Former Member · Accepted solution]

I perceive I am having nearly the exact same issue you are facing, however trying to access note 1845042 says it is 'not released'

Any chance you downloaded and could share the contents here?

Only difference is that I am on sapwebdisp.exe 740 patch 12 (April 2013).  Was curious if that patch also contains the issue.  The strange thing is that I have the same version in non-production systems and am not facing the issue. 

[Former Member · Accepted solution]

You will have to upgrade to the latest patch level (40) on 7.40 to have the fix.

[Former Member · Accepted solution]

Hi Samuli

I assumed the same - applied that patch after I posted.  Did not resolve the issue thus far.  I have a High ticket with SAP right now. 

[Former Member]

I ran -checkconfig which verifies the connectivity to the message server is OK!  I am not authorized to post a *.jpg

dev_webdisp.txt.zip

Profile.txt.zip

[Former Member]

There is something wrong with your configuration. Share your configuration, edit sensitive information if required.

The system type (parameter wdisp/system_<xx>) determines how Web Dispatcher works. Only with system types SILOC and EXTSRV Web Dispatcher will not try to query the message server, otherwise it will. Currently your Web Dispatcher is unable to query the message server. If this is intended behaviour, you will have to setup one or more systems of type SILOC or EXTSRV. Otherwise Web Dispatcher has nothing to do, it has no destinations where to dispatch requests.

[Former Member]

Not familiar with wdisp/system_<xx>?  Is that new with Web Disp 7.20?

[Former Member]

It's not required if you have only one system with a message server. Clearly the Web Dispatcher is unable to query your message server. Double check the configuration entries and make sure the Web Dispatcher can connect to the message server. You are aware that you have requested the Web Dispatcher to use HTTPS for querying the message server?

[Former Member]

And for God's sake provide the configurations, traces/logs, etc. as text attachments, not embedded in the message. If required, switch to the advanced editor in order to see the attachment options.

[Former Member]

hi Daniel,

You might have already done that but just want to make sure if only redirect is not working and other URL working ok in your case? and you have copied icmbnd.new to icmbnd as per note 421359

Thanks,

Supriya

[Former Member]

Hello Supriya,

SAP Note 421359 validity date is 06.09.2007.  It pertains to binding ports on unix and i am running a standalone SAP Web dispatcher version 7.20 patch 421 with a NW 7.30 backend. 

I already have a working Web Dispatcher using the identical profile parameters pointing to the identical Central Instance.  The only thing I have not dione is do a Global Invalidation of the ABAP server cache.

Regards,

Dan Mead

[Former Member]

Thank you for the traces, next time do the same without someone having to ask for them. From your trace:

[Thr 3716] *** WARNING => IcmParseSubParam: unknown subparam "TO" for parameter: PREFIX=/, TO=/sap/public/bc/its/mimes/zcnp_disc/99/default.html, LOGFILE=access_log, MAXSIZEKB=5000, SWITCHTF=month, FILEWRAP=on [icxxpara.c   429]

See the correct syntax for icm/HTTP/logging_<xx>, link attached.

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/442541e0804bb8e10000000a42189b/frameset.htm

In case fixing the logging parameter doesn't fix the redirect problem try the following

icm/HTTP/redirect_0 = PREFIX=/,TO=/sap/public/bc/its/mimes/zcnp_disc/99/default.html

in other words having no whitespaces in the parameters. See the correct syntax for icm/HTTP/redirect_<xx>, link attached.

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/3d993fb08c72d1e10000000a42189c/frameset.htm

[Former Member]

I removed the white space in the parameter. Recycled and that didn't fix anything.  I understand thess !DIAG, !DIAGS, and !ALL are group names used for a dual stack JAVA/ABAP.  I just have an ABAP implementation. 

SAP Note 1812953  has the error I am getting.

Would setting  wdisp/enable_j2ee_groups =FALSE do anything?

[Former Member]

Have you set is/HTTP/default_root_hdl either in Web Dispatcher, the backend systems or both? The groups you refer to are valid groups for the ABAP backend, the Java group is called !J2EE. Can you try with an older patch level, anything older than 400?

[Former Member]

Are you by any chance accessing the Web Dispatcher with HTTP? That could explain the problem since you have configured Web Dispatcher to use HTTPS and you have not defined a protocol for the rewrite.

[Former Member]

I am connecting using https:// protocol.  I can call https://<my_url.com>/sap/admin.  Just can't call a service from the backend.

I already have a working Web Dispatcher version 700 patch 327 which is successfully connecting to the same NW 7.30 backend. I used and modified its profile for post processing step after installing this 7.20 Web Dispatcher.

is/HTTP/default_root_hdl=abap is set on the standalone SAP Web Dispatcher.

There is no firewall issue as i can telent to all backend ports and as mentioned -checkconfig is error free.

[Former Member]

Found SAP Note 1820449 08.02.2013

Symptom

After the backend server comes back up in service following a temporary service outage, web dispatcher still considers the server not reachable, as can be seen from the web administration interface. Accessing the server via web dispatcher is no longer possible while direct access to the server works, with errors like the following in the web dispatcher trace,

ERROR => no valid destination server available for '!J2EE' rc=4 {0068b94a} [http_route_mt.c 3360]
WARNING => redirect failed request to foreign destination '!ALL' [http_route_m 3384]
WARNING => original destination was '!J2EE' [http_route_m 3387]
ERROR => no valid destination server available for '!ALL' rc=4 {0068b94a} [http_route_mt.c 3360]
WARNING => redirect failed request to foreign destination '!ALL' [http_route_m 3384]
WARNING => original destination was '!ALL' [http_route_m 3387]
ERROR => no valid destination server available for '!ALL' rc=4 {0068b94a} [http_route_mt.c 3360]

Suposed to have been fixed in patch 418?  I have already patched my Web Dispatcher to 421.

[Former Member]

Remove (or comment out)

is/HTTP/default_root_hdl=abap

from the Web Dispatcher configuration, restart and test again. ICM admin is a special case, it will work regardless how your backed is setup. Can you test anything something besides / (root), for example /sap/public/bc/ping? Can you test NW720 with a patch release lower than 400?

[Former Member]

Commented out is/HTTP/default_root_hdl=abap.  Recycled, same issue.  It would appear the back end is reciving a handshake asI found the Web Dispatcher IP in the ICM trcae.  I do not have the paramtere icm/traffic_control set anywhere?  I keep seeing Nettimeout (30) exceeded by peer.

ICM_Trace.txt.zip