SMDAgentApplication log warning: smd.eem.age init: no executor libs found

[Former Member]

We upgraded to Solman v7.01sp23 ehp1 sp06 and found this warning in Diagnostic startup log. What is the impact of this warning and how do we fix it? I've copied saposcol 7.11 to smd's 2 exe directories. Do i also have to upgrade kernel files? The smdsystem.log has no errors when the agent is started.

Portion of smdagentapplication.log:

Nov 5, 2010 11:27:09 AM [Thread[Thread-5,5,main]] Warning com.sap.smd.wily.ho

stagent.SapAgent - startActions(): Action ECP|sisecp00_ECP_02 AbapInstance

[EXCEPTION]

com.sap.smd.wily.hostagent.TransientException: Destination not available:ECP|si

secp00_ECP_02

........

at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:16

2)

at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.ja

va:300)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl

.java:330)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:20

1)

at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721

)

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

Nov 5, 2010 11:27:10 AM [Thread[Thread-5,5,main]] Warning com.sap.smd.eem.age

let.ext.ExtManager - init: no executor libs found

[Former Member]

Hi,

Did you check your services Host controller and host exe are running?

Check the host agent logs can be find under host agent home directory.

Normally its in the program files/sap if it is windows server.

Cheers

Vanga Reddy

[Former Member]

Is the host agent and host controller part of diagnostic install? if not how does it get installed as I dont think this is installed in our system.

[Former Member]

I would recommend you to Upgrade your SAP Kernel to the latest patch level and check.

[Former Member]

Hi,

As per the latest diagnostics setup, host agent is mandatory to be installed and running in all the hosts that diagnostics agent running.

Check the latest setup documents for more information.

Cheers

[Former Member]

Hi, thank you. I check the latest diagnostic setup and it is indeed a requirement although not automatically installed when diagnostics is installed.

In this case, would it make a difference if I install after having installed diagnostics? If my managed systems are running Netweaver 7.01 would this impact the kernel and any other executables for the managed system? My managed systems are based on NW7.01 and Diagnostic Agent is v7.11

[Former Member]

Thanks for your help.

OK I installed the host agent in one of our windows server with existing diagnostic agent v7.11 (SAP said its ok to install after diagnostic installation). when I restarted the diagnostic agent, I am getting this error in smdagentapplication.log: Any ideas?

Nov 9, 2010 4:10:29 PM [Thread[Thread-68757,5,main]] Warning com.sap.smd.wily.hostagent.SapAgent - startActions(): Action SapStartSrv_sj-itsep01d_IPD_ cannot be started: Destination not available:SapStartSrv_sj-itsep01d_IPD_

Nov 9, 2010 4:51:37 PM [Thread[Thread-6,5,main]] Error com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed

[EXCEPTION]

com.sap.smd.wily.hostagent.PermanentException: Configuration Error: invalid property sysno for destination SapStartSrv_sj-itsep01d_IPD_

at com.sap.smd.wily.hostagent.sapcontrol.SapControlDestination.open(SapControlDestination.java:54)

at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(AgentConfigVO.java:85)

at com.sap.smd.wily.hostagent.config.AgentConfigXmlHandler.endElement(AgentConfigXmlHandler.java:172)

at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:156)

at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1957)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1850)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2446)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1847)

at com

Thread[Thread-6,5,main]] Warning com.sap.smd.wily.hostagent.SapAgent - startActions(): Action SapStartSrv_sj-itsep01d_IPD_ cannot be started: Destination not available:SapStartSrv_sj-itsep01d_IPD_

[Former Member]

Hi,

Good see the updates and installations of hostagent.

Please check your saphostcontrol and saphostexec services are running.

Could you post the Host agent startup logs also available at C:\Program Files\SAP\hostctrl\work?

Cheers

Vanga Reddy

[Former Member]

I can see 2 errors 1) the sapcrypto.dll cant be found 2) Interface OscolPlugin OscolInterface: no data found [saposcolweb. 1023]

How do i fix this?

[Thr 1460] Tue Nov 09 16:39:44 2010

[Thr 1460] MtxInit: -2 0 0

[Thr 1460] *** ERROR => DlLoadLib: LoadLibrary(sapNThalib.dll) Error 126 [dlnt.c 241]

[Thr 1460] Error 126 = "The specified module could not be found."

DlLoadLib('sapNThalib.dll') failed: -2 => HA support disabled

CCMS agent initialization: return code 0.

CCMS agent start: return code 0.

Initializing SAPHostControl Webservice

[Thr 7828] Tue Nov 09 16:39:45 2010

[Thr 7828] *** ERROR => CCMS: ShmAlCreate (SAPSYSTEM=99) returns error 3 [alxxappl.c 2364]

[Thr 1460] =================================================

[Thr 1460] = SSL Initialization on PC with Windows NT

[Thr 1460] = (711_REL,Jun 25 2009,mt,ascii,SAP_UC/size_t/void* = 8/64/64)

[Thr 1460] *** ERROR => DlLoadLib: LoadLibrary(C:\Program Files\SAP\hostctrl\exe\sapcrypto.dll) Error 126 [dlnt.c 241]

[Thr 1460] Error 126 = "The specified module could not be found."

[Thr 1460] *** ERROR => secudessl_LoadLibrary(): Unable to load "C:\Program Files\SAP\hostctrl\exe\sapcrypto.dll" [ssslsecu.c 387]

[Thr 1460] *** ERROR => Loading of SSL library failed -- NO SSL available!

[Thr 1460] =================================================

[Thr 1460]

[Thr 1460] <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_LIB_NOT_FOUND

SapSSLInit failed => https support disabled

Starting WebService Named Pipe thread

Starting WebService thread

Webservice named pipe thread started, listening on port
.\pipe\sapcontrol_99

[Thr 7828] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Webservice thread started, listening on port 1128

[Thr 7828] CCMS: Initalized shared memory of size 40000000 for monitoring segment.

[Thr 7828] CCMS: Checking Downtime Configuration of Monitoring Segment.

[Thr 7828] CCMS: AlMsUpload called by wp 1998.

[Thr 7828] CCMS: AlMsUpload failed for C:\Program Files\SAP\hostctrl\work\ALMTTREE.DAT.

[Thr 1760] Tue Nov 09 16:51:38 2010

[Thr 1760] *** ERROR => Interface OscolPlugin OscolInterface: no data found [saposcolweb. 1023]

[Thr 1760] Tue Nov 09 16:56:37 2010

[Thr 1760] *** ERROR => Interface OscolPlugin OscolInterface: no data found [saposcolweb. 1023]

[Former Member]

Hi,

Is it SAPHostControl and SAPHostExec are running?

See if SAPCCMSR.99 service also running.

saphost control and SAPCCMSR are registered with port 99.

So if you start host control it will stop with conflicting iwth port 99.

Stop SAPCCMSR.99 and start host control.

I had simial situation in my SAP Servers and we just disabled SAPCCMSR service and run host agent services.

It is not recommended to run both SAPCCMSR and host control services in same host.

[Former Member]

Thank you for your response.

The 2 services are running OK

I stop sapccmsr and put it in manual mode. I restarted saphostcontrol and saphostexec. The same error in startsrv.log is showing.

I also restarted the diagnostic agent and it shows previous error: (machine name =sj-itsep01d, sid=IPD)

Nov 11, 2010 6:42:50 PM [Thread[Thread-7,5,main]] Warning com.sap.smd.wily.hostagent.SapAgent - startActions(): Action SapStartSrv_sj-itsep01d_IPD_ cannot be started: Destination not available:SapStartSrv_sj-itsep01d_IPD_