SMD Agent 13 - With LMSERVICE 12.4?

Good day,
I am running SolMan Diag 12.4, I see there is a SMD Agent 13(2007/08/20 Support Package 13 of SMD AGENT 7.00, note 1086460) available for download.
The note does not exist? Can I run the agent on 13 on my satellite systems, or must I stay with 12? Does your SMDAGENT version and LMSERVICE versions need to be the same?
Anyone running version 13 of the agent?
Both notes 1049867 and 1086460 in /swdc do not exist.
Thanks,
Derek

Hi Derek,
Please, don't use a SMD agent with a version upper than LMService.
LMService / Agents and Notes SPS13 will be released this week.
Regards,
Xavier

Similar Messages

Monitoring SMD Agent with CCMS

Hi gurues, I need to know if there is any way to monitor SMD Agent installed in an application server via CCMS CEN system on a Solution Manager.
Right now we have CEN Monitoring define on Solution Manager, and several SMD Agents over the whole landscape, and it is critical for us to get alerted when this SMD goes down, so we are thinking about monitoring through Solutin Manager, isthat possible or we must do it in another way?
Regards
Gustavo

It's so typical SAP; I was looking for exactly the same question. SAP changed from 7.1 the OSCOL to run by the host agent instance and will not install the OSCOL to the SAP instance. You also will not be able to download OSCOL separatly.
But OSCOL is needed to monitor processes on host side. If the host agent don't starts also the OSCOL will not start (on LINUX side) and so you are not be able to monitor the SMD process.
The only chance is to start the SMD via init script.
A better way would be to implement a GRMG availability monitoring; this can be implemented in the CEN system independent from the monitored host. In the first solution the host has to be create itself the basis to monitor itself... that's nonsense.
I absolutly don't understand why SAP always and everywhere ignore his own design concept and reinvent the wheel. It would be so easy to design and implement the availability moniroring on SAP development side but they don't have a focus on that. It is the same with SAP router connection via host agent to the CEN system. It was implemented as very last feature after a lot of disgruntled customers (administrators).

Smd agent problem

I ve got problem with registering agent in solution manager diagnostic. The following message is in the log:
registering agent on server......
Exception - Registering agent on server <hostname>:50104 failed Time out occured when calling method 'configure' on object com.sap.smd.api.IAgentContext_Stub@6eb2c1 possible com.sap.smd.server.util.concurrent.TimeoutException. And this situation is going to repeat all the time

Hello Damian,
Please check your SMD patch? LMSERVICE SP 9 patch 4 or SP10 patch 1.
(See SAP note: 999138)
Also ensure your SMD agent is running, stop it and start it at OS Level on the monitored system.
Hope this helps,
Dolores

Start of SMD agent fails!

Hi!
After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error Exception ID: 1160572286256
Registering agent on server myhost.de:50004failed:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
However, the manual setup of the agent succeeds:
./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
SMD Agent Setup is in process ...
- STEP 1: checking JDK location
JDK location is consistent: /usr/java14_64/bin
- STEP 2: checking JDK Version
JDK Version is correct: 1.4.2
- STEP 3: checking Connection to SMD Server
SMD Server check completed successfully
- STEP 4: generating Runtime Properties
runtime.properties has been created.
- STEP 5: generating Launcher
smdagent.bat has been created.
smdagent.sh has been created.
- STEP 6: generating SecStore
secstore.properties: has been created.
secstore.properties: user has been set.
secstore.properties generation completed successfully.
- STEP 7: checking P4 Connection and SMD Agent Registration
SMD Agent Registration succeeded
SMD Agent Setup completed successfully
During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
What can we do?
Thanks for all hints solving our problem!
Greetz,
André Richter

Hi Rahul,
please try SMD Agent 7.00 SP10! We had no problems with this version!
Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
Regards
André

SMD Agent doesn't work

Hello,
I have been trying to install SMD Agent in my BI system but Solution Manager can't check it, this is the message in Solman_setup
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
Step Wilyhost Agent Details
Created destination QBB|svs978_QBB_01
Created action QBB - QBB AbapSystem
Created action QBB|svs978_QBB_01 - QBB|svs978_QBB_01 AbapInstance
Created 2 action(s).
0 Wilyhost Agent(s) from host svs978 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
do you know something??? i restarted the agent but nothing happens
Thanks!!!!

Hello...
For JAVA
Software Components
Vendor Name Version Provider Location Applied
sap.com ADSSAP 7.01 SP4 (1000.7.01.4.0.20090417021200) SAP AG SAP AG 20091103161136
sap.com BASETABLES 7.01 SP4 (1000.7.01.4.0.20090417015900) SAP AG SAP AG 20091103153957
sap.com BI_MMR 7.01 SP4 (1000.7.01.4.0.20090417021807) SAP AG SAP AG 20091103161215
sap.com BI_UDI 7.01 SP4 (1000.7.01.4.0.20090416221700) SAP AG SAP AG 20091103162333
sap.com CAF 7.01 SP4 (1000.7.01.4.0.20090417194106) SAP AG MAIN_NW701P04_C 20091103163937
sap.com CAF-UM 7.01 SP4 (1000.7.01.4.0.20090417194111) SAP AG MAIN_NW701P04_C 20091103161325
sap.com CORE-TOOLS 7.01 SP4 (1000.7.01.4.0.20090417021948) SAP AG SAP AG 20091103154019
sap.com ISAGENT 8.1 SP0 (8.1.0.0.20090605095817) SAP AG SAP AG 20091210142716
sap.com JLOGVIEW 7.01 SP4 (1000.7.01.4.0.20090417020000) SAP AG SAP AG 20091103154104
sap.com JSPM 7.01 SP4 (1000.7.01.4.2.20090918151100) SAP AG SAP AG 20091201201543
sap.com KM-KW_JIKS 7.01 SP4 (1000.7.01.4.0.20090514115300) SAP AG SAP AG 20091103161349
sap.com LM-SERVICE 7.01 SP5 (1000.7.01.5.2.20091211060559) SAP AG SAP AG 20091224192630
sap.com LM-TOOLS 7.01 SP5 (1000.7.01.5.3.20091208123420) SAP AG MAIN_NW701P05_C 20091228135344
sap.com SAP-JEE 7.01 SP4 (1000.7.01.4.1.20090612152648) SAP AG SAP AG 20091103154150
sap.com SAP-JEECOR 7.01 SP4 (1000.7.01.4.0.20090417015900) SAP AG SAP AG 20091103154414
sap.com SAP_JTECHF 7.01 SP4 (1000.7.01.4.2.20090612144700) SAP AG SAP AG 20091103154520
sap.com SAP_JTECHS 7.01 SP4 (1000.7.01.4.2.20090612152905) SAP AG SAP AG 20091103162132
sap.com SWLIFECYCL 7.01 SP4 (1000.7.01.4.0.20090511115334) SAP AG MAIN_NW701P04_C 20091103151458
sap.com UMEADMIN 7.01 SP4 (1000.7.01.4.0.20090417195012) SAP AG MAIN_NW701P04_C 20091103165828
For ABAP
SAP_BASIS     701     0004     SAPKB70104
SAP_ABA     701     0004     SAPKA70104
ST-PI     2008_1_700     0001     SAPKITLRD1
PI_BASIS     701     0004     SAPK-70104INPIBASIS
CRMUIF     500     0003     SAPK-50003INCRMUIF
SAP_BW     701     0004     SAPKW70104
SAP_AP     700     0016     SAPKNA7016
BBPCRM     500     0015     SAPKU50015
CPRXRPM     400     0015     SAPK-40015INCPRXRPM
ST     400     0021     SAPKITL431
BI_CONT     704     0004     SAPK-70404INBICONT
ST-A/PI     01L_CRM570     0000          -
ST-ICO     150_700     0022     SAPK-1507MINSTPL
ST-SER     701_2008_2     0005     SAPKITLOQ5
LM Components were updated for EHP1 SPS21, I installed SMD Agents in DEV and some QA servers and they work, but this one specially works as a fail over for a PRD cluster enviroment, and for that reason I'm using logical name, in SMSY it is configure with the same name, do you have any ideas?
Thanks!!!

SMD agent passowrd issue

Hi Experts,
In our solution manger system, we forgot the SMD agent password. without i can't able to do EWA for java stack. So kindly help me to how to reset the password for this.
Thanks & Regards,
Sampath.

Hi
when you performed the SMD Setup Wizard in the managing system, created the SMD_ADMIN user and the enter the passowrd
please reset the password for the smd_admin user in the managing system (satelite system and try)
else use the section 4.9.2 in the diagnostics setup guide 7.11 on [https://websmp108.sap-ag.de/diagnostics|https://websmp108.sap-ag.de/diagnostics] > media library as below
4.9.2 Change the Diagnostics Agent credentials
This section provides information about how to change the credentials (login and/or password) of the J2EE user used to connect the Diagnostics Agent to the Managing System.
Prerequisites
All the Diagnostics Agents must be connected to the Managing System before updating the password of the J2EE user used by these Diagnostics Agents
Procedure
1. You can either change the password of the J2EE user used by the agents or create a new J2EE user in User Management.
2. Open the Agent Administration application
In the Agent Credentials panel, fill the previous login of the Diagnostics Agents and enter the new one (or enter the same login with a new password). Click on the Update all agents button.
3. All the agents are disconnected and reconnected with the new credentials
jansi

Does solution manager 4.0 require SMD Agent?

we have solman 4.0 abap+java with sp11.we are in the process of configuring sol mananager diagnostics for sattlite systems.
for monitoring solution manager java stack it self from solution manager do we need to install SMD AGENT even thogh solution manger it self has SMD server ? still solution manger need SMD AGENT ?

Hi,
SMD Agents are mandatory to run Diagnostics on sattelite systems.
Each Agent is connected to SMD Server and is able to run task or collect information from central request (SMD Server).
If you do not have them, you will not be able to run any tools in Diag.
SMD Server is one sub-component of Solution Manager 4.0.
Regards,
Frederic

Error while installing SMD agent

Hi ,
1) Can any one please justify/brief the need of installing SMD agent on ABAP stack?
2) When I tried to install the SMD 711 agent on ABAP stack I could see the below error when i click sapinst.exe.
    " Running msiexec failed with return code 1063: undefined
      command line was :
       msiexec.exe /norestart /L vcredist_x64.log /i vcredist_x64.msi /qn "
I tried with Changing the environment variable of Temp and tmp to C:\usr\sap\<sid>\tmp and also tried with directory c:\temp but in vain .
enivronment:-   Windows 64-bit.
Note:- SMD agent was successfully installed on Development systemn
Please suggest.
Thank you
Jayanth

Hi ,
Log from vcredist_x64.log. Please have a look
" Product: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64) -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Action ended 2:47:00: SxsInstallCA. Return value 3.
Action ended 2:47:00: INSTALL. Return value 3.
MSI (s) (FC:38) [02:47:00:489]: Windows Installer installed the product. Product Name: Microsoft redistributable runtime DLLs VS2005 SP1(x86_x64). Product Version: 8.0.50727.762. Product Language: 1033. Installation success or error status: 1603.
Does this mean that , I should download new sapinst file for service market place and try again ??
Thank you
Jayanth

SMD Agent

Hi,
I am trying to install SMD agents(711) on EP 7.0 system ,Got below error when trying to lauch the intsaller (sapinst)
guiengine: No GUI server connected; waiting for a connection on host xxxxxx, port 21200 to continue with the installation
Jan 11, 2011 5:18:58 PM [Info]: *************************
Jan 11, 2011 5:18:58 PM [Info]: Starting Server
Jan 11, 2011 5:18:58 PM [Info]: Reading server configuration.
Jan 11, 2011 5:18:58 PM [Info]: Reading service configuration SAPinstService.
Jan 11, 2011 5:18:58 PM [Info]: Configuring LogManager ...
Jan 11, 2011 5:18:58 PM [Info]: *************************************************
Jan 11, 2011 5:18:58 PM [Info]: Starting SL Controller ...
Jan 11, 2011 5:18:58 PM [Info]: StorageService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Initializing SecurityManager ...
Jan 11, 2011 5:18:58 PM [Info]: Key Store management switched off.
Jan 11, 2011 5:18:58 PM [Info]: Configuring HTTPManager ...
Jan 11, 2011 5:18:58 PM [Info]: WebstartService switched off.
Jan 11, 2011 5:18:58 PM [Info]: RoleService switched off.
Jan 11, 2011 5:18:58 PM [Info]: AlertService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Starting NotesService ...
Jan 11, 2011 5:18:58 PM [Info]: ProcessService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Starting MIDService ...
Jan 11, 2011 5:18:58 PM [Info]: Starting FileService ...
Jan 11, 2011 5:18:58 PM [Info]: LogService switched off.
Jan 11, 2011 5:18:58 PM [Info]: MailService switched off.
Jan 11, 2011 5:18:58 PM [Info]: Starting services ...
Jan 11, 2011 5:18:58 PM [Info]: Starting service "SAPinstService" ...
Jan 11, 2011 5:18:59 PM [Info]: Service "SAPinstService" started
Jan 11, 2011 5:18:59 PM [Info]: Services started.
Jan 11, 2011 5:18:59 PM [Info]: Starting HTTP server listening on port 4239 ...
Jan 11, 2011 5:18:59 PM [Info]: HTTP server started.
Jan 11, 2011 5:18:59 PM [Info]: SL Controller started.
Jan 11, 2011 5:18:59 PM [Info]: Starting GUI ...
Jan 11, 2011 5:18:59 PM [Error]: java.lang.reflect.InvocationTargetException: null
Jan 11, 2011 5:18:59 PM [Error]: java.lang.reflect.InvocationTargetException: null
Jan 11, 2011 5:18:59 PM [Error]: GUI start failed.
Please help me to solve the issue.
Thanks,
Srini K

Hi,
I have to cope with the same issue on exactly one of our 60 systems. I have no difficulties to start the SAPInst on any of the other systems, but I can't find any differences in their configurations.
I already tried to apply a newer version of SAPInst (as suggested), but this did not help either (package SAPINST7102_2-20003627.SAR, Rel. 7.10 PL 80 for SunOS).
Do you have any other suggestions how to get the SAPInst up and running on this final system?
Thanks in advance for your help!
Ulf

SMD Agent for ABAP Only Systems

Everything I have read states that the SMD Agent is only for JAVA Stack. Then I read a post here stating to install the SMD on the ABAP systems. Can anyone clear this up? I have a mix of Java only, Abap only and dual stack systems. Can anyone help clear this issue up for me?

Hello Donna,
SMD Agent can be installed on Java Stack, Java-ABAP Stack and ABAP Stack. It is not there only for Java as it can be used with ABAP and Dual stack also. Hope this answers the question that you have brought up.
Thanks,
Mark

SMD Agent SR3 on NW2004s SR2

Hi all,
We are running NW2004s SR2 on our Solution Manager system. We upgraded component ST-SER to 700_2008_1. The older SMD agent appears to not work correctly with this level according to SAP.
My question is, is it possible to install the standalone engine for SMD Agent SR3 without upgrading our entire system to SR3? (kernel, installation, Java)
We tried doing the SMD SR3 standalone install but are seeing some strange issues.
If anyone has an answer for me on whether I have to upgrade the entire system or not that would be much appreciated.
Thank you.

Solution Manager is a combined ABAP + Java installation, components of both must be in sync. It's not advised to install separate support packages or updates for certain components only, there are dependencies between them.
Why don't you upgrade t the latest service pack - for both ABAP + Java? This will avoid lots of compatibility problems...
Markus

SR3 SMD Agent on SP15

Hi
Our Solution Manager is on SP14 and Managed System is on SP15. I want to install the SMD Agent. As per the note 1126895 it is possible and suported. LMSERVICE is SP14.
I used note 1170855 to install it and it was successfull but the status is "in Progress" in http:////<hostname>:<port>/smd page. It says "DEPLOYING APPLICATION". It never finishes.
I checked the log file jvm_SMDAgent.out and it says that
Starting SMDAgent ...
Running SMD Agent ...
Establishing connection to server 'ms://<hostname>:8177/P4
[ms://<hostname>:8177/P4] Waiting for connection ...
[ms://<hostname>:8177/P4] Checking server availability...
[ms://<hostname>:8177/P4] Authentication in progress ...
[ms://<hostname>:8177/P4] Connection established .
[ms://<hostname>:8177/P4] Registering agent on server ...
Exception occured. Please check log files.[Exception ID:1219178405804 ]
[ms://<hostname>:8177/P4] Waiting for connection ...
[ms://<hostname>:8177/P4] Checking server availability...
[ms://<hostname>:8177/P4] Authentication in progress ...
[ms://<hostname>:8177/P4] Connection established .
[ms://<hostname>:8177/P4] Registering agent on server ...
It never finishes.
It is failing at deployment application.
The log file SMDSystem.0.log states following -
Aug 19, 2008 4:30:04 PM [Thread[Thread-2,5,main]] Info
[AgentContext.offlineDeployApplication] ENTERING - deploying file
com.sap.smd.agent.application.runtime_7.0014.20080429115048.0000.war
Aug 19, 2008 4:40:05 PM [Thread[SMDAgent connection thread,5,main]]
Error [Exception ID: 1219178405804 ] java.rmi.RemoteException -
error counter: 1
[EXCEPTION]
java.rmi.RemoteException: Agent Registration failed: Time out occurred
when calling method 'offlineDeployApplication' on object
[com.sap.smd.api.IAgentContext_Stub@1de64fc2] after 600000 ms.
possible cause: com.sap.smd.server.util.concurrent.TimeoutException
at com.sap.smd.SMDServerHandle.internalRegisterAgent
Anybody has experienced it.
Please let me know.
Regards.
SS

Hello,
Would you kindly share the solution?
Think I run into a similar issue.
Many Thanks,
Jan

Why SMD agent on ABAP only?

OK. I don't get it. Why install SMD Agent on ABAP only systems???
Isn't SMD Agent used primarily for Java???
I have 37 systems of which only 8 have a java component. If I install SMD Agent everywhere I'll
need a much bigger SolMan server!!!
What is SAP policy on SolMan 7 Enh 1 OS/DB migration???
Can I migrate from this little Intel Linux box to a serious AIX LPAR?
Will SAP give me a migration key???
Ken Chamberlain
University of Toronto

About the migration, you can migrate without problems. You'll need study the following process "Heterogeneous system copy".
There's a component that checks just this kind of problems related with migration. BC-INS-MIG.
Check the documentation below.
http://www.sapdb.info/homogeneous-and-heterogeneous-system-copy/
http://www.fulleffectsolutions.co.uk/Html/technical-sap-hetero.html

How to install SMD Agent on a MSCS?

Hello helpers,
we have installed a PI 7.1 (double stack) on a MSCS environment. The next step is to connect the PI 7.1 SAP system to our SolMan and to install the diagnostics agent. Unfortunately I wasn't able to find any documentation explaining an installation of the SMD Agent in a MSCS environment.
Does anybody know what has to be done? Do I have to install 3 agents, one on every MSCS node and one in the SCS/ASCS cluster resource group, or is only one agent needed in the SCS/ASCS cluster resource group?
Looking forward for any answers,
Sascha Piotrowsky

Hi Sascha,
To distribute a solution to the diagnostics the install path must be verified in TC SMDIAG_WIZARD. To verify the install paths an installed SMD-AGENT is neccessary.
Yes
Another point is that we like to monitor the J2EE Servers and Dispatchers from the 2 instances on "nodeA" and "nodeB". So in my opinion at least 2 SMD-Agent should be installed, one on every node. Do you agree?
No, you need one SMD Agent, this agent can then monitor multiple instances on one virtual host. The connection is only between virtual host and agent, not between instance and agent.
But what shall I do with the ASCS00/SCS01 instance. Does an SMD-Agent installation bring any effort on "clusterSID" or is it a must?
It's not a must, only relevant if you want to receive host metrics from this host. As this is only virtual, I would not install one here.
Best regards
Michael

H E A P   C O R R U P T E D - and smd agent shows not running

Hello Gurus,
My SMD agent is goes down every day when i check the status:
I found the heap corroupted everyday with the below warnings:
nbcsaplpa018:nedadm 19> tail hs_err_pid1888352.log
H E A P   C H E C K -
Suspension of other threads succeeded.
Heap corruption found in object at address 0x070000004ac38268. Class of object is not in the reserved heap memory area (0x002e006e006f0072).
H E A P   C O R R U P T E D -
Please suggest
Regards,
Munish

Please fine the file SMDAgentApplication.0.log for logs again : other file in next reply.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[SMDAgentAppLog]/>
<!PATTERN[SMDAgentApplication.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
<!ENCODING[ISO8859_1]/>
<!FILESET[0, 10, 1000000]/>
<!PREVIOUSFILE[SMDAgentApplication.9.log]/>
<!NEXTFILE[SMDAgentApplication.1.log]/>
<!LOGHEADER[END]/>
Mar 24, 2010 1:53:17 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Mar 29, 2010 10:57:12 AM [Thread[Thread-174,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Mar 30, 2010 12:18:05 PM [Thread[Thread-229,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 1, 2010 1:59:00 PM [Thread[Thread-311,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 1, 2010 2:00:32 PM [Thread[Thread-340,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 9, 2010 5:41:47 PM [Thread[Thread-546,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 28, 2010 5:44:24 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 29, 2010 3:26:39 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 29, 2010 9:09:56 AM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 30, 2010 10:13:43 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 31, 2010 4:00:07 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 1, 2010 3:04:42 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 2, 2010 4:09:21 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 2, 2010 9:02:55 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 20, 2010 3:07:02 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 21, 2010 5:32:08 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 12:46:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 8:28:13 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 3:30:13 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 9:15:34 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 7:00:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 2:56:56 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 11:25:29 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found

SMD Agent 13 - With LMSERVICE 12.4?

Similar Messages

Maybe you are looking for