cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

System Monitoring Grey - DAA has not received XML

Go to solution
Private_Member_19084
Active Contributor

on ‎01-14-2015 12:55 PM

0 Kudos

Hi experts,

we have upgraded Host Agent und Diagnostic on one system.

Now I get the issue, that a lot of metrics are grey and I get the error "Configuration-XML has not received the Agent".

Does anybody know what this means?
The DAA is connected. I have already done a restart and Re-Registration into SLD.

Also I did send again the configuration (via workcenter).

Kind regards

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

divyanshu_srivastava3
Active Contributor
‎01-14-2015 12:57 PM
0 Kudos

It's a know issue - 1854525 - "Configuration XML <nbr> likely did not reach the agent" - Solution Manager 7.10

Regards,

Show replies
Show replies
Private_Member_19084
Active Contributor
‎01-14-2015 1:08 PM
0 Kudos

Hello Divyanshu, again, and thx again,

Dammit! I did only search in german in SMP, in the future I will also look for english descriptions...

I will try the note, thx

Private_Member_19084
Active Contributor
‎01-15-2015 6:06 AM
0 Kudos

Hi Divyanshu,

the problem is still not solved.

I did follow the note, just step 4.

1-3 I couldn't do as we are not using WDP.

Step 5 I didn't find.

After that, I did restart the Agent again and did also connect it again.

However, still the same issue.

Kind regards

divyanshu_srivastava3
Active Contributor
‎01-15-2015 6:27 AM
0 Kudos

Can 6ou provide me the agent logs ?

Also try to register agent directly to solman.

Private_Member_19084
Active Contributor
‎01-15-2015 7:34 AM
0 Kudos

I will catch the log....what do you mean with, register dirctly?

divyanshu_srivastava3
Active Contributor
‎01-15-2015 7:38 AM
0 Kudos

Re-register this on solman rather than on sld

Henk
Active Participant
‎01-15-2015 3:11 PM
0 Kudos

Hi Christian,

Execute the SMDA registration script as follows:

smdsetup.sh managingconf hostname:"sapms://<solman_fqdn>" port:”<solman_port>" user:”<solman_userid>" pwd:”<solman_userid_password>"


For instance:


smdsetup.sh managingconf hostname:"sapms://solmanhost.company.com" port:"8000" user:"SMD_ADMIN" pwd:”PASSWORD"


Then restart the agent. This should register it directly at Solution Manager.


I hope this helps.


Kind regards,



Henk.

Private_Member_19084
Active Contributor
‎01-16-2015 7:37 AM
0 Kudos

Hello Henk,

did also not solve the issue

Kind regards

divyanshu_srivastava3
Active Contributor
‎01-16-2015 7:43 AM
0 Kudos

Can you see any error in logs which says some installation.property file is missing ?

If yes, then you are getting this because you used 70swpm for agent installation and now you will have to install using swpm*.

However, if you do not want to update, i have a work around.

roland_hennessy
Contributor
‎01-16-2015 11:15 AM
0 Kudos

Hi,

Maybe SAP note 1855064 - Error occurred when calling the DPC Push web service will solve the issue?

Kind regards,

Roland

Private_Member_19084
Active Contributor
‎01-19-2015 8:12 AM
0 Kudos

Hello Divyanshu,

where can I find the log?
There are a lot in work directory.

In Agent workcenter, I can not see one.

Kind regards

divyanshu_srivastava3
Active Contributor
‎01-19-2015 8:16 AM
0 Kudos

Check in managed system smagent log folder and landscape ui. Whatever error you see share it with us.

Private_Member_19084
Active Contributor
‎01-19-2015 8:26 AM
0 Kudos

I got a lot of this in SMDSystem.2.log

ation.e2emai/_Default_Configuration.properties Failed.
[EXCEPTION]
java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 64
        at javax.crypto.CipherInputStream.a(DashoA13*..)
        at javax.crypto.CipherInputStream.read(DashoA13*..)
        at javax.crypto.CipherInputStream.read(DashoA13*..)
        at java.util.Properties$LineReader.readLine(Properties.java:434)
        at java.util.Properties.load0(Properties.java:353)
        at java.util.Properties.load(Properties.java:341)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:426)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.getDefaultProperties(ApplicationConfigStore.java:382)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:268)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:326)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:124)
        at com.sap.smd.core.runtime.agent.SMDFileTransferServicep4_Skel.dispatch(SMDFileTransferServicep4_Skel.java:163)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:763)
Caused by: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 64
        at iaik.security.cipher.v.b(Unknown Source)
        at iaik.security.cipher.z.b(Unknown Source)
        at iaik.security.cipher.z.engineDoFinal(Unknown Source)
        at javax.crypto.Cipher.doFinal(DashoA13*..)
        ... 16 more


Jan 19, 2015 6:54:03 AM [Thread[Thread-55,5,main]                     ] Error      [Exception ID: 1421646843724 ] java.io.IOException
[EXCEPTION]
java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 64
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:435)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.getDefaultProperties(ApplicationConfigStore.java:382)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:268)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:326)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:124)
        at com.sap.smd.core.runtime.agent.SMDFileTransferServicep4_Skel.dispatch(SMDFileTransferServicep4_Skel.java:163)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:763)

Private_Member_19084
Active Contributor
‎01-19-2015 8:29 AM
0 Kudos

This one in dpc.0.log

Jan 16, 2015 10:30:09 AM [Thread[ExRun:dpc:job_2,5,dpc:job:ExecTG]] Warning    [DPCServicePushVersionJob.getAgentName] Unable to resolve agent server name; DPC Push event will not contain the information.
Jan 16, 2015 10:40:28 AM [Thread[ExRun:dpc:job_1,5,dpc:job:ExecTG]] Warning    [DPCServicePushVersionJob.getAgentName] Unable to resolve agent server name; DPC Push event will not contain the information.
Jan 16, 2015 10:41:29 AM [Thread[ExRun:dpc:job_1,5,dpc:job:ExecTG]] Warning    [DPCServicePushVersionJob.getAgentName] Unable to resolve agent server name; DPC Push event will not contain the information.
Jan 16, 2015 11:22:33 AM [Thread[Thread-56,5,main]] Error      [DPCService.initWSConnection] Error occurred when initializing DPC Web Service client. DPCService is DISABLED.
[EXCEPTION]
com.sap.smdagent.plugins.connectors.p4.exceptions.P4ConfigStoreException: Error to access to agent configuration 'global configuration'.; nested exception is:
        java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 242
        at com.sap.smd.agent.plugin.connectors.InitialContextLoader.getGlobalConf(InitialContextLoader.java:214)
        at com.sap.smd.agent.plugin.connectors.InitialContextLoader.getDPCWebserviceURL(InitialContextLoader.java:508)
        at com.sap.smd.agent.plugin.connectors.webservice.WSConnectorFactory.configureDPCClient(WSConnectorFactory.java:66)
        at com.sap.smd.dpc.DPCService.initWSConnection(DPCService.java:73)
        at com.sap.smd.dpc.DPCService.init(DPCService.java:45)
        at com.sap.smd.dpc.DPCServiceFactory.getInstance(DPCServiceFactory.java:138)
        at com.sap.smd.dpc.DPCServiceFactory.getService(DPCServiceFactory.java:130)
        at com.sap.smd.core.plugin.service.ServiceEntityHandle.getObjectAs(ServiceEntityHandle.java:191)
        at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.getObjectAs(PseudoEntityHandle.java:140)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl._getObjectAs(ObjectProxyImpl.java:627)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.getObjectAs(ObjectProxyImpl.java:574)
        at com.sap.smd.core.plugin.service.ServiceContextImpl.getService(ServiceContextImpl.java:62)
        at com.sap.smd.dpc.DPCServiceFactory.init(DPCServiceFactory.java:79)
        at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
        at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)
        at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
        at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
        at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
        at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
        at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
        at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)
        at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)
        at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)
        at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:111)
        at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:154)
        at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:731)
        at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:97)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:763)
Caused by: java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 242
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:435)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.getDefaultProperties(ApplicationConfigStore.java:382)
        at com.sap.smd.agent.plugin.connectors.InitialContextLoader.getGlobalConf(InitialContextLoader.java:209)
        ... 34 more

Private_Member_19084
Active Contributor
‎01-19-2015 8:33 AM
0 Kudos

They I got in smdagent_trace.0.trc


#1.#005056B46D4300170000000300001A4F00050CDDBED08DFC#1421521412197#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[Thread-43,5,main]##0#0#Warning##Plain###[WSConnectorFactory] Cannot set the timeout on webservice proxy
com.sap.smd.agent.wsclients.saposcol.SAPOscolStub@2713d33a#
#1.#005056B46D4300020000000800001A4F00050CE0823ABADA#1421533280647#SMDloggerSystem##SMDloggerSystem#######Thread[SLD-Registration,1,main]##0#0#Info##Plain###[SLD Registration http://<solman host>:5<solman no>00(user: slddsuser)] SLD Da
ta of agent published to SLD Server with success.#
#1.#005056B46D4300020000000900001A4F00050CE0823ABDB0#1421533280648#SMDloggerSystem##SMDloggerSystem#######Thread[SLD-Registration,1,main]##0#0#Info##Plain###[SLD Registration http://<solman host>:5<solman no>00(user: slddsuser)] SLD Da
ta of agent will published again at Sun Jan 18 22:40:20 CET 2015#
#1.#005056B46D4300020000000A00001A4F00050CEA9127F795#1421576480749#SMDloggerSystem##SMDloggerSystem#######Thread[SLD-Registration,1,main]##0#0#Info##Plain###[SLD Registration http://<solman host>:5<solman no>00(user: slddsuser)] SLD Da
ta of agent published to SLD Server with success.#
#1.#005056B46D4300020000000B00001A4F00050CEA9127F9FC#1421576480750#SMDloggerSystem##SMDloggerSystem#######Thread[SLD-Registration,1,main]##0#0#Info##Plain###[SLD Registration http://<solman host>:5<solman no>00(user: slddsuser)] SLD Da
ta of agent will published again at Mon Jan 19 10:40:20 CET 2015#
#1.#005056B46D43001B0000000100001A4F00050CEEB4136EA1#1421594246475#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-65,5,main]##0#0#Info##Plain###Returned service object :com.sap.smd.core.runtime.agent.AgentSelfCheckS
ervice@e88cf92#
#1.#005056B46D43001C0000000000001A4F00050CEEB47EB833#1421594253506#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-44,5,main]##0#0#Info##Plain###Returned service object :com.sap.smd.core.runtime.agent.AgentSelfCheckS
ervice@e88cf92#
#1.#005056B46D43001B0000000200001A4F00050CEEB47FF7C4#1421594253588#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-65,5,main]##0#0#Info##Plain###Returned service object :com.sap.smd.core.runtime.agent.AgentSelfCheckS
ervice@e88cf92#
#1.#005056B46D430016000000A300001A4F00050CF1DC32B1D9#1421607804514#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-56,5,main]##0#0#Info##Plain###Returned service object :OsService_44e995bf#
#1.#005056B46D4300180000000100001A4F00050CF1DC34688B#1421607804626#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-55,5,main]##0#0#Error##Java###Extracting configuration from secstore file /usr/sap/DAA/SMDA97/SMDAgen
t/applications.config/com.sap.smd.agent.application.connectors/_Default_Configuration.properties Failed.
[EXCEPTION]
{0}#1#java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 241
        at javax.crypto.CipherInputStream.a(DashoA13*..)
        at javax.crypto.CipherInputStream.read(DashoA13*..)
        at javax.crypto.CipherInputStream.read(DashoA13*..)
        at java.util.Properties$LineReader.readLine(Properties.java:434)
        at java.util.Properties.load0(Properties.java:353)
        at java.util.Properties.load(Properties.java:341)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:426)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.getDefaultProperties(ApplicationConfigStore.java:382)
        at com.sap.smd.agent.plugin.connectors.webservice.WSConnectorFactory.setEndPointUrl(WSConnectorFactory.java:338)
        at com.sap.smd.agent.plugin.connectors.webservice.WSConnectorFactory.configureWSEndPoint(WSConnectorFactory.java:47)
        at com.sap.smd.agent.plugins.datacollector.create.saposcol.util.SapOsColWSProcess.<init>(SapOsColWSProcess.java:37)
        at com.sap.smd.agent.plugins.datacollector.os.OsCollect.readSapOsCol_From_WS(OsCollect.java:345)
        at com.sap.smd.agent.plugins.datacollector.os.OsCollect.readSapOsCol(OsCollect.java:303)
        at com.sap.smd.agent.plugins.datacollector.os.OsCollect.readStoreContent(OsCollect.java:207)
        at com.sap.smd.agent.plugins.datacollector.os.OsCollect.collect(OsCollect.java:122)
        at com.sap.smd.agent.plugins.datacollector.os.OsCollectp4_Skel.dispatch(OsCollectp4_Skel.java:60)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:763)
Caused by: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 241
        at iaik.security.cipher.v.b(Unknown Source)
        at iaik.security.cipher.z.b(Unknown Source)
        at iaik.security.cipher.z.engineDoFinal(Unknown Source)
        at javax.crypto.Cipher.doFinal(DashoA13*..)
        ... 20 more

#
#1.#005056B46D4300180000000200001A4F00050CF1DC346952#1421607804627#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[Thread-55,5,main]##0#0#Warning##Plain###[WSConnectorFactory] Cannot set the timeout on webservice proxy
com.sap.smd.agent.wsclients.saposcol.SAPOscolStub@635b157b#
#1.#005056B46D4300020000000C00001A4F00050CF4A0152713#1421619680847#SMDloggerSystem##SMDloggerSystem#######Thread[SLD-Registration,1,main]##0#0#Info##Plain###[SLD Registration http://<solman host>:5<solman no>00(user: slddsuser)] SLD Da
ta of agent published to SLD Server with success.#
#1.#005056B46D4300020000000D00001A4F00050CF4A01529DD#1421619680848#SMDloggerSystem##SMDloggerSystem#######Thread[SLD-Registration,1,main]##0#0#Info##Plain###[SLD Registration http://<solman host>:5<solman no>00(user: slddsuser)] SLD Da
ta of agent will published again at Mon Jan 19 22:40:20 CET 2015#
#1.#005056B46D4300180000000300001A4F00050CFAF31CFAE4#1421646843673#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-55,5,main]##0#0#Info##Plain###Returned service object :com.sap.smd.core.runtime.agent.SMDFileTransfer
Service@78a48f79#
#1.#005056B46D4300180000000400001A4F00050CFAF31DC2D0#1421646843724#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-55,5,main]##0#0#Error##Java###Extracting configuration from secstore file /usr/sap/DAA/SMDA97/SMDAgen
t/applications.config/com.sap.smd.agent.application.e2emai/_Default_Configuration.properties Failed.
[EXCEPTION]
{0}#1#java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 64
        at javax.crypto.CipherInputStream.a(DashoA13*..)
        at javax.crypto.CipherInputStream.read(DashoA13*..)
        at javax.crypto.CipherInputStream.read(DashoA13*..)
        at java.util.Properties$LineReader.readLine(Properties.java:434)
        at java.util.Properties.load0(Properties.java:353)
        at java.util.Properties.load(Properties.java:341)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:426)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.getDefaultProperties(ApplicationConfigStore.java:382)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:268)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:326)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:124)
        at com.sap.smd.core.runtime.agent.SMDFileTransferServicep4_Skel.dispatch(SMDFileTransferServicep4_Skel.java:163)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:763)
Caused by: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 64
        at iaik.security.cipher.v.b(Unknown Source)
        at iaik.security.cipher.z.b(Unknown Source)
        at iaik.security.cipher.z.engineDoFinal(Unknown Source)
        at javax.crypto.Cipher.doFinal(DashoA13*..)
        ... 16 more

#
#1.#005056B46D4300180000000500001A4F00050CFAF31DC3FE#1421646843724#SMDloggerSystemConsole##SMDloggerSystemConsole#######Thread[Thread-55,5,main]##0#0#Info##Plain###Exception occured. Please check log files.[Exception ID:
1421646843724 ] #
#1.#005056B46D4300180000000600001A4F00050CFAF31DC498#1421646843724#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-55,5,main]##0#0#Error##Java###[Exception ID: 1421646843724 ] java.io.IOException
[EXCEPTION]
{0}#1#java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 64
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:435)
        at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.getDefaultProperties(ApplicationConfigStore.java:382)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:268)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:326)
        at com.sap.smd.core.runtime.agent.SMDFileTransferService.sendFile(SMDFileTransferService.java:124)
        at com.sap.smd.core.runtime.agent.SMDFileTransferServicep4_Skel.dispatch(SMDFileTransferServicep4_Skel.java:163)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:763)

divyanshu_srivastava3
Active Contributor
‎01-19-2015 9:16 AM
0 Kudos

Re-register agent using SMD setup script and use hostname parameter to supply the virtual hostname for which you are installing diag agent.

For eg - smdsetup managingconf hostname:"servername" port:"xxxxx" user:"SOLMAN_ADMIN" pwd:"xxxx" servername:"Managed System Virtaul Hostname"

Regards,

Private_Member_19084
Active Contributor
‎01-19-2015 2:13 PM
0 Kudos

Hello Divyanshu,

we still get the same error.

I think I will open an OSS-Ticket.

kind regards

Answers (0)

Ask a Question