Solution Manage Diagnostics - error in the system setup

Hello,
I have installed SMD and I installed one system with the Setup Wizard of the SMD. According to the result of the setup, it was successful.
However, when I do a self check in SMD, I get the five following errors in the Monitored Setup node :
5 error(s) found:
No DB agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No JVM startup parameters setting status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Roles assignment status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No SSO Setup status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Telnet agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
Can anybody help me ?
Thank you

If you goto http://server:port/smd >>> Diagnostic Setup >>> Diagnostic System >>> Setup Wizard, do you have a message similar to:
Last Diagnostics setup wizard execution on Tue Oct 09 13:34:44 2007 :
- 0 setup steps disabled by user
- 13 setup steps succesfully executed
- 0 setup steps executed with warnings
- 0 setup steps in error
If you do, your Diagnostic server is correctly setup.
For Managed system, same thing, http://server:port/smd >>> Diagnostic Setup >>> Managed Systems >>> Setup Wizard, or check setup results to make sure it's completed.

Similar Messages

SOLUTION MANAGER UPGRADE - Error when shadow system Starting

Hi All, We are upgrading our Solman system from 7.0 EHP 1 to SOLMAN 7.1. But the system is uable to start the Shadow
system. *** ERROR => DpHdlDeadWp: W0 (pid 12046) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12046) exited with exit code 255 *** ERROR => DpHdlDeadWp: W4 (pid 12050) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12050) exited with exit code 255 DpMBufHwIdSet: set Hardware-ID ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296] MBUF state ACTIVE DpWpBlksLow: max wp blocks in queue is 800 (80 %) MBUF component UP DpMsgProcess: 1 server in MBUF DpAppcBlksLow: max appc blocks in queue is 500 (50 %) *** ERROR => DpHdlDeadWp: W3 (pid 12049) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12049) exited with exit code 255 Sun Jan 8 21:50:33 2012 *** ERROR => DpHdlDeadWp: W2 (pid 12048) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12048) exited with exit code 255 *** ERROR => DpHdlDeadWp: W5 (pid 12051) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12051) exited with exit code 255 *** ERROR => DpHdlDeadWp: W6 (pid 12052) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12052) exited with exit code 255 *** ERROR => DpHdlDeadWp: W7 (pid 12053) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12053) exited with exit code 255 *** ERROR => DpHdlDeadWp: W8 (pid 12054) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12054) exited with exit code 255 *** ERROR => DpHdlDeadWp: W9 (pid 12055) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12055) exited with exit code 255 *** ERROR => DpHdlDeadWp: W10 (pid 12056) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12056) exited with exit code 255 *** ERROR => DpHdlDeadWp: W11 (pid 12057) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12057) exited with exit code 255 kill(12045,0) -> ESRCH: process died DpStartStopMsg: send stop message (myname is >solmanqazone_KSQ_04 <) DpStartStopMsg: Write AD_STARTSTOP message with type= 0, name=solmanqazone_KSQ_04 , sapsysnr= 4, hostname=solmanqazone AdGetSelfIdentRecord: > < AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 60 AdCallRegisteredCvtToExt: opcode 60 call 102164870 AdCallRegisteredCvtToExt: opcode 60 exit rc=SAP_O_K AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 4 AdCallRegisteredCvtToExt: opcode 4 call 102160ff8 AdCallRegisteredCvtToExt: opcode 4 exit rc=SAP_O_K DpConvertRequest: net size = 189 bytes NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufSend starting NiIWrite: hdl 17 sent data (wrt=562,pac=1,MESG_IO) MsINiWrite: sent 562 bytes MsISnd2: send msg (ms hdr/msg 110/452 bytes) to name -, type 4, key - DpStartStopMsg: stop msg sent NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=274,pac=1,MESG_IO) NiBufIIn: NIBUF len=274 NiBufIIn: packet complete for hdl 17 NiBufSend starting NiIWrite: hdl 17 sent data (wrt=114,pac=1,MESG_IO) MsINiWrite: sent 114 bytes MsISnd2: send msg (ms hdr/msg 110/4 bytes) to name MSG_SERVER, type 0, key - MsSndName: MS_NOOP ok Send 4 bytes to MSG_SERVER NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=114,pac=1,MESG_IO) NiBufIIn: NIBUF len=114 NiBufIIn: packet complete for hdl 17 NiBufReceive starting MsINiRead: received 114 bytes MsIReceive: received msg (ms hdr/msg 110/4 bytes), flag 3, from MSG_SERVER , typ 0, key - Received 4 bytes from MSG_SERVER Received opcode MS_NOOP from msg_server, reply MSOP_OK MsOpReceive: ok MsISendKeepalive : keepalive sent to message server NiIRead: hdl 17 recv would block (errno=EAGAIN) Sun Jan 8 21:52:21 2012 NiIPeek: peek for hdl 17 timed out (r; 1000ms) NiIRead: read for hdl 17 timed out (1000ms) DpHalt: no more messages from the message server DpHalt: sync with message server o.k. DpHalt: detach from message server ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 12730] *** ERROR => e=28 semget(20465,1,2016) (28: No space left on device) [semux.c 498] *** ERROR => SemRq: Implicit SemInit failed. Key=65 [semux.c 1129] *** ERROR => Es2Cleanup: SemRq SEM_ES2_ADM (rc=1) [es2xx.c 1082] SemRq( 38, 1, -1) enter SemRq( 38, 1, -1) exit rtc=0, 0us SemRel( 38, 1 ) enter SemRel( 38, 1 ) exit rtc=0, 0us ShmDelete2( 73 ) DpHalt: cleanup event management DpHalt: cleanup shared memory/semaphores SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 7 ) = 0740 (octal) SemKeyPermission( 8 ) = 0740 (octal) SemKeyPermission( 10 ) = 0740 (octal) SemKeyPermission( 11 ) = 0740 (octal) SemKeyPermission( 12 ) = 0740 (octal) SemKeyPermission( 13 ) = 0740 (octal) SemKeyPermission( 14 ) = 0740 (octal) SemKeyPermission( 15 ) = 0740 (octal) SemKeyPermission( 16 ) = 0740 (octal) SemKeyPermission( 17 ) = 0740 (octal) SemKeyPermission( 18 ) = 0740 (octal) SemKeyPermission( 19 ) = 0740 (octal) SemKeyPermission( 20 ) = 0740 (octal) SemKeyPermission( 21 ) = 0740 (octal) SemKeyPermission( 22 ) = 0740 (octal) *** ERROR => e=28 semget(20422,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 24 ) = 0740 (octal) *** ERROR => e=28 semget(20424,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 25 ) = 0740 (octal) *** ERROR => e=28 semget(20425,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 26 ) = 0740 (octal) *** ERROR => e=28 semget(20426,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 27 ) = 0740 (octal) *** ERROR => e=28 semget(20427,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 28 ) = 0740 (octal) *** ERROR => e=28 semget(20428,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 29 ) = 0740 (octal) *** ERROR => e=28 semget(20429,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 30 ) = 0740 (octal) *** ERROR => e=28 semget(20430,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 31 ) = 0740 (octal) *** ERROR => e=28 semget(20431,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 35 ) = 0740 (octal) *** ERROR => e=28 semget(20435,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 42 ) = 0740 (octal) *** ERROR => e=28 semget(20442,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 43 ) = 0740 (octal) *** ERROR => e=28 semget(20443,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 44 ) = 0740 (octal) *** ERROR => e=28 semget(20444,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 45 ) = 0740 (octal) *** ERROR => e=28 semget(20445,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 47 ) = 0740 (octal) *** ERROR => e=28 semget(20447,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 48 ) = 0740 (octal) *** ERROR => e=28 semget(20448,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 49 ) = 0740 (octal) *** ERROR => e=28 semget(20449,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 50 ) = 0740 (octal) *** ERROR => e=28 semget(20450,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 51 ) = 0740 (octal) *** ERROR => e=28 semget(20451,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 53 ) = 0740 (octal) *** ERROR => e=28 semget(20453,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 54 ) = 0740 (octal) *** ERROR => e=28 semget(20454,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 55 ) = 0740 (octal) *** ERROR => e=28 semget(20455,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 56 ) = 0740 (octal) *** ERROR => e=28 semget(20456,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 57 ) = 0740 (octal) *** ERROR => e=28 semget(20457,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 58 ) = 0740 (octal) DpCleanupSharedResources: MpiCleanup ShmCleanup( 62 ) ShmCreate( 62, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 62, 3 ) ShmKeySharedMMU( 62 ) = 0 (octal) ShmProtect: shmat key 62 prot 3/0 done ShmCreate( 62, 0, 2, -> 0xfffffffe1d400000 ) MpiCleanup() -> MPI_OK DpCleanupSharedResources: removing Semaphore-Management DpCleanupSharedResources: removing request queue ShmCleanup( 31 ) ShmCreate( 31, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 31, 3 ) ShmKeySharedMMU( 31 ) = 0 (octal) ShmProtect: shmat key 31 prot 3/0 done ShmCreate( 31, 0, 2, -> 0xffffffff24000000 ) DpCleanupSharedResources: ShmCleanup SHM_SYS_ADM_KEY ShmCleanup( 1 ) ShmCreate( 1, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 1, 3 ) ShmKeySharedMMU( 1 ) = 0 (octal) ShmProtect: shmat key 1 prot 3/0 done ShmCreate( 1, 0, 2, -> 0xffffffff78100000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_ADM_KEY ShmCleanup( 2 ) ShmCreate( 2, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 2, 3 ) ShmKeySharedMMU( 2 ) = 0 (octal) ShmProtect: shmat key 2 prot 3/0 done ShmCreate( 2, 0, 2, -> 0xffffffff28800000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_CA_KEY ShmCleanup( 3 ) ShmCreate( 3, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 3, 3 ) ShmKeySharedMMU( 3 ) = 0 (octal) ShmProtect: shmat key 3 prot 3/0 done ShmCreate( 3, 0, 2, -> 0xffffffff24800000 ) DpCleanupSharedResources: ShmCleanup SHM_PF_KEY ShmCleanup( 4 ) ShmCreate( 4, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 4 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_SAPSCSA_AREA_KEY ShmCleanup( 5 ) ShmCreate( 5, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 5 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PXA_KEY ShmCleanup( 6 ) ShmCreate( 6, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 6 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_VB_ADM_KEY ShmCleanup( 7 ) ShmCreate( 7, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 7 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_AREA_KEY ShmCleanup( 8 ) ShmCreate( 8, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 8 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_ROLL_AREA_KEY ShmCleanup( 9 ) ShmCreate( 9, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 9 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_CALI_BUFFER ShmCleanup( 11 ) ShmCreate( 11, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 11, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_CCC_KEY ShmCleanup( 12 ) ShmCreate( 12, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 12, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_ALERT_AREA_KEY ShmCleanup( 13 ) ShmCreate( 13, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 13, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_PRES_BUF ShmCleanup( 14 ) ShmCreate( 14, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 14, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup DVS_SHM_KEY ShmCleanup( 15 ) ShmCreate( 15, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 15, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_SEM_MONI_BUFFER ShmCleanup( 16 ) ShmCreate( 16, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 16, 3 ) ShmCreate( 16, 0, 2, -> 0xffffffff29004000 ) ShmDelete2( 10 ) Sun Jan 8 21:52:22 2012 DpCleanupSharedResources: ShmCleanup SHM_ROLL_ADM_KEY ShmCleanup( 17 ) ShmCreate( 17, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 17, 0, 2, 0xffffffff7fffe9e0 ) ShmCreate( 10, 0, 2, 0xffffffff7fffe828 ) ShmKeyPermission( 10 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_ADM_KEY ShmCleanup( 18 ) ShmCreate( 18, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 18 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_TBUFF ShmCleanup( 19 ) ShmProtect( 52, 3 ) ShmKeySharedMMU( 52 ) = 0 (octal) ShmProtect: shmat key 52 prot 3/0 done ShmCreate( 52, 0, 2, -> 0xffffffff77600000 ) DpCleanupSharedResources: ShmCleanup SHM_ES_ADM_T ShmCleanup( 53 ) ShmCreate( 53, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 53 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_OBJ_BUFFER ShmCleanup( 54 ) ShmCreate( 54, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 54 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_RSPO_LOCAL_KEY ShmCleanup( 55 ) ShmCreate( 55, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 55 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PF_AS_KEY ShmCleanup( 56 ) ShmCreate( 56, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 56 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PROFILE ShmCleanup( 57 ) ShmCreate( 57, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 57, 3 ) ShmKeySharedMMU( 57 ) = 0 (octal) ShmProtect: shmat key 57 prot 3/0 done ShmCreate( 57, 0, 2, -> 0xffffffff75700000 ) DpCleanupSharedResources: ShmCleanup SHM_ENQID_KEY ShmCleanup( 58 )
Regards, VIjay K.G

Hi,
From logs:
28: No space left on device
Check the disk space. If linux, use df -h command. Windows its easier
Check if any drive / file system is 100% used up.
Regards,
Srikishan

ERROR while CREATING RFC FOR SOLUTION MANAGER DIAGNOSTICS

Dear all,
Hi,
I am configuring solution manager 7.0.
In SPRO>basic setting >operation>solution manager diagnostics > create RFC for solution manager diagnostics i am getting this error
program WEBADMIN not registerred.
can any one tell me how to register this program in sap gateway.
best regards
azeem

Hi Azeem,
Just before creating the rfc connection do this step.
Set-Up Solution Manager Connection to Solution Manager Diagn
Use
Check the connection to function Solution Manager Diagnostics.
Default Settings
The function Solution Manager Diagnostics is installed on the Java instance of the Solution Manager system by default.
Activities
If the default values are correct, save the settings.
To run the Solution Manager Diagnostics in another system, enter the required data and save.
Also check that your java is active.
Regards
Ashok

Solution landscape doesn't appear in Solution Manager Diagnostics

Dear all,
I have configured 6 Solution Landscapes in transaction solution_manager. One for ECC5, one for PI 7.0, one for BI 7.0, one for Solution Manager 7.0, one for SRM 4.0 and finally one for NW 04 Portal.
When I go to my Solution Manager Diagnostics URL
https://solman.domain.com:50001/smd and I do Diagnostics Setup --> Managed Systems --> Setup Wizard, I see there all the Solution Landscapes I have configured except for the NW 04 Portal one. Any ideas why I can not see this landscape? I am trying to think if I have missed any configuration but I can not think of something
Many thanks
Andreas

Sad to say, Vista isn't a supported system for Acrobat XI.

Solution Manager information for Java stack systems

Hi,
Could someone please help with the setup of Solution Manager, and how to connect to the backend of a Java stack system. For our ERP systems this is working via RFC, but I was hoping to get more information on the procedure for java. I can specify manually via SMSY, but I am sure there must be a setup that can pull the information for the system itself. Could anyone shed some light on this if possible please.
Regards,
Chris

Dear Chris,
ABAP Stacks use RFC as you know for inter system communications.
Java stack systems use Solution Manager Diagnostics.
You will need to run Solman_Setup > Managed System Configuration
First you should visit the link http://service.sap.com/diagnostics
There you will see a link to the media library, and there you will find complete documentation.
Hope you find this information Helpful.
Regards,
Paul

Solution Manager Diagnostics - Installation

I have installed SM EHP1 and have also installed SMD. However during the Basic configuration of SM, I'm getting Diagnostics Configuration errors during the Automatic Configuration phase of the Diagnostics configuration. The errors showing up are:
1. Cannot call Diagnostics Setup web service
2. Web Service URL: http://atl-osm-01.oversightsystems.com:8100/DiagSetupServices/Di...
3. SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
4. Error when processing Web service call
5. Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
What am I missing here?
Thanks for the help.

Hello Hans.
Have you solved the problem? We have a similar problem with Solution Manager 7.0 EHP1 SP27.
Errormessage (parts are in German):
Web Service URL: http://solman.company.com:8100/DiagSetupServices/DiagSetupConfig?style=document
Cannot call Diagnostics Setup web service
SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not found")
Beim Prozessieren eines Web Service-Aufrufs ist ein Fehler aufgetreten.
Fehler beim Aufruf von Funktionen der SOAP Runtime: SRT: Unsupported xstream found: ("HTTP Code 404 : Not found")
Note: We have changed the http and https-Ports of ICM. Solution Manager is working fine, but Solution Manager Diagnostics Setup does not work.
Thank you for a hint.
Best regards,
Tobias

How to stop SAP Solution Manager Diagnostics instance?

Dear community.
I've got a question. We are working on solman 4.0 with installed SMD (Solution Manager Diagnostics). For this tool is runnig an separated java instance on our server. The problem is, that we don't need the SMD, becaucse we have no JAVA systems to monitor. Is it possible to stop the SMD instance? If yes, how can I do it?
Many thanks in advance...
Michael

Solution manager itself has a java stack so are you saying you don't monitor solution manager java side of things?
SMD does both ABAP and Java application monitoring with varying levels of details, interactions, reporting etc so disabling SMD, to me, defeats the whole purpose of having Solution Manager 4
SAP wants customers to use this tool as best practice and guidelines suggest
On the other hand what advantage do you have of stopping this instance? It would still be sitting in your landscape taking up resources and should you come to use things like SLD and other java applications which I believe will be sooner than later you will have to setup/configure SMD again.
SAP best practice is to have a single SLD and this will definitely be monitored using SMD

Solution manager diagnostics

Hello.
I have installed SMD agent in a monitored system in order to obtain EWA non-ABAP from this system.
I go to http://<host>:<port>/smd and the agent is running. I go to setup wizard for this managed system and the result is ok, all the semaphores are green.
The problem is that, when i try to do the other task, the solution manager diagnostics don't recognize the setup done.
I receive this message : -No setup or configuration steps performed yet-
I,ve followed the note 1014999 but the result is not ok.
I don't know what step i'm missing, so if someone has got an answer, please, tell me, because i've tried lot of things and i don't know how can i continue.
Thanks a lot.
Best regards

Hello.
Yes, I have run setup wizard for solution diagnostics first and run the upgrader etc...
Now SAP is connected to the system in order to solve the problem as well as we continue our investigations. I you've got more ideas, please, tell us.
Thanks a lot.
Best regards

Solution Manager Installation Error "SAP SOLUTION MANAGER 7.0 EHP 1"

I am new to SAP and currently trying to install SOLMAN 7.0 EHP 1 on Windows Server 2008 R2. I have read the documentation also. For JDK I have used "j2sdkfb-1_4_2_24-rev-b06-windows-amd64.exe" which looks to be working fine.
The installation process runs fine until it hits "Start Instance" the message on the bottom says "Starting instance xxx/DVEBMGSOO" (where xxx is my sid) and then its times out after 10 minute. After timing out I get the following error on the window.
An error occurred while processing option SAP Solution Manager 7.0 EhP1 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step: ABAP processes of instance ORC/DVEBMGS00 ABAP: UNKNOWN did not start after 10:00 minutes. Giving up.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
Though the installation steps are not fully completed but I do see SAP management Console and when I open it I see two process running "msg_server.exe" & "igswd.exe" The process dispwork.EXE starts in the beginning and then stops and stays stopped. I tried restarting all the process again but only tow of them starts and the process "dispwork.EXE" starts but then stops again. I also did a NEW installation considering a file could have been corrupted or something else but the installation process stops and the same place. I am sure ppl have installed SOLMAN on windows 2008 R2 and this error seems common to me. Please assist. Any tips would be nice.
Edited by: amirsd on Aug 3, 2011 5:53 PM

Hi,
Please check the below
1) ip/host entries should be in /etc/hosts
2) patch the latest kernel for 2008 R2
and re run installation
Regards,
Ram

Solution Manager Diagnostics don't display data

Hi,
I'm setting up Solution Manager Diagnostics at Solution Manager SP 22. I've installed Wily Introscope Enterpise Manager at Solution Manager Server, and Wily Introscope Agents at Solution Manager and Satellite systems as well.
Wily Introscope is working properly, I receive statistics from all agents, and also I can see most of the graphics. BUT, after I install SMD Agent, I can't receive any data in Root Cause Analysis Workcenter -> End-To-End Analysis -> system -> Workload Analysis.
Here I can see a plot with all values at 0. If I try Enterprise Portal tab -> Portal Activity Reporting, I don't have any data.
At Aplication Server Java tab -> J2EE Engine, I only can see forms like:
     E2E CV PPMS ID Variable
     E2E Installation Number Variable
     E2E SID Variable       <SID>         <SID>
     E2E Metric Type Variable(multiple values)
               SERVLETS
               WEB DYNPRO APPLICATI ONS
               JCO CALLS
              SQL STATEMENTS
InfoProvider
              0SMD_PE2H
              0SMD_PERH
But if I execute or check this form, I receive this message:
Value "SERVLETS" for variable "E2E Metric Type Variable(multiple values)" is invalid.
I've also followed SAPNote 1435043 - E2E Workload Analysis - No applicable data found, and checked prerequisites, RFC's, Jobs, Extractors and executed SOLMAN_SETUP transaction.
I've followed all guides I've found for Diagnostics, but I don't know how can I solve this.
Please, could you help me?
Thanks in advance and regards.
Tomas.

Hi Tomas,
I have exactly the same problem, I am on Solman SPS22, LMSERVICE SP06 patch2.
and the satellite system pre-requisites and definition in SMSY are correct, also the MDX PARSER RFC is wrking fine.
any idea on why is the Portal activity reporing is blank, while i get data under all the other tabs.
Also, the agent application .log file shows the below warning
"PadcService@1cbd1cbd: file portalActivity_6057051_1278074505498.txt could not be deleted"
but i could not find the file in the satellite system.
Regards,
kaustubh.
Edited by: Kaustubh Krishna on Jul 12, 2010 11:21 AM

Configuration error description: The system cannot find the path specified

Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068643839
Exit facility code:            1203
Exit error code:               1
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time:                    2012-10-26 00:24:37
End time:                      2012-10-26 00:32:07
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121026_002259\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xF57C3D6F%400xFB92A9BB
Machine Properties:
Machine name:                  TEST-PC
Machine processor count:       4
OS version:                    Windows Vista
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Sql Server 2008      SQL                  MSSQL10.SQL
Database Engine Services                 1033                 Standard Edition
10.0.1600.22    No
Sql Server 2008      SQL                  MSSQL10.SQL
SQL Server Replication                   1033                 Standard Edition
10.0.1600.22    No
Sql Server 2008      SQL                  MSSQL10.SQL
Full-Text Search                         1033
Standard Edition     10.0.1600.22    No
Sql Server 2008      SQL                  MSAS10.SQL
Analysis Services                        1033
Standard Edition     10.0.1600.22    No
Sql Server 2008      SQL                  MSRS10.SQL
Reporting Services                       1033
10.0.1600.22    No
Sql Server 2008      TEST                 MSSQL10.TEST
Database Engine Services                 1033                 Standard Edition
10.0.1600.22    No
Sql Server 2008      TEST                 MSSQL10.TEST
SQL Server Replication                   1033                 Standard Edition
10.0.1600.22    No
Sql Server 2008      TEST                 MSSQL10.TEST
Full-Text Search                         1033
Standard Edition     10.0.1600.22    No
Sql Server 2008      TEST                 MSAS10.TEST
Analysis Services                        1033
Standard Edition     10.0.1600.22    No
Sql Server 2008      TEST                 MSRS10.TEST
Reporting Services                       1033
10.0.1600.22    No
Sql Server 2008      SQLSERVER            MSSQL10.SQLSERVER              Database Engine Services
1033                 Enterprise Evaluation Edition 10.0.1600.22    No
Sql Server 2008      SQLSERVER            MSSQL10.SQLSERVER              SQL Server Replication
1033                 Enterprise Evaluation Edition 10.0.1600.22    No
Sql Server 2008      SQLSERVER            MSSQL10.SQLSERVER              Full-Text Search
1033                 Enterprise Evaluation Edition 10.0.1600.22    No
Sql Server 2008      SQLSERVER            MSAS10.SQLSERVER               Analysis Services
1033                 Enterprise Evaluation Edition 10.0.1600.22    No
Sql Server 2008      SQLSERVER            MSRS10.SQLSERVER               Reporting Services
1033                                      10.0.1600.22
No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008
Management Tools - Basic                 1033                 Enterprise Evaluation Edition 10.0.1600.22
No
Sql Server 2008
Management Tools - Complete              1033                 Enterprise Evaluation Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity                1033                 Enterprise Evaluation Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Backwards Compatibility     1033                 Enterprise Evaluation Edition 10.0.1600.22    No
Sql Server 2008
Client Tools SDK                         1033
Enterprise Evaluation Edition 10.0.1600.22    No
Sql Server 2008
Integration Services                     1033                 Enterprise Evaluation
Edition 10.0.1600.22    No
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         C:\instal_sw\SQL Server 2008\SQL Server 2008\x64\setup\
Installation edition:          EVAL
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Automatic
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121026_002259\ConfigurationFile.ini
ENABLERANU:                    False
ERRORREPORTING:                False
FEATURES:                      SQLENGINE,REPLICATION,BOL,SNAC_SDK,OCS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    sqlserver2008
INSTANCENAME:                  SQLSERVER2008
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
MEDIASOURCE:                   C:\instal_sw\SQL Server 2008\SQL Server 2008\
NPENABLED:                     0
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           Test-PC\Test
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121026_002259\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0xFB92A9BB
Configuration error description: The system cannot find the path specified
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121026_002259\Detail.txt
Feature:                       SQL Client Connectivity SDK
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0xFB92A9BB
Configuration error description: The system cannot find the path specified
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121026_002259\Detail.txt
Feature:                       SQL Server Books Online
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Microsoft Sync Framework
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121026_002259\SystemConfigurationCheck_Report.htm

Hi Maggie,
Even i am facing the same problem while installing sql server 2008 R2 on windows server 2012 R2
The required error message is provided below:
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-11-24 06:23:13
End time: 2014-11-24 06:47:19
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141124_061929\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xCEC86A55%400xFB92A9BB
Machine Properties:
Machine name: M2MBUILDTEST01
Machine processor count: 2
OS version: Windows Server 2008
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: C:\SQL Server 2008\Developer RTM\x64\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: swg\gverma
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: swg\gverma
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: SWG\gverma
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141124_061929\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: C:\SQL Server 2008\Developer RTM\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: SWG\gverma
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: swg\gverma
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: SWG\gverma
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141124_061929\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xFB92A9BB
Configuration error description: The system cannot find the file specified
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141124_061929\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xFB92A9BB
Configuration error description: The system cannot find the file specified
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141124_061929\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xFB92A9BB
Configuration error description: The system cannot find the file specified
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141124_061929\Detail.txt
Feature: Analysis Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141124_061929\SystemConfigurationCheck_Report.htm

1)    Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration?       i. The list of the modules that are being managed by SAP Solution Manager(s)      ii. The performance metrics of those modules/components at th

1)
Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration?
i. The list of the modules that are being managed by SAP Solution Manager(s)
ii. The performance metrics of those modules/components at the high level
iii. The information about Early Watch Alerts (or situations to watch for)
2)
Is there a full SNMP interface for getting the above information from SAP Solution Manager?
3)
Is that understanding that SAP has SNMP support for forwarding alerts to a 3rd party system, correct?
4)
Does SAP has both free and licensed? If yes then what are the advantages of licensed over the open/free version?

Mugunthan
Yes we have applied 11i.AZ.H.2. I am getting several errors still that we trying to resolve
One of them is
===========>>>
Uploading snapshot to central instance failed, with 3 different messages
Error: An invalid status '-1' was passed to fnd_concurrent.set_completion_status. The valid statuses are: 'NORMAL', 'WARNING', 'ERROR'FND     at oracle.apps.az.r12.util.XmlTransmorpher.<init>(XmlTransmorpher.java:301)
     at oracle.apps.az.r12.extractor.cpserver.APIExtractor.insertGenericSelectionSet(APIExtractor.java:231)
please assist.
regards
girish

Multiple Solution Manager Connectivity to 1 Satellite system

HI..
I have a requirement. There is already an existing landscape with solution manager ECC, BI etc. The solution manager is configured for EWA, Maintenance optimizer etc. I now have to install a new solution manager and connect it to the same set of satellite systems so that I receive the EWA, configure MOPZ again. Will this create any kind of a problem and technically how can we do it? I have two ideas for this scenario
1. Connect the new solution manager to the same satellite systems and do configuration as normal. Got this idea from the below link but not sure how it will work.
Re: send EWA report to more than one solution manager
2. Is it possible to push data from the existing solution manager to the new solution manager?
Would highly appreciate technical suggestions. Thx in advance for your help.

Hello,
You need the SMD Agent in order to have ABAP data going to the Solution Manager. Some RFCs are established directly from Managed System to the Solution Manager to extract E2E Change Analysis, Exception Analysis. The Workload Analysis and Host Information (SAPOSCOL) is extracted from WIly EM
Having that said, you can imagine that you cannot have only RFCs and you cannot have only data extracted from WIly EM.
I suggest you to take a look at the FWK Administration in the solman_workcenter, choose the Managed System tab, and start looking into the details of each extractor. Some have an RFC destionation, others have SOLMANDIAG. The SOLMANDIAG are coming from the Solution Manager Java stack, which is responsible to poll the Wily EM.
The reason you need two SMD Agents is because the SMD Agent connects to the ABAP stack, retrieves data, and then connects to the Wily Enterprise Manager. The Solution Manager polls data from the Wily EM and persists it in the BW.
The SMD Agent doesn't support connecting to two Wily EMs at the same time.
So it is required to have TWO SMD agents polling data from the ABAP stack, at the same time, one of them reporting to one Wily EM, and the other reporting to the other Wily EM.
Each solution manager has it's own Wily EM, and it will pull the ABAP data from the Wily EM.
It is not possible to make the two Solution Manager's connect to one Wily EM, since the setup framework needs to see a SMD Agent available to run the setup wizard and to create the destinations. So each Solution Manager needs a SMD Agent running in the physical host.
I hope it is clear for you.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Feb 6, 2012 9:44 PM
Edited by: Guilherme Balbinot on Feb 6, 2012 9:49 PM

Solution Manager Diagnostics: Agent Architecture

Hi there,
current I write a degree dissertation about Solution Manager Diagnostics. In different books, documentations and manuals I read about Agents which must be installed on the managed system. But I find no exactly description about the agents architecture. In a book about the Solution Manager is written, that the structure includes two tiers. The first tier are the core agents, but there is nothing explained about the second tier ... Is a core agent the same like a host agent?
Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
Thanks and best regards,
Andreas

> Can anybody explain me (exactly) the differnt functions of the agents (core, host, diagnostics, wily-agent)?? Or maybe some links will be helpful.
I would start with
http://service.sap.com/diagnostics
There are lots of (detailed) documentations available.
Markus

ALC-PDG-001-000-ALC-PDG-010-015-The conversion operation timed out before it could be completed. Please report this error to the system administrator.

I am getting the error when trying to convert a word file to pdf.
My Adobe Lifecycle ES is installed on 2GM RAM . Is this the issue for the below error.
ALC-PDG-001-000-ALC-PDG-010-015-The conversion operation timed out before it could be completed. Please report this error to the system administrator.
Please provide me a valuable solution. I am new to Adobe ls es.

This is a forum for Acrobat desktop product. For LiveCycle, try this forum
http://forums.adobe.com/community/livecycle/livecycle_es/pdf_generator_es

Solution Manage Diagnostics - error in the system setup

Similar Messages

Maybe you are looking for