cancel
Showing results for 
Search instead for 
Did you mean: 

Error processing Patch History

deborah_tolley2
Explorer
0 Kudos

Originally though I was getting this error because there were no patches installed, but have now installed Patch 02 (4.2 SP02 Patch 02) and am still getting the error, so that's not the problem.

Saw the post about back slashes in the paths and confirmed that the paths do use '\', even tried changing to forward slashes but still didn't work.  Copied and pasted the path from the server just to confirm and still doesn't work.

All other components are able to retrieve data, patch history is the only problem.

Here's a clip of the log:

javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: Not supported in SOAP 1.1 at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:180) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116) at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:189) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:276) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:104) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147) at com.sun.proxy.$Proxy39.executeOperation(Unknown Source) at com.sap.ps.bitool.tools.configwizard.e2e.SAPHostAgentOperationsWrapper.downloadBOEHistoryInfo(SAPHostAgentOperationsWrapper.java:525) at com.sap.ps.bitool.data.PatchHistoryExtractor.run(PatchHistoryExtractor.java:75) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) Caused by: javax.xml.soap.SOAPException: Not supported in SOAP 1.1 at org.apache.axis2.saaj.SOAPFactoryImpl.createFault(SOAPFactoryImpl.java:202) at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:169) ... 11 more |8E70A5307D164780BD2B9260447C263F28f|2016 06 28 19:58:07.515|-0400|Error| |>>|E| |BISupportTool| 7312|  1|main            | ||||||||||||||||||||||InterruptedException in Patch History java.lang.InterruptedException: There was an error processing Patch History information for host xxxxxxxx at com.sap.ps.bitool.data.PatchHistoryExtractor.run(PatchHistoryExtractor.java:124) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

Accepted Solutions (1)

Accepted Solutions (1)

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Deborah,

Thanks for reporting the problem.

Did you copy the operations.d folder to BI hosts?  Check the "Configure SAP Host Agent for BIPST) steps here:

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=439649059#GettingStartedGuide(BIrunningon...

If you have further trouble, please let me know.


Cheers

Toby



alfons_gonzalez
Active Participant
0 Kudos

Hi Toby,

We are suffering same issue but we have checked that operation.d folder is already copied to BI hosts. This is the message error we retrieve

  1. com.sap.ps.bitool.data.hardware.saphostcontrol.OperationExceptionFault: Command execution failed.

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)

  at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:135)

  at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238)

  at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:189)

  at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:276)

  at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:104)

  at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77)

  at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147)

  at com.sun.proxy.$Proxy39.executeOperation(Unknown Source)

  at com.sap.ps.bitool.tools.configwizard.e2e.SAPHostAgentOperationsWrapper.downloadBOEHistoryInfo(SAPHostAgentOperationsWrapper.java:525)

  at com.sap.ps.bitool.data.PatchHistoryExtractor.run(PatchHistoryExtractor.java:75)

  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

|5B8BD66C72674C6AAE0BF47648C24AB3286|2016 07 19 10:35:43.020|+0200|Error| |>>|E| |BISupportTool|  880| 17|Thread-3        | ||||||||||||||||||||||Unable to gather Patch History data from Landscape.

  1. java.lang.NullPointerException: while trying to read the field 'host' of a null object returned from java.util.ArrayList.get(int)

  at com.sap.ps.bitool.data.ExtractionManager.processPatchHistory(ExtractionManager.java:632)

  at com.sap.ps.bitool.data.ExtractionManager.run(ExtractionManager.java:205)


Rest of tool features works fine and we have validated succesfully the SAP WSDL adress on both servers.


Thanks,


Alfons

Toby_Johnston
Advisor
Advisor
0 Kudos

Hi Alfons,

Could you reproduce the error again and then on the BI server, go to C:/Program Files/SAP/hostctrl/work and zip up the log files dev_saphostexec, sapstartsrv.log, and sapstart.log and send to my email toby.johnston@sap.com.  This should provide some clue as to why the operation failed.

Thanks

Toby

Answers (0)