If, for some reasons, you have to change the MetricCollectionDefinition.xml for some agents, make sure, you do not use any XML Pretty Printer (like Notepad++ with XML add-on). According my tests, the SAPControlWSCollector interprets added \n and \r (by the pretty printer), although these characters are outside the CDATA area.

You’ll notice gray metrics in technical monitoring as well as following errors within the diagnostics agent’s protocol, it a MetricCollectionDefinition.xml was formated using an XML Pretty Printer and uploaded to a Diagnostics Agent.

[MAIJobObserver] ERROR occurred for metric collection 00000000000000000002[com.sap.smd.mai.model.collector.SAPControlWSCollector].
com.sap.smd.mai.model.collector.CollectorException: [SAPControlWSCollector.collect] Connection to SAPControl Web Service failed. Collector : [SAPControlWSCollector]
Id: 00000000000000000002, SID:
, instance number:

at com.sap.smd.mai.model.collector.SAPControlWSCollector.collect(SAPControlWSCollector.java:147)
at com.sap.smd.mai.job.MetricJobRunner.run(MetricJobRunner.java:32)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
Caused by: java.rmi.RemoteException: [WSConnectorFactory] Illegal sid

at com.sap.smd.agent.plugin.connectors.webservice.WSConnectorFactory.configureSAPStartSrvEndPoint(WSConnectorFactory.java:237)
at com.sap.smd.mai.model.collector.SAPControlWSCollector.connect(SAPControlWSCollector.java:504)
at com.sap.smd.mai.model.collector.SAPControlWSCollector.collect(SAPControlWSCollector.java:145)
… 4 more

This is at leasst valid for any Diagnostics Agent >7.40.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply