Introscope Host adapter turns red in managed system config

[Former Member]

Hi all,

I am performing the managed system configuration for ABAP and Portal systems.

The Host agent adapter turns red after executing the activity.

The error seems to be common.

1905704 - note is not helpful as we don't use a web dispatcher.

we have checked note 1822831 and have made the logical port creation again..but that too didn't help.

kindly help in resolving the issue.

Also, one more doubt, how critical is this step in a ABAP only instance..can we ignore this step.

[Former Member · Accepted solution]

Hello,

What about this note 1944357 - Managed System Configuration Error - "CX_SOAP_CORE : Error when calling SOAP Runtime funct...

BR,

K.

[Former Member · Accepted solution]

Hi Kamil,

Thanks for the reply..

The note 1944357 points to the notes 1905704 - and 1822831 which is not applicable.

in our case we don't use web dispatcher.

so kindly guide .

Thanks,

Subhashini.

[Former Member · Accepted solution]

please share the error screen shot.

[Former Member · Accepted solution]

Hi Sunil,

The error screenshot i have given for your reference.

Thanks,

Subhashini

[Former Member · Accepted solution]

have you gone through the note 1822831? the note has the detailed explanation about the error you are getting.

[Former Member · Accepted solution]

Hello,

Could you check LM-Service?

• http 500 (Server Error) :
  - This error can be due to a proxy (Web Dispatcher, ICM...) involved in the WS call : reconfigure the logical port in SOAMANAGER (see troubleshooting section below) so that it reaches directly the Java Dispatcher instead of going through a WS proxy. If reconfiguring the Logical Port solves the issue, you may open a ticket in component BC-CST-IC (when ICM is the failing proxy) or BC-CST-WDP (when Web Dispatcher is the failing proxy).
  - If the error is thrown in a fast way (below 1 minute response time) and no Web Service proxy is involved in the call, the error is actually due to an unexpected run-time error on Solution Manager Java side. Make sure the last LM-Service deployment had no error logs.
  - If the error is thrown after 5 minutes or more, it can be due to a timeout issue in the Web Service layers, while the requested service actually performs correctly in the background. Refer to timeout error message in the next section.

BR,

K.

[Former Member · Accepted solution]

Hi Sunil,

I have made all the changes as specified by the note....

but still the error is occuring...

the logical ports are recreated and webservice ping is successful...

but still the configuration is not successful with the host adapter...

kindly guide.

Thanks,

Subhashini

[Former Member · Accepted solution]

Hi Kamil,

LM-service was latest..and deployment don't have any errors...

we have updated LM-srevice to latest patch sepcifically for this issue...but still it didn't reolve our error

Is there any thing other this which is missing...

kindly guide.

Thanks,

Subhashini

[Former Member · Accepted solution]

Hi Subhashini,

Give a try  1837656 - Extractor Setup returns "CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: (...

and 1852733 - Unsupported xstream found ( "HTTP Code 500 : Timeout ") while running manage system config...

BR,

K.

[Former Member]

did you checked the note 1659135

[Former Member]

Thanks Sunil for the reply....

I have checked the note...my ping works fine without any error, and all settings are as per the note..

but still the error is there.

Kindly guide.

Thanks,

Subhashini.