Web service ping failed (RC=503).Erreur du Service...

Hello,

I'm trying to install solution manager 7.1 sp4 according to the
Installation guide "configuration of SAP Solution Manager 7.1" .
in step 5.3 "logical ports Creation" of system preparation.
i followed the step's in the documentation link , when i choose the
Ping Web Service pushbutton i got the error
"Web service ping failed (RC=503).Erreur du Service ping : Service
Unavailable " as shown in the attached document

NB i checked the note oss 1659135 but don't help

Please advice
Hicham ABDELMOTTALIB

SAP Managed Tags:
SAP Solution Manager

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

Hi,

Please try to access the URL of the web service via IE and see detailed information.

and please also check if application sap.com/tc~smd~ws~agent~monitoring.has been started

successfully via VA.

You can also try to redeploy LM-SERVICE component and see if it helps.

Thanks.

Jim

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi, Jim

What is the detailed information you need on the WS I do not see Web Services Navigator?

I am restart sap.com/tc~smd~ws~agent~monitoring.has bot not resolved.

Why redeploy LM-SERVICE, we in installation no errors occurred.

Hi,

Please open the URL of the web service directly via IE, you will see detailed error.

Thanks.

Jim

Hi, Jim

I do not understand you tell the Jim on which of the four screens WS_URL.jpg that you need to press?

Regards, Anvar.

Hi, Jim

I am chek all URLs, all OK by next list

http://hostname.sap.kz:51200

CO_DIAGSTP_WS_AGT_SMDAGENT_MON
Logical Port Name = LP_WS_SMDAGENT_MONITORING
URL Access Path = /DiagSetupServices/DiagSetupConf?style=document
CO_DIAG_WILY_WS_MANAGED_SETUP
Logical Port Name = LP_WS_MANAGED_SETUP
URL Access Path = /ManagedSetupWS/Config1?style=document
CO_E2E_MAI_CONFIGURATION
Logical Port Name = LP_E2E_MAI_CONFIGURATION
URL Access Path = /E2E_MAI_Configuration/Push?style=document
CO_E2E_PROBLEM_CONTEXT_MANAGER
Logical Port Name = LP_E2E_PROBLEM_CONTEXT_MANAGER
URL Access Path = /ProblemContextWS/Config1?style=document
CO_DIAGSTP_WS_DIAG_SETUP
Logical Port Name = DIAGSTP_WS_LOCAL_PORT
URL Access Path = /DiagSetupServices/DiagSetupConf?style=document
CO_BIMON_CFGBOBJMON_SERVICE_VI
Logical Port Name = LP_BIMON_CFGBOBJMON_SERVICE
URL Access Path = /BOBJMonService/default?style=document

Regards, Anvar.

Hi Anvar,

Did you find the solution?

Thanks.

Regards,

Stephan

Discussion moved from About SCN to SAP Solution Manager.

When posting, please select an appropriate space where topic experts will see and reply to it: SCN Site Index

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello, Hicham Abdelmottalib

Could you please describe how you solved the problem because we have a similar problem with the same version solution manager 7.1 sp8.

Regards, Anvar.

Hi,

In the step 5.2 did you run soamanager and then click on Simplified Web service configuration.

In the Api settings did you

Select all and Save.

Start back again with 5.2 as executed and then 5.3

Can you check this not is valid for you.

Note 1801045 - SolMan Setup: Error Message in Logcal Port creation

Thanks

Rishi abrol

Hello, Rishi

Thank you for your response, but unfortunately the note did not help.

On a working version of SAP Solution Manager 7.1 SPS04 we installed SPS08 and then we did not perform step 4.4 in the System Preparation.

Error:

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")

We have reinstalled the agent version DIAGAGT73SP03_0-20006983.SAR Installation of DIAGNOSTICS AGENT 7.3 SP03 platform HP-UX on IA64 64bit.

Tried to solve the problem of sap notes 1837656, 1752309, 1659135, 1752309, 1822831, 1663549, but not resolved.

Regards, Anvar.

Hi,

I checked that you Java patches are at SP12.

As you are getting the below 503 error which means

http 503 (Service Unavailable)

- Make sure your Solution Manager java stack is operational. This error is thrown when the java stack has not completed its startup procedure, or when a deployment is pending. For troubleshooting, check if the Java Web Services endpoints are reachable (http 404 case - troubleshooting)

As per note this Note 1822831 - Web Service Soap Errors in solman_setup

did you patch your Java system using JSPM?

Thanks

Rishi abrol

Hi,

not JSPM, we using /usr/sap/DSM/DVEBMGS12/SDM/program/RemoteGui.sh

Regards, Anvar.

Hi,

Can you also check and post the ICM and the default trace and std_server<>.o* of the java system.

Thanks

Rishi Abrol

Hello Anvar,

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

BR,

Kamil

Hi,

I'm sorry but I do not know where to get this information

Regards, Anvar.

Hi,

You should always use JSPM or SUM tool to do the patch upgrade.

If you have patched the java why have you kept the ABAP at lower version.

Can you please check the logs which i asked and post them and see if you see any error.

Is the Java side of the solution manager running fine....

Thanks

Rishi Abrol

Hi,

Thanks

Rishi abrol

Hello, Kamil

Thanks for your advice.

SAP Note 1837656 does not solve the problem.

Regards, Anvar.

Hi, Rishi

We abap instance also parched please see screenshot abap_sps.jpg.

In trace in SMICM_ALL_LOG.TXT one error

[Thr 01] *** ERROR => NiIBindSocket: could not delete file '/tmp/.sapstream64999' (hdl 1; errno=0) [nixxi.cpp 3725]

In /usr/sap/SID/DV*/work/std_server0.out in std_server0.out.txt no error.

Regards, Anvar.

Hi,

All the service look to start properly on the java side.

Can you please check what is the kernel patch level you are at.

Please check the below note.

1629748 - traffic control timeout does not work properly

Thanks

Rishi abrol

Hi, Rishi

Current kernel patch level 401, please see attach file kernel_sps.jpg.

Now i am download SAPEXEDB_500-20006704 and SAPEXE_500-20006703.SAR, but be loaded at 2 hours.

kernel release 720

kernel make variant 720_EXT_REL

DBMS client library

compiled on HP-UX B.11.31 U ia64 for hpia64

compiled for 64 BIT

compilation mode UNICODE

compile time Sep 15 2013 19:42:08

update level 0

patch number 500

source id 0.500

Regards, Anvar.

Hi, Richi

I am updated kernel up 500, problem not solved.

Regards, Anvar.

HI, Rishi

Although there is now displayed in the file /usr/sap/DAA/SMDA97/SMDAgent/logdpc.0.log mistake that was not previously

Sep 30, 2013 12:40:22 PM [Thread[ExRun:dpc:job_1,5,dpc:job:ExecTG]] Error [DPCServicePushVersionJob.pushVersioninfo] Error occurred when calling the DPC Push web service. (http://tttttt.sap.hh:8012/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=001).

[EXCEPTION]

java.rmi.RemoteException: Service call exception; nested exception is:

com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://tttttt.sap.hh:8012/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=001"

at com.sap.smd.agent.wsclients.dpc.BindingStub.e2eDpcPushCfgVersion(BindingStub.java:138)

at com.sap.smd.agent.wsclients.dpc.BindingStub.e2eDpcPushCfgVersion(BindingStub.java:148)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.smd.api.util.SynchronizedProxy$SyncHandler.invoke(SynchronizedProxy.java:32)

at com.sun.proxy.$Proxy11.e2eDpcPushCfgVersion(Unknown Source)

at com.sap.smd.dpc.job.DPCServicePushVersionJob.pushVersioninfo(DPCServicePushVersionJob.java:88)

at com.sap.smd.dpc.job.DPCServicePushVersionJob.run(DPCServicePushVersionJob.java:53)

at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)

at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)

at java.lang.Thread.run(Thread.java:743)

Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://tttttt.sap.hh:8012/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=001"

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:998)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1452)

at com.sap.smd.agent.wsclients.dpc.BindingStub.e2eDpcPushCfgVersion(BindingStub.java:131)

... 12 more

Regards, Anvar.

Hi,

Can you please check this note for this issue.

1839894 - Diagnostics Agent log shows "Invalid Response Code: (401) Unauthorized"

Thanks

Rishi Abrol

Ask a Question

Top Q&A Solution Author

User

Count