6.40 Ramp-Up: Dispatcher problem

[Former Member]

Hi,

we have installed the WAS 6.40 unicode version (ABAP + Java) and Adobe Document Services as part of the Ramp Up.

The installation was done successfully without any problems and Support Packages (ABAP, BASIS) have been applied up to level 3, in addition the ABAP kernel has been upgraded to patch level 19.

We have the following issues:

1. In the Microsoft Management Console the disp+work

(dispatcher) process is in yellow status: "Running but dialog queue info unavailable" even though we can logon to the system through the GUI and do not see any error messages in the system.

2. When we try to test print any Adobe Form through transaction code "SFP", we get the following error message:

"Test for function group /1BCDWB/SM00000001 Function module /1BCDWB/SM00000001

Runtime: 7,670,791 Microseconds

Exception SYSTEM_ERROR

Message ID: FPRUNX Message number: 001

Message: Adobe document services error: SOAP Runtime Exception CSoapExceptionTransport : (1001)

...

3. The trace file in the ICM Monitor ("SMICM") shows the following error messages:

[Thr 4636] *** INFO => the EXTBIND attribute in parameter

icm_server_port_<xx> for service 8000 is not necessary on Windows - i

[Thr 4636] Tue Jul 27 17:58:19 2004

[Thr 4636] *** WARNING => IcmNetCheck: NiAddrToHost(10.0.0.1) took 11 seconds [icxxtool.c 431]

[Thr 4636] *** WARNING => IcmNetCheck: 1 possible network problems detected - please check the network/DNS settings [icxxtool.c

[Thr 3940] Tue Jul 27 17:58:28 2004

[Thr 3940] IcmJ2EEScheduleFunc: WARNING: no HTTP service defined

[Thr 4896] Tue Jul 27 18:02:02 2004

[Thr 4896] *** ERROR => IcmCreateCacheInvalMsg: no HTTP/HTTPS service active [icxxmsg.c 2903]

[Thr 4896] *** ERROR => IcmCreateCacheInvalMsg: no HTTP/HTTPS service active [icxxmsg.c 2903]

[Thr 4896] *** ERROR => IcmCreateCacheInvalMsg: no HTTP/HTTPS service active [icxxmsg.c 2903]

We also posted this as a Ramp-Up OSS message but maybe someone on this forum came across this as well before...

Thanks,

Guenther

Message was edited by: Guenther Schober

Message was edited by: Guenther Schober

[Former Member]

To resolve step 3, remove the EXTBIND=1 parameter from the instance profile. EXTBIND is only needed when using ports < 1024.