SMDAgent and SAPOSCOL error on startup

[neeta_patel2]

Dear all,

Have installed an SMD Agent in PI 7.1 system (virtual system) and on startup there is an error:

The process saposcol is running.

Any ideas? Thanks!

Neeta

<property name="ErrorsOut">

<value>0</value>

</property>

<property name="Collisions">

<value>0</value>

</property>

</LanInterface>

</LAN>

<MonitoredProcesses>

</MonitoredProcesses>

</saposcol>

Dec 7, 2009 3:16:24 PM [Thread[SAPOsCol,5,main]] Error

com.sap.smd.wily.hostagent.action.SapOsColAction - doRun(): Error

parsing saposcol XML output

[EXCEPTION]

com.sap.smd.wily.hostagent.PermanentException:

com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error:

com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 38(:main:, row:178, col:60)(:main:, row=178, col=60) ->

com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 38(:main:, row:178, col:60)

at com.sap.smd.wily.hostagent.action.AbstractAction.handleError

(AbstractAction.java:324)

at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml

(SapOsColAction.java:156)

at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun

(SapOsColAction.java:428)

at com.sap.smd.wily.hostagent.action.AbstractAction.run

(AbstractAction.java:53)

at

com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run

(PooledExecutor.java:728)

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

Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException:

Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported

character: 38(:main:, row:178, col:60)(:main:, row=178, col=60) ->

com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 38(:main:, row:178, col:60)

at com.sap.engine.lib.xml.parser.DOMParser.parse

(DOMParser.java:139)

at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse

(DocumentBuilderImpl.java:127)

at javax.xml.parsers.DocumentBuilder.parse

(DocumentBuilder.java:76)

at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml

(SapOsColAction.java:153)

... 4 more

Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported

character: 38(:main:, row:178, col:60)

at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read

(EncodedDataReader.java:207)

at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read

(EncodedDataReader.java:205)

at

com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read

(AdvancedXMLStreamReader.java:143)

at com.sap.engine.lib.xml.parser.XMLParser.scanAttValue

(XMLParser.java:1469)

at com.sap.engine.lib.xml.parser.XMLParser.scanAttList

(XMLParser.java:1577)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement

(XMLParser.java:1712)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent

(XMLParser.java:2442)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement

(XMLParser.java:1843)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent

(XMLParser.java:2442)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement

(XMLParser.java:1843)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument

(XMLParser.java:2845)

at com.sap.engine.lib.xml.parser.XMLParser.parse0

(XMLParser.java:231)

at

com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException

(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse

.....

.....

....

[raguraman_c · Accepted solution]

Hi,

Check this note

1003509

This should solve your problem.

Feel free to revert back.

-=-Ragu

[neeta_patel2 · Accepted solution]

Hi Ragu,

Thanks for the response. We are running EHP1 on our Solution manager server and the version of LMSERVICE is:

sap.com LM-SERVICE 7.01 SP4 (1000.7.01.4.0.20090616054816) SAP AG SAP AG 20091020113507

The note refers to an older version.

Regards, Neeta

[Former Member · Accepted solution]

Latest version for LM-SERVICE is SP5. Try patching it to the latest level.

[Former Member · Accepted solution]

Hello,

Have you got any solution?

I am also getting the same error and looking for solution..

saposcol exited with error code -999

Error parsing saposcol XML output

regards

Manoj

[francois_keen]

Hi Neeta.

Which OS your PI system runs on?

If it's on Solaris, I had a similar issue with my SMD agent not reporting data in Wily for the SMD hostagent metrics and this was first related to an xml parsing problem.

In order to solve my issue, SAP released of new version of saposcol to correct this a month ago (7.01 patch level75). My sattellite was an NW7.0 EHP1 system but it looks like SAP hasnt released anything yet regarding saposcol 7.1 as the newest on SWDC is from november.

I would open an OSS message as I'm confident you're facing a bug.

Cheers

francois

[Former Member]

Dear Neeta,

Latest version for LM-SERVICE is SP5 and they have corrected saposcol problem in this version so you will have to patch your system to get rid of this error with SAPOsCol.

Regards

Shailesh

[neeta_patel2]

HI Shailesh,

We did install the new LMSERVICE on Solution manager - but after doing this, does the managed system configuration need to be re-run? we are facing issues with saposcol in the managed systems (monitored).

Thanks, Neeta

[Former Member]

Dear Neeta,

Yes try executing the managed system setup again and paste the logs if you have any problems again.

The Problem should be solved.

Regards

Shailesh

[Former Member]

Hello Neeta,

Did you install the SAP Host Agent after installing the SMD Agent 7.11 as

http://help.sap.com/saphelp_nwpi71/helpdata/en/48/c6f9627a004da5e10000000a421937/content.htm

There is a new "Diagnostics Setup Guide* delivered by SAP in the middle of Novembre 2009 :

Diagnostics Agent 7.11 -Setup Guide

Best regards

P. Cuennet

[neeta_patel2]

Hi,

What is the SAP Hostagent and can this be installed on a NW7.0 EHP1 system? Are both the SMDAgent and SAP Hostagent required on the monitored systems?

Thanks, Neeta