SAP Knowledge Base Article - Preview

2392232 - Web Dispatcher checkconfig returns illegal OK code: 302

Symptom

When running the checkconfig option of the SAP Web Dispatcher, it returns an error about code 302. Below are some examples:

 

> sapwebdisp pf=<WDP profile> -checkconfig

[...]

Checking external servers with URL "/":
Checking external server http://<HOST>...ERROR: illegal OK code: 302

[...]

> sapwebdisp pf=<WDP profile> -checkconfig

[...]

Checking ABAP servers with URL "/sap/public/icman/ping":
Checking ABAP server http://<HOST>...ERROR: unexpected OK code: 302
ERROR: check node "/sap/public/icman/ping"in transaction sicf

[...]



The 302 response can also be seen on the SAP Web Dispatcher trace file (dev_webdisp). For example:

*** WARNING => Failed to read group info for system [SID] (ABAP,HTTP) from [hostname]: Found(302)

It can also be seen on the Web Admin UI, at the "backend system info", or at the "monitor application servers" menus (at the latter, there would be a red triangle, and the information about the "redirect response" is seen when hovering the mouse over the red triangle).


Read more...

Environment

  • SAP Web Dispatcher all releases

Product

ABAP platform all versions ; SAP NetWeaver all versions

Keywords

Webdispatcher HTTP HTTPS Internet Communication Manager Load balancing balancer , KBA , BC-CST-WDP , Web Dispatcher , BC-CST , Client/Server Technology , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.