JSPM - SDTServer issue

Hi,
I did a startup of JSPM, as I am preparing to start an update of the Java Support Packs. It seems when i run the 'go' script in UNIX it is waiting for an SDTServer on port 6240. I did a ps command with a grep on SDT and it seems there is nothing running. i also did a nestat and grep it for 6240 but again there is nothing listening on that port. i had a look in the lib directory under JSPM and it seems there are jar files relating to the SDT Server. Does anyone know how i can start this or does the script start this up and it takes a long time?
Thanks,
Mani

Hi
If another running instance of JSPM is using port 6240, use this instance or stop it.
If another application is using port 6240, in the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/param/jspm_config.txt file, change the value of the /dialog/SDTServerConnection/port property by specifying a port that is currently not in use and try to start JSPM.
Regards
Shridhar Gowda

Similar Messages

  • JSPM patching issue after system refresh

    We have recently done a System Refresh of Java-Addin box from a source system whic was on SP-13 on to a  target system which was on SP-14.  
    After the refresh we found the target system is now on SP13.   When I tried to apply SP-14, JSPM reports that the patch is already applied.  How do I go about ? Does this mean that SP-14 is already existing.  How to make the system recognise that the current patch is on SP-13. What needs to be done?
    Thanks in advance.
    Umamahesh

    This is not a bug in JSPM,  if the System Refresh is done through SAPINST you shouldn't have such issues. 
    I think that since some of the files in J2EE are not updated after the manual system refresh and JSPM must be pointing to the earlier Patch level.  
    Especially files under  ..../bootstrap/SAP AG are not updated
    In JSPM by default the forcemode is disabled so given the manual way to enable the option
    Hope this is clear
    Regards
    Shaji

  • JSPM ISSUE

    i have issue with when i upgrade Portal from SP18 to SP21. Please find the JSPM Logs as below..
    #1.#C0000A0B26780000000000676CF86CF800049C546871E050#1297786250322#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Jav
    a###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcd#
    #1.#C0000A0B26780000000000686CF86CF800049C546871E050#1297786250322#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Jav
    a###Connecting to SDM Server on host , port ...#2#GMU-EPDB#50018#
    #1.#C0000A0B26780000000000696CF86CF800049C546872CAB0#1297786250382#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Jav
    a###You can find additional information in SDM log file . If SDM has performed no action, this file does not exist.#1#/usr/sap/GDP/JC
    00/SDM/program/log/sdmcl20110215161050.log#
    #1.#C0000A0B267800000000006A6CF86CF800049C546872D668#1297786250385#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Jav
    a###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcdcontent#
    #1.#C0000A0B267800000000006B6CF86CF800049C546872DA50#1297786250386#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Jav
    a###Connecting to SDM Server on host , port ...#2#GMU-EPDB#50018#
    #1.#C0000A0B267800000000006C6CF86CF800049C54687372A8#1297786250425#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Jav
    a###You can find additional information in SDM log file . If SDM has performed no action, this file does not exist.#1#/usr/sap/GDP/JC
    00/SDM/program/log/sdmcl20110215161050.log#
    #1.#C0000A0B267800000000006D6CF86CF800049C5468737E60#1297786250428#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.SystemInitializer.retrieveSdmSubstVariables(SystemInitializer.java:1574)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jsp
    m.gui.SystemInitializer.retrieveSdmSubstVariables(SystemInitializer.java:1574)#Java###Retrieval of SDM substitution variables has finish
    ed.##
    #1.#C0000A0B267800000000006E6CF86CF800049C5468745538#1297786250483#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.deployment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:162)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.dep
    loyment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:162)#Java###File has been parsed and the relative deployment data mo
    del has been extracted.#1#/usr/sap/GDP/JC00/j2ee/JSPM/config/dodf.xml#
    #1.#C0000A0B267800000000006F6CF86CF800049C54687493B8#1297786250499#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.tools.ApplicationSnapshot.isApplicationSnapshotSupported(ApplicationSnapshot.java:320)#######Thread[main,5,main]##0#0#Info#1#com.s
    ap.sdt.jspm.tools.ApplicationSnapshot.isApplicationSnapshotSupported(ApplicationSnapshot.java:320)#Java###Component found on the sys
    tem. It supports restore of application settings after deployment.#2#sap.com/CORE-TOOLS 7.00.18.0#7.00.5#
    #1.#C0000A0B26780000000000706CF86CF800049C54687497A0#1297786250500#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:892)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm
    .gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:892)#Java###Application settings will be restored after deployme
    nt.##
    #1.#C0000A0B26780000000000716CF86CF800049C5468842800#1297786251520#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.cvers.CVersQuery#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.cvers.CVersQuery#Java###This system is not under NWDI cont
    rol.##
    #1.#C0000A0B26780000000000726CF86CF800049C546884DBB0#1297786251566#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.DialogController.execute(DialogController.java:531)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogControlle
    r.execute(DialogController.java:531)#Java###Login dialog has been processed.##
    #1.#C0000A0B26780000000000736CF86CF800049C546885D5B0#1297786251630#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:372)#######Thread[main,5,main]##0#0#Info#1#com
    .sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:372)#Java###Starting dialog...#1#S
    electPackageType#
    #1.#C0000A0B26780000000000896CF86CF800049C54691E9340#1297786261640#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:261)#######Thread[main,5,main]##0#0#In
    fo#1#com.sap.sdt.jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:261)#Java###You have c
    hosen for Inbox granulation.#1#Support Package Stack#
    #1.#C0000A0B267800000000008A6CF86CF800049C54691E9340#1297786261640#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:409)#######Thread[main,5,main]##0#0#Info#1#com
    .sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:409)#Java###Dialog : you have chose
    n Next.#1#SelectPackageType#
    #1.#C0000A0B267800000000008B6CF86CF800049C54691E9728#1297786261641#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:414)#######Thread[main,5,main]##0#0#Info#1#com
    .sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:414)#Java### dialog has been proces
    sed.#1#SelectPackageType#
    #1.#C0000A0B267800000000008C6CF86CF800049C54691E9B10#1297786261642#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.newsdu.SDUProvider.getSPStacksAllowedForDeployment(SDUProvider.java:700)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.ne
    wsdu.SDUProvider.getSPStacksAllowedForDeployment(SDUProvider.java:700)#Java###Getting all support package stacks allowed for deployment
    from inbox ...#1#/usr/sap/trans/EPS/in#
    #1.#C0000A0B267800000000008D6CF86CF800049C54691E9EF8#1297786261643#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt
    .jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log
    file .#1#/usr/sap/GDP/JC00/j2ee/JSPM/log/log_2011_02_15_16_10_14/SCAN_INBOX_01.LOG#
    #1.#C0000A0B267800000000199A6CF86CF800049C5469AEB5B0#1297786271086#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j700.usagetypeslibrary.MainInfo#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.usagetypeslibrary.MainInfo#Java###Loaded usage t
    ype data from data source .#1#jdbc/pool/GDP#
    #1.#C0000A0B26780000000019B96CF86CF800049C5469C34368#1297786272433#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:253)#######Thread[main,5,main]##0#0#Error#1#com.sap.s
    dt.jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:253)#Java###There are some ERROR messages in the ch
    ild log .#1#/usr/sap/GDP/JC00/j2ee/JSPM/log/log_2011_02_15_16_10_14/SCAN_INBOX_01.LOG#
    #1.#C0000A0B26780000000019BA6CF86CF800049C5469C34B38#1297786272435#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.Abstra
    ctPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
    #1.#C0000A0B26780000000019BB6CF86CF800049C5469C34F20#1297786272436#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j2ee.tools.sdmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:494)#######Thread[main,5,main]##0#0#Err
    or#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:494)#Java###java.util.z
    ip.ZipException: The file access permissions do not allow the specified action. /usr/sap/trans/EPS/in/dump/SDMKIT21_0-10003463.JAR##
    #1.#C0000A0B26780000000019BC6CF86CF800049C5469C34F20#1297786272436#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j2ee.tools.sdmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:489)#######Thread[main,5,main]##0#0#Err
    or#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:489)#Java###Could not e
    xtract SDM patch archive /usr/sap/trans/EPS/in/dump/SDMKIT21_0-10003463.JAR to read its version information.##
    #1.#C0000A0B26780000000019BD6CF86CF800049C5469C35308#1297786272437#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j2ee.tools.sdmdetection.DetectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:380)#######Thread[main,5,main]##0#0#Er
    ror#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:380)#Java###Cannot de
    tect if there are SDM archives in directory /usr/sap/trans/EPS/in.##
    #1.#C0000A0B26780000000019BE6CF86CF800049C5469C35308#1297786272437#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .j2ee.tools.newsdu.NewNonDeployableSDUProvider.listInbox(NewNonDeployableSDUProvider.java:255)#######Thread[main,5,main]##0#0#Error#1#co
    m.sap.sdt.j2ee.tools.newsdu.NewNonDeployableSDUProvider.listInbox(NewNonDeployableSDUProvider.java:255)#Java###Could not detect new kern
    el and SDM archives.##
    #1.#C0000A0B26780000000019BF6CF86CF800049C5469C35308#1297786272437#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.newsdu.SDUProvider.getSPStacksAllowedForDeployment(SDUProvider.java:757)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.n
    ewsdu.SDUProvider.getSPStacksAllowedForDeployment(SDUProvider.java:757)#Java###Error while analyzing the content of the Inbox directory.
    #1.#C0000A0B26780000000019C06CF86CF800049C5469C35308#1297786272437#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .jspm.gui.deployment.SpecifyQueueStep.prepareUI(SpecifyQueueStep.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.gui.d
    eployment.SpecifyQueueStep.prepareUI(SpecifyQueueStep.java:735)#Java###Cannot detect new components in Inbox directory.##
    #1.#C0000A0B26780000000019C16CF86CF800049C5469C35AD8#1297786272439#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractP
    haseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#JSPM/JSPMPhases/JSPM_MAIN#
    #1.#C0000A0B26780000000019C26CF86CF800049C5469C35AD8#1297786272439#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractP
    haseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2011/02/15 16:10:22#
    #1.#C0000A0B26780000000019C36CF86CF800049C5469C35AD8#1297786272439#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractP
    haseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2011/02/15 16:11:12#
    #1.#C0000A0B26780000000019C46CF86CF800049C5469C35AD8#1297786272439#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractP
    haseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:00:49.570#
    #1.#C0000A0B26780000000019C56CF86CF800049C5469C35AD8#1297786272439#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt
    .ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractP
    haseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#

    Please find SCAN_INBOX_01.LOG..
    lParser.parseSoftwareFeatureStackTag(SPXmlParser.java:752)#Java###APPLICATION-SYSTEM tag is missing in the stack definition file.##
    #1.#C0000A0B26780000000019976CF86CF800049C5469ACFC48#1297786270973#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.spxmlparser.SPXm
    lParser.parseSPXml(SPXmlParser.java:443)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml
    (SPXmlParser.java:443)#Java###Parsing of stack definition file has finished.#1#/usr/sap/trans/EPS/in/stack.xml#
    #1.#C0000A0B26780000000019986CF86CF800049C5469AD2358#1297786270983#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.spstackanalyzer.
    SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:177)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.spstackanalyze
    r.SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:177)#Java###Scan of the Inbox directory for stack definition files has finishe
    d.##
    #1.#C0000A0B26780000000019996CF86CF800049C5469AD2358#1297786270983#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.newsdu.filter.SP
    StackFilterImpl.getNewUsages(SPStackFilterImpl.java:419)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.filter.SPSt
    ackFilterImpl.getNewUsages(SPStackFilterImpl.java:419)#Java###Support package stack contains product and usage definitions.#1#sap.co
    m/SAP NETWEAVER#
    #1.#C0000A0B267800000000199B6CF86CF800049C5469AEF818#1297786271103#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.newsdu.filter.SP
    StackFilterImpl.accept(SPStackFilterImpl.java:354)#######Thread[main,5,main]##0#0#Warning#1#com.sap.sdt.j2ee.tools.newsdu.filter.SPStack
    FilterImpl.accept(SPStackFilterImpl.java:354)#Java###Support package stack with version () is rejected because it contains no
    applicable components.#3#sap.com/SAP NETWEAVER#7.0 (2004S)#/usr/sap/trans/EPS/in/stack.xml#
    #1.#C0000A0B267800000000199C6CF86CF800049C5469AEFC00#1297786271104#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:362)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.
    sdmdetection.DetectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:362)#Java###Scanning the Inbox directory for SDM c
    omponent archive files with name ...#1#sdmkit.jar#
    #1.#C0000A0B267800000000199D6CF86CF800049C5469AF03D0#1297786271106#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectSdmkitFiles(DetectSDMComponent.java:305)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection
    .DetectSDMComponent.detectSdmkitFiles(DetectSDMComponent.java:305)#Java###SDM archive found.#1#/usr/sap/trans/EPS/in/SDMKIT21_0-1000
    3463.JAR#
    #1.#C0000A0B267800000000199E6CF86CF800049C5469B08688#1297786271205#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectSdmkitFiles(DetectSDMComponent.java:305)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection
    .DetectSDMComponent.detectSdmkitFiles(DetectSDMComponent.java:305)#Java###SDM archive found.#1#/usr/sap/trans/EPS/in/dump/SDMKIT21_0
    -10003463.JAR#
    #1.#C0000A0B267800000000199F6CF86CF800049C5469B11AF8#1297786271243#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:368)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.
    sdmdetection.DetectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:368)#Java###Scan of the Inbox directory for SDM co
    mponent archive files has finished.#1#sdmkit.jar#
    #1.#C0000A0B26780000000019A06CF86CF800049C5469B11EE0#1297786271244#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:370)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.
    sdmdetection.DetectSDMComponent.detectComponentsFromDirectory(DetectSDMComponent.java:370)#Java###Analyzing the results of the scan of t
    he Inbox directory for SDM component archive files:##
    #1.#C0000A0B26780000000019A16CF86CF800049C5469B11EE0#1297786271244#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:442)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.s
    dmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:442)#Java###Detecting version of SDM component from
    archive file...#1#/usr/sap/trans/EPS/in/SDMKIT21_0-10003463.JAR#
    #1.#C0000A0B26780000000019A26CF86CF800049C5469B13268#1297786271249#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.logProcessInfo(OsProcessController.java:139)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logPro
    cessInfo(OsProcessController.java:139)#Java###Process ID , name has been started.#2#3#rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/extr
    act#
    #1.#C0000A0B26780000000019A36CF86CF800049C5469B13268#1297786271249#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.logProcessInfo(OsProcessController.java:141)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logPro
    cessInfo(OsProcessController.java:141)#Java###Command line: #2#  #rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract #
    #1.#C0000A0B26780000000019A46CF86CF800049C5469B13650#1297786271250#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.logProcessInfo(OsProcessController.java:142)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logPro
    cessInfo(OsProcessController.java:142)#Java###Standard out: #2#  #/usr/sap/GDP/JC00/j2ee/JSPM/tmp/DeleteDir_01.OUT#
    #1.#C0000A0B26780000000019A56CF86CF800049C5469B218E0#1297786271308#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProce
    ssController.java:126)#Java###Process ID has been started.#1#3#
    #1.#C0000A0B26780000000019A66CF86CF800049C5469B21CC8#1297786271309#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsPro
    cessController.java:182)#Java###Waiting for process ID , name to finish.#2#3#rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019A76CF86CF800049C5469B21CC8#1297786271309#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsPro
    cessController.java:215)#Java###Process ID , name has been finished, exit code .#3#3#rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/ex
    tract#0#
    #1.#C0000A0B26780000000019A86CF86CF800049C5469B220B0#1297786271310#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.io.SdtFile.logInfo(Sd
    tFile.java:901)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.io.SdtFile.logInfo(SdtFile.java:901)#Java###File has been de
    leted.#1#/usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019A96CF86CF800049C5469B220B0#1297786271310#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.io.SdtFile.logInfo(Sd
    tFile.java:901)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.io.SdtFile.logInfo(SdtFile.java:901)#Java###File has been de
    leted.#1#/usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019AA6CF86CF800049C5469B22498#1297786271311#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.io.SdtFile.logInfo(Sd
    tFile.java:901)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.io.SdtFile.logInfo(SdtFile.java:901)#Java###Directory has be
    en created.#1#/usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019AB6CF86CF800049C5469B22498#1297786271311#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:468)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.s
    dmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:468)#Java###Extracting the file from the SDM com
    ponent archive file...#2#version.txt#/usr/sap/trans/EPS/in/SDMKIT21_0-10003463.JAR#
    #1.#C0000A0B26780000000019AC6CF86CF800049C5469B70E68#1297786271633#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.readVersionInformation(DetectSDMComponent.java:537)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdete
    ction.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:537)#Java###Detecting SDM component by parsing file...#1#/us
    r/sap/GDP/JC00/j2ee/JSPM/tmp/extract/version.txt#
    #1.#C0000A0B26780000000019AD6CF86CF800049C5469B71250#1297786271634#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.readVersionInformation(DetectSDMComponent.java:572)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdete
    ction.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:572)#Java###Detection of SDM component has finished. SDM version
    with release , support package level , and patch level found in .#5#SAP_JAVASL#7.00#21#0#/usr/sap/GDP/JC00/j2ee/JSPM/t
    mp/extract#
    #1.#C0000A0B26780000000019AE6CF86CF800049C5469B71638#1297786271635#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.logProcessInfo(OsProcessController.java:139)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logPro
    cessInfo(OsProcessController.java:139)#Java###Process ID , name has been started.#2#4#rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/extr
    act#
    #1.#C0000A0B26780000000019AF6CF86CF800049C5469B71A20#1297786271636#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.logProcessInfo(OsProcessController.java:141)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logPro
    cessInfo(OsProcessController.java:141)#Java###Command line: #2#  #rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract #
    #1.#C0000A0B26780000000019B06CF86CF800049C5469B71A20#1297786271636#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.logProcessInfo(OsProcessController.java:142)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logPro
    cessInfo(OsProcessController.java:142)#Java###Standard out: #2#  #/usr/sap/GDP/JC00/j2ee/JSPM/tmp/DeleteDir_01.OUT#
    #1.#C0000A0B26780000000019B16CF86CF800049C5469B7C600#1297786271680#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProce
    ssController.java:126)#Java###Process ID has been started.#1#4#
    #1.#C0000A0B26780000000019B26CF86CF800049C5469B7C9E8#1297786271681#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsPro
    cessController.java:182)#Java###Waiting for process ID , name to finish.#2#4#rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019B36CF86CF800049C5469B7C9E8#1297786271681#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessControl
    ler.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsPro
    cessController.java:215)#Java###Process ID , name has been finished, exit code .#3#4#rm -rf /usr/sap/GDP/JC00/j2ee/JSPM/tmp/ex
    tract#0#
    #1.#C0000A0B26780000000019B46CF86CF800049C5469B7C9E8#1297786271681#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.io.SdtFile.logInfo(Sd
    tFile.java:901)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.io.SdtFile.logInfo(SdtFile.java:901)#Java###File has been de
    leted.#1#/usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019B56CF86CF800049C5469B7CDD0#1297786271682#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.io.SdtFile.logInfo(Sd
    tFile.java:901)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.io.SdtFile.logInfo(SdtFile.java:901)#Java###File has been de
    leted.#1#/usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019B66CF86CF800049C5469B7CDD0#1297786271682#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:442)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.s
    dmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:442)#Java###Detecting version of SDM component from
    archive file...#1#/usr/sap/trans/EPS/in/dump/SDMKIT21_0-10003463.JAR#
    #1.#C0000A0B26780000000019B76CF86CF800049C5469B7D1B8#1297786271683#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.io.SdtFile.logInfo(Sd
    tFile.java:901)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.io.SdtFile.logInfo(SdtFile.java:901)#Java###Directory has be
    en created.#1#/usr/sap/GDP/JC00/j2ee/JSPM/tmp/extract#
    #1.#C0000A0B26780000000019B86CF86CF800049C5469B7D1B8#1297786271683#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sdmdetection.Det
    ectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:468)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.s
    dmdetection.DetectSDMComponent.detectSDMComponentFromSdmkit(DetectSDMComponent.java:468)#Java###Extracting the file from the SDM com
    ponent archive file...#2#version.txt#/usr/sap/trans/EPS/in/dump/SDMKIT21_0-10003463.JAR#
    GMU-EPDB:gdpadm 26>

  • JSPM Connection Problem Waiting for SDTServer to connect ...

    Hello folks
    I have a Solution Manager EPH1, SPS25 on AIX 5.3 with Db2 9.5 FP6
    I'm Trying to run JSPM but i have problems on SDTServer connection, here you have the shell that i have
    bz1adm@sapbt309:/usr/sap/BZ1/DVEBMGS23/j2ee/JSPM 3> go
    Current log directory is /usr/sap/BZ1/DVEBMGS23/j2ee/JSPM/log/log_2011_02_06_22_10_25.
    Waiting for SDTServer to connect ...
    I checked whether SDM was running and is running normally
    bz1adm@sapbt309:/usr/sap/BZ1/DVEBMGS23/SDM/program 11> ./StartServer.sh
    Starting SDM - Software Deployment Manager...
    tc/SL/SDM/SDM/sap.com/SAP AG/7.0104.20090324110103.0000
    JStartupFramework is active
    Operation mode of SDM in JStartupFramework is "Integrated".
    Check if Server is running already.
    Another SDM Server is running already and correctly replied to a "Ping"
    Could not start SDM. Processing error. Return code: 4
    and here you have the jspm_config.txt
    bz1adm@sapbt309:/usr/sap/BZ1/DVEBMGS23/j2ee/JSPM/param 11> more jspm_config.txt
    /context/name = Jspm
    see com.sap.sdt.ucp.dialog.DialogFactoryProperties
    /dialog/directory = config/dialog
    #/dialog/serverConnection = TestServerConnection
    #/dialog/serverConnection = UaServerConnection
    #/dialog/UaServerConnection/port = 6240
    #/dialog/UaServerConnection/port = 4240
    /dialog/serverConnection = SDTServerConnection
    /dialog/SDTServerConnection/mode = SDTGui
    /dialog/SDTServerConnection/port=6240
    /dialog/SDTServerConnection/SDTGui/launch = true
    /dialog/SDTServerConnection/SDTGui/config = jspm
    /dialog/recordNameSpace = J2EEInputRecording
    /dialog/recording = off
    /dialog/autoCreateVariables = on
    Any Ideas?? I'm using VNC server directly to server and normally i ran the JSPM on server, the detail is that on QAS is working without problems
    Thanks and hope that you can help me
    Edited by: Cheiros on Feb 6, 2011 11:24 PM

    Hello folks
    I solved the problem, the problem was with VNC Server (the resolution)
    I appreciate your interest and your answers
    Have a nice day

  • JSPM waiting for SDTserver in SAPNW7.3

    Dear Experts,
    JSPM is not coming up with the above states (long known problem), here is the error message from JSPM.LOG:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[/usr/sap/BJ1/J02/j2ee/JSPM/log/log_2011_08_18_15_44_18/JSPM.LOG]/>
    <!PATTERN[JSPM.LOG]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Aug 18, 2011 3:44:18 PM [Info]: Starting JSPM bootstrap...
    Aug 18, 2011 3:44:18 PM [Info]: Command line: -boot=unx -rootdir=/usr/sap/BJ1/J02/j2ee/JSPM
    Aug 18, 2011 3:44:19 PM [Info]: No new JSPM content found in directory /usr/sap/BJ1/J02/j2ee/JSPM/deploy.
    Aug 18, 2011 3:44:19 PM [Info]: Local copy of SAP JVM is up to date.
    Aug 18, 2011 3:44:19 PM [Info]: Bootstrap will not launch JSPM process.
    Aug 18, 2011 3:44:19 PM [Info]: JSPM bootstrap completed successfully.
    Aug 18, 2011 3:44:19 PM [Info]: Command line: -rootdir=/usr/sap/BJ1/J02/j2ee/JSPM -tracelevel=FINEST run JSPM -properties=jspm_c                             onfig.txt
    Aug 18, 2011 3:44:19 PM [Info]: JSPM version is 7.30.0.0.196.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping has started.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping common execution has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.db.DBFactoryManager has been initialized with code all and version 0                 
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code all and versi                             on 630.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code all and versi                             on 700.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code all and versi                             on 710.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code all and versi                             on 700.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code all and versi                             on 710.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping common configuration has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and versi                             on 0.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and versi                             on 630.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and versi                             on 700.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and versi                             on 710.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code UNX and versi                             on 0.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.tools.UtilFactoryManager has been initialized with code UNX and vers                             ion 0.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping configuration for UNX has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code 710 and versi                             on 0.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping configuration for 710 has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping has ended.
    tdsbwdev:/usr/sap/BJ1/J02/j2ee/JSPM/log/log_2011_08_18_15_44_18 # cat JSPM.LOG
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[/usr/sap/BJ1/J02/j2ee/JSPM/log/log_2011_08_18_15_44_18/JSPM.LOG]/>
    <!PATTERN[JSPM.LOG]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Aug 18, 2011 3:44:18 PM [Info]: Starting JSPM bootstrap...
    Aug 18, 2011 3:44:18 PM [Info]: Command line: -boot=unx -rootdir=/usr/sap/BJ1/J02/j2ee/JSPM
    Aug 18, 2011 3:44:19 PM [Info]: No new JSPM content found in directory /usr/sap/BJ1/J02/j2ee/JSPM/deploy.
    Aug 18, 2011 3:44:19 PM [Info]: Local copy of SAP JVM is up to date.
    Aug 18, 2011 3:44:19 PM [Info]: Bootstrap will not launch JSPM process.
    Aug 18, 2011 3:44:19 PM [Info]: JSPM bootstrap completed successfully.
    Aug 18, 2011 3:44:19 PM [Info]: Command line: -rootdir=/usr/sap/BJ1/J02/j2ee/JSPM -tracelevel=FINEST run JSPM -properties=jspm_config.txt
    Aug 18, 2011 3:44:19 PM [Info]: JSPM version is 7.30.0.0.196.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping has started.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping common execution has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.db.DBFactoryManager has been initialized with code all and version 0.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code all and version 630.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code all and version 700.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code all and version 710.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code all and version 700.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code all and version 710.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping common configuration has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and version 0.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and version 630.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and version 700.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.j2ee.J2eeFactoryManager has been initialized with code UNX and version 710.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code UNX and version 0.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.tools.UtilFactoryManager has been initialized with code UNX and version 0.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping configuration for UNX has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Factory manager com.sap.sdt.jspm.JspmFactoryManager has been initialized with code 710 and version 0.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping configuration for 710 has been completed.
    Aug 18, 2011 3:44:20 PM [Info]: Bootstrapping has ended.
    Please advise.
    System Abap+Java SAPNW73 on DB297FP4 SUSE10
    Thanks in advance,
    Rudi

    Dear Rudi,
    The server do not recognizes the host, start with different host
    start JSPM - in the command line
    go-remoteUI
    now you will get message waiting for SDT server to connect)
    open the web browser on the other host
    http://<host>:5XX19
    were host is host name of the server xx is the instance no.
    now start the JSPM GUI -JSPM will started locally and the proceed as usually.
    Regards
    APS Pets

  • JSPM startup fails with IBM JDK 1.4.2 SR13

    Hi experts,
    I´m upgrading my Portal to EHP1 SP06. After the upgrade I checked SDM and JSPM, SDM is working fine but the JSPM don´t start any more.
    I just getting the information after starting the script 'go' under AIX:
    'Waiting for SDTServer to connect ...'
    Nothing happened after 10min...
    Just want to let you that this issue is caused by a buggy version of the AIX JDK.
    There is a new sapnote 1422869 for this issue, please have a look.
    Solution
    Use the actual recommended "IBM JDK 1.4.2 SR13 FP4 ifix" or SR13 without any FP.
    The problem was introduced with SR13 FP2 and is in FP3 and FP4 too.
    Install the recommended "IBM JDK 1.4.2 SR13 FP4 ifix" to solve the problem (see SAP note 1008311 or 1024539). As a workaround you can use the remote GUI from another system using a not affected JDK.
    I installed IBM JDK 1.4.2 SR13 without any FP and the JSPM is working again
    You can get the new Java versions directly from IBM, click here to download it.
    Regards,
    Jens

    Hi,
    While installing solution manager 4 (SLES x86_64) I also run into the problem "ibjvm.so preloadLibrary: /opt/IBMJava2-amd64-142/jre/bin/j9vm/libj9vm22.so: cannot open shared object file: No such file or directory" during the phase "Create Java users"
    I've taken your advice (Chris B) and the installation carries on with out a problem. (and the java instance has started)
    When I stop and start sap, I then cannot get the Java instance to start again!
    The error in the "std_bootstrap.out" has the message; "libjvm.so preloadLibrary: /opt/IBMJava2-amd64-142/jre/libj9vm22.so: cannot open shared object file: No such file or directory
    libjvm.so failed to load: j9vm22"
    I have set all the environmental variables including the LD_LIBRARY_PATH and JAVA_HOME
    I was wondering if you had the same problem, else if anyone else could please please help.
    Thanks,
    Chris G
    Message was edited by: Chris Geladaris

  • Unable to connect JSPM

    We are installed sap solution manager 7.0 EHP1,now we want to download patches
    But confusion is that how to find our SP level and in which steps we download SP ( like SP03 etc)
    we have Fujitsu solution and we are connected to VNC server, when we run JSPM  from
    Usr/sap/SID/central instance/j2ee/jspm/go its waiting many hour in u201Cwaiting for SDTserver to connectu201D
    but not show jspm, only one time I see jspm from same path but not run go we run startgui but after that when we run again its prompt connection to jspm could not be established and prompt to host name u201Clocalhostu201D and port u201C6240u201D we also run suse linux command netstat to check port 6240 is used but not used and then we also change jspm xxxconfig.xml file and change different port but failed.
    Please guide me related to our issue
    Regards
    rayyan

    Thankx for ur reply
    following out are jspm logs stdgui.err file
    com.sap.sdt.server.core.services.tool.ToolConnectFailedException: Connection to JSPM could not be established, see following messages.
    Could not connect to host localhost on port 6240.
    java.net.ConnectException: Connection refused
    java.net.ConnectException: Connection refused
         at com.sap.sdt.server.core.services.tool.AbstractToolService.connectTool(AbstractToolService.java:88)
         at com.sap.sdt.server.core.services.tool.AbstractToolService.addGui(AbstractToolService.java:61)
         at com.sap.sdt.server.ext.jump.AbstractJumpService.addGui(AbstractJumpService.java:76)
         at com.sap.sdt.gui.core.admin.SDTGuiAdmin.logon(SDTGuiAdmin.java:229)
         at com.sap.sdt.gui.core.SDTGui.initLocalGui(SDTGui.java:166)
         at com.sap.sdt.gui.core.SDTGui.initGui(SDTGui.java:130)
         at com.sap.sdt.gui.core.SDTGui.start(SDTGui.java:73)
         at com.sap.sdt.gui.core.SDTGui.main(SDTGui.java:57)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
         at java.lang.reflect.Method.invoke(Method.java:391)
         at com.sap.sdt.server.core.admin.GuiManager.startAsMethod(GuiManager.java:178)
         at com.sap.sdt.server.core.admin.GuiManager.startGui(GuiManager.java:109)
         at com.sap.sdt.server.core.admin.SDTServerAdmin.startGui(SDTServerAdmin.java:814)
         at com.sap.sdt.server.core.admin.SDTServerAdmin.start(SDTServerAdmin.java:583)
         at com.sap.sdt.server.core.SDTServer.start(SDTServer.java:82)
         at com.sap.sdt.server.core.SDTServer.main(SDTServer.java:54)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
         at java.lang.reflect.Method.invoke(Method.java:391)
         at com.sap.sdt.util.misc.MethodCall.invoke(MethodCall.java:80)
         at com.sap.sdt.util.misc.BootStrapper.start(BootStrapper.java:77)
         at SDTGui.main(SDTGui.java:50)
    Caused by: com.sap.sdt.util.diag.JavaException: java.net.ConnectException: Connection refused
    java.net.ConnectException: Connection refused
         at com.sap.sdt.util.net.AbstractCommLink.connect(AbstractCommLink.java:85)
         at com.sap.sdt.server.core.services.tool.AbstractToolAdapter.connectTool(AbstractToolAdapter.java:135)
         at com.sap.sdt.server.core.services.tool.AbstractToolService.connectTool(AbstractToolService.java:81)

  • JSPM: Error while detecting start profile for instance with ID _c.

    Hi Experts,
    we have an error when we start JSPM with message "cannot initialize application data. Error while detecting start profile for instance with ID _c." . Until now nothing has been updated yet. The system can be started up and shut down without any problem. The profiles are found in /usr/sap/PMA/SYS/profile
    Our BI system is currently Netweaver 7.0 with SPS14. We plan to update it to SPS20. But when we start JSPM, we have abover error.
    could somebody give a help? Thank you very much.
    Rongfeng
    P.S. the log file DETECT_SYSTEM_PARAMETERS_01.LOG:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DETECT_SYSTEM_PARAMETERS_01.LOG]/>
    <!PATTERN[DETECT_SYSTEM_PARAMETERS_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    #1.5^H#C000995FC0200000000000207BD47BD40004789C01294DB0#1258511336558#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#Java###Initializing JSPM data model...##
    #1.5^H#C000995FC0200000000000217BD47BD40004789C01295968#1258511336561#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#Java###Detected profile directory .#1#/usr/sap/PMA/SYS/profile#
    #1.5^H#C000995FC0200000000000227BD47BD40004789C0141AFE0#1258511338156#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#Java###Detecting the parameters of the database...##
    #1.5^H#C000995FC0200000000000237BD47BD40004789C014205D0#1258511338178#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#Java###Executing command with arguments .#2#dbinfo#/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
    #1.5^H#C000995FC0200000000000247BD47BD40004789C01421570#1258511338182#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#5#com.sap.sdt.dmt.main.DMT#
    #1.5^H#C000995FC0200000000000257BD47BD40004789C01421958#1258511338183#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2#  #/opt/IBMJava2-amd64-142/jre/bin/java -cp .:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/sdt_dmt.jar:/oracle/client/10x_64/instantclient/ojdbc14.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jddi.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/opensqlsta.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/frame.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jperflib.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/util.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/opensqlsta.jar:/sapmnt/PMA/global/security/lib/tools/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/tools/iaik_jce.jar:/sapmnt/PMA/global/security/lib/tools/iaik_smime.jar:/sapmnt/PMA/global/security/lib/tools/iaik_jsse.jar:/sapmnt/PMA/global/security/lib/tools/w3c_http.jar:/sapmnt/PMA/global/security/lib/tools/iaik_ssl.jar:/sapmnt/PMA/global/security/lib/engine/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/engine/iaik_jce.jar com.sap.sdt.dmt.main.DMT -rootdir=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM -descriptor=csrt29_PMA -logfile=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01.LOG dbinfo /usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
    #1.5^H#C000995FC0200000000000267BD47BD40004789C01422128#1258511338185#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2#  #/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01_01.OUT#
    #1.5^H#C000995FC0200000000000277BD47BD40004789C01424838#1258511338195#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#5#
    #1.5^H#C000995FC0200000000000287BD47BD40004789C014253F0#1258511338198#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#5#java#
    #1.5^H#C000995FC0200000000000297BD47BD40004789C017402B0#1258511341454#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#5#java#0#
    #1.5^H#C000995FC02000000000002A7BD47BD40004789C01741638#1258511341459#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#Java###Command has been executed.#1#dbinfo#
    #1.5^H#C000995FC02000000000002B7BD47BD40004789C017421F0#1258511341462#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#Java###Detection of the parameters of the database has finished. Database type is , database name is and database version is .#3#ORA#Oracle#10.2.0.2.0#
    #1.5^H#C000995FC02000000000002C7BD47BD40004789C01744CE8#1258511341473#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#Java###Parameter has been detected. Parameter value is .#2#/J2EE/StandardSystem/DefaultProfilePath#/usr/sap/PMA/SYS/profile/DEFAULT.PFL#
    Sorry, I don't know how to format post 
    Edited by: Rongfeng Shi on Nov 18, 2009 4:20 AM

    Hi Rongfeng,
    There is not much information about the error in the log file you have pasted above.
    Please repeat the issue and catch the log files once again.
    Are you able to open SDM ?
    Best Regards
    Raghu

  • Application Deployment issue in Webdynpro project

    Hi,
    I have created an sample Webdynpro project which just displays the name. EAR file has been transformed to SCA file using NWPACKTOOL for deploying the application in JSPM.
    When i tried to deploy the SCA file i am getting an exception as,
    Deployment Items -
         1. Client path 'C:\usr\sap\WP1\SYS\EPS\in\test1.sca'
              Deploy status is 'Aborted'
              Description:'1. Item is skipped because of failed deployment of item 'test.com_test' and because the applied error strategy is OnErrorStop
              2. Contains Aborted deployment component:
    test.com_test'.
              SCA : name 'test', vendor 'test.com', location 'local', version '1000.1.0.1.0.20110810105342'
              Contained DCs:
                   1.1 : Relative path 'C:\usr\sap\WP1\SYS\EPS\in\test1.sca --> test.sca.ear'
                        Deploy status is 'Aborted'
                        Description:'1. ASJ.dpl_ds.006193 Error while deploying ear file C:\usr\sap\WP1\J00\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\56\test1_sca1312954437078\DEPLOYARCHIVES\test.sca.ear; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while [validating application test.com/test.
         The test.com/test application was processed from [developmentserver] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [BRMS_Content_Archive, z_com.sap.security.policy-configurations, utl_handler, developmentserver, Monitoring Configurator, component.info_handler, servlet_jsp, connector, classification_handler, CTCContainer, JDBCConnector, PortalRuntimeContainer, dbcontentcontainer, scheduler~container, Content Container, src.zip_handler, PCD Content Deployment Handler, ConfigurationsContainer, orpersistence, appclient, JMSConnector, Cluster File System, Cache Configuration Upload, com.sap.security.ume, SCA Composites Container, metamodelrepository, textcontainer, eden_handler, Galaxy_Content_Archive, uddi_handler, MigrationContainer, com.sap.security.login-modules, webservices_container, EJBContainer, dbschemacontainer, MDRContainer, com.sap.security.policy-configurations, app_libraries_container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].'.
                        SDA : name 'test', vendor 'test.com', location 'local', version '2', software type ('J2EE', s
    Can some one help me in deploying the SCA file?
    Please let me know how to resolve this issue.
    Thanks in Advance!!
    Regards
    MG
    Edited by: madhanssmile on Aug 10, 2011 2:34 PM

    go to "DC Metadata" "used DC"  , and "Properties" in context menu
    for all you your components.
    problematic component reference probable has check box "deploy time" checked.
    remove that reference.
    usually only "Build time"  check box must be checked. try to do so.

  • JSPM Error while applying As Java Patch to PI 7.1

    Dear All
    I am facing an issue when trying to patch new Pi 7.1 Ehp1 Java patch through JSPM
    steps i did
    . since the download manger is not working for us i click on the link and down load all the patches to windows machine ( Installed machine is AIX)
    all the patches were downloded in SCA.zip " LMNWATOOLS04_0-20003137.SCA.zip" format which is not recognizable through JSPM
    i rename all the file taking off zip extension "LMNWATOOLS04_0-20003137.SCA" , but now the initiating is working but it throws an error saying to revise all the selected patches?
    " Error occured, while reading refactoring configuration from SDU file /usr/sap/trans/EPS/in/ESREGBASIC04_0-20003135.SCA. java.io.IOException: java.io.IOException: "
    how can i deploy these patches comes with SCA.zip format ? i know only SCA  can be deployed , but since i have downloaded them directly it converted to SCA.zip
    please advice me  how to resoleve this urgently
    appreciate your coperation with regard to this
    Buddhike

    > how can i deploy these patches comes with SCA.zip format ? i know only SCA  can be deployed , but since i have downloaded them directly it converted to SCA.zip
    It is fine just to delete the .zip at the end. The issue has another reason.
    Have you patched the JSPM before you applied the patches?

  • Error while applying LM-tools patch using JSPM

    hi all,
    I got error while applying LM-Tool patch using JSPM. following is the error log. How can i rectify it. please help.
    Mar 29, 2010 12:49:57... Info:
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: DROP TABLE "BC_MID_TREE"
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: DROP TABLE "BC_MID_TREE"
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE TABLE "BC_MID_TREE"("NODE_ID" RAW(16)  NOT NULL, "PARENT_I
    D" RAW(16)  , "NODE_TYPE" NUMBER(10) DEFAULT 0 NOT NULL, "NAME" NVARCHAR2(30) DE
    FAULT ' ' NOT NULL, "TS" TIMESTAMP  NOT NULL, "USER_ID" NVARCHAR2(30)  )
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE TABLE "BC_MID_TREE"("NODE_ID" RAW(16)  NOT NULL, "PARENT_I
    D" RAW(16)  , "NODE_TYPE" NUMBER(10) DEFAULT 0 NOT NULL, "NAME" NVARCHAR2(30) DE
    FAULT ' ' NOT NULL, "TS" TIMESTAMP  NOT NULL, "USER_ID" NVARCHAR2(30)  )
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE INDEX "BC_MID_TREE_R" ON "BC_MID_TREE"("PARENT_ID")
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE INDEX "BC_MID_TREE_R" ON "BC_MID_TREE"("PARENT_ID")
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE UNIQUE INDEX "BC_MID_TREE_U" ON "BC_MID_TREE"("PARENT_ID",
    "NAME")
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE UNIQUE INDEX "BC_MID_TREE_U" ON "BC_MID_TREE"("PARENT_ID",
    "NAME")
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: ALTER TABLE "BC_MID_TREE" ADD PRIMARY KEY ("NODE_ID") NOT DEFERRA
    BLE INITIALLY IMMEDIATE ENABLE VALIDATE
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Statement successf
    ully executed: ALTER TABLE "BC_MID_TREE" ADD PRIMARY KEY ("NODE_ID") NOT DEFERRA
    BLE INITIALLY IMMEDIATE ENABLE VALIDATE
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Next archive objec
    t : dbtables/BC_MID_TREE_ITEM.gdbtable
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Next archive objec
    t : dbtables/BC_MID_TREE_ITEM.gdbtable
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  <<< Analyze table
    BC_MID_TREE_ITEM >>>
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  <<< Analyze table
    BC_MID_TREE_ITEM >>>
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  predefined action
    is: >>>DROP_CREATE<<<
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  predefined action
    is: >>>DROP_CREATE<<<
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Action: DROP_CREAT
    E
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:  Action: DROP_CREAT
    E
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:    DROP TABLE "BC_M
    ID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info:  CREATE TABLE "BC_MID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info: (
    Mar 29, 2010 12:49:57... Info: "NODE_ID" RAW(16)  NOT NULL,
    Mar 29, 2010 12:49:57... Info: "ITEM_ID" RAW(16)
    Mar 29, 2010 12:49:57... Info: )
    Mar 29, 2010 12:49:57... Info:  CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TRE
    E_ITEM"
    Mar 29, 2010 12:49:57... Info: (
    Mar 29, 2010 12:49:57... Info: "ITEM_ID"
    Mar 29, 2010 12:49:57... Info: )
    Mar 29, 2010 12:49:57... Info:  ALTER TABLE "BC_MID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info: ADD PRIMARY KEY ("NODE_ID")
    Mar 29, 2010 12:49:57... Info: NOT DEFERRABLE INITIALLY IMMEDIATE ENABLE VALIDAT
    E
    Mar 29, 2010 12:49:57... Info:
    Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info:    DROP TABLE "BC_M
    ID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info:  CREATE TABLE "BC_MID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info: (
    Mar 29, 2010 12:49:57... Info: "NODE_ID" RAW(16)  NOT NULL,
    Mar 29, 2010 12:49:57... Info: "ITEM_ID" RAW(16)
    Mar 29, 2010 12:49:57... Info: )
    Mar 29, 2010 12:49:57... Info:  CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TRE
    E_ITEM"
    Mar 29, 2010 12:49:57... Info: (
    Mar 29, 2010 12:49:57... Info: "ITEM_ID"
    Mar 29, 2010 12:49:57... Info: )
    Mar 29, 2010 12:49:57... Info:  ALTER TABLE "BC_MID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info: ADD PRIMARY KEY ("NODE_ID")
    Mar 29, 2010 12:49:57... Info: NOT DEFERRABLE INITIALLY IMMEDIATE ENABLE VALIDAT
    E
    Mar 29, 2010 12:49:57... Info:
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: DROP TABLE "BC_MID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: DROP TABLE "BC_MID_TREE_ITEM"
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE TABLE "BC_MID_TREE_ITEM"("NODE_ID" RAW(16)  NOT NULL, "ITE
    M_ID" RAW(16)  )
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE TABLE "BC_MID_TREE_ITEM"("NODE_ID" RAW(16)  NOT NULL, "ITE
    M_ID" RAW(16)  )
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TREE_ITEM"("ITEM_ID"
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TREE_ITEM"("ITEM_ID"
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: ALTER TABLE "BC_MID_TREE_ITEM" ADD PRIMARY KEY ("NODE_ID") NOT DE
    FERRABLE INITIALLY IMMEDIATE ENABLE VALIDATE
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Statement successf
    ully executed: ALTER TABLE "BC_MID_TREE_ITEM" ADD PRIMARY KEY ("NODE_ID") NOT DE
    FERRABLE INITIALLY IMMEDIATE ENABLE VALIDATE
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE_ITEM successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE_ITEM successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE_ITEM successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Runtime XML of BC_
    MID_TREE_ITEM successfully written
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Analysis and adjus
    tment of tables successfully executed
    Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info:  Analysis and adjus
    tment of tables successfully executed
    Mar 29, 2010 12:49:57... Info: Finished successfully: development component 'tc/
    slm/mid/dd'/'sap.com'/'MAIN_APL70P18_C'/'2712380'/'0', grouped by
    Mar 29, 2010 12:49:57... Info: Starting to save the repository
    Mar 29, 2010 12:49:57... Info: Finished saving the repository
    Mar 29, 2010 12:49:57... Info: Starting: Update: Selected development component
    'tc/archtech/browser/viewer/locator'/'sap.com'/'MAIN_APL70P18_C'/'2712383'/'0' u
    pdates currently deployed development component 'tc/archtech/browser/viewer/loca
    tor'/'sap.com'/'MAIN_APL70VAL_C'/'1496536'/'0'.
    Mar 29, 2010 12:49:57... Info: SDA to be deployed: /usr/sap/IRX/DVEBMGS02/SDM/ro
    ot/origin/sap.com/tc/archtech/browser/viewer/locator/MAIN_APL70P18_C/0/2712383/t
    carchtechbrowserviewerlocator.sda
    Mar 29, 2010 12:49:57... Info: Software type of SDA: J2EE
    Mar 29, 2010 12:49:57... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A
    pplication) *****
    Mar 29, 2010 12:49:58... Info: Starting cluster instance processes.
    Mar 29, 2010 12:50:03... Info: Starting the instance JC_PRDCIXI_IRX_02 running o
    n host PRDCIXI_svc
    Mar 29, 2010 12:50:03... Info: Starting the instance JC_PRDCIXI_IRX_02 processes
    . The instance is running on host PRDCIXI_svc
    Mar 29, 2010 12:50:03... Info: Starting the process dispatcher
    Mar 29, 2010 12:50:03... Info: Starting the process server0
    Mar 29, 2010 6:49:58 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE App
    lication) *****
    Mar 29, 2010 6:49:58 PM  Error: Aborted: development component 'tc/archtech/brow
    ser/viewer/locator'/'sap.com'/'MAIN_APL70P18_C'/'2712383'/'0', grouped by softwa
    re component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P19_C'/'1000.7.00.19.0.200904271432
    29''/'0':
    SDM could not start the J2EE cluster on the host PRDCIXI! The online deployment
    is terminated.
    A timeout occured during the cluster running verification.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDepl
    oyerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    Mar 29, 2010 6:49:58 PM  Info: Starting to save the repository
    Mar 29, 2010 6:49:59 PM  Info: Finished saving the repository
    Mar 29, 2010 6:49:59 PM  Info: Starting: Update: Selected software component 'LM
    -TOOLS'/'sap.com'/'MAIN_APL70P19_C'/'1000.7.00.19.0.20090427143229''/'0' updates
    currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P14_C'/'1
    000.7.00.14.1.20080124101556''/'0'.
    Mar 29, 2010 6:49:59 PM  Error: Aborted: software component 'LM-TOOLS'/'sap.com'
    /'MAIN_APL70P19_C'/'1000.7.00.19.0.20090427143229''/'0':
    Failed deployment of SDAs:
    development component 'tc/archtech/browser/viewer/locator'/'sap.com'/'MAIN_APL70
    P18_C'/'2712383'/'0' : aborted
    Please, look at error logs above for more information!
    Mar 29, 2010 6:49:59 PM  Info: Starting to save the repository
    Mar 29, 2010 6:49:59 PM  Info: Finished saving the repository
    Mar 29, 2010 6:49:59 PM  Info: Restoring the state of the instance (JC_PRDCIXI_I
    RX_02) process server0 from Stopped to Running
    Mar 30, 2010 12:50:00... Error: Received exception when restoring Engine state:
    A timeout occured during the cluster state restore verification.
    Mar 30, 2010 12:50:00... Error: -
    At least one of the Deployments
    failed -
    Regards,
    Priya

    Hi Priya,
    As per your error message, there is problem with the SDM is not starting after finishing deployment on SAP J2EE Engine Deployment. Development component are not deployed properly due to error message
    > SDM could not start the J2EE cluster on the host PRDCIXI! The online deployment is terminated. A timeout occured during the cluster running verification. P
    Please check the default timeout and increased as requred.
    Please check the below thread to rectify this issue.
    SDM Troubleshooting  : http://help.sap.com/saphelp_nw04/helpdata/de/76/fb72ec091f4bf8a2d8ba321bb7e8d9/frameset.htm
    SDM Troubleshooting  : https://cw.sdn.sap.com/cw/docs/DOC-29627:
    Hope it helps
    Regards
    Arun

  • EHP Upgrade Issue - Java Stack

    Hi,
    Our Source System at NW 7.0 SP13 and we are upgrading the system to EHP1 SP03.
    Upgrade failed at Downtime > DEPLOY_ONLINE_DEPL phase.
    Error log:
    Sep 9, 2009 10:11:51 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
    Sep 9, 2009 10:11:51 PM [Error]:             com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error
    JSPM version is 7.01.3.0.15. Current JSPM log directory is /usr/sap/XPD/JC00/j2ee/JSPM/log/log_2009_09_09_16_09_42.
    Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:698) [Thread[main,5,main]]: The deployment of the queue failed.
    Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file /usr/sap/trans/EPS/in/XPD.xml.
    Sep 9, 2009 10:11:51 PM [Error]:      com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2009/09/09 22:09:42.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2009/09/09 22:11:51.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:02:08.248.
    Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
    I went through the following link , proceeded with option 2, But still getting same error.  
    Portal Upgrade Issue
    Please advise the resolution for the issue I have.
    Thanks in advance
    Regards
    Srinivas
    Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM
    Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM

    Issue resolved

  • Seeburger BIC Mapping deployment issue in PI 7.1

    Hi experts
    We have upgraded from XI 3.0 to PI 7.1 and seeburger is also upgraded to  a compatible version.(2.x).
    Mappings_user.sda was used in 3.0 environment.
    But we are not able to deploy the same in 7.1. I think sda format is not supported in 7.1.
    Is there any way to convert .sda to .sca and deploy?
    Or how can we generate a compatible deployment file for 7.1?
    I have tried using BIC mapping designer,but it shows the option for .sda and .jar only.
    Thanks in advanceDhanish Joseph

    Hi
    I have installed BICMD  632 version and imported .BICMD project file.
    Then assigned sda/sca number to it and created deploy file.(Mapping_user00.sda).
    Then installed this in PI system using JSPM.
    I have tested allmost all the mappings successfully except one in PI system.(EDI 990 message).
    When i send data to PI  data comes to channel and it shows conversion error. But detailed information not available.
    In seeburger monitoring  the message goes to recovery mode.
    I have used the input 990 X12 and tested in Seeburger BIC MD. And there it is success!!!!!! So i am confused what is happening when it comes to PI system.
    I faced some issues>>>
    1.  while importing project file into BIC MD it asked for apply some autocorrection  for one map.(different than this). I have clicked on cancel
    2. When i assigned SDA number to my project i have selected 2.1.0  SDA version( 1.8.0 option was also there).
    Your prompt reply is greatly appreciated .
    Thanks

  • Issue installing PI 7.1 EHP1 on AIX,Oracle

    Hi Friends,
    I am installing PI 7.1 EHP1 on AIX,Oracle.Iam facing some issue during installation(25th phase of installation).
    I have 10 Gb RAM and 20 Gb SWAP.
    Do you have any idea?
    sapinst.log:
    13.10.2009 11:02:22
    GetProcessList
    FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
    INFO 2009-10-13 11:02:22.229
    Connect to message server (s0001079/3901) succeeded.
    INFO 2009-10-13 11:02:22.229
    Disconnect from message server (s0001079/3901) succeeded.
    WARNING[E] 2009-10-13 11:02:22.240
    CJS-30087  Instance XDN/SCS01 [PARTIAL] did not stop after 2:00 minutes. Giving up.
    ERROR 2009-10-13 11:02:23.421
    FCO-00011  The step stopInstance with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_Instance|ind|ind|ind|ind|1|0|stopInstance was executed with status ERROR .
    WARNING 2009-10-13 11:02:23.576
    Could not get property IDs of the JavaScript object.
    ERROR 2009-10-13 11:02:23.577
    FJS-00010  Could not get value for property .

    Hi Milos,
    The problem is with the starting of the SCS instance by sapinst, on AIX the port that we used (SAP default) 3901 during the input step for SCS was in usage at AIX by some application
    nimsh 3901/tcp # NIM Service Handler
    nimsh 3901/udp # NIM Service Handler
    I had to free up the port for some time, stop processes running on the port and then continued with my installation. After the installation was complete, I changed the port number of SCS to 3601 and gave the port back to AIX application.
    Beaware that you have to change the port number is various places, including Config tool, all the JSPM, Configtool properties
    Check if this helps to resolve your problem, else I will have to recollect if I resolved it differently.
    Regards,
    Nilesh

  • Issue with deployment

    We tried deploying the component through JSPM, but JSPM is not working properly, so we are trying to deploy the software components through SDM.
         We have started to deploy the all the component together it is getting stuck after some time.
         We have started to deploy the component one by one it is still getting stuck after some time.
    Can anybody please help us out.
    Below is the  log.
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[G:\usr\sap\NWB\DVEBMGS00\SDM\program\log\sdmlog20090413.log]/>
    <!PATTERN[sdmlog20090413.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    Apr 13, 2009 3:02:25 PM  Info:
    Apr 13, 2009 3:02:25 PM  Info: ===============================================
    Apr 13, 2009 3:02:25 PM  Info: =   Starting to execute command 'remotegui'   =
    Apr 13, 2009 3:02:25 PM  Info: ===============================================
    Apr 13, 2009 3:02:27 PM  Info: SDM started successfully.
    Apr 13, 2009 3:06:12 PM  Info:
    Apr 13, 2009 3:06:12 PM  Info: ===============================================
    Apr 13, 2009 3:06:12 PM  Info: =   Starting to execute command 'remotegui'   =
    Apr 13, 2009 3:06:12 PM  Info: ===============================================
    Apr 13, 2009 3:06:14 PM  Info: SDM started successfully.
    Apr 13, 2009 3:06:48 PM  Info:
    Apr 13, 2009 3:06:48 PM  Info: ============================================
    Apr 13, 2009 3:06:48 PM  Info: =   Starting to execute command 'server'   =
    Apr 13, 2009 3:06:48 PM  Info: ============================================
    Apr 13, 2009 3:06:48 PM  Info: Starting SDM - Software Deployment Manager...
    Apr 13, 2009 3:06:48 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0009.20060817110748.0000
    Apr 13, 2009 3:06:49 PM  Info: ====================================
    Apr 13, 2009 3:06:49 PM  Info: JControl is shutting SDM Server down
    Apr 13, 2009 3:06:49 PM  Info: ====================================
    Apr 13, 2009 3:06:49 PM  Info: Server finished sending back the answer of the ShutdownRequest.
    Apr 13, 2009 3:06:49 PM  Info: Shutting dispatcher down
    Apr 13, 2009 3:06:54 PM  Info:
    Apr 13, 2009 3:06:54 PM  Info: ============================================
    Apr 13, 2009 3:06:54 PM  Info: =   Starting to execute command 'server'   =
    Apr 13, 2009 3:06:54 PM  Info: ============================================
    Apr 13, 2009 3:06:54 PM  Info: Starting SDM - Software Deployment Manager...
    Apr 13, 2009 3:06:55 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0009.20060817110748.0000
    Apr 13, 2009 3:06:57 PM  Info: SDM operation mode successfully set to: Integrated
    Apr 13, 2009 3:06:58 PM  Info: JStartupFramework is requesting to start the SDM Server.
    Apr 13, 2009 3:06:58 PM  Info: Start the SDM Server integrated in the JStartupFramework.
    Apr 13, 2009 3:06:58 PM  Info: Initializing Network Manager (50017)
    Apr 13, 2009 3:06:58 PM  Info: Starting SDM Server listening on port 50018
    Apr 13, 2009 3:06:58 PM  Info: SDM started successfully.
    Apr 13, 2009 3:08:44 PM  Info:
    Apr 13, 2009 3:08:44 PM  Info: ===============================================
    Apr 13, 2009 3:08:44 PM  Info: =   Starting to execute command 'remotegui'   =
    Apr 13, 2009 3:08:44 PM  Info: ===============================================
    Apr 13, 2009 3:08:45 PM  Info: SDM started successfully.
    Apr 13, 2009 3:11:44 PM  Info:
    Apr 13, 2009 3:11:44 PM  Info: ===============================================
    Apr 13, 2009 3:11:44 PM  Info: =   Starting to execute command 'remotegui'   =
    Apr 13, 2009 3:11:44 PM  Info: ===============================================
    Apr 13, 2009 3:11:45 PM  Info: SDM started successfully.
    Apr 13, 2009 3:11:52 PM  Info: Opened client connection to punitp02979 (IP address punitp02979/<ipaddress>, remote port 2561)
    Apr 13, 2009 3:11:52 PM  Error: Wrong password supplied - Request for Logon rejected. Remaining logon attempts until SDM server will be shut down: 2
    Apr 13, 2009 3:11:55 PM  Info: Close client connection to punitp02979/<ipaddress>, remote port 2561
    Apr 13, 2009 3:12:04 PM  Info:
    Apr 13, 2009 3:12:04 PM  Info: ===============================================
    Apr 13, 2009 3:12:04 PM  Info: =   Starting to execute command 'remotegui'   =
    Apr 13, 2009 3:12:04 PM  Info: ===============================================
    Apr 13, 2009 3:12:05 PM  Info: SDM started successfully.
    Apr 13, 2009 3:15:02 PM  Info:
    Apr 13, 2009 3:15:02 PM  Info: ===============================================
    Apr 13, 2009 3:15:02 PM  Info: =   Starting to execute command 'remotegui'   =
    Apr 13, 2009 3:15:02 PM  Info: ===============================================
    Apr 13, 2009 3:15:04 PM  Info: SDM started successfully.
    Apr 13, 2009 3:15:11 PM  Info: Opened client connection to punitp02979 (IP address punitp02979/<ipaddress>, remote port 2654)
    Apr 13, 2009 3:15:11 PM  Info: Request for Logon as admin accepted
    Apr 13, 2009 3:16:14 PM  Info: Loading archive 'G:\usr\sap\trans\EPS\in\BPMDMAPPLI06_4.sca'
    Apr 13, 2009 3:16:27 PM  Info: Actions per selected component:
    Apr 13, 2009 3:16:27 PM  Info: No action: Selected development component 'com.sap.mdm.uwl'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'1' will not update currently deployed development component 'com.sap.mdm.uwl'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'0'.
    Apr 13, 2009 3:16:27 PM  Info: No action: Selected development component 'com.sap.mdm.uwl.config'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'1' will not update currently deployed development component 'com.sap.mdm.uwl.config'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'0'.
    Apr 13, 2009 3:16:27 PM  Info: Initial deployment: Selected software component 'BP_MDM_APPLICATION'/'sap.com'/'SAP AG'/'1000.5.50.6.4.20090119093241''/'1' will be deployed.
    Apr 13, 2009 3:16:27 PM  Info: No action: Selected development component 'com.sap.pct.mdm.appl.masteriviews'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'1' will not update currently deployed development component 'com.sap.pct.mdm.appl.masteriviews'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'0'.
    Apr 13, 2009 3:16:27 PM  Info: Initial deployment: Selected development component 'com.sap.pct.mdm.appl.packages.mdm_550'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'1' will be deployed.
    Apr 13, 2009 3:16:37 PM  Info: Saved current Engine state.
    Apr 13, 2009 3:16:39 PM  Info: Starting: Initial deployment: Selected development component 'com.sap.pct.mdm.appl.packages.mdm_550'/'sap.com'/'SAP AG'/'5.50.20090119083803.0000'/'1' will be deployed.
    Apr 13, 2009 3:16:39 PM  Info: SDA to be deployed: G:\usr\sap\NWB\DVEBMGS00\SDM\root\origin\sap.com\com.sap.pct.mdm.appl.packages.mdm_550\SAP AG\1\5.50.20090119083803.0000\com.sap.pct.mdm.appl.packages.mdm_550.epa
    Apr 13, 2009 3:16:39 PM  Info: Software type of SDA: single-module
    Apr 13, 2009 3:16:39 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Module) *****

    Hi,
    You could check the most recent logs under the SDM log directory:
    <drive>:\usr\sap\<sid>\JC00\SDM\program\log
    esp ones like sdm_*.err. These normally contain information about issues related to memory while loading the archives for deployment. We had memory issue resulting in SDM getting hung.
    Hope it helps.
    Regards,
    Srikishan

Maybe you are looking for

  • Placed file turns grayscale - need it to be in color - help!

    I am faily new/inexperienced with photoshop.  I have created a new file and am trying to place an image that is in color.  When I place it, it turns grayscale.  Can someone please advise me on this?

  • Spell Check button doesn't work anymore

    When I click on "Spell Check" button, it seems all works fine, but as soon as I click on "Change" button, or "Go back/Edit" or "Post Message", I receive the following error message : Your spell session has expired - please go back to the posting page

  • It is possible not to delete a file temp.dbf

    Hello! Please help me in this question: - I recovery my database from full copy (simply restore from archive files) - Restoration became to return base as of yesterday - But in yesterday's full copy file temp.dbf (temporary tablespace) not exist - I

  • Google services

    Since version 22 of Firefox (now i'm on 25), very few links posted after google searches are working. I keep getting this message. "Firefox can't establish a connection to the server at www.googleadservices.com. The site could be temporarily unavaila

  • Compile error: Returning a local object to a reference variable

    Hi all... I just need to know that when I return from a function with a local object to a reference, I am getting a compile error (Error name is "badarglval2"). Actually I'm sure that the error is closely related to Sun Solaris Compiler. According to