Upgrade EP6 SP11 to EP6 SP13 - SDM Return Code: 4

Hi,
We are installing EP6 Sp13 on our existing Ep6 SP11 and we are getting the below error during the installation phase "Deploy via SDM/J2EE".  Error is as shown in the
callSdmViaSapinst.log :
05/09/29 14:14:10 -  ***********************************************************
05/09/29 14:14:11 -  Start updating EAR file...
05/09/29 14:14:11 -  start-up mode is lazy
05/09/29 14:14:11 -  EAR file updated successfully for 218ms.
05/09/29 14:14:11 -  Start updating...
05/09/29 14:14:11 -  EAR file uploaded to server for 110ms.
05/09/29 14:14:13 -  ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.connectors.sap..
                     Reason: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:592)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                          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(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.connectors.sap in container connector.
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:382)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:379)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:148)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3033)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:580)
                          ... 10 more
                     Caused by: java.lang.NullPointerException
                          at com.sap.engine.services.connector.jca.deploy.DeployAdmin.mergeDescriptorsConfigProps(DeployAdmin.java:3068)
                          at com.sap.engine.services.connector.jca.deploy.DeployAdmin.mergeDescriptors(DeployAdmin.java:2976)
                          at com.sap.engine.services.connector.jca.deploy.ContainerImpl.makeUpdate(ContainerImpl.java:736)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:376)
                          ... 16 more
                     For detailed information see the log file of the Deploy Service.
Thanks.
regards,
Mike

Hi Mike,
I would first try to stop the installation and start again to see if it continues for where it stopped.
If this do not works, I would try to stop the patch upgrade,
start the SDM and undeploy the com.sapportals.connectors.sap.sda, stop again the SDM and then restart the upgrade.
You also might like to check the SAP Notes 841299, 751175, 750360, 710966 as your problem seems to be related to the sap connectors.
Hope this helps,
Robert

Similar Messages

  • NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews

    We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
    ECC5.0
    Abap Stack
    EP6 SP13
    Java Stack
    latest versions of MSS and ESS BPs
    The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
    With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
    Any help on this will be greatly appreciated.
    Thanks in advance.
    Regards, Neeta

    Hi,
    Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
    http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
    The error message I get is (rather long....):
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
        ... 53 more
    See full exception chain for details.
    Correction Hints
    Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
    Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
    Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    Version 
    DOM version 
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
    J2EE Engine 6.40 patchlevel 95420.313
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system SunOS, version: 5.10, architecture: sparcv9
    Other
    Session Locale en_US
    Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwddispwda
    No information available
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwdcorecomp
    No information available
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 50 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
         ... 53 more
    Thanks, Neeta

  • Upgrade Ep6 to NW04s portal - deploy error

    I am upgrading our EP 6 system to NW04s w/Portal. Java AS only. No ABAP. In the DEPLOY_ONLINE phase it is stopping after about 2 hours.
    When I restart it, from the logs it appears to be restarting from the beginning instead of where it stopped. But I can't find the true cause of why it's stopping in the first place.
    My arch logs are not full and my tablespaces are ok, so the DB didn't fill up with anything more than it should.
    The logs show that most items were deployed, even though with warnings.  2 errored out, although I can't find why in the detailed logs:
    Aug 4, 2006 12:10:42 PM  Info: Summarizing the deployment results:
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/ADSSAP08_0-10003001.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIIBC06_0.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/BIWEBAPP06_1.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIMMR08_0-10002782.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIUDI08_0-10002781.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5***03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUA03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUY02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5COM02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5DCO02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5ESS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5HRA03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5INV02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MTC02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PLA02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PRS02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5QIN02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SAL02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SUP02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAF08_0-10003464.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFKM08_0-10003478.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFUM08_0-10003472.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPPSERV08_0-10003474.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPWDC08_0-10003557.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPBC208_0-10003489.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/FSCMBD03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/ISHERCSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMKWJIKS08_0-10003021.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCBC08_0-10003491.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCM08_0-10003492.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCOLL08_0-10003493.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMPORTAL08_0-10003487.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMTOOLS08_0-10003486.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/NETPDK08_0-10003351.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/RTC08_0-10003494.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/RTCSTREAM08_0-10003488.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPCRMDIC03_0.sca
    Aug 4, 2006 12:10:42 PM  Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPEU08_0-10003026.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPCUIGP03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPASR03_0.sca
    Aug 4, 2006 12:10:42 PM  Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPESS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPMSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/UMEADMIN08_0-10003471.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/UWLJWF08_0-10003490.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCBASE08_0-10003602.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCFLEX08_0-10003616.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCFRAMEWORK08_0-10003624.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITGP08_0-10003617.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITXX08_0-10003615.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/WDEXTENSIONS08_0-10003618.SCA
    Aug 4, 2006 12:10:42 PM  Error: Processing error. Return code: 4

    Hello,
    We are having the exact same issue when DEPLOY_ONLINE encounters WDEXTENSIONS08_0-10003618.SCA as part of the NW2004s upgrade process.
    We just submitted an OSS message to SAP about it --- but I am wondering if you have received a solution already? 
    Is this a bad support package that SAP released?

  • Upgrade from SP11 to SP14

    Hi All,
    I'm currently trying to upgrade from SP11 to SP14. I started with upgrading the J2EE Engine.
    Whe doing so the Installation stops at step 17 with the
    following error message in log-file callSdmViaSapinst.log:
    ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
                         Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
    Has anybody encountered a similar problem and can help me?
    Thanks,
    Stephan

    Hi Vasu,
    here is the complete StackTrace as found in callSdmViaSapinst.log. I hope this is what you meant by installation path. BTW, restarting the installation didn't help.
    Regards,
    Stephan
    05/12/12 14:24:31 -  ***********************************************************
    05/12/12 14:24:36 -  Start updating EAR file...
    05/12/12 14:24:36 -  start-up mode is lazy
    05/12/12 14:24:39 -  EAR file updated successfully for 2766ms.
    05/12/12 14:24:39 -  Start deploying ...
    05/12/12 14:24:42 -  EAR file uploaded to server for 2547ms.
    05/12/12 14:24:56 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
                         Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].; nested exception is:
                              com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
                              at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
                              at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
                              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:387)
                              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:290)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
                              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:294)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                              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(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
                         ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
                              at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
                              at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
                              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:387)
                              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:290)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
                              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:294)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                              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(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:482)
                              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:294)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                              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(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
                         Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
                              at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
                              at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
                              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:387)
                              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:290)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
                              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:294)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                              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(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
                         ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
                              at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
                              at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
                              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:387)
                              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:290)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
                              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:294)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                              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(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
                              at com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException.writeReplace(WebDeploymentException.java:99)
                              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                              at java.lang.reflect.Method.invoke(Method.java:324)
                              at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
                              at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
                              at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
                              at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
                              at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
                              at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
                              at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:135)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:296)
                              ... 8 more
                         For detailed information see the log file of the Deploy Service.
    05/12/12 14:24:56 -  ***********************************************************
    Dec 12, 2005 2:24:56 PM  Info: End of log messages of the target system.
    Dec 12, 2005 2:24:56 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Dec 12, 2005 2:24:56 PM  Error: Aborted: development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050606164207.0000':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
    Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].; nested exception is:
         com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
         at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
         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:387)
         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:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
         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:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
         at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
         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:387)
         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:290)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
         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:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Dec 12, 2005 2:24:57 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Dec 12, 2005 2:24:57 PM  Info: --------------- Deployment was successful -----------------
    Dec 12, 2005 2:24:57 PM  Info: Summarizing the deployment results:
    Dec 12, 2005 2:24:57 PM  Error: Admitted: D:TempSAP_SP14J2EE-RUNT-CDJ2EE-ENGONLINESAPJTECHS14_0.SCA
    Dec 12, 2005 2:24:57 PM  Error: Processing error. Return code: 4

  • After upgrading to Lion the bookmarks in Preview returns error message.

    After upgrading to Lion the bookmarks in Preview returns error message : The File "****" couldn't be opened because you don't have permission to view it. To change the perimssion, select the item in finder and Choose File info.  I have bookmarked plenty of files in Preview.  How to overcome this error message???

    Doesn't work Steve. I think it is an issue with Preview being sandboxed (check the sandbox column in Activity Monitor: Preview = Yes). Sandboxed apps restrict file access to those the user has explicitly selected. My theory is that this causes the unfortunate side effect of bookmarked or linked PDFs not working. A simple test: open a file with bookmarks, manually open the bookmarked file and then select the bookmark in the first file - it should open with no complaints about permissions (which leads to a weak workaround: open all the PDFs you intend to work with!).

  • ECC 6 Upgrade Error : RETURN CODE in RSVBCHCK.DV2

    Dear all,
    We are doing an upgrade from 4.6c to ECC6.0, we have faced the below error (warnings) in the CHECKS.LOG file.
    A2EEMCEX 151 Entries for application "03" still exist in the extraction queue ->
      Long text:
        Cause
          You are not allowed to change the extract structure &V#& for
          application "03". This is because unprocessed entries are still present
          in an extraction queue of application "03" for at least one client.
          If an extraction structure is changed for which there are still open
          entries in an extraction queue, these entries can no longer be read and
          the collective update terminates.
        What to do
          Start the collective update using the "Job-Control" function in the
          <DS:TRAN.LBWE>Logistics Extract Structure Customizing Cockpit</>.
          You can get an overview of logistic extraction queues in the
          <DS:TRAN.LBWQ>Log. Queue Overview</>.
    A2EEMCEX 141 Struct. Appl. "03" cannot changed because restruct. -> Long text" ""MC03BF0SETUP""300"
      Long text:
        Cause
          Changing the extract structure &V#& for application "03" is not
          permitted, because the restructure table &V#& for the extractor still
          contains data in &V#&.
          You cannot change the structure in this status, because when you load
          an InfoPackage from BW, this leads to errors.
        What to do
          <DS:TRAN.LBWG>Delete</> the entries for all restructure tables for
          application "03".
    A2EEMCEX 141 Struct. Appl. "04" cannot changed because restruct. -> Long text" ""MC04P_0ARBSETUP""300"
      Long text: see above
    A2EEMCEX 141 Struct. Appl. "04" cannot changed because restruct. -> Long text" ""MC04P_0COMSETUP""300"
    Re: Upgrade Question: SMQ1 Queues and an Error during JOB_RSVBCHCK2 &
    CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.MX1
    Where in we they have advised to delete the structure in LBWG.
    Here we don't have a BW team, but if I delete that will it lose any data? or how do I tackle this problem
    Pl advise
    If I am write this is used by vertex
    Regards
    Senthil

    Those extract structures can be "rebuilt" using the transaction SBIW. They are needed if you initially fill the data into BI/BW or if you must re-load everything. It's safe to delete them.
    Markus

  • SAINT upgrade : error: return Code:0212

    Hi!
    i going to update SPAM/SAINT upgrade.
    My machine has 4.7ee (IDES Edition), Oracle 8i and Windows as OS.
    When i check Spam level by default Version 620/0008. i am tring to upgrade Version 620/00223( bec. when i search in service market place, only Version 22, 23 only available).
    Q: Is it possible to upgrade directly from Version 08 to 23???.
    Anyhow, i was extracted .car file in eps\in directory as sidadm admin.
    And i go to 000 as DDIC user, and use SPAMload packagefrom appl server.
    then, Import SPAM/SAINT update.
    The Import was terminated along with following message.
    Error in Step: CHECK_REQUIREMENTS
    Cause of error: TP_CANNOT_CONNECT_SYSTEM
    Return Code: 0212
    Error Message: Could not access files as supposed (see SLOG for more details).
    And
    In SPAM,
    Status : SPAM update is being processed.
                 Spam status: RED
                 Import step: CHECK_REQUIREMENTS
    Kindly give me solution pls......
    regards
    raghu

    hi!
    i was reconfigured TMS. Now diff error will appear.
    Error in Step:
    Cause of error: CANNOT_CREATE_COFILES
    Return Code: 7
    kindly give solutions pls......
    regards
    raghu

  • Tp unlocksys during upgrade returns code 0232

    Hi all,
    I'm upgrading a system from 4.5B to ECC 6.0. I need to unlock the system in order to log in with a user different from DDIC.
    SAPup is now in phase PARCONV_UPG (387/505). The shadow instance is not available any more, so SAPup is working only in the real instance.
    When I try to execute
    tp unlocksys TEC pf=/usr/sap/trans/bin/TP_DOMAIN_TEC.PFL
    an error occurs ( see below  )
    I have also tried with
    tp unlocksys TEC pf=<dir_trans>//DEFAULT.TPP
    with the same results.  Any ideas?
    Thank you very much in advance.
    Best Regards
    TRACE-INFO: 16:    *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("libdb2.a(shr_64.o)") FAILED      1935  0.006630
    TRACE-INFO: 17:                          "      0509-022 Cannot load module shr_64.o.
    TRACE-INFO: 18:                         0509-026 System error: A file or directory in the path name does not exist."  (errno=2,No such file or directory)
    TRACE-INFO: 19:    Could not load DB2 library libdb2.a(shr_64.o).  No database connection possible.
    TRACE-INFO: 20:                                                                                77  0.006707
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0232
    tp finished with return code: 232
    Edited by: Francisco José Martínez Carretero on Aug 31, 2010 3:50 PM

    HI...
    we are upgrading SCM 7.02 System SP0 to SP7 using SUM on AIX [ SUM 1.0 SP7 P2]
    We were in phase just to start Downtime Phase.
    We completed backup and immediately Business Users requested to post pone the Downtime Phase to evening .
    & When users were trying to login they are getting message
    "Upgrade still running : Logon Not possible"
    We unlocked it as below
    host.domain.com:sidadm> pwd
    /<SUM>/abap/var
    host.domain.com:sidadm> tp unlocksys <SID> pf=/<SUM>/abap/var/DEFAULT.TPP
    This is tp version 380.03.82 (release 720, unicode enabled)
    Warning: unknown parameter DYNAMIC_PARAMETERS in parameter file (line 18).
    Warning: unknown parameter DYNAMIC_PARAMETERS in parameter file (line 18).
    Warning: Parameter DBCONFPATH is no longer used.
    tp finished with return code: 0
    meaning:
      Everything OK
    host.domain.com:sidadm>
    *** Finally is is just rewrite of same but specifying that when using SUM where DEFAULT.TPP is existing on AIX ***

  • Upgrade from SP11 to SP19

    Hi,
    We are planning to upgrade from SP11 to SP19. EP system is on UNIX.
    And we dont have any KMC for Portal.
    Can anyone forward me the documents or step-by-stp guides or links for this?
    And i need information what are the advantages with SP19 for portal?
    I can say thanks with points.
    Here i am adding my mail id: <b>[email protected]</b>
    Thanks in Advance,
    Sanjeev

    All the guides for upgrading to a new support package can be found in the SAP MarketPlace  at <a href="http://service.sap.com/nw04maintenance">NW04 Maint</a>.
    SP19 will have all the latest bug fixes, which is why you should apply it.
    Cheers

  • SDM Server Stopping with return Code 8 in WAS 6.4

    Hi
    I have got full version of JAVA for WAS 6.4.  Im able to install the whole thing successfully.   After successful installation SDM Server is stopping with (I mean the instance of Server 0 is in Yellow) return Code 8.
    Can any one tell me how to fix the problem
    thanks
    raj

    Run sdm in "mode=integrated". The problem is: you run SDM in standalone mode.
    For more information about howto change mode look up in your directory:
    sdm_directory\program\doc\SDMCommandLineDoc630_en_final.pdf

  • Are return codes from APIs different when upgrading DOT from 8.0.3 to 8.1.4/8.2.3 (7-mode only)

    Customer is looking to upgrade from DOT 8.0.3 to 8.1.4/8.2.3 (7-mode). There are no real API changes between these upgrades other than additional functionality being added. Howver, are the return codes from APIs any different when upgrading DOT from 8.0.3 to 8.1.4/8.2.3 (7-mode only)? Any help on this to help confirm would be greatly appreciated. Many Thanks in advance. Luke

    Thanks. I had the Portal 3.0.6/3.0.7/3.0.8 to Portal 3.0.9 upgrade scripts and instructions, but thought that was my last step. I hesitated on running the Portal Configuration Assistant. None of the instructions told me what to do at this point.
    Anyways, it looks that by running the Portal Configuration Assitant at the end of the 1.0.2.2 9iAS install, it created a new repository for Portal 3.0.9 in my database. Since I gave it a different schema name, I now have two portal repositories. The old Portal 3.0.6 repository (jvac_portal30) and the new Portal 3.0.9 repository (j_portal30).
    So, I assume I have to perform the upgrade scripts on the Portal 3.0.6 repository to get it to 3.0.9. Since we really did not have very much in the repository, we may just manually recreate everything in the new 3.0.9 repository. I have ssen several discussion threads about the upgrade and problems, so I am very leary to do it.
    In regards to our J Server propblem, we left for lunch. Came back and rebooted several more times, double checked all our configuration files (made no changes), stopped and restarted Apache several more times, and then by some miracle everything started working.
    null

  • WAS 640 Upgrade to SP11

    I am planning to upgrade my laptop WAS 640 SP9 installation to SP11. Where can I finds a document that outlines the steps to do this upgrade ? How about the upgrade files ? Where to find these ? Please advise.
    Thanks !

    HI Srikanth..
    Just now i am also going for an upgradation to SP11.So i hope i can help u a bit on that.
    The first thing u shud do is to get the required pdf guide
    (<b>Support Package Stack Guide - SAP NetWeaver 04 SP Stack 11</b>) from <b>service.sap.com/instguidesnw04</b>..It will  give u the step by step upgradation help.
    Below are the patches or upgrade files in ur words , that u need to download from <b>service.sap.com/swdc</b>
    1)CTRLORA11_0-20000118.SAR
    2)J2EERT11_0-10001982.SAR
    3)J2EERTOS11_0-20000118.SAR
    4)SAPINST11_0-20000118.SAR
    (Assuming ur underlying DB is oracle & window as ur OS)
    Extract the files using SAPCAR and start ur journey towards SP11.
    Note: Do follow the pre- & post-installtion steps.
    Do send me the feedback n also the points , if it helps u.
    Regards,
    sandip agarwal

  • DBM Error return code -11 in LC10 Administration in SCM System Live Cache

    Hello,
    We have installed SCM 4.1 on Solaris on one box and LC 7.5 on another solaris box.
    For kernel upgrade, we shut down Live Cache using LC10>administration on SCM server. After kernel patch, other patches for ABAP stack, we upgraded LC to SP11 build 35.
    Since then, we get following error in LC10.
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Name and Server : LCA - gva1073
    DBMRFC Function : DBM_EXECUTE
    Command : dbm_version
    Error : DBM Error
    Return Code : -11
    Error Message : tp error: Terminating. [nlsui0.c 1934] pid
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Also, in DB59, when we try to check connection, we get following error -
    General Connection Data
    Connection Name....: LCA
    Database Name......: LCA
    Database Server....: gva1073
    tp Profiles........: no_longer_used
    DBM User...........: CONTROL
    Test Scope
    1. Execute an external operating system command (DBMCLI)
    2. Determine status using TCP/IP connection SAPDB_DBM (DBMRFC
    command mode)
    3. Determine status using TCP/IP connection SAPDB_DBM_DAEMON (DBMRFC
    session mode)
    4. Test the SQL connection (Native SQL at CON_NAME)
    Application Server: gva1075_SCD_03 (
    SunOS )
    1. Connect. test with "dbmcli db_state"
    Successful
    2. Connect. test with command mode "dbmrfc db_state"
    Unsuccessful
    dbm_system_error
    Name and Server : LCA - gva1073
    DBMRFC Function : DBM_EXECUTE
    Command : db_state
    Error : DBM Error
    Return Code : -11
    Error Message : tp error: Terminating. [nlsui0.c 1934] pid
    3. Connect. test with session mode "dbmrfc db_state"
    Unsuccessful
    dbm_system_error
    Name and Server : LCA - gva1073
    DBMRFC Function : DBM_CONNECT
    Error : DBM Error
    Return Code : -11
    Error Message : tp error: Terminating. [nlsui0.c 1934] pid
    4. Connect. test with "native SQL" ( LCA )
    Successful
    ++++++++++++++++++++++++++++++++++++++++++++++++++++
    Can anybody please help?
    Thanks and regards,
    Vaibhav

    Hello Vaibhav,
    while using transaction LC10, the error 11 "tp error: Terminating. [nlsui0.c ...]" occurs. The user authorization with tp fails and the application server cannot connect to the liveCache.
    I assumed, that it's due to a library version mismatch, tp cannot use the liveCahe UNICODE libraries.
    Please check, that the tp call at the command line works properly. And a dbmcli call in the transaction SM49 with the tp options
    (dbmcli ::
    -d <LC-SID> -n <LC-servername> -tpp <profile> -tpi <system-SID>
    -tpc <connection - LCA/LDA> dbm_version)
    works also properly.
    I recommend you to update the liveCache client software on the Application server.
    If you've got access to OSS/Service Market Place, then please take a look at note
    649814 how to update the liveCache client software on the application server.
    < Please also review the SAP notes 847736 & 831108 > 
    Before the liveCache client version will be upgraded on the application
    server you can use the workaround by switching off the central authorization for the liveCache LCA/LDA connections:
    In transaction LC10, choose Integration and deactivate the option Central authorization, then save.
    If you are the official SAP customer, I recommend you to create the ticket to SAP on 'BC-DB-LVC' queue.
    Thank you and best regards, Natalia Khlopina

  • StopServer.sh fails with return code 1

    I am trying to install Java Add-on Install (Step 3 of Add-on INstall) into newly upgraded NW 7.0 system and I am getting the following error.  I tried to stop sdm using StopServer.sh, but it fails.  I tried to start server using StartServer.sh, it probably starts, but just hangs there without coming out.  If I cancels, the Installation fails.  Any ideas how to resolve this?
    INFO       2008-10-28 17:38:00.442 [syuxccuren.cpp:264]
               CSyCurrentProcessEnvironmentImpl::setGroup(PSyGroup)
    Real group ID set to 201.
    INFO       2008-10-28 17:38:00.453
               CJSlibModule::writeInfo_impl()
    Output of /bin/sh -c /usr/sap/CNP/DVEBMGS01/SDM/program/StopServer.sh is written to the logfile sh.log.
    WARNING    2008-10-28 17:38:00.898
               CJSlibModule::writeWarning_impl()
    Execution of the command "/bin/sh -c /usr/sap/CNP/DVEBMGS01/SDM/program/StopServer.sh" finished with return code 1. Output:
    Starting '/usr/java14_64/bin/java' '-Xmx256M' -jar '/usr/sap/CNP/DVEBMGS01/SDM/program/bin/SDM.jar' shutdown 'sdmguiport=50118' 'sdmhome=/usr/sap/CNP/DVEBMGS01/SDM/program'
    JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine.
    ERROR      2008-10-28 17:38:00.900 [iaxxinscbk.cpp:260]
    MUT-02041  SDM call of stopServer ends with returncode 1
    ERROR      2008-10-28 17:38:00.903
               CJSlibModule::writeError_impl()
    MUT-03025  Caught ESAPinstException in Modulecall: SDM call of stopServer ends with returncode 1.
    ERROR      2008-10-28 17:38:01.424 [sixxcstepexecute.cpp:951]
    FCO-00011  The step registerSDMTargets with step key |NW_Addin_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|9|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|registerSDMTargets was executed with status ERROR ( Last error reported by the step :Caught ESAPinstException in Modulecall: SDM call of stopServer ends with returncode 1.).
    INFO       2008-10-28 17:38:32.158 [sixxcstepexecute.cpp:1004]
    An error occured and the user decide to stop.\n Current step "|NW_Addin_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|9|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|registerSDMTargets".
    Regards,
    Giridhara Tadikonda

    For some reason, the problem didn't surface again. 
    I am running AIX 5.3 and Java version SR10.
    I stopped the sapinst, shutdown my laptop, went home.  After some time I logged in and I had tried to use StopServer.sh and it returned with code 0.  I tried to start and stop again.  I felt everything seems tobe fine.  So I had started sapinst and it bypassed that stage very strangely without doing anything.
    Regards,
    Giridhara.

  • Premiere Elements 13 serialize Return Code = 14

    I have 24 AOO licences of Premiere Elements 13 that I need to deploy with SCCM.
    I have created an .msi with AAMEE as I was told by Adobe support. Next I tried to create a prov.xml with the following command:
    adobe_prtk.exe --tool=VolumeSerialize --generate --serial=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx --leid=V7{}PremiereElements-EMT13-Win-GM --regsuppress=ss --eulasuppress --provfilepath="path to desired folder"
    I get Return Code = 14. I am running the command prompt as administrator. What have I done wrong?

    I'd like to know what to do with this. I ran into the same problem, basically trying to force PSE13 and PRE13 silent installations the same way as 12 because I have no access to the new creative cloud packager. We purchased volume licensing for 12 which came with a version 13 upgrade and the only official directions I could find to build a silent installer require creative cloud packager which is nowhere to be found on our LWS page. What am I supposed to do?

Maybe you are looking for