Issues in diagnostics configuration

[Former Member]

Hi All,

Below are the system details::

Solman 7.01 (SAP EHP1 for solution manager 7.0)

Oracle 10.2.0.4.0

SunOS 5.9

The following error occurs during Basic configuration->Diagnostics Configuration.

1)Cannot call Diagnostics Setup web service

2)Web Service URL: http://r3XXX.ZXZXZC.local:8160/DiagSetupServices/DiagSetupConfig?style=document

3)Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")

4)Error when processing Web service call

5)SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")

The workaround i have done  is following the instructions given in KBA 1726533 - SOAP runtime error "HTTP Code 404 " during Diagnostics Configuration  &   

following few steps as per KBA 1752309 - Web service invocation problem caused by Unsupported xstream found ("HTTP Code 404 : Not Found") during SOLMAN_SETUP

Even after keeping parameter system/type = DS in instance profile +restart, still the same  5  errors are coming , due to which diagnostics configuration is getting  failed .

Let me know if anyone can provide your solutions /workarounds . 

Regards

Ram

[Former Member]

Hi All ,

LM SERVICE is patched as per hr sap note  1514414 - LM-SERVICE 701 SP08 patch 0.

Now am getting one last error in diagnostics configuraion & further the rfcs SOLMANDIAG and WEBADMIN are working fine , but it throws error ,below is the error am getting ::

Mon Nov 03 08:49:10 2014 RFC Failed to create TCP/IP RFC on ABAP side (SM59)

Step RFC Details

Failed to create TCP/IP RFC on ABAP side (SM59)

!! Exception :      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE

Exceptions

com.sap.aii.proxy.framework.core.BaseProxyException:      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE

at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)

at com.sap.sup.admin.setup.abapproxy.tcpiprfc.TcpIpRfcProxy_PortType.inst_Create_Tcpip_Rfcdest(TcpIpRfcProxy_PortType.java:16)

at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:987)

at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:961)

at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:376)

at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)

at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)

at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:282)

at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:35)

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:331)

at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)

at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)

at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)

at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)

at SoapServlet.doPost(SoapServlet.java:51)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

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)

Let me know if anyone can help on this as this was one error is the last one where am unable to find the exact problem !!!

Regards

Bharat

[Sriram2009]

Hi Bharat

Your Source system version & SP level?

BR

SS

[Former Member]

Hi Sriram ,

Solution Manager 7.0 EHP1 SPS25

Regards

Bharat

[Sriram2009]

Hi

Could you refer the SAP KBA

1829825 - Cannot call Diagnostics Setup web service

BR

SS

[Former Member]

Hi Sriram ,

Am getting different error , the KBA is not the exact one .

Regards

Bharat

[Sriram2009]

Hi

Better you can raise the SAP Support ticket

BR

SS

[Former Member]

Hi Bharatram,

Could you refer this note

1726533 - SOAP runtime error "HTTP Code 404 " during Diagnostics Configuration

Regards,

Dhuvaraganathan M.

[Former Member]

Hi Dhuvaraganathan,

I have already  checked that KBA article 1726533 ,still the issue is same .

I have posted in it my first query .

Regards

Ram

[Sriram2009]

Hi Ram

Could you refer the SAP KBA

1663549 - Web service invocation problem caused by Unsupported xstream found ("HTTP Code 401 : Unaut...

BR

Ram

[giri_ayyagari]

Hi Bharatram

First check your antivirus/firewall settings make sure nothing blocking. if you still experience issues i suggest uninstall it and reinstall.

Let us know hod did it go.

-Giri

[Former Member]

Hi Ramakrishna,

Stop and start SAP host agent also along with DAA agent .

Thanks,

Prakash

[Former Member]

Hi Prakash Reddy ,

restart of hostagent did not solve the issue

Further there is no daa agent running too.

Regards

Ram

[Former Member]

Hi Ram,

DAA (diagnostic agent ) agent should up and running and it should connect to solman too.

Thanks,

Prakash