SP-Stacks 10 theough JSPM in NW2004s

Hi,
   I have installed NW2004s and my Support Package Stack level is 9 & now i am tring to update it to SP-Stacks through JSPM but at check Queue i am error in  sap.com/SAP KERNEL & Status is REVISE.
Details Messages:
Kernel with support package level SAP KERNEL and version 7.00.236.0 that is located in
<HOSTNAME>\sapmnt\trans\EPS\in invalid. Kernel with patch level KERNEL UNICODE WINDOWS_X86_64 and version 7.00236.0 with archives names
<HOSTNAME>\sapmnt\trans\EPS\in\SAPEXEDB_236-20001361.SAR is invalid. Required archives SAPEXE.SAR are missing from Kernel archive set
<HOSTNAME>\sapmnt\trans\EPS\in\SAPEXEDB_236-20001361.SAR
For this i downloaded SAPEXE_236-20001354 & SAPEXEDB_236-200013612 to 3 time but everytime i am getting same error.
Its a java stand alone.
I also search SDN but not getting solution
Any idea?
Nayak

As the above error says it can not copy the files, Please check your windows permission for sidadm user.
Also try to update the jspm using the sdm directly, then update the other stack using the JSPM.
Thanks for help,
I think my JSPM updated to 21 bcoz as per advice when i am trying to updated JSPM through SDM it showing:
SDM has not calculated any deployment actions.
Possible reasons:
All selected archives have already been deployed before in the same or in a higher version.
But still now my JSPM not starting it showing following error:
D:\usr\sap\DEO\JC00\j2ee\JSPM>go.bat
Current log directory is D:\usr\sap\DEO\JC00\j2ee\JSPM\log\log_2010_03_23_13_06_
04.
Updating JSPM content...
com.sap.sdt.util.diag.DiagException: Could not check and update JSPM content.
Cannot copy D:\usr\sap\DEO\JC00\j2ee\JSPM\deploy\config to directory D:\usr\sap\
DEO\JC00\j2ee\JSPM.
Cannot copy D:\usr\sap\DEO\JC00\j2ee\JSPM\deploy\config to D:\usr\sap\DEO\JC00\j
2ee\JSPM\config using Windows console operation. 1
        at com.sap.sdt.jspm.bootstrap.Bootstrap.migrate(Bootstrap.java:486)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.main(Bootstrap.java:272)
        at Jspm.main(Jspm.java:28)
Caused by: com.sap.sdt.tools.io.SdtFileException: Cannot copy D:\usr\sap\DEO\JC0
0\j2ee\JSPM\deploy\config to D:\usr\sap\DEO\JC00\j2ee\JSPM\config using Windows
console operation. 1
        at com.sap.sdt.tools.io.win.WinFileOperation.copyDirectory(WinFileOperat
ion.java:235)
        at com.sap.sdt.tools.io.win.WinFileOperation.copyToDir(WinFileOperation.
java:195)
        at com.sap.sdt.tools.io.SdtFile.copyToDir(SdtFile.java:577)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.copyContent(Bootstrap.java:780)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.copyNewApplicationContent(Bootst
rap.java:729)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.migrate(Bootstrap.java:478)
        ... 2 more
com.sap.sdt.tools.io.SdtFileException: Cannot copy D:\usr\sap\DEO\JC00\j2ee\JSPM
\deploy\config to directory D:\usr\sap\DEO\JC00\j2ee\JSPM.
Cannot copy D:\usr\sap\DEO\JC00\j2ee\JSPM\deploy\config to D:\usr\sap\DEO\JC00\j
2ee\JSPM\config using Windows console operation. 1
        at com.sap.sdt.tools.io.SdtFile.generateSdtFileException(SdtFile.java:87
2)
        at com.sap.sdt.tools.io.SdtFile.copyToDir(SdtFile.java:582)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.copyContent(Bootstrap.java:780)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.copyNewApplicationContent(Bootst
rap.java:729)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.migrate(Bootstrap.java:478)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.main(Bootstrap.java:272)
        at Jspm.main(Jspm.java:28)
Caused by: com.sap.sdt.tools.io.SdtFileException: Cannot copy D:\usr\sap\DEO\JC0
0\j2ee\JSPM\deploy\config to D:\usr\sap\DEO\JC00\j2ee\JSPM\config using Windows
console operation. 1
        at com.sap.sdt.tools.io.win.WinFileOperation.copyDirectory(WinFileOperat
ion.java:235)
        at com.sap.sdt.tools.io.win.WinFileOperation.copyToDir(WinFileOperation.
java:195)
        at com.sap.sdt.tools.io.SdtFile.copyToDir(SdtFile.java:577)
        ... 5 more
com.sap.sdt.tools.io.SdtFileException: Cannot copy D:\usr\sap\DEO\JC00\j2ee\JSPM
\deploy\config to D:\usr\sap\DEO\JC00\j2ee\JSPM\config using Windows console ope
ration. 1
        at com.sap.sdt.tools.io.win.WinFileOperation.copyDirectory(WinFileOperat
ion.java:235)
        at com.sap.sdt.tools.io.win.WinFileOperation.copyToDir(WinFileOperation.
java:195)
        at com.sap.sdt.tools.io.SdtFile.copyToDir(SdtFile.java:577)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.copyContent(Bootstrap.java:780)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.copyNewApplicationContent(Bootst
rap.java:729)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.migrate(Bootstrap.java:478)
        at com.sap.sdt.jspm.bootstrap.Bootstrap.main(Bootstrap.java:272)
        at Jspm.main(Jspm.java:28)
ERROR: could not update JSPM
Press any key to continue . . .
Can anyone help me
Regards
Manoj

Similar Messages

  • Stack File for JSPM when using Maintenance Optimizer

    Hello,
    As you know JSPM looks for a stack file when applying a support pack stack.  When using maintanance optimizer I see no way to get a stack file.  I end up having to do the work twice:  once to get the files in maintenance optimizer, and again I have to go to marketplace swdc to choose the files and create the list of downloads again only to save a stack file.
    Am I missing something?  Is this double work really necessary?

    Hello John,
    It seems that you are doing double work.
    If you use the download type as "SLM" then you have a chance to transfer the XML to SLM. Else if you choose the download type as "Download Manager" then the XML should be created in the EPS/in folder of the Solution Manager system.
    You also need to check whether you have applied all the applicable notes for the Solution Manager stack from the note 1122966 and that the BC sets for MOPZ are activated correctly.
    Finally check the permissions on the EPS/in folder of Solution Manager to check whether there is a issue with authorizations.
    A SLG1 log ( filtered by the username who creates the MOPZ transaction and time at which the transaction was created ) will reveal the errors in the process.
    Regards
    Amit

  • Problems with JSPM upgrading NW2004S to SP11

    Hi,
    I am really frustrated with JSPM
    I've installed the sneak preview NW2004S and ran JSPM to upgrade it to SP11.
    After 3 days of trials, I was able to get it to the point where it installed part of the SP11 pack.
    Now it is stuck at EBPC. It gives the error that portal container runtime is not running. The server is running in safe mode.
    I tried to restart the server in normal mode and retry it - but JSPM puts the server back to safe mode.
    Any suggestions

    I did not finally resolve the SP11 problem since SP12 was released on 5/25.
    I'm installing SP12 instead.
    Lessons learnt:
    1. For some apps like EPBC, its easier to deploy directly with the SDM rather than JSPM.
    2. Sneakpreview has extra apps that conflict with applying SP12 patch
    so
    Undeploy sap.com/TestSuiteUUIE and sap.com/cafUIptn~common
    otherwise
    Message : Failed to deploy application 'sap.com/tc~wd~samples~testsuite~uuie' for deployment state listener 'com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook'.
    [EXCEPTION]
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'E:usrsapJ2EJC01j2eeclusterserver0.tempwebdynpropublicsap.comtc~wd~samples~testsuite~uuiewebdynproApplicationscom.sap.tc.webdynpro.tests.uuie.TestSuiteUUIETestSuiteUUIE.xml' into the database. Reason: Development Object 'sap.com/TestSuiteUUIE' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
         at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
         at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
         at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
         at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)

  • Error while updating JAVA stack patchs

    hi i was updating JAVA stack patches from JSPM. and i got this error
    10/12/09 15:53:33 -  Start updating EAR file...
    10/12/09 15:53:33 -  start-up mode is lazy
    10/12/09 15:53:33 -  EAR file updated successfully for 118ms.
    10/12/09 15:53:33 -  Start deploying ...
    10/12/09 15:53:41 -  EAR file uploaded to server for 7537ms.
    10/12/09 15:53:43 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
                         Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
                            com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                            at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:569)
                            at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                            at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                            at java.security.AccessController.doPrivileged(AccessController.java:207)
                            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
                         Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                            at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1052)
                            at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                            at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                            at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                            at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                            at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                            at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3187)
                            at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
                            at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                            at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                            at java.security.AccessController.doPrivileged(AccessController.java:207)
                            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    predecessor system -
                         com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                            at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1052)
                            at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                            at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                            at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                            at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                            at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                            at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3187)
                            at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
                            at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                            at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                            at java.security.AccessController.doPrivileged(AccessController.java:207)
                            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
                         For detailed information see the log file of the Deploy Service.
    10/12/09 15:53:43 -  ***********************************************************
    Dec 9, 2010 3:53:43 PM   Info: End of log messages of the target system.
    Dec 9, 2010 3:53:43 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Dec 9, 2010 3:53:43 PM   Error: Aborted: development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0013.20070703112808.0000'/'8', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214121635''/'7':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
    Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
            com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Dec 9, 2010 3:53:43 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:43 PM   Info: Finished saving the repository for 205 ms.
    Dec 9, 2010 3:53:43 PM   Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214121635''/'7' will be deployed.
    Dec 9, 2010 3:53:43 PM   Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214121635''/'7':
    Failed deployment of SDAs:
    development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0013.20070703112808.0000'/'8' : aborted
    Please, look at error logs above for more information!
    Dec 9, 2010 3:53:43 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:43 PM   Info: Finished saving the repository for 209 ms.
    Dec 9, 2010 3:53:43 PM   Info: Starting: Update: Selected software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214120518''/'7' updates currently deployed software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210170522''/'0'.
    Dec 9, 2010 3:53:43 PM   Error: Aborted: software component 'BI_UDI'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214120518''/'7':
    No further description found.
    Dec 9, 2010 3:53:43 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:44 PM   Info: Finished saving the repository for 313 ms.
    Dec 9, 2010 3:53:44 PM   Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100118105934''/'7' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210162941''/'0'.
    Dec 9, 2010 3:53:44 PM   Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100118105934''/'7':
    No further description found.
    Dec 9, 2010 3:53:44 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:44 PM   Info: Finished saving the repository for 229 ms.
    Dec 9, 2010 3:53:44 PM   Info: Starting: Update: Selected software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20100122081155''/'5' updates currently deployed software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'0'.
    Dec 9, 2010 3:53:44 PM   Error: Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20100122081155''/'5':
    No further description found.
    Dec 9, 2010 3:53:44 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:44 PM   Info: Finished saving the repository for 210 ms.
    Dec 9, 2010 3:53:44 PM   Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100118110644''/'7' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P14_C'/'1000.7.00.14.1.20080124101556''/'0'.
    Dec 9, 2010 3:53:44 PM   Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100118110644''/'7':
    No further description found.
    Dec 9, 2010 3:53:44 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:45 PM   Info: Finished saving the repository for 353 ms.
    Dec 9, 2010 3:53:45 PM   Info: Starting: Update: Selected software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214204516''/'5' updates currently deployed software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210194048''/'0'.
    Dec 9, 2010 3:53:45 PM   Error: Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214204516''/'5':
    No further description found.
    Dec 9, 2010 3:53:45 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:45 PM   Info: Finished saving the repository for 213 ms.
    Dec 9, 2010 3:53:45 PM   Info: Starting: Update: Selected software component 'SAP-EU'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100118101502''/'5' updates currently deployed software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'0'.
    Dec 9, 2010 3:53:45 PM   Error: Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100118101502''/'5':
    No further description found.
    Dec 9, 2010 3:53:45 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:45 PM   Info: Finished saving the repository for 213 ms.
    Dec 9, 2010 3:53:45 PM   Info: Starting: Update: Selected software component 'VCFLEX'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214204617''/'5' updates currently deployed software component 'VCFLEX'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210153724''/'0'.
    Dec 9, 2010 3:53:45 PM   Error: Aborted: software component 'VCFLEX'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214204617''/'5':
    No further description found.
    Dec 9, 2010 3:53:45 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:45 PM   Info: Finished saving the repository for 331 ms.
    Dec 9, 2010 3:53:45 PM   Info: Starting: Update: Selected software component 'VCFRAMEWORK'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214204625''/'5' updates currently deployed software component 'VCFRAMEWORK'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210153730''/'0'.
    Dec 9, 2010 3:53:45 PM   Error: Aborted: software component 'VCFRAMEWORK'/'sap.com'/'SAP AG'/'1000.7.00.21.0.20091214204625''/'5':
    No further description found.
    Dec 9, 2010 3:53:45 PM   Info: Starting to save the repository
    Dec 9, 2010 3:53:46 PM   Info: Finished saving the repository for 230 ms.
    Dec 9, 2010 3:53:46 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Dec 9, 2010 3:53:46 PM   Error: -
    At least one of the Deployments failed -
    lgsep:/usr/sap/LEP/JC00/SDM/program/log #

    Hi ,
    Please check :
    https://wiki.sdn.sap.com/wiki/display/WDJava/Clusterwideexception-FailedtodeployWebDynprocontentforapplication
    Regards,
    Nibu Antony
    Edited by: Nibu Antony on Dec 13, 2010 2:52 PM

  • Restarting JSPM with different options

    I get the error 'Cannot find AAS usage in all usages array' when applying Support Package Stack 15 in JSPM
    I would like to apply SAPJTECHS SP16 as instructed in note 1231975 to fix this issue.
    However, JSPM fails immediately after login without giving me any options.
    Is there a way to 'reset the JSPM inport queue' or to force JSPM to give me options instead of going straight to reimporting and failing?
    Regards,
    Aubrey Smith

    Aubrey,
    I am facing the same issue.   How did you resolve?
    Thanks,
    Jeff

  • PI 7.0 Service pack level

    In PI 7.0 system
    SXMB_IFR    > Integration repository > logon as PISUPER > from menu bar     help > Information
    If you do the above it shows a pop up screen
    SAP Netweaver
    Exchange infrastructure
    System information
    Application :Design : Integration builder
    User          : pisuper
    Language   : English
    Server        : hostname_sid_00
    Server node: server 0
    Runtime enviroinment
    Java version  1.6.0_05
    Java vendor  Sun micro system
    Version
    Service pack  9 
    Release 645_VAL_REL
    Latest change 378089
    Sync time $(sync time)
       Now I have to increase the Service pack from 9 to 12
    What Should I do for this and how to do.Please tell me the procedure.I would be grateful for your help

    PI7.0 contains both ABAP & JAVA stack.
    You must upgrade patch level 9 to 12 for both stack.
    Only JSPM upgrade is not enough. go through service.sap.com/sp-stacks and see patch level for each components  for ABAP & JAVA stack.
    1st upgrade ABAP patches then go for Java patches.

  • NW App Svr dies with SP06 upgrade

    Hi,
    I have NW04s SP04 version of developer workplace
    on my box.
    I am upgrading to NW04s SP06.      
    Using JSPM, I have deployed NW04s-SP06 versions of JSPM, UC kernel,
    IGS, SAP-JEE and SDMKIT.jar. After SAP-JEE was deployed successfully,          
    I tried deploying SAP-JEECOR which failed to deploy.
    Now when I start j2ee server using SAP MMC, J2EE engine crashes
    with exit code -11113.
    SDM and dispatcher still start successfully in SAP MMC.
    JVM heap is 1024M. My box has 2GB RAM.
    I, still, have to deploy SP06 packages like core tools, base tables,
    DI files, logview, buildt, jtech ones, ume, caf eu, iks, NWDS,
    etc, etc.                  
    I cannot deploy any more SP06 stack packages. Everything has come              
    to a DEAD HALT. My objective is to have full fledged j2ee engine with          
    usage types DI, EP and CRM 5.0 for NW04s SP06.
    Appreciate your help. I need to get Nw04s SP06 working on my box.
    I have generated an internal message: 304072.            
    I researched and researched  but no light at the end of tunnel.
    Thank you.
    -shashank date

    Hello,
    In order to continue the patching please go to the JSPM direcotry and open JSPM\config\dodf.xml file. There the order of compoents are describe.Please follow the order that si desribed there or deploy compoents below:
    SAP_JAVASL
    BASETABLES, CORE-TOOLS, JLOGVIEW, SAP-JEE, SAP-JEECOR, SAP_JTECHF
    ADSSAP, ADSSAPOFF, BI_MMR, BI_UDI, KM-KW_JIKS, SAP_JTECHS, LM-TOOLS, CAF, CAF-UM, UMEADMIN
    If would like not to care about the order of compoents, then download the SPStack for your usage type from the SMP and select to apply a support package stack from the JSPM.
    More info you could find on http://service.sap.com/jspm
    Best regards
    Nina
    JSPM Development team

  • Patch of SOLMAN to SPS 15

    Hi!
    I ahve the problem to patch SOLMAN from SPS 13 to SPS 15.
    When I try to patch them the following error appears:
    Please include the CRT for ...
    Can some one describe  the order of patch of components or to tell how do I get the appropriate CRT?
    Thank you very much!
    regards
    Thom

    Hi Thom,
    Here is a time table for applying SPS from 13 to 15
    1.) Make a database backup
    2.) Stop CI und DB. Then change the kernel. Start DB and CI
    3.) Apply latest SPAM/SAINT patch
    4.) Apply OSS Note 1075012 before continue
    5.) Apply SP13
    6.) SAINT upgrade to ST-SER 700_2008_1
    7.) Apply SP14 and 15
    8.) Finally apply OSS Note 1128026
    9.) If needed apply Java Stack 15 via JSPM on OS level
    Remarks:
    If you are starting from SP12 then you first have to apply OSS Note 1042866. Direct after do an upgrade via SAINT to ST-SER 700_2007_1. Afterwards apply SP12 via SPAM and continue at topic 1.).
    Before starting you should set dynamically the profile parameter rdisp/max_wprun_time to 3000 seconds via transaction RZ11. Make sure you have always 2.5GB free space in directory /usr/sap/trans.
    Cheers, Ingo.

  • How Do I Apply Maintenance To A NetWeaver Developer Workplace Instance?

    I have NetWeaver 7.0 Developer Workplace installed on my Windows XP workstation.  The current support package level is 09.  I want put on support package level 15.  Should I install Support Package Stack 15 with JSPM, or should I maintain the individual components with SDM?  Is there some better way to apply maintenance to Developer Workplace?
    Thanks,
    Michael

    hi
    i think it will be better if you install sp stack 15 with jspm.
    refer this blog.
    Installing Additional Usage Types on NetWeaver 7.0 AS Java Using JSPM
    JSPM: Better Know It Now Than Later

  • NW2004s: SPS installation for dual-Stack-Installation (Java/ABAP) - PI(XI)

    Hello,
    we want to apply a new SP stack to a NW2004s (ECC 6.0) - dual stack (Java/ABAP) with PI(XI).
    The ABAP stack is sucessfully patched yet,
    but the Java stack needs still to be patched!
    In the SPS guide for SPS 9 and some OSS notes you can read that during the patching of the Java stack, the whole system (ABAP and Java engine) are restarted several times. But the JSPM should ask you before the restart.
    Do you have experiences how long the patching of the Java stack will take (downtime)?
    How often needs the system to be restarted?
    Is it possible to work with the ABAP engine (ABAP development, etc.) during the installation of the Java SPS with JSPM until the system needs to be restarted?
    How is it possible to minimize the downtime of the system during the Java SPS installation?
    Thanks in advance!
    Best regards,
    Stephan

    Hi Stephan,
    "Do you have experiences how long the patching of the Java stack will take (downtime)?"
    I believe this is most highly dependent on the hardware.  Although some patches will deploy more objects than others, the deploy time is shorter on better/faster hardware.  I applied SP9 on my laptop PC (java only, no ABAP stack) and it took a few hours total -- including my processing and error correcting time.  My laptop has only 2 GB RAM so this process was greatly slowed by the amount of available memory (I was running other applications, like Outlook, etc.) resulting in a lot of disk swapping.
    "How often needs the system to be restarted?"
    Again, I have a java only installation, no ABAP, but I believe there was only 1-2 system restarts.  The system had to be restarted after the application of the java kernel part of the patch, then shutdown and restarted again for the offline deployment phase.  I cannot remember if there was a restart after the online deployment phase.
    "Is it possible to work with the ABAP engine (ABAP development, etc.) during the installation of the Java SPS with JSPM until the system needs to be restarted?"
    Yes.
    "How is it possible to minimize the downtime of the system during the Java SPS installation?"
    I think the best way is to have the best hardware!  Also, be sure to be thoroughly prepared by reading the guide, all of the Notes, etc.  I was slowed by a previously correctable error (my administrator password had been previously changed and I had not changed it in the secure store -- Note 701654).
    Best Regards,
    Matt

  • JSPM error in NW2004s SR1 installation

    Hi,
    I have just freshly installed NW2004s Application Server SR1. Then I tried to run JSPM to patch it up. When logging onto SDM as the first screen in JSPM, I got the following error:
    The execution ended in error.
    com.sap.sdt.util.diag.DevelopmentSupportRequiredException: Assertion failed for (Could not parse version string content. For input string: "${SP-Patchlevel}") at com.sap.sdt.util.diag.SDT.check(SDT.java:36).
    More information can be found in the log file C:\usr\sap\JAV\JC01\j2ee\JSPM\log\log_20060727155309\JSPM_PROCESS_1_01.LOG.
    When I looked at the JSPM_PROCESS_1_01.log, I found the followings at the bottom of the log:
    #1.5#C000C0A801650000000000AE0037FB1E000419908952E9A0#1154008476740#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#aborted#
    I've already had my JAVA_HOME and PATH set already, and they both point to the same JDK (which is the only JDK I have in the machine). SDM doesn't seem to have problems as I can logon with the remoteGUI in SDM. Does anyone have any idea what's wrong or what I'm missing?
    Thanks,
    Marc

    Hello Marc,
    I ran into the same issue. After a lot of trial and error I eventuelly found out, was the problem was...
    I had to do two things to resolve this:
    1. Download the XML file containing the SP stack definition:
    -You'll find the instructions for downloading this file on the Support Package Stacks Download Page for NW2004s in the box 'Additional information'.
    -Put the XML file in the JSPM inbox (Folder '/usr/sap/trans/EPS/in' on a standard installation).
    2. Update the SDM:
    -Download the file with the description 'SP07 for SAP SOFTW. DELIV. MANAGER 7.00' from the Support Package Stacks Download Page
    -SAP Note 860939 explains how to update the SDM
    Hope this helps...
    Regards,
    Bjoern

  • Error in JSPM to try update stack java.

    Hi. sdn team.
    We have problem with JSPM . The problem it's  .
    I try to validate error in LOG FILE  "   E:\usr\sap\SME\DVEBMGS01\SDM\program\log\sdmcl20090729210415.log"
    INTO FILE:
    Jul 29, 2009 9:04:22 PM  Error: Aborted: development component 'tc/sec/ume/wd/approval'/'sap.com'/'MAIN_APL70VAL_C'/'1219306'/'0', grouped by software component 'UMEADMIN'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.16.0.20080610192745''/'0':
    Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
    com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
    i try to search notes fot this problem and validate the next notes:
    Note 1228507 - Config Tool does not properly save password in Secure Store
    Note 701654 - Deployment aborts due to wrong J2EE Engine login information
    Apply this notes recomended in this forum. my system not response with this change.
    in another link of this forum recomenden execute apply this stacks in level Operating System
    We try apply stack of java in leve OS with the next comands:
    in sapmmc disable process SDM
    sdm jstartup "mode=standalone"
    sdm deploy "file=E:\usr\sap\trans\EPS\in\ADSSAP16_0-10003001.SCA" "updateVersions=all"
    But send the next error:
    Upload information in adobe-XMLForm.sda file.
    Processing...
    Processing error. Return code: 4
    Pease HELPME The session of configuracion it's for 17Ago, and we  need SP18 READY.
    BEST REGARDS
    LUIS CUPA
    Edited by: Luis Isaac Cupa Rosales on Jul 30, 2009 1:14 AM
    Edited by: Luis Isaac Cupa Rosales on Jul 30, 2009 1:16 AM

    Hi Sunny and Debasis Sahoo
    tks for you response, but i try to change passwords in secure store in configtool,
    change: admin/password/<SID> in configtool and restart all server.
    in transaction SU01 the user J2EE_ADMIN is not found this user is create with sap_all and password equal to value in parameter in secure store in configtool.
    Reset Server, and try execute DEPLOY of componnent sap.com/ADSSAP
    and send the next error:
    Jul 30, 2009 10:14:35... Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'5', grouped by :
    Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
    com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
    PLEASE HELPME
    Note: " Note: " in tool visual Administrator,  it's necesary connect with user SAP* to connect, validate in configtool and this user it's active.
    the password in tool visual administrator to user default <sid>adm  (use value change in secure store )  it's not valid " "
    Regards,
    Luis Cupa.

  • Update Java Support Package Stack in JSPM

    Hi all,
    When i update Java Support Package Stack in JSPM i can't start the dispatcher
    [Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 920] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 920] JLaunchCloseProgram: good bye (exitcode = -11113)
    When i goto the log-file of the dispatcher (server.0.log):
    E:
    usr
    sap
    P01
    DVEBMGS01
    j2ee
    cluster
    dispatcher
    bin
    services
    log_configurator
    log_configurator.jar
    Loading model: {parent,local,references}
    The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
         at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
         at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
         at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
    #1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
    #1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
    Somebody know how to solve this problem?
    Thanks in advance,
    Cheung

    defaulttrc.0.trc"
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[0, 2, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.1.trc]/>
    <!NEXTFILE[defaultTrace.1.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
    #1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
    #1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
    #1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
    #1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
    #1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
    #1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
    #1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
    #1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
    #1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
    #1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
    #1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
    #1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
    #1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
    #1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
    #1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
    #1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
    #1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
    #1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
    #1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
    #1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#
    #1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
    #1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
    #1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
    #1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
    #1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
    #1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
    #1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
    #1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
    #1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
    #1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
    #1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
    #1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
    #1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
    #1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
    #1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
    #1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
    #1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
    #1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
    #1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
    #1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
    #1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#

  • JSPM - applying SP stacks

    Hi Guys,
    I have just installed As Java 2004s + EP and it is at SP6. Now, i want to
    update it to SP8. I have downloaded the stack 8.
    I know JSPM is used to apply the stack. According to the documentation i
    have,all the files have to be placed in the usr/sap/trans/EPS/in and then
    applied.
    But do these SCA files need to be extracted with sAPCAR like the kernel SAR
    files?
    What steps need to be done before starting JSPM and what steps after?
    Can someone throw some light?
    Regards
    Cyrus

    Hi Cyrus,
    No other considerations. Just place them in EPS\in as
    stated by Costas. Login as <sid>adm and run go.bat from
    .../j2ee/JSPM/ folder. It shows the list where you
    select the target SP level for the component. Its
    recommended to update <i>only jspm</i> first and restart it and then the other components.
    Regards
    Srikishan

  • Change R/3 client after EP7 / NW2004s double stack installation (UME settin

    Hello everyone,
    we have install NW2004s with choosing usage type EP as double stack installation (means ABAP and Java) and using SAP R/3 as user persistence. At the install point, only the client 001 is known / can be used. After the installation (EP test runs without errors) we do a client copy to create a ABAP client (100) for usage as CUA/ User store. Later we patch also the ABAP and Java to SP6. Now the UME settings of the EP ar still pointing  to the client 001. But we want to use the client 100. Question is, where should we change the client -> in the Portal, system administration -> system configuration -> UME configuration -> R/3 or in the visual administrator of the WAS ?? Is there some concerns to change this HUME settings ?? (means JAVA will hangs or.... ?? Have any body some experience with this or tips ??
    thanks
    mario

    Hi Luis,
    yes this works with no Problems. Following steps you should take / recomended to do:
    1. take your ABAP client Copy from Client 001 to your new Client on which now resident your UME
    2. look if all EP related User (J2EE_admin, maybe ADS_user..) and also the User which you have created are copy to the new client
    3. Go in the Portal to System Administration, SystemConfiguration, then UME Settings, and Change in the SAP Config the Client 001 to your new Client. Before Save take a connection test
    4. Aslo you can do this Change with the visual Admin, but we do this in the EP System Admin iView
    5. Restart the Portal / WAS
    Tipp: If the connection-test faild later (we had this also) it works nevertheless o.k. as long you had the right settings - maybe thats a bug in the UME settings of SPS6
    mario

Maybe you are looking for

  • Error"This order cannot be processed"is appearing  while saving in QA32

    Hi Experts, When I am going for Qa32 transaction after UD code selection I did stock posting, while saving QA32 transaction one error is occuring "Order cannnot be processed". For material inspn type 13 is active. in the last financial year that is t

  • How do I add SRV record to my DNS for Office 365?

    How do I add the following record? Add the SIP SRV record for Lync web conferencing. Create a new SRV record. In the new record, make sure that the fields are set to precisely the following values: Record Type: SRV Service: _sip Protocol: _tls Port:

  • How do i connect to a database in ssxa(site studio external application)

    Hi, I'm working with jdev11g 11.1.1.6, and im using oracle UCM 11g R1 server, i installed the ssxa patch to my jdev... im new to it could somebody helps me to connect to he data base from my application... Its very important in my project..

  • Incorrect pdf dimension shown in Bridge CS3

    I didn't see that this problem has been posted previously, but the dimensions shown for pdf documents in Bridge are much smaller than the actual document dimensions. It would be nice if I could confirm the page dimensions without opening a pdf in Acr

  • Material Scrapping - Profit Centre

    Great Gurus we have define Profit Centre for each finish material. while scrapping the material . T-Code: MB1A , Movement type : 551 Selecting Cost Centre  xxxx. Profit Centre comes automaically. that is Profit Centre for Plant. Now requirement is ho