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

Similar Messages

Solution Manager key error when installing ECC6

hi
Iam installing ECC6 abap+java and facing a problem with the solution manager generated key.Each time iam putting in the key its says its the wrong one.
i dont know where iam making a mistake.i managed to generate one before when upgarding to ECC6 and it work withou any problems.
am i making a mistake somewhere?
help appreciated

Hi,
Let me know your SID, Instance No, and Host name. Also write what SOLMAN Key you have entered. I can cross-check that is correct or not.
Rgds,
Mahesh Bansal

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.

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 upgrade issue on Linux

Hi Alll,
Need your inputs/thoughts on this issue.
We are planning for Solution Manager upgrade from 3.1 to 4.0 and for this the setup and plan is as below:
The production data of the solution manager has been copied as a VMX FILE(VM Player) file on to a test server and we have plans to upgrade that and check and then upgrade on the production system.
The test machine has got a different IP address and hostname. From the test machine when I start the sap instance its affecting the Production machine and dueto which the production will not work until I stop the SAP Instance on the test machine.
It cannot be a IP conflict or hostname conflict as we have them differently on the test machine. But still there is an issue. The IT dept says the issue is with the starting up of the instance and we dont know where to see what exactly is the problem.
I am new to upgradation stuffs, this is my 1st assignment and I am not sure from where to start!!
Can anyone of you tell me where to check for the details?
SOLMAN is installed on a unix machine with oracle 9.2 and we are planning to upgrade it to SOLMAN 7.0
any suggestions on where to look out for the possible issue?

Hi,
I did this a lot and know the side effects a little.
My recipe:
1. Start the copy without network and manage it from the VMWare Console. Change the IP address and make sure all references to the hostname (DNS and /etc/hosts) point to the new one. I hope you're working consistently with hostnames and no IP addresses.
2. Configure the firewall (iptables) on the copied system to block all requests from and to the original production server. If there is any communication with other SAP servers (like monitoring agents, SLD, or others) block this too!
3. Re-enable the network in VMWare.
Alternatively: Can't you simply put this in a VLAN or a real seperated network with just the server and a management workstation?
Hope that helps..
Nikolaus

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

Dns error when trying to start ssgd 4.4

Hi,
I get the following error when trying to start a fresh install of SSGD 4.4 on sun solaris 10 sparc machine
bash-3.00# /opt/tarantella/bin/tarantella start
Starting Secure Global Desktop server (version 4.40.917). Please wait...
2008/05/12 18:34:43.082 (pid 27580) server/common/fatalerror #1210597482966
Sun Secure Global Desktop Software (4.4) FATAL ERROR:
The configured DNS name of the server (unknown) couldn't be
resolved in DNS.
The server can't start.
Check your DNS configuration.
I tried changing the servername in the httpd.conf file but still get the above errors. What could be the possibel reasons for this error.
Thanks,

Hi,
I changed the peerdns name to "penguin.everett.nl"
Cbash-3.00# /opt/tarantella/bin/tarantella status
Array members (1):
- penguin.everett.nl (primary): NOT ACCEPTING CONNECTIONS.
bash-3.00#
However, when I now start the tarantella I get the following error :
bash-3.00# /opt/tarantella/bin/tarantella stop
Secure Global Desktop services are not currently running.
bash-3.00# /opt/tarantella/bin/tarantella start
Starting Secure Global Desktop server (version 4.40.917). Please wait...
javax.naming.NameNotFoundException: asad.properties [Root exception is java.io.FileNotFoundException: /opt/tarantella/var/serverconfig/global/beans/asad.properties]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.sco.jndi.toolkit.provider.SimpleContinuation.getSimpleException(SimpleContinuation.java:62)
at com.sco.jndi.toolkit.provider.SimpleContinuation.getSimpleException(SimpleContinuation.java:82)
at com.sco.jndi.toolkit.provider.ToolkitContext.namingException(ToolkitContext.java:386)
at com.sco.jndi.toolkit.provider.ToolkitContext.namingException(ToolkitContext.java:401)
at com.sco.jndi.toolkit.provider.ToolkitContext.nameNotFound(ToolkitContext.java:436)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.FileNotFoundException: /opt/tarantella/var/serverconfig/global/beans/asad.properties
at com.sco.jndi.provider.file.FileCacheObject.<init>(FileCacheObject.java:62)
at com.sco.jndi.provider.file.FileCacheObject.<init>(FileCacheObject.java:39)
at com.sco.jndi.provider.file.FileCache.lookup(FileCache.java:83)
at com.sco.jndi.provider.file.FileCache.lookup(FileCache.java:68)
at com.sco.jndi.provider.file.FileContext.child(FileContext.java:612)
at com.sco.jndi.provider.file.FileContext.f_lookupLink(FileContext.java:889)
... 12 more
java.io.IOException: Failed to load all Beans : javax.naming.NameNotFoundException: asad.properties [Root exception is java.io.FileNotFoundException: /opt/tarantella/var/serverconfig/global/beans/asad.properties]
at com.sco.tta.server.server.JServer.<init>(JServer.java:327)
at TTAServer.run(TTAServer.java:391)
at java.lang.Thread.run(Thread.java:619)
bash-3.00# /opt/tarantella/bin/tarantella status
Array members (1):
- penguin.everett.nl (primary): NOT ACCEPTING CONNECTIONS.
bash-3.00#

I get an error when attempting to start genius. It says "Unsuccessful Action: The action you attempted to perform did not complete successfully. Please try again later." Help!

I get an error when attempting to start genius. It says "Unsuccessful Action: The action you attempted to perform did not complete successfully. Please try again later." Help!

From an existing Discussion:
Go to Safari --> Preferences
Click Security
Show Cookies
Type "apple.com" in to top search field
Select All
Click Remove
Click Done
Repeat the above to confirm they are gone (mine took two attempts)
Choose Update Genius again in iTunes.
iTunes 9 - can't update genius https://discussions.apple.com/thread/2151150

Error when the engine starts

Hi all,
I'm getting this error when my engine starts. What can be happening? How can I avoid it?
fuego.transaction.DatabaseException: Se ha producido un error al acceder a la base de datos.
Detalle:InstrucciÃ³n SQL: 'DELETE FROM PWKTODO WHERE WKTDKEY = ? WKTDKEY:'caducator.'
at fuego.server.persistence.jdbc.JdbcToDoItemPersMgr.delete(JdbcToDoItemPersMgr.java:806)
at fuego.server.persistence.Persistence.deleteToDoItem(Persistence.java:758)
at fuego.server.execution.AbstractToDoQueue.persist(AbstractToDoQueue.java:46)
at fuego.server.execution.EngineExecutionContext.persistToDoItems(EngineExecutionContext.java:2054)
at fuego.server.execution.EngineExecutionContext.persist(EngineExecutionContext.java:1207)
at fuego.transaction.TransactionAction.beforeCompletion(TransactionAction.java:132)
at fuego.connector.ConnectorTransaction.beforeCompletion(ConnectorTransaction.java:692)
at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:375)
at fuego.transaction.TransactionAction.commit(TransactionAction.java:302)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:207)
at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:118)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 29 seconds
BEA1-29DC678B1DDE2A93EEAE
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1418)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1330)
at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:189)
at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:64)
at weblogic.jdbc.wrapper.Connection.preInvocationHandler(Connection.java:92)
at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:482)
at fuego.jdbc.FaultTolerantConnection.prepareStatement(FaultTolerantConnection.java:541)
at fuego.server.persistence.jdbc.JdbcToDoItemPersMgr.delete(JdbcToDoItemPersMgr.java:763)
at fuego.server.persistence.Persistence.deleteToDoItem(Persistence.java:758)
at fuego.server.execution.AbstractToDoQueue.persist(AbstractToDoQueue.java:46)
at fuego.server.execution.EngineExecutionContext.persistToDoItems(EngineExecutionContext.java:2054)
at fuego.server.execution.EngineExecutionContext.persist(EngineExecutionContext.java:1207)
at fuego.transaction.TransactionAction.beforeCompletion(TransactionAction.java:132)
at fuego.connector.ConnectorTransaction.beforeCompletion(ConnectorTransaction.java:692)
at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:375)
at fuego.transaction.TransactionAction.commit(TransactionAction.java:302)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:207)
at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:118)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1343)
at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:189)
at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:64)
at weblogic.jdbc.wrapper.Connection.preInvocationHandler(Connection.java:92)
at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:482)
at fuego.jdbc.FaultTolerantConnection.prepareStatement(FaultTolerantConnection.java:541)
at fuego.server.persistence.jdbc.JdbcToDoItemPersMgr.delete(JdbcToDoItemPersMgr.java:763)
... 26 more

The only thing I'd caution you strongly against doing is to undeploy a project that has active instances in production.
If you do this, the instances currently running through the processes in the project will be lost and cannot be resurrected.
If this is not in production, then undeploying the project obviously won't do you any harm.
Probably not the cause of the problem, but the only time I've seen a similar error was when an incorrect JDBC driver was used for the Engine. If this is not a new installation and you're on the latest patchset and you haven't done anything odd with the JDBC driver, then you might want to give support a call to see if they've run into a similar issue in the past.
Dan

Error when trying to start the ToolsAndFrameworks to access Endeca workbenc

Hi All,
I am getting the below error when trying to start the ToolsAndFrameworks.
Starting Workbench (background process)
The BASEDIR environment variable is not defined correctly
This environment variable is needed to run this program
Regards
SK

Hi SK,
This occurs in those cases where the Endeca environment variables are not set properly. Make sure all the Endeca environment variables are set before starting the Tools services.
Executing the 'mdex_setup_ini' and 'installar_sh.ini' will setup the Endeca environment variables. Below are the commands for the same.
source /local/endeca/MDEX/6.3.0/mdex_setup_sh.ini
source /local/endeca/PlatformServices/workspace/setup/installer_sh.ini
HTH,
Mahesh

I get an error that says that LR5 encounterd a preview cach error when trying to start LR5 and that it will try to fix it the next time it starts. What can I do to fix this error?

I get an error that says that LR5 encountered a preview cache error when trying to start LR5 and that it will try to fix it the next time it starts. What can I do to fix this error?

Go to the folder with you Lightroom Catalog (usually in Pictures) and delete the folder ending in .lrpreviews
This contains the previews for the files Lightroom has linked to. They will need to be rebuilt which can be done while working or selecting an amount you want to rebuild and accessing the rebuild command in the Library Dropdown menu...

Solution Manager Upgrade to EHP1 7.01

Hi
Need some help. Could you please share upgrade doc/exp with me, we are planning for upgrade solution manager from sp17 to sp19.
Stack level 18 or 19 is the part of EHP1 of Solution Manager version 7.01.
What is the process to upgrade the support pack to sp level 19? i have no exp to upgrade to EHP1 level..Any difference ?
Thanks in advance
Amar

Hi Amarjit,
Solution manager upgrade to EHP1 is same like other stack upgrade. You can do it using SAINT/JSPM. But only thing you need is good preparation.
Check upgrade guide on http://service.sap.com/solutionmanager.
Also, check SAP Note 1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1 and SAP Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade
Thanks
Sunny

Any solution for 4280 error when using Itunes to burn CDs?

Any solution for 4280 error when using Itunes to burn CDs?

http://support.apple.com/kb/TA38101?viewlocale=en_US

Solution Manager Upgrade master media not found on download area

Hi All,
We have downloaded solution manager upgrade media from service marketplace. We are performing non-unicode upgrade.
From the download area, we cannot find Upgrade master dvd or media. Media found are:
51031485_1_SOLMAN4_UPGRADE
51031485_2_SOLMAN4_UPGRADE
Please advice.
Many Thanks,
Nischal

I have managed to get prepare going.

Solution Manager ChaRM Issues when Upgrading Satellite System

When upgrading a satellite system that is connected to Solution Manager's Change Request Management, is there anything that we need to be aware of?
Will Change Documents still be able to go to completion (Production status) if we modify the landscape from the time the Change Document is In Development to the time it is moved to Production?
1. Normal Correction (In Development) Development (ECC 5.0) -> Quality (ECC 5.0) -> Production (ECC 5.0)
2. Landscape is changed to Development (ECC 6.0) -> Quality (ECC 6.0) -> Production (ECC 5.0)
3. Normal Correction moved to To Be Tested -> Consolidated -> Production
Will the Normal Correction be in error because the landscape changed for the iBASE?
Are there any other lessons learned that anyone has experienced with Change Request Management or Implementation during and after an upgrade?
Thank You,
Carlen
Edited by: Carlen Yuen on Jan 13, 2009 1:50 AM
Edited by: Carlen Yuen on Jan 13, 2009 1:51 AM

Thanks Subhashini!
We had issues updating the Task List in the past. After we update the landscape and refresh the project and update the Task List, do you foresee any other problems?
Are there any additional items we should look out for? For example, we understand it is a requirement to release all transports prior to beginning the upgrade. However, since the release of the transport locks the change into the cycle for the next production move, this will present a problem if the change is not yet ready to be moved into Production. Do you have any further insight to any additional issues such as this?
Thanks again!
Carlen

SOLUTION MANAGER UPGRADE - Error when shadow system Starting

Similar Messages

Maybe you are looking for