Upgrade Solution Manager 4 to 7.1

Hi all,
Is it possible to have a direct upgrade from a solution manager 4 to 7.1? Or do i need to do other installation or upgrade before it is comparable for 7.1?
Pls advise. Thanks
Regard
Gary

Hello,
Solution manager 4 is synonymous with Solution Manager 7.0
The upgrade guide refere to the source system being
SAP Solution Manager 7.0
SAP Enhancement Package 1 for Solution Manager 7.0
And the target system being SAP Solution Manager 7.1
Therefore the answer is yes, you can upgrade from release 4.0/7.0 to 7.1
Have you visited
https://websmp105.sap-ag.de/~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=00200797470000065932
And also
http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 7.1. Upgrades
Regards,
Paul

Similar Messages

  • Java process table empty after upgrade solution manager 7.1 Sp10

    Hi Experts,
    I have installed solution manager 7.1 SP3 and completed the SP10 patch upgrade using SUM tool. The upgrade was completed successfully. After upgrade igswd was red. Then i copied the Igs files in kernel files. Now ABAP instance and Igs is working now but JAVA is not coming up. JAVA process table also empty. Can any one help me to solve this issue. Attached the error for reference.
    trc file: "dev_disp", trc level: 1, release: "721"
    sysno      00
    sid        VSM
    systemid   562 (PC with Windows NT)
    relno      7210
    patchlevel 0
    patchno    201
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
    pid        5448
    kernel runs with dp version 138000(ext=120000) (@(#) DPLIB-INT-VERSION-138000-UC)
    length of sys_adm_ext is 592 bytes
    *** SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (00 5448) [dpxxdisp.c   1316]
      shared lib "dw_xml.dll" version 201 successfully loaded
      shared lib "dw_xtc.dll" version 201 successfully loaded
      shared lib "dw_stl.dll" version 201 successfully loaded
      shared lib "dw_gui.dll" version 201 successfully loaded
      shared lib "dw_mdm.dll" version 201 successfully loaded
      shared lib "dw_rndrt.dll" version 201 successfully loaded
      shared lib "dw_abp.dll" version 201 successfully loaded
      shared lib "dw_sym.dll" version 201 successfully loaded
      shared lib "dw_aci.dll" version 201 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    rdisp/dynamic_wp_check : 1
    rdisp/calculateLoadAverage : 1
    Tue Apr 01 19:02:09 2014
    *** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 6 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6479]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    display_tcp_ip: 0
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    DpIPCInit2: start server >VKCSOL_VSM_00                           <
    DpShMCreate: sizeof(wp_adm) 42864 (2256)
    DpShMCreate: sizeof(tm_adm) 5517056 (27448)
    DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
    DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080
    DpShMCreate: sizeof(comm_adm) 1384080 (2744)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm) 0 (296)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm) 0 (80)
    DpShMCreate: sizeof(vmc_adm) 0 (2160)
    DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
    DpShMCreate: sizeof(gw_adm) 48
    DpShMCreate: sizeof(j2ee_adm) 3952
    DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000DDE0050, size: 7174832)
    DpShMCreate: allocated sys_adm at 000000000DDE0060
    DpShMCreate: allocated wp_adm_list at 000000000DDE30B0
    DpShMCreate: allocated wp_adm at 000000000DDE32A0
    DpShMCreate: allocated tm_adm_list at 000000000DDEDA20
    DpShMCreate: allocated tm_adm at 000000000DDEDA70
    DpShMCreate: allocated wp_ca_adm at 000000000E330980
    DpShMCreate: allocated appc_ca_adm at 000000000E340390
    DpShMCreate: allocated comm_adm at 000000000E34FDA0
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 000000000E4A1C40
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated gw_adm at 000000000E4A1CF0
    DpShMCreate: allocated j2ee_adm at 000000000E4A1D30
    DpShMCreate: allocated ca_info at 000000000E4A2CB0
    DpShMCreate: allocated wall_adm at 000000000E4A2D40
    DpCommAttachTable: attached comm table (header=000000000E34FDA0/ft=000000000E34FDB0)
    DpSysAdmIntInit: initialize sys_adm
    rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
    dia token check not active (10 token)
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
    rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> EsILock: use spinlock for locking
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    <ES> Info: em/initial_size_MB( 16383MB) not multiple of em/blocksize_KB( 4096KB)
    <ES> Info: em/initial_size_MB rounded up to 16384MB
    Using implementation view
    <EsNT> Using memory model view.
    <EsNT> Memory Reset disabled as NT default
    <ES> 4095 blocks reserved for free list.
    ES initialized.
    mm.dump: set maximum dump mem to 192 MB
    mm.dump: set global maximum dump mem to 192 MB
    EsRegisterEmCheck: Register EmGetEsHandles at 000000013FC48640
    DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
    MPI: dynamic quotas disabled.
    MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 5824
      argv[0] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=65000
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=VSM
      argv[7] = -DSAPMYNAME=VKCSOL_VSM_00
      argv[8] = -DSAPPROFILE=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 4.0.1 4.0.1 5.1) [dpxxdisp.c   1702]
    ***LOG Q0K=> DpMsAttach, mscon ( VKCSOL) [dpxxdisp.c   12707]
    MBUF state LOADING
    DpStartStopMsg: send start message (myname is >VKCSOL_VSM_00                           <)
    DpStartStopMsg: start msg sent
    CCMS: Initialized monitoring segment of size 60000000.
    CCMS: Initialized CCMS Headers in the shared monitoring segment.
    CCMS: Checking Downtime Configuration of Monitoring Segment.
    CCMS: AlMsUpload called by wp 1024.
    Tue Apr 01 19:02:10 2014
    01.04.2014 13:32:10.628 PID=5448, TID=5744 SapTimer info. QPC/Windows time mismatch. System suspended, busy, missing ticks. Mismatch QpcTime-WindowsTime:  -168 millisec (max +0). Slept 1000 millisec, Qpc elapsed: +1000 millisec, WindowsUtc elapsed +1168 millisec. SapTime-WindowsUtcTime=-1 seconds. TotalTimeCorrection=+0 millisec, QpcTime-WindowsUtcTime=-1028 millisec (*).
    Tue Apr 01 19:02:11 2014
    CCMS: AlMsUpload successful for D:\usr\sap\VSM\DVEBMGS00\log\ALMTTREE.DAT (2189 MTEs).
    Tue Apr 01 19:02:13 2014
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpJ2eeLogin: j2ee state = CONNECTED
    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 %)
    Tue Apr 01 19:02:21 2014
    DpModState: change server state from STARTING to ACTIVE
    Tue Apr 01 19:02:23 2014
    ***LOG Q0I=> NiIRead: P=127.0.0.1:61107; L=127.0.0.1:65000: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5086]
    *** ERROR => NiIRead: SiRecv failed for hdl 33/sock 1008
        (SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:61107; L=127.0.0.1:65000) [nixxi.cpp    5086]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5824)
    *** ERROR => DpProcKill: kill failed [dpntdisp.c   397]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Regards
    Jose H.

    Hi Ashutosh,
    Thanks for your immediate reply. Please find the log below.
    trc file: "dev_server0", trc level: 1, release: "721"
    node name   : ID3506750
    pid         : 8068
    system name : VSM
    system nr.  : 00
    started at  : Sat Mar 29 13:41:08 2014
    arguments  :
       arg[00] : D:\usr\sap\VSM\DVEBMGS00\exe\jlaunch.exe
       arg[01] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
       arg[02] : -DSAPINFO=VSM_00_server
       arg[03] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
       arg[04] : -DSAPSTART=1
    Used property files
    -> files [00] : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3506700  : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3506750  : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3506700            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID3506750            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : VKCSOL
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    [Thr 19300] Sat Mar 29 13:41:08 2014
    [Thr 19300] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 19300] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 19300] JLaunchInitSignalHandling: signal handling is disabled
    [Thr 4928] WaitSyncSemThread: Thread 4928 started as semaphore monitor thread.
    [Thr 23444] JLaunchRequestFunc: Thread 23444 started as listener thread for np messages.
    [Thr 19300] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    [Thr 19300] MPI: dynamic quotas disabled.
    [Thr 19300] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    [Thr 19300] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
    [Thr 19300] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
    [Thr 19300] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
    [Thr 19300] CCMS: CCMS Monitoring Initialization finished, rc=0.
    [Thr 19300] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048m [jstartxx.c   2800]
    [Thr 19300] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID3506750]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4
    -> java parameters    : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0 -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 4.1.024 1.6-b04
    -> java vm vendor     : SAP Java Server VM (SAP AG)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> stack size         : 2M
    -> root path          : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120 sec.
    [Thr 19300] JLaunchISetDebugMode: set debug mode [no]
    [Thr 9092] JLaunchIStartFunc: Thread 9092 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 2097152 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -XX:MaxNewSize=600M
    -> arg[  4]: -XX:NewSize=600M
    -> arg[  5]: -XX:MaxPermSize=512M
    -> arg[  6]: -XX:PermSize=512M
    -> arg[  7]: -XX:+UseConcMarkSweepGC
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -XX:TargetSurvivorRatio=90
    -> arg[ 10]: -XX:SurvivorRatio=4
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -verbose:gc
    -> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
    -> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
    -> arg[ 17]: -Djco.jarm=1
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Djava.security.policy=./java.policy
    -> arg[ 20]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 21]: -Dsun.io.useCanonCaches=false
    -> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
    -> arg[ 27]: -XX:+JavaMonitorsInStackTrace
    -> arg[ 28]: -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar
    -> arg[ 29]: -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0
    -> arg[ 30]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile
    -> arg[ 31]: -Dstartup.mode=SAFE
    -> arg[ 32]: -Dstartup.action=UPGRADE
    -> arg[ 33]: -Dsys.global.dir=D:\usr\sap\VSM\SYS\global
    -> arg[ 34]: -Dapplication.home=D:\usr\sap\VSM\DVEBMGS00\exe
    -> arg[ 35]: -Djava.class.path=D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 36]: -Djava.library.path=D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\VSM\DVEBMGS00\exe;D:\usr\sap\VSM\SYS\exe\uc\NTAMD64
    -> arg[ 37]: -Dmemory.manager=2048M
    -> arg[ 38]: -Xmx2048M
    -> arg[ 39]: -Xms2048M
    -> arg[ 40]: -Xss2M
    -> arg[ 41]: -DLoadBalanceRestricted=no
    -> arg[ 42]: -Djstartup.mode=JCONTROL
    -> arg[ 43]: -Djstartup.ownProcessId=8068
    -> arg[ 44]: -Djstartup.ownHardwareId=I0649086862
    -> arg[ 45]: -Djstartup.whoami=server
    -> arg[ 46]: -Djstartup.debuggable=no
    -> arg[ 47]: -Xjvmx
    -> arg[ 48]: -XsapSystem=00
    -> arg[ 49]: -XmonGcCallback
    -> arg[ 50]: -DSAPINFO=VSM_00_server
    -> arg[ 51]: -DSAPSTART=1
    -> arg[ 52]: -DSAPSTARTUP=1
    -> arg[ 53]: -DSAPSYSTEM=00
    -> arg[ 54]: -DSAPSYSTEMNAME=VSM
    -> arg[ 55]: -DSAPMYNAME=VKCSOL_VSM_00
    -> arg[ 56]: -DSAPDBHOST=VKCSOL
    -> arg[ 57]: -Dj2ee.dbhost=VKCSOL
    (CompilerOracle read from file D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)
    [Thr 9092] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 20084] Sat Mar 29 13:41:10 2014
    [Thr 20084] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
    2.781: [GC 2.781: [ParNew: 409600K->2306K(512000K), 0.0126041 secs] 409600K->2306K(1994752K), 0.0127881 secs] [Times: user=0.05 sys=0.00, real=0.01 secs]
    [Thr 20084] Sat Mar 29 13:41:11 2014
    [Thr 20084] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 20084] JLaunchISetClusterId: set cluster id 3506750
    [Thr 20084] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 20084] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    Sat Mar 29 13:41:23 2014
    15.071: [GC 15.071: [ParNew: 411906K->16315K(512000K), 0.0306641 secs] 411906K->16315K(1994752K), 0.0309011 secs] [Times: user=0.13 sys=0.00, real=0.03 secs]
    Sat Mar 29 13:41:32 2014
    24.118: [GC 24.118: [ParNew: 425915K->29114K(512000K), 0.0363407 secs] 425915K->29114K(1994752K), 0.0365634 secs] [Times: user=0.11 sys=0.02, real=0.04 secs]
    [Thr 18736] Sat Mar 29 13:41:38 2014
    [Thr 18736] JHVM_RegisterNatives: com.sap.mona.api.JMonAPI
    [Thr 18736] CCMS: openMonitoringSegment(): inside static JMON Lib: already connected.
    [Thr 17644] JHVM_RegisterNatives: com.sap.mw.rfc.driver.CpicDriver
    [Thr 19340] JHVM_RegisterNatives: com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 7816] Sat Mar 29 13:41:39 2014
    [Thr 7816] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7816] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 25/sock 7884
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17936] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 7888
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    31.816: [GC 31.816: [ParNew[Thr 21936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 21936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 7856
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 2800] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 2800] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 9/sock 7860
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    : 438714K->67978K(512000K), 0.0626636 secs] 438714K->67978K(1994752K), 0.0628963 secs] [Times: user=0.11 sys=0.08, real=0.06 secs]
    [Thr 7276] Sat Mar 29 13:41:40 2014
    [Thr 7276] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7988
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 24572] Sat Mar 29 13:41:42 2014
    [Thr 24572] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24572] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 8132
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 5092] Sat Mar 29 13:41:43 2014
    [Thr 5092] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5092] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 8088
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 20084] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 24276] Sat Mar 29 13:41:44 2014
    [Thr 24276] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 8480
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 1316] Sat Mar 29 13:41:45 2014
    [Thr 1316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 1316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 9292
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 13068] Sat Mar 29 13:41:46 2014
    [Thr 13068] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 13068] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19652] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
    [Thr 17680] Sat Mar 29 13:41:47 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 23760] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 23760] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 10/sock 5976
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:41:48 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:41:49 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:41:50 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6272
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 5348] Sat Mar 29 13:41:51 2014
    [Thr 5348] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5348] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6336
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17548] Sat Mar 29 13:41:52 2014
    [Thr 17548] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17548] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6548
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 4216] Sat Mar 29 13:41:53 2014
    [Thr 4216] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 4216] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6424
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 23788] Sat Mar 29 13:41:54 2014
    [Thr 23788] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 23788] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6844
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6100] Sat Mar 29 13:41:55 2014
    [Thr 6100] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6100] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7448
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6828] Sat Mar 29 13:41:56 2014
    [Thr 6828] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6828] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6216
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 644] Sat Mar 29 13:41:57 2014
    [Thr 644] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 644] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 5992
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7376] Sat Mar 29 13:41:58 2014
    [Thr 7376] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7376] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6136
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24096] Sat Mar 29 13:41:59 2014
    [Thr 24096] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24096] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6004
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24460] Sat Mar 29 13:42:00 2014
    [Thr 24460] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24460] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6276
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 13452] Sat Mar 29 13:42:01 2014
    [Thr 13452] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 13452] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7328
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17884] Sat Mar 29 13:42:03 2014
    [Thr 17884] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17884] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 7372
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6616] Sat Mar 29 13:42:04 2014
    [Thr 6616] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6616] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7200
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 3136] Sat Mar 29 13:42:05 2014
    [Thr 3136] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 3136] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6344
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 8284] Sat Mar 29 13:42:06 2014
    [Thr 8284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 8284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7380
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19240] Sat Mar 29 13:42:07 2014
    [Thr 19240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6940
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 21316] Sat Mar 29 13:42:08 2014
    [Thr 21316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 21316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 5988
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 22436] Sat Mar 29 13:42:09 2014
    [Thr 22436] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 22436] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 7368
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 20936] Sat Mar 29 13:42:10 2014
    [Thr 20936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 20936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7528
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 18784] Sat Mar 29 13:42:11 2014
    [Thr 18784] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 18784] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 4460
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 21320] Sat Mar 29 13:42:12 2014
    [Thr 21320] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 21320] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6148
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 19632] Sat Mar 29 13:42:13 2014
    [Thr 19632] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19632] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 5948
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 8684] Sat Mar 29 13:42:14 2014
    [Thr 8684] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 8684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6012
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 7468] Sat Mar 29 13:42:15 2014
    [Thr 7468] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7468] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6032
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 5588] Sat Mar 29 13:42:16 2014
    [Thr 5588] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5588] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 1032
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 2036] Sat Mar 29 13:42:17 2014
    [Thr 2036] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 2036] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6052
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 6692] Sat Mar 29 13:42:18 2014
    [Thr 6692] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6692] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6188
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 5184] Sat Mar 29 13:42:19 2014
    [Thr 5184] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5184] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6192
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 5604] Sat Mar 29 13:42:20 2014
    [Thr 5604] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5604] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6220
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 15996] Sat Mar 29 13:42:21 2014
    [Thr 15996] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 15996] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:22 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:23 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:24 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:26 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6064
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19856] Sat Mar 29 13:42:27 2014
    [Thr 19856] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19856] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6184
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24128] Sat Mar 29 13:42:28 2014
    [Thr 24128] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24128] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6248
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 13684] Sat Mar 29 13:42:29 2014
    [Thr 13684] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 13684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6260
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7384] Sat Mar 29 13:42:30 2014
    [Thr 7384] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7384] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6264
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7432] Sat Mar 29 13:42:31 2014
    [Thr 7432] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7432] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6292
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6700] Sat Mar 29 13:42:32 2014
    [Thr 6700] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6700] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6304
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7272] Sat Mar 29 13:42:33 2014
    [Thr 7272] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7272] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6340
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19864] Sat Mar 29 13:42:34 2014
    [Thr 19864] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19864] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6392
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 5608] Sat Mar 29 13:42:35 2014
    [Thr 5608] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5608] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6404
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7160] Sat Mar 29 13:42:36 2014
    [Thr 7160] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7160] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6416
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 14536] Sat Mar 29 13:42:37 2014
    [Thr 14536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 14536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7340
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24404] Sat Mar 29 13:42:38 2014
    [Thr 24404] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24404] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6232
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 22756] Sat Mar 29 13:42:39 2014
    [Thr 22756] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 22756] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6076
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6284] Sat Mar 29 13:42:40 2014
    [Thr 6284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 7472
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 12696] Sat Mar 29 13:42:41 2014
    [Thr 12696] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 12696] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6380
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24180] Sat Mar 29 13:42:42 2014
    [Thr 24180] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24180] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6420
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 23444] Sat Mar 29 13:42:43 2014
    [Thr 23444] JLaunchRequestFunc: receive command:17, argument:0 from pid:20668
    [Thr 23444] JLaunchIShutdownInvoke: set shutdown interval (stop:1396080763/end:1396080883/TO:120)
    [Thr 23444] JLaunchProcessCommand: Invoke VM Shutdown
    [Thr 23444] JHVM_FrameworkShutdownDirect: invoke direct shutdown
    [Thr 8780] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
    [Thr 8780] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
    [Thr 5188] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.sadm.ShmCache
    [Thr 7240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6376
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6536] Sat Mar 29 13:42:44 2014
    [Thr 6536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6852
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 18244] Sat Mar 29 13:42:46 2014
    [Thr 18244] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 18244] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:47 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:48 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 22796] CCMS: closeMonitoringSegment(): inside static JMON Lib: nothing to do.
    [Thr 8780] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
    [Thr 17680] Sat Mar 29 13:42:49 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    Heap
    par new generation   reserved 614400K, committed 614400K, used 313963K [0x000000007fff0000, 0x00000000a57f0000, 0x00000000a57f0000)
      eden space 409600K,  60% used [0x000000007fff0000, 0x000000008f028658, 0x0000000098ff0000)
      from space 102400K,  66% used [0x0000000098ff0000, 0x000000009d2528e8, 0x000000009f3f0000)
      to   space 102400K,   0% used [0x000000009f3f0000, 0x000000009f3f0000, 0x00000000a57f0000)
    concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a57f0000, 0x00000000ffff0000, 0x00000000ffff0000)
    concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 70349K [0x00000000ffff0000, 0x000000011fff0000, 0x000000011fff0000)
    [Thr 18896] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 18896] JLaunchCloseProgram: good bye (exitcode = 0)
    Regards
    Jose H.

  • Upgrade Solution Manager 7.1 add-on ST-ICO

    Hi everybody
    I'm upgrading from Solman 7.01 to 7.1.
    In the prepartion I'm stucked at the phase ADD-ON selection.
    The following stack is the target:
    SAP_BASIS 702 0009 SAPKB70209 SAP Basis Component
    SAP_ABA 702 0009 SAPKA70209 Cross-Application Component
    PI_BASIS 702 0009 SAPK-70209INPIBASIS Basis Plug-In
    ST-PI 2008_1_700 0005 SAPKITLRD5 SAP Solution Tools Plug-In
    SAP_BS_FND 702 0007 SAPK-70207INSAPBSFND SAP Business Suite Foundation
    SAP_BW 702 0009 SAPKW70209 SAP Business Warehouse
    SAP_AP 700 0026 SAPKNA7026                                                                               
    WEBCUIF 701 0006 SAPK-70106INWEBCUIF SAP Web UI Framework
    BBPCRM 701 0006 SAPKU70106 BBPCRM
    BI_CONT 706 0002 SAPK-70602INBICONT Business Intelligence Content
    CPRXRPM 500_702 0005 SAPK-50005INCPRXRPM SAP Portfolio and Project Management 5.0 (ABAP)
    ST 710 0004 SAPKITL704 SAP Solution Manager Tool
    ST-BCO 710 0002 SAPK-71002INSTBCO ST-BCO 710: Add-On Installation
    SOCO 101 0001 SAPK-10101INSOCO SAP Solution Composer Server
    ST-A/PI 01N_700SOL 0001 SAPKITAS1H Application Servicetools for SolMan 7.0-
    ST-ICO 150_700 0031 SAPK-1507VINSTPL
    ST-SER 701_2010_1 0010 SAPKITLOSA SAP Solution Manager Service Tools
    The phase is suggesting correctly to keep the version for the component
    ST-ICO 150_700
    ST-PI
    ST-SER 701_2010_1
    after I continue I get the message that the KEEP YOURS decision is no longer valid and I need to decide whether I upgrade with SAINT or ADD-ON CD. Neither of those is working.
    The XML file I used is the SPS04_upgrade_stack.xml from the Patch CD
    Any idea`?
    Thanks for your help
    Murat

    Hi,
    For info, we have the same problem.
    In our case, Solman run with a temporary key (hw change before upgrade).
    After install of new license key and restart the "Configuration" phase, we can go on with "Keep version"
    Best regards,
    TH

  • Export DVD for product CRM/SOLMAN Upgrade Solution Manager 7.1

    Hello Experts,
    It is my first time doing an upgrade and I have a problem, the SOLMANUP tool gives me: "Enter at least the mount point containing "Export DVD for product CRM/SOLMAN"", I downloaded from SMP the 12 parts of the SAP Solution M. 7.1 Upgr.Export (51039400), I got now 1 .exe file and 11 .RAR files and when I put the path, the SOLMANUP doesnt recognize as a valid mount point, any advices?
    Regards,
    Paul

    Hi Paul,
    Have you already checked note 1577909?
    Note: 1462137 - Add. info. about Upgrading to SAP Solution Manager 7.1
    Please enter mount points for the DVDs required for the upgrade.
    Enter at least the mount point containing "Export DVD for product
    CRM/SOLMAN"
    Please check if the requested Data Carrier is mounted on any of the mount points:
           Path                                     Description
          +                                        +             +
         1 /usr/sap/SMP/SOLMANUP/51042010
         2 /usr/sap/SMP/SOLMANUP/51040039
         3 /usr/sap/SMP/SOLMANUP/51040119
         4 /usr/sap/SMP/SOLMANUP/51040868_2/DVD_OS_
         5 /usr/sap/SMP/SOLMANUP/upgrade_export_dvd
         6 /usr/sap/SMP/SOLMANUP/upgrade_export_dvd
    You will have to download all the archives and then extract them. Please go through the
    SAP Note 886535 for these kind of archives. Once everything is archived
    and extracted, provide the path.
    Thanks
    Regards
    Vikram

  • Upgrading Solution Manager SP13

    Hi All,
    We have decided to upgrade the Solution Manager system 7.0 SP13 to SP17. The issue we are having is one of the sapdata2 mount is 96% full.
    But other sapdata mounts (sapdata1, sapdata3, sapdata4) are having sufficient space of around 20GB individually.
    If i start the SP upgrade at this stage will space issue in sapdata2 mount, create some issue ?
    We cant add more space for sapdata2 mount at this stage.
    Kindly advice
    OS is Solaris
    Database : Oracle 10.2
    Regards
    Naveen

    You can do this by 2 way.
    1. Loging to OS level & check.
    2.Goto tcode DB02>Current Sizes>Data files.
    This will show you all datafiles. Here check which the tablespaces which are inside sapdata2 folder
    Here check which are the tablespaces which are in sapdata2 & as said above analyze top tables & indexes.
    Hope this helps.
    Thanks,
    Sushil

  • Solution Manager 3.2 Upgrade problem.

    Hello all.
    I am trying to upgrade Solution Manager 3.2 to  version 4, my OS - Solaris 9 on SPARC, RDBMS - Oracle 10.2.0.2
    On phase TR_QUEUE2HEAP of PREPARE module a get an error:
    ERROR: Unable to expand queue.
           Return Code = -1, Reason = "Internal error: Attribute set 01 is missing for OCS package is missing for OCS p"
    Check log file 'SPDA_EXPAND_QUEUE.LOG' for details.
    SEVERE ERROR: (R3uppat.c:22890) RC = RC_ERROR
    continue
    cancel
    After I select "Contunue", a get a  "SEVERE ERROR(S) OCCURRED IN TR_QUEUE2HEAP !!!"
    I cant find file SPDA_EXPAND_QUEUE.LOG.
    This is log  from TRQUEUE2HEAP.LOG:
    1 ETQ201XEntering upgrade-phase "TR_QUEUE2HEAP" ("20070222162516")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '02', GwService = 'sapgw02'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPSM4
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
    4 ETQ399 Parameter "spam_queue_with_syncmarks" has been reset from SAPup parameter file
    4 ETQ399 (trc) Syncmark handling done by SPAM (gpv_spam_queue_with_syncmarks=TRUE)
    4 ETQ399 (trc) R3upQueueExpand: Expand mode = REQUEST
    4 ETQ230 Starting RFC Login to: System = "SM4", GwHost = "r3devsrv01", GwService = "sapgw02"
    4 ETQ359 RFC Login to: System="SM4", Nr="02", GwHost="r3devsrv01", GwService="sapgw02"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SPDA_EXPAND_QUEUE" by RFC
    4 ETQ010 Date & Time: 20070222162517
    I cant find any notes or messages regarding this error.
    Please help me !

    Dolores, may be You can help me once more ?
    Next problem : phase Conflict Check,
    Conflicts found.
           Check log file 'SPDA_CONFLCHK.LOG' for details.
           To resolve the conflicts you must repeat the module and change your Add-on or
           Support Package selection or add Conflict Resolution Patches (CRT).
    From SPDA_CONFLCHK.LOG:
    2EETN388 The following CRTs of the Add-On "ST" rel."400" must be included as well:
    3WETN389 CRT &4"SAPKITL412" for Support Package &1"SAPKB70006" of the Software Component &2"SAP_BASIS" rel.&3"700"
    3WETN389 CRT &4"SAPKITL414" for Support Package &1"SAPKB70007" of the Software Component &2"SAP_BASIS" rel.&3"700"
    How I can add those CRT 's ?
    I have unpacked them to EPS/in, but it didnt help me.

  • Is Solution Manager required for ECC 6.0 upgrade?

    We will upgrade our system from 4.7 to ECC 6.0.  Is Solution Manager a required tool in ECC 6.0?  My understanding is Solution Manager has to be run on a different server, ie.  we will have to buy a new server.   We have a small SAP implementation with only FI & CO modules, so we are trying to cut our costs if we could.  Can anybody share their experience?  Thanks for any input.

    In an Upgrade , Solution Manager is required for Upgrade Keys and downloading the support packs . Now a days to download the support packs you have to approve it in Solution Manager otherwise it won't show up in your download basket.
    May be SAP can provide you the keys & approve the SPs ( they used to do that before ) , in that case it isn't required.
    You can also manage your upgrade project in Solman . Sooner or later you need to install solution manager. it's a nice system.Many good features like central monitoring, early watch alert etc etc ...
    Thanks
    Prince Jose

  • Solution Manager Upgrade Issue for "Business Process Monitoring"

    Hello,
    We had upgrade Solution Manager 7.1 SP08 to SP11.
    Earlier our BP Monitories were working fine which are not working now, also we are not able to use function “Load Monitor”.

    We are facing below major issues
    1. No system in Logical Component
    2. No RFC destination found
    3. Unable to load Monitors
    Also the BPMon configuration is not working post upgrade
    Kindly help us to resolve these issues.

  • Solution Manager 3.1 upgrade to 3.2

    Hi,
    I have to upgrade Solution Manager to 3.2 SP Stack 15 or  7.0 SP Stack 09.
    Now I have Solution Manager 3.1, in detail: SAPKB62052 and SAPKU31010
    How can I do it?
    My problem is:
    I have to upragde Solution Manager because I have on my notebook Microsoft Internet Explorer 7.0 so SAP GUI doesn't display F1, F4 and so on.
    I know it's the html problem, I want to use note 950975 but from last year due to this note I can do it only by Solution Manager
    u2022     SAP Solution Manager 7.0 SP Stack 09
    u2022     SAP Solution Manager 3.2 SP Stack 15 (with limited functionality)
    So the first I have to upgrade SAP Solution Manager than implement the note.
    Regards,
    Betta Woroch

    Hi,
    I use 620 GUI because it was installed in 2005 when SAP was started in my company.
    I use F1 when the focus is in field e.g. in transaction AS01 field ANLA.ANLN1
    The same problem occurs in SBWP transaction, there the message is not display content.
    In SR13 transaction is only one item: PlainHtmlHttp:
    Variante: IWBHELP1
    Platform: WIN32
    Area: IWBHELP
    Server names: HELP.SAP.COM
    Path: saphelp_erp2004/helpdata
    Language: EN
    Default: Yes
    In my company is SAP Fixed Assets:
    SAP_BASIS SAPKB62048
    SAP_ABA     SAPKA62048
    SAP_APPL SAPKH47022
    This problem occurs after upgraded Microsoft Internet Explorer to 7.0 in my notebook. There is Win XP Professional SP2
    Regards
    Betta Woroch

  • Upgrade to Solution Manager 7.1 missing Master upgrade DVD

    Hi,
    I'm upgrading Solution Manager 7.0 EHP1 to Solution Manager 7.1 .  I've got the following error;
    Please enter mount points for the DVDs required for the upgrade.
    Enter at least the mount point containing "Upgrade master DVD"
    I Can't find this "Upgrade master DVD" on market place. I've opend an OSS message but no answer yet. Anyone had that problem?
    Thanks!

    I had the same issue. It turns out that what it was really asking for was a SAP Kernel DVD in the correct format.
    When I downloaded the SAP Kernel DVD from the Market Place, the Zip file included a directory for my platform at the first level on the DVD, and then in that directory it contains the LABEL.ASC file.
    You need to ensure that when you stage the Kernel DVD, the LABEL.ASC files etc should be in the Top Level directory, or it won't be recognised as a DVD, and you'll get the erroneous message about needing an "Upgrade Export DVD" (which does not exist for Solman 7.1).
    Hope this helps!

  • 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

  • Migration / Upgrade SAP Solution Manager

    Hi
    We are using Solution Manager 3.1, W2000 Server, Intel, Oracle.
    Now it is necessery to Upgrade Solution Manager 4.0, to new Hardware with Windows x64, AMD, Oracle.
    It was very helpfull for me, if somebody could explain me the steps to do that.
    Thank you very much
    Selim

    first of all it is obsolete (because based on 8.1.7) and did not cover the central needs of the request ( Oracle9 to Oracle10 during a 32Bit/64 Bit migration)
    second it is based on Unix, will not help Windows users very much.
    third it is not supported, the only supported resources are documented via http://service.sap.com/instguides look for your version, homogenious system copy guide.
    fourth: there are some mistakes in it: you need a new saplicense, at least on windows.
    fith: it does not document at all what additional manual steps are necessary if the system is a newer system with a lot of functional links into other systems.
    Peter

  • Error While Applying patch ST-PI 2008_1_700 to solution Manager

    Dear Techies,
    Thanks alot for your fast response.
    We are trying to upgrade Solution Manager Stack from
    ST-PI 2005_1_700  to ST-PI 2008_1_700 ,
    While applying patch it was suddenly stopped with an error
    "Manual modification adjustment is neccessary"
    While I tried to adjust it.
    In Note correction tree. This the message with " green tick"
    "0001293326 EWA: Newest ST-PI Is Rated 'Outdated'; Wrong RTCCTOOL Date"
    and is not allowing me to proceed further.
    How to go about.
    Thanks in advance.
    regards,
    Kiran

    Hi Varun,
    Thanks for your reply.
    As suggested by you, I executed "RTCCTOOL" programme.
    It Has given that 4 notes were in red status.
    They are.
            1. [Note 69455  ]      Addon upgrade ST-A/PI 01N_700SOL
            Description     "Servicetools for Applications Plug-In" for Solution Manager 4.0-7.10  (Addon delta upgrade package)
            Implementation  From http://service.sap.com/supporttools->ST-A/PI download the addon upgrade package ST-A/PI           
                                     01N_700SOL. Upload to tx SAINT (just as you would  do for an installation) and install as per note 69455
                                     Then restart report RTCCTOOL and choose 'List->Refresh from SAPNet'.
            4. [Note 539977  ]     ST-PI Support Packages
    Description     Addon supportpackage level 4 for ST-PI 2008_1_700 for 7.00 [patches up to level 4 for Basis tools for  services]
    Implementation  Open http://service.sap.com/supporttools-> ST-PI 2008_1_700 ->Supportpk. Add patch SAPKITLRD4 (and predecessors if not yet implemented) to download basket. Release basket via  Maintenance optimizer. Upload from frontend int  transaction SPAM, define a queue and import the queue.
            6. [Note 539977  ]     Note 1312413 for ST-PI
            Description     Maintenance Certificates for SPAM/SAINT may get periodically overwritten by invalid ones on ST-PI  
                                   2008_1_7* SP 00. Prevent this proactively,even if you do not yet use the automatic maint. certificate 
                                  distribution.
             Implementation  We recommend that you implement the Supportpackage SP1 for ST-PI 2008_1* to solve the error. Only if 
                                      not possible implement note 1312413   with not version >=12 using SNOTE. Regarding automatic maint.
                                      certificate distribution see http://service.sap.com/maintenancecertificate.
            9. [Note 1293326  ]    EWA serviceprep correct. in sequence.
    Description     Wrong alerts appear in EWAlert Service preparation section (Newest ST-PI Rated Outdated / Wrong
                          RTCCTOOL Date) if Solution Manager ST-SER < 701_2008_2 SP1 and satellites on ST-PI 2008_1* / ST-A/PI 01L*.
    Implementation  Implement the coding correction of this note 1293326   with SNOTE to solve the wrong service preparation alerts. Else if you do not mind the wrong alerts simply set this recommendation manually to green after reading.
    These are in green status
    Successfully implemented addons/ transports/ notes
            2. [Note 69455  ]    Proc. after addon impl.
            3. [Note 539977  ]   Addon ST-PI 2008_1_700
            5. [Note 539977  ]   Note 1300023 for ST-PI
            7. [Note 539977  ]   Note 1293657 for ST-PI
            8. [Note 12103  ]    Collectors and TCOLL.
    While I tried to implement the note "69455" system is giving the message that there are no valid corrections and is coming out of the process
    "Note 0000069455 cannot be implemented since no valid correction is available."
    And is same for other notes also.
    How to go ahead.
    Thanks in advance.
    Regards,
    Kiran

  • How to generate xml-file for SAP Fiori (UI add-on) with Solution Manager 7.0.1?

    Hello Guru,
    could you please help with my issue with Fiori Installation.
    We want to install SAP Fiori Front-End (GW+UI) on the Sandbox system with SAP Netweaver 7.3.1. (SP14)
    Gateway component (SAP GW CORE 200 SP10) was installed without any problems.
    But I need to install UI-add-on (NW UI Extensions v1.0) and when I try to install it via SAINT, transaction said me that I need to generate xml-file for it (as in General notes for UI add-on mentioned).
    But I have Solution Manager 7.0.1 and in MOPZ for this version I do not have option  "install Add-on" as it written in Guide for ui add-on installation.
    Could you please help me with advice how to generate xml-file for UI add-on installation on SolMan v.7.0.1?
    If where is no way, but only to upgrade Solution Manager, maybe somebody could give me xml-file for your system (for NW 731) and I will change it to my needs, I will be very grateful!
    Thanks in advance for any help!!!
    Bets regards,
    Natalia.

    Hello Guru,
    could you please help with my issue with Fiori Installation.
    We want to install SAP Fiori Front-End (GW+UI) on the Sandbox system with SAP Netweaver 7.3.1. (SP14)
    Gateway component (SAP GW CORE 200 SP10) was installed without any problems.
    But I need to install UI-add-on (NW UI Extensions v1.0) and when I try to install it via SAINT, transaction said me that I need to generate xml-file for it (as in General notes for UI add-on mentioned).
    But I have Solution Manager 7.0.1 and in MOPZ for this version I do not have option  "install Add-on" as it written in Guide for ui add-on installation.
    Could you please help me with advice how to generate xml-file for UI add-on installation on SolMan v.7.0.1?
    If where is no way, but only to upgrade Solution Manager, maybe somebody could give me xml-file for your system (for NW 731) and I will change it to my needs, I will be very grateful!
    Thanks in advance for any help!!!
    Bets regards,
    Natalia.

  • Activate BI reports for PPM in solution manager 7.1

    Dear experts
    Recently we upgrade solution manager to 7.1 SP8. We also run project and portfolio management in the same system and using internal BI.
    After I activate BI reports I want to transfer the date from PPM to BI and as I said they are in the same system.
    which jobs do I have to run ? ( I already run  E2E_EFWK_HOUSEKEEPER and E2E_EFWK_RESOURCE_MGR jobs)
    Thanks
    Muly Zohar

    Dear experts
    Recently we upgrade solution manager to 7.1 SP8. We also run project and portfolio management in the same system and using internal BI.
    After I activate BI reports I want to transfer the date from PPM to BI and as I said they are in the same system.
    which jobs do I have to run ? ( I already run  E2E_EFWK_HOUSEKEEPER and E2E_EFWK_RESOURCE_MGR jobs)
    Thanks
    Muly Zohar

Maybe you are looking for

  • Not able to download or access account info

    Hi, For the past few days I have not been able to download songs from iTunes.  Furthermore, it seems that I cannot access my account information either, despite the fact that iTunes shows me as being logged in and displays my $$ balance.  When I sele

  • Spry Autosuggest widget

    Hi all I an trying to use the spry auto suggest widget and so far it works fine but I would like to be able to have the results div overlay my web page rather than push the contents down as I am new to all this I would appreciate any possible help or

  • Camera not working in Apple apps on ML 10.8.1

    PhotoBooth, FaceTime and QuickTime both say that there is no camera attached when I open them on my MBP mid 2010 Skype works just fine... Please sort this out Apple. /W

  • ITunes Doesn't Work...?

    I've downloaded and installed iTunes three times on my computer. Each time, my computer tells me that iTunes is a program that has been completely installed. However, when I click on it to bring it up OR connect my iPod to my computer, iTunes does no

  • Idvd 8 can't burn crashhh

    Can,t burn disk image or burn direct to DVD. He crash after learn theme he don't go to movie??? he crash after just 1 minutes??? before from 1 year never problem?? Solution please! Michel