Solman 7.1 SP11 HTTP Code 503 : Service Unavailable

[Former Member]

Dear Gurus,

I need your help as I have problems with my Solman 7.1 SP11.

I have just upgraded my Solman 7.1 SP11 and I already applied sap notes 1933506 latest version 9.

When I accessed solman_setup, I found the same error messages in these two steps:
- solman_setup - configure connectivity - configure web dispatcher - via system settings (icm/httpurlloc) - test connectivity
- solman_setup - configure connectivity - set authentication policy for agents - use basic authentication (user/password)

Error Message: Error while calling Diagnostics setup web service. Check note 1822831.
CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 503 : Service Unavailable")
CX_SOAP_FAILURE : Error when processing Web service call
CX_SOAP_CORE : Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 503 : Service Unavailable")

I tried to troubleshoot using these below sap notes but still not able to solve the issue:
- snote 1752309 - Web service invocation problem caused by Unsupported xstream found
- snote 2018474 - Unsupported xstream found (HTTP Code 503  Service Unavailable)
- snote 1822831

This error message is encountered in my productive client (001). However if I access the solman_setup from client 000, it has no problem and working fine.

My solman has: (as recommended by sap note 1483508)

- ST 710 SP11 (SAPKITL711)

- LM-SERVICE 7.10 SP11 (1000.7.10.11.1.20140505095300)

I appreaciate if you can advise me.

Thank you.

Regards,
Stephan

[divyanshu_srivastava3 · Accepted solution]

Hi stephan,

Try to reconfigure logical ports using SOAMANAGER.

Regards,

Divyanshu

[Former Member · Accepted solution]

Dear Sriram and Divyanshu,

I apologize for late reply. I have tried both your ways but still the errors persist.

I found in my SMD Agent administration showing that my solman SMD agent is connected but "no server name". Is this related?

Regards,

Stephan

[divyanshu_srivastava3 · Accepted solution]

I don't think this is related to agents as you know this is client customising problem probably.

I will come back to your query once a reach back.. my home

Regards,

Divyanshu

[Former Member · Accepted solution]

Hi Divyanshu,

Thank you.

Regards,

Stephan

[Sriram2009 · Accepted solution]

Hi Stephan

Could you check this SAP Note

1663549 - Unsupported XStream found error

Regards

SS

[Former Member · Accepted solution]

Hi Sriram,

Thanks for the reply. I tried that one before as well but it didnt work.

Thanks.

Regards,

Stephan

[Sriram2009 · Accepted solution]

Hi Stephan

Thanks for your info

Better you can raise the ticket to SAP Support. this may be a new bug

Regards

Sriram

[divyanshu_srivastava3 · Accepted solution]

Hi Stephan,

What happened when you used this note:

1917038 - CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTPCode 500 : Internal ...

Regards,

[divyanshu_srivastava3 · Accepted solution]

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

[Former Member · Accepted solution]

Hi Divyanshu,

For 1917083, I do not use Webdispatcher and I have increased the PROCTIMEOUT to 1800 but still it did not work and I also run the step to create the Logical Ports as well.

For 1852733, I do not encounter such error, but I did find that my SMD Agent has no server name. It says <no server name> which you  told me that it had nothing to do with my initial error.

Thanks.

Regards,

Stephan

[divyanshu_srivastava3 · Accepted solution]

Hi Stephan,

I am really sorry for my reply in which I wrote it's not related to agent. I think I replied on your message by mistake, it was some other solman issue. Perhaps, because I was using my mobile phone to access SCN while I was travelling.

You should fix this hostname thing, at least. And try to re-execute this step.

I will get back to you on this with some more info.

Regards,

Divyanshu

[Former Member · Accepted solution]

Hi Divyanshu,

No problem. Thank you for the reply. However I am still checking on it and I will let you know next week. The note 1852733 that you gave did help me a bit to discover the error.

Thank you.

Regards,

Stephan

[Former Member · Accepted solution]

Hi Divyanshu,

Sorry for late reply. I managed to fix the agent on my solman to have the server name registered. However I am still having error with the initial issue.

Do you have anymore suggestions?

Thanks.

Regards,

Stephan

[divyanshu_srivastava3 · Accepted solution]

Hi Stephan,

There is one KBA which is related to a similar issue. However, this happens when their are permission issues and app is not started.

2018474 - Unsupported xstream found: ("HTTP Code 503 : Service Unavailable")

and

1440724 - Addressing server nodes directly in AS Java

Also, can you share default trace at the time you get this error ?

Regards,

Divyanshu

[Former Member · Accepted solution]

Hi Divyanshu,

I will check on your sap notes and will let you know later. Another this is in SOAMANAGER, for all Consumer Proxy including CO_BIMON_CFGBOBJMON_SERVICE_VI - LP_BIMON_CFGBOBJMON_SERVICE - ping service and I will get error message:

Web service ping failed (RC=503). Service Ping ERROR: Service
Unavailable

Thanks.

Regards,

Stephan

[Former Member · Accepted solution]

Hi Divyanshu,

I have tried both sap notes:

2018474 - it does not apply to me since I do not find errors with after checking from the guide

1440724 - I have tried this sap note but the problem persists

When I rerun the error, I could not find any related errors in the default trace, but I found something in the applications.0.log.

defaultTrace.7.trc:

        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

#
#1.#005056A100AB007D0000002C00002D3F0004FDA9608EBC29#1404803818109#com.sap.smd.server##com.sap.smd.server#SMD_AGT#105##ADBDF203066F11E4AF7A0000003018B2#adbdf203066f11e4af7a0000003018b2-0#adbdf203066f11e4af7a0000003018b2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###[SMDManager.registerPendingAgent] Receive registration for an already existing entry. Registration REJECTED
Existing entry :
AgentHandleEntry: com.sap.smd.SMDManager$AgentHandleEntry@92414
         JNDI key         : sapdev.sap.jjsea.com_DA1_SMDA97@2014.07.08-15.10.58.662
         Server Name      : sapdev
         ID               : sapdev.sap.jjsea.com_DA1_SMDA97
         CanonicalHostName: sapdev.sap.jjsea.com
         HostName         : sapdev
         Address          : 192.168.5.30
         AgentHandleWrap  : com.sap.smd.local.AgentHandleWrapper@ef43fbf
Incoming entry:
AgentHandleEntry: com.sap.smd.SMDManager$AgentHandleEntry@6ad6bb2f
         JNDI key         : null
         Server Name      : sapdev
         ID               : sapdev.sap2.jjsea.com_DA1_SMDA97
         CanonicalHostName: sapdev.sap2.jjsea.com
         HostName         : sapdev
         Address          : 192.168.5.31
         AgentHandleWrap  : com.sap.smd.local.AgentHandleWrapper@379b4175#
#1.#005056A100AB007D0000002D00002D3F0004FDA9608EBE5D#1404803818110#com.sap.smd.server##com.sap.smd.server#SMD_AGT#105##ADBDF203066F11E4AF7A0000003018B2#adbdf203066f11e4af7a0000003018b2-0#adbdf203066f11e4af7a0000003018b2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Java###Agent Registration failed
[EXCEPTION]
{0}#1#com.sap.smd.server.manager.SMDException: [SMDManager.registerPendingAgent] Receive registration for an already existing entry. Registration REJECTED
Existing entry :
AgentHandleEntry: com.sap.smd.SMDManager$AgentHandleEntry@92414
         JNDI key         : sapdev.sap.jjsea.com_DA1_SMDA97@2014.07.08-15.10.58.662
         Server Name      : sapdev
         ID               : sapdev.sap.jjsea.com_DA1_SMDA97
         CanonicalHostName: sapdev.sap.jjsea.com
         HostName         : sapdev
         Address          : 192.168.5.30
         AgentHandleWrap  : com.sap.smd.local.AgentHandleWrapper@ef43fbf
Incoming entry:
AgentHandleEntry: com.sap.smd.SMDManager$AgentHandleEntry@6ad6bb2f
         JNDI key         : null
         Server Name      : sapdev
         ID               : sapdev.sap2.jjsea.com_DA1_SMDA97
         CanonicalHostName: sapdev.sap2.jjsea.com
         HostName         : sapdev
         Address          : 192.168.5.31
         AgentHandleWrap  : com.sap.smd.local.AgentHandleWrapper@379b4175
        at com.sap.smd.SMDManager.registerPendingAgent(SMDManager.java:3959)
        at com.sap.smd.SMDServerHandle.internalRegisterAgent(SMDServerHandle.java:330)
        at com.sap.smd.SMDServerHandle.registerAgent(SMDServerHandle.java:197)
        at com.sap.smd.SMDServerHandlep4_Skel.dispatch(SMDServerHandlep4_Skel.java:77)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

applications.0.log:

#1.#005056A100AB00810001DFB00000104A0004FDA906A5BE1E#1404802309668#/Applications/AdminConsole/Abap#sap.com/tc~smd~e2ebwextractor#com.sap.sup.admin.abap.rfc.configuration.AbapConfRepository#J2EE_GUEST#0##0F0B557AFDC511E38B870000003018B2#0f0b557afdc511e38b870000003018b2-0#0f0b557afdc511e38b870000003018b2#Thread[ExRun:default_3,5,default:ExecTG]##0#0#Info#1#com.sap.sup.admin.abap.rfc.configuration.AbapConfRepository#Plain#[8312] Read the property 'numberOfRfcConnectionsInJcoPool', value 10'.###

#1.#005056A100AB00810001DFB10000104A0004FDA906A5BE9C#1404802309668#/Applications/AdminConsole/Abap#sap.com/tc~smd~e2ebwextractor#com.sap.sup.admin.abap.rfc.ManagedAbapRfcManager#J2EE_GUEST#0##0F0B557AFDC511E38B870000003018B2#0f0b557afdc511e38b870000003018b2-0#0f0b557afdc511e38b870000003018b2#Thread[ExRun:default_3,5,default:ExecTG]##0#0#Info#1#com.sap.sup.admin.abap.rfc.ManagedAbapRfcManager#Plain#[8312] Reused the pool 'SmdPool#WEBADMIN' with the following Abap Connection data 'user=SMD_RFC, client=001, language=EN, host=localhost, , systemNumber=00, locale=true'.###

#1.#005056A100AB00810001DFB20000104A0004FDA906A5E66A#1404802309678#/Applications/AdminConsole/Abap#sap.com/tc~smd~e2ebwextractor#com.sap.sup.admin.abap.rfc.configuration.AbapConfRepository#J2EE_GUEST#0##0F0B557AFDC511E38B870000003018B2#0f0b557afdc511e38b870000003018b2-0#0f0b557afdc511e38b870000003018b2#Thread[ExRun:default_3,5,default:ExecTG]##0#0#Info#1#com.sap.sup.admin.abap.rfc.configuration.AbapConfRepository#Plain#[8312] Read the property 'numberOfRfcConnectionsInJcoPool', value 10'.###

#1.#005056A100AB00810001DFB30000104A0004FDA906A5E6B9#1404802309678#/Applications/AdminConsole/Abap#sap.com/tc~smd~e2ebwextractor#com.sap.sup.admin.abap.rfc.ManagedAbapRfcManager#J2EE_GUEST#0##0F0B557AFDC511E38B870000003018B2#0f0b557afdc511e38b870000003018b2-0#0f0b557afdc511e38b870000003018b2#Thread[ExRun:default_3,5,default:ExecTG]##0#0#Info#1#com.sap.sup.admin.abap.rfc.ManagedAbapRfcManager#Plain#[8312] Reused the pool 'SmdPool#WEBADMIN' with the following Abap Connection data 'user=SMD_RFC, client=001, language=EN, host=localhost, , systemNumber=00, locale=true'.###

#1.#005056A100AB00810001DFB40000104A0004FDA906A60DD7#1404802309688#/Applications/AdminConsole/Abap#sap.com/tc~smd~e2ebwextractor#com.sap.sup.admin.abap.rfc.configuration.AbapConfRepository#J2EE_GUEST#0##0F0B557AFDC511E38B870000003018B2#0f0b557afdc511e38b870000003018b2-0#0f0b557afdc511e38b870000003018b2#Thread[ExRun:default_3,5,default:ExecTG]##0#0#Info#1#com.sap.sup.admin.abap.rfc.configuration.AbapConfRepository#Plain#[8312] Read the property 'numberOfRfcConnectionsInJcoPool', value 10'.###

#1.#005056A100AB00810001DFB50000104A0004FDA906A60E24#1404802309688#/Applications/AdminConsole/Abap#sap.com/tc~smd~e2ebwextractor#com.sap.sup.admin.abap.rfc.ManagedAbapRfcManager#J2EE_GUEST#0##0F0B557AFDC511E38B870000003018B2#0f0b557afdc511e38b870000003018b2-0#0f0b557afdc511e38b870000003018b2#Thread[ExRun:default_3,5,default:ExecTG]##0#0#Info#1#com.sap.sup.admin.abap.rfc.ManagedAbapRfcManager#Plain#[8312] Reused the pool 'SmdPool#WEBADMIN' with the following Abap Connection data 'user=SMD_RFC, client=001, language=EN, host=localhost, , systemNumber=00, locale=true'.###

#1.#005056A100AB002F000001BC0000104A0004FDA9083A7296#1404802336191#/Applications/AdminConsole/Scheduler##com.sap.sup.admin.scheduler.JmsScheduler####092E4A42FDCC11E38C8F0000003018B2#092e4a42fdcc11e38c8f0000003018b2-0#092e4a42fdcc11e38c8f0000003018b2#SAPEngine_System_Thread[impl:5]_75##0#0#Warning#1#com.sap.sup.admin.scheduler.JmsScheduler#Plain#[3926] The Scheduler is inactive: the Upgrader has not been run successfully!###

#1.#005056A100AB0023000001B60000104A0004FDA90A0445DA#1404802366195#/Applications/AdminConsole/Scheduler##com.sap.sup.admin.scheduler.JmsScheduler####04A03ED1FDC611E3843F0000003018B2#04a03ed1fdc611e3843f0000003018b2-0#04a03ed1fdc611e3843f0000003018b2#SAPEngine_System_Thread[impl:5]_51##0#0#Warning#1#com.sap.sup.admin.scheduler.JmsScheduler#Plain#[3992] The Scheduler is inactive: the Upgrader has not been run successfully!###

Thanks.

Regards,

Stephan

[Former Member · Accepted solution]

Dear All,

Finally I managed to solve my own problem. The issue for HTTP 503 Service Unavailable in solman setup - configure webdispatcher is caused by client - proxy settings in SICF.

After I removed the client proxy settings, I am able to complete my solman_setup without the HTTP 503 error.

Thanks.

Regards,

Stephan

[Sriram2009]

Hi Stephan

Check this SAP Note

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

1917038 - CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTPCode 500 : Internal ...

1944357 - Managed System Configuration Error - "CX_SOAP_CORE : Error when calling SOAP Runtime funct...

1880334 - Error while calling Diagnostics setup web service with HTTP Code 307 : TEMPORARY REDIRECT

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

BR

SS