Managed System Configuration - Failing

[neeta_patel2]

Hi,

I am running the Solution Manager Wizard to configure end to end diagnostics and the initial and and basic configuration is complete.

In the Managed System configuration to connect an ABAP system, in the "Check Pre-requisites" is failing with:

No installation Path found in one of the Host - set the path in the setup wizard

No Instance path found! - set the instance path in the setup wizard.

Any ideas?

Thanks, Neeta

[Former Member · Accepted solution]

Hi,

Look liks the SMSY setting is not correct,

Do maintain the correct data source for the system definition, ( Preferably SLD then RFC). The step should go through.

PS: You can connect the systems (Maintain ABAP connection) through SMSY configuration wizard and skip that step too. (Hope you have taken care of the pre-requisites in managed systems)

Hope this helps.

Do revert for any issues.

Thanks,

Jagan

[Former Member · Accepted solution]

Is the issue resolved or persists?

[neeta_patel2 · Accepted solution]

Hi,

No thi sissue is not resolved... We added the corresponding java stack to the existing solution manager abap stack version EHP1 with a local SLD. The SMSY information is not getting updated with the java stack information - so that appears to be a problem with the pre-requsite checks for the managing system (solution manager)

I am trying to set up the SMDAgent but the pre-requisite steps are failing in the wizard - as above.

Thanks, Neeta

[Former Member · Accepted solution]

Hi,

Try to maintain the Java stack system information manually in SMSY.

Along with the Application server ABAP, select the APplication server Java too in SELECTION OF MAIN INSTANCES tab and then define the Java stack system in System Components section in SMSY.

Define the server node, dispatcher node and J2ee server node properly for java system under the INSTANCES tab.

And then execute the SMDagent setup wizard in managed system setup wizard.

This way should work.

[Former Member · Accepted solution]

HI,

If you have SLD as Datasource, Have you setup Landscape_Fetch Job?. If it fails,look at the logs.

this job should run fine. If SLD is not Proper, Do an SLDcheck and sort all the SLD issues.

But yes, you do have an option of defining the Java instance manually, But still, you willl get the same error such as installation path not found!..Etc.

Thanks,

Jagan

[neeta_patel2 · Accepted solution]

Hi Jagan,

We have manually setup the smsy information, instances, components for the Solution manager java stack. The sattelite system (managed system) information is also all setup in SMSY in solution mgr. We are still getting in the pre-requisite step:

No setup status found in Diagnostics repository for <hostname>/D01

No relevant Main instances found with the Diagnostic relevant product verison!

No software component version found!

No installation path found in one of the Host!

No instance path found!

Should I ignore the above and proceed to install the SMDAgent on the managed host which is running ECC6.0 & which version of the SMDAgent do I need? EHP1 or is there a specific version for ECC6.0?

NOTE that the SMDAgent is running on Solution manager (version is EHP1)

Thanks!

Neeta

[Former Member · Accepted solution]

Hi,

Yes, you may ignore these errors in SOLMAN_SETUP pre-requisites, and proceed with the setup in Managed systems setup wizard.

It'll work provided you have correctly maintained, manually, the server/dispatcher/j2ee instance nodes for Java nodes and correct host and component version for ABAP based instance.

For the SMD agent version, you may refer to the SAP Note 1274287 - End-to-End Diagnostics SP18(EHP1)- SP19 - SP20 - SP21

Hope this helps.

[neeta_patel2 · Accepted solution]

Hi ,

Continuing with the SMD Wizard setup of the managed system (abap) and now get the following:

Step Wilyhost Agent Details

Created 0 action(s).

1 Wilyhost Agent(s) from host saperdsrv1 is connected to the EM.

90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: SAP OsCol - null

Please check SMDAgentApplication log files for warnings and errors.

Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(<hostname>:5001).

We have Wily EM installed on a separate server.

The SMDAgentApplication log file has the following errors:

Nov 16, 2009 3:26: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(AbstractXMLParser.java:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)

... 7 more

Nov 16, 2009 3:27:23 PM [Thread[Thread-20,5,main]] Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR

Nov 16, 2009 3:27:23 PM [Thread[Thread-22,5,main]] Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR

Nov 16, 2009 3:28:23 PM [Thread[Thread-21,5,main]] Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because stat:

Regards, Neeta

Edited by: Neeta Patel on Nov 16, 2009 3:35 PM

Edited by: Neeta Patel on Nov 16, 2009 3:36 PM -

[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

[neeta_patel2 · Accepted solution]

Manoj,

What is the exact error message? Execute the command saposcol -xml and look at the xml output. In our case, a couple of lines in the xml were too long. SAP provided a new saposcol that fixed that for SUN platform.

Regards, Neeta