Cannot deploy with NWDS 2004s SP9

Hi all,
I just recently upgraded to NWDS 2004s SP9 from 2004 SP14. Each time I attempt to deploy and run a WebDynpro project (one of my older projects), I get the following error:
<b>Application error occurred during request processing:</b>
<b>Details:</b> com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:493) The ID of this error is <b>Exception id: [00059A3C7800004800000200000093000041F13A6E7E3A9].</b>
I've found the threads and oss note that tell me to re-deploy sap.com/cafeugpuidtcompcons, (etc) but I when I look for that particular DC, its not there.
Any suggestions?

No need to apologize, we've all been in that situation before.
The logs can be found under:
\usr\sap\<SID>\JCXX\j2ee\cluster\server0\log
Generally defaultTrace.trc will contain this sort of thing. Normally it's best to read these with a log viewer of some kind, either the standalone log viewer or the one integrated into Visual Administrator. You can also just open the logs in a text editor, but they are hard to read and the timestamps aren't human-readable.
If you search for the ID of the exception, you may find some more info there that will help track down what the problem is. Or perhaps someone else has seen this problem before and will speak up.

Similar Messages

  • Cannot deploy app files to j2ee engine in NWDS

    Hi,
      I`ve got NWDS ver. 2.0.15 and I am trying to deploy some files to app server but I got message
    Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
    I am almost 100%  it`s because I need to use proxy to connect the server. I set up proxy settings in window->preferences->workbench->proxy but I think this option doesn't affect to j2ee engine connection. Cause for example I can access portal on port 50000 using my browser (with set up proxy), but I cannot deploy PAR file what`s more the settings window->preferences->SAP Enterprise portal are correct and the same which I used to connect portal using web browser.
      I was thinking about other way to check the connection and SDM Remote GUI came on my mind. Does anybody know how to set up proxy in this program?

    Rich,
      I did it and I am absolutley sure that host and message server are correct. I think that the problem is that to connect server the connection should be via proxy. And I think beacuse of it connection desnt work.
    Look at my example I can connect portal via web browser with configured proxy, but I cannot deploy PAR file using NWDS with the same port and host as I used in browser.
    I have configured proxy in NWDS (window->preferences->workbench->proxy) but I am affraid that this setting doesnt take affect to j2ee engine settings and Enterprise portal deployment settings.
    Now I am looking for tool which gives me possibility to connect SDM some other way with proxy. Or maybe there is some soft that allows me to set all outgoing network connections to go via proxy.

  • Webdynpro Application is not Deploying into Netweaver 2004s From NWDS CE

    Hi,
    I Developed Webdynpro Application in NWDS CE 7.1 SP5.
    I Am using Netweaver 2004s AS JAVA .
    After Deploying application i will get page can not be displayed and in the browser url is following below
    http://localhost:-1/webdynpro/dispatcher/demo.sap.com/firstapp/FirstApp?SAPtestId=2
    my actual port is 50000 but it gives -1.
    and also i need one clarification NWDS CE 7.1 Applications Supports the Netweaver 2004s or
    it requires Netweaver CE 7.1 AS JAVA.
    We have to develop applications using webdynpro,mobile perspectives in NWDS CE 7.1 SP5
    Is it Supports Netweaver 2004s.
    Thanks
    Subbarao

    Hi
    NetWeaver CE 7.1 uses Java 5 and so does the NWDS CE 7.1 by default. The server you have is NW 2004s SP 9 which runs on Java 1.4. So you simply can not build with Java 5 and deploy it to a server with JRE 1.4, you will get a class unsupported version error.
    Next you are using NWDS CE 7.1 to connect to server 2004s. The architecture of the Java servers in SAP is changed. 2004s has SDM and dispatcher and a server process at its simplest form. In CE theres an ICM and server. (SDM & Dispatcher combined). You no more give the message port number when you set up the JEE server of NWDS 7.1 instead you would use instance number. When you register a NW 2004s server with NWDS 7.1 (instance numbers are available for 7.0 servers as well), the studio fails to find the deploy mechanism (SDM or ICM) hence you see a port -1.
    Lastly the architecture of WebDynpro is greatly changed from NW 7.0 to NW 7.1 so dont even think of deployment to previous versions.
    Regards
    LNV

  • Deploy PAR with NWDS SP19

    Hi All,
      I am trying to deploy the PAR file from NWDS, it brings up the dialog and after i enter my password, the deployment progress is stuck, let us say at 80% and my NWDS is hung. I have to terminate it and reopen it again. I upgraded my NWDS recently from SP15 TO SP19. also my portal is on SP19. is this a bug with NWDS Patch.
    Also, Just now I found that I am not able to deploy PAR files from the System Administration > Support> Portal Runtime --> Administration Console on Ep 6.0 SP19.
    Did any of you guys encounter the same problems?
    Any Help is appreciated.
    Thanks
    Message was edited by:
            Reddy

    Hi Reddy,
    It sounds like some of the pluggins may be corrupted, have you tried reinstalling the NWDS?
    Krishna Reddy

  • Cannot deploy BPEL process with SSO to BPELConsole activated

    I cannot deploy BPEL process with SSO to BPELConsole activated. Here is the error I get from JDeveloper (sorry for the french error message):
    Problème détecté lors de la connexion au serveur "ssdvoiagu.dev.local.csst.qc.ca" sur le port "7781" : java.security.AccessControlException: access denied (com.collaxa.security.DomainPermission generique read)
    at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
    at java.security.AccessController.checkPermission(AccessController.java:427)
    at com.collaxa.security.OC4JSecurityService.checkAccess(OC4JSecurityService.java:16)
    at com.collaxa.security.SecurityService.checkDomainAccess(SecurityService.java:26)
    at com.collaxa.cube.fe.util.ServletUtils.getLocatorWithoutUrlRewrite(ServletUtils.java:162)
    at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:332)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Target BPEL process manager runs under SOA 10.1.3.3. When the SSO to BPELConsole is disabled, the deployment works just fine. Is there any way to make it work with SSO?

    Please check:
    http://blog.jpoot.com/category/oracle-appserver/oid-ldap/
    We had some issues with SSO and SSL but everything is running now.
    Marc

  • Help with installing GP in NWDS 2004s

    Hi all:
    (I feel sorry for the English, I will not write well)
    I install the NWDS 2004s on my computer, now I need to develop GP. Use a manual I found on this site, but I left the following error:
    [Image|http://img402.imageshack.us/my.php?image=errorgr1.jpg]
    I followed the instructions in the manual of this link:
    [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f7be53bb-0b01-0010-1c96-be3cb6799c1b]
    thanks

    Hi Pablo,
    Welcome. Did u followed step by step of this guide? In the first step the work folder is DC and in the next is SC. Re-check your configuration and files location.
    DC Folder
    Extract this file:
    https://www.sdn.sap.com/irj/sdn/softwaredownload?download=/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/gp_api_nw04s.zip
    into this folder  (Replace Program Files to Archivos de Programa ):
    C:Program FilesSAPIDEIDE70eclipsepluginscom.sap.tc.ap_2.0.0compCAFDCssap.comcafeugp
    after that you should have a folder called api into gp folder.
    Next, extract this file:
    https://www.sdn.sap.com/irj/sdn/softwaredownload?download=/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/gp_topleveldcs.zip
    into this folder  (Replace Program Files to Archivos de Programa ):
    C:Program FilesSAPIDEIDE70eclipsepluginscom.sap.tc.ap_2.0.0compCAFSCssap.comCAF\_compTopLevelDCs
    after that you should have these files:
    sap.com caf eu gp api wd.dcref
    sap.com caf eu gp api.dcref
    into TopLevelDCs folder.
    Best Regards,
    Pedro Nunes

  • Cannot deploy web dynpro applications

    Hello,
    I'm starting to develop web dynpro applications, and I can run them on the nwds, but I cannot deploy them to the SDM, i always get the following error:
    /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Settings
    SDM host : myserver
    SDM port : 50118
    URL to deploy : file:.../Temp/temp53918Welcome.ear
    Deployment exception : Server myserver did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server myserver at port 50118: No route to host: connect
    Inner exception was :
    Server myserver did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server myserver at port 50118: No route to host: connect
    I have installed Sneak Preview SAP NetWeaver 2004S SR 1, i can access the  enterprise portal with no problems.
    I would be appreciate if anybody could help me with this issue.
    Regards,
    Leandro Fonseca

    At the same time if more users are deploying then you may such 'deployment aborted' errors check if there are more child instances for the J2EE engine.If not ask your basis administrator to create more child nodes to balance the load on the server instance.Also You can find out the server details at
    "http:
    <hostname:portnum>\index.html"select system configuration-you can get the details of the SDM and the j2ee engine from there.You need to have proper credentials to get the information from the above url.
    Provide those details in the NWDS.

  • Cannot Deploy CAF-DC

    Hello!
    I just tried to build i simple CAF-DC with a simple Entity-Service. I use NWDS 7.0.0 and Netweaver 2004s Sneak Preview. When trying to Deploy the corresponding DCs to the j2ee-engine, I get the following output:
    06/08/21 10:24:14 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/mycomp..
                         Reason: Exception during generation of components of application sap.com/mycomp in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/mycomp in container EJBContainer.
                              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:304)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
                              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:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/mycomp in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
                              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:3139)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
                              ... 10 more
                         Caused by:
    java.lang.NoClassDefFoundError: com/sap/caf/rt/exception/CAFDeleteException
                              at java.lang.Class.getDeclaredMethods0(Native Method)
                              at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                              at java.lang.Class.privateGetPublicMethods(Class.java:1778)
                              at java.lang.Class.getMethods(Class.java:832)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:156)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:247)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                              ... 16 more
                         For detailed information see the log file of the Deploy Service.
    06/08/21 10:24:14 -  ***********************************************************
    Aug 21, 2006 10:24:14... Info: End of log messages of the target system.
    Aug 21, 2006 10:24:14... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Aug 21, 2006 10:24:14... Error: Aborted: development component 'mycomp'/'sap.com'/'local'/'20060821095935':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/mycomp..
    Reason: Exception during generation of components of application sap.com/mycomp in container EJBContainer.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/mycomp in container EJBContainer.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Aug 21, 2006 10:24:15... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Aug 21, 2006 10:24:15... Error: -
    At least one of the Deployments failed -
    I looked to the projects that correspond to the DCs. I found the class com/sap/caf/rt/exception/CAFDeleteException in the ejbModule. So why is it not found during deployment. What can I do?
    Thank you in advance.
    Jörg

    Hi
    This problem may be because of version mismatch,
    why dont you install the latest version of NWDS 7.0.7,
    and try doing the same,
    I think it will help,
    Regards
    Deepak

  • Oracle Forms 11gR2 - Cannot deploy locally from within Forms

    I cannot deploy locally from within forms.  The server is up and running and I can deploy the form by putting the correct URL in the address line of the browser window.  When I try to deploy from within forms it comes up with some crazy URL that differs everytime.
    This is what the URL should be and this works from the browser:
    http://machinename:7002/forms/frmservlet?form=WRD608ADMIN_11g.fmx&userid=&otherparams=useSDI=yes
    Here is one of the URLs it came up with when I try to run it from within Forms:
    http://localhost:60231/lysVL2VjqT33znjfvLwanktVRxTIc6dEwVeRNXXRmhYU2qjf
    Localhost is always there, but the rest varies.
    In Forms, I have the Preferences, Runtime set to:
    http://machinename:7002/forms/frmservlet
    Where machine name is my PC, it is the same for this address as the URL above that works directly from the browser.
    So what am I missing?
    Thank you in advance.

    Generally speaking, it is discouraged to manually edit any of the configuration files if they are managed by WLS Console or EM.  In this case, default.env is managed by EM.  Therefore, changes to the file should be done through EM.  If however, you want to alter the file manually, the following is likely the best way to accomplish this:
    1.  Stop the WLS Admin Server and Node Manager
    2.  Locate the proper file you wish to edit.  By proper I mean, there are several copies of most config files.  Most of the config files found in the Oracle Home are actually template files and are not used at runtime.  Altering these will not give you the change you want.  The default.env you want would be here (assuming Windows)
    C:\Oracle\Middleware\user_projects\domains\ClassicDomain\config\fmwconfig\servers\WLS_FORMS\applications\formsapp_11.1.2\config
    If you are using a "Development" installation type, the above path will reflect AdminServer instead of WLS_FORMS.  Remember that Development installations are not for multi-user purposes.  Production deployments require the "Deployment" installation type, which can also include the Builders.
    Do NOT make any changes yet.
    3.  Once you find the correct file, create a backup copy.  Then open the file for edit (not the backup).
    4.  Make the desired changes and save.
    5.  Restart Node Manager and Admin Server if you plan to use them.
    For more information about using EM to manage your configuration, refer to the product documentation:
    http://docs.oracle.com/cd/E38115_01/doc.111210/e24477/configure.htm#CHDCCGHI

  • Cannot deploy EAR.  There are already active sessions

    Hi WebDyn Pro's,
    I'm running NW SP14
    Sporadically, I cannot deploy my WebDynpro app to the NW server.  In NWDS, I indicate to Deploy and run.  I get an error in the console indicating:
    <b>"Cannot log in.  There are already active sessions.  Session id 0 An administrator logged in via API /"</b>
    I restarted the server and the NWDS workstations but that didn't help.  I've had this same error in the past.  Usually it goes away.  I thought I solved it, but evidently not.
    On the NW server, I cannot log into SDM GUI either.  I get the same error.
    As mentioned above, this error occurs sporadically.  I can deploy just fine 50 times.  And then all of sudden I start getting this error, even though no one has touched the server.
    Thoughts?
    Thanks,
    Kevin

    Hi,
    Have you checked if anyone else is actually using SDM to deploy?
    There are some quite significant deployment tasks that my basis team perform which will occupy the SDM tool for a long time and stop me and my other developers from deploying anything.
    I've also caused this problem myself when my SDM deployment has stalled - I've been deploying a custom B2B .ear file and the deployment has just got stuck in processing for ages.  In the end I've had to kill the SDM task from Windows Task Manager but this causes SDM to think someone is still logged in so I've then had to restart the SDM service from the SAP Management Console.
    If this is not the case I'd suggest raising it through OSS if you can't find any relevant messages on there.
    Hope this helps,
    Gareth Ryan.

  • Cannot deploy process flow package specification from file

    Hi,
    we are using owb 11gr2 on linux. We successfully managed to deploy mappings and tables into a specification file, and then deploy from that file into the target database (RAC). But when we try to deploy a process flow package we run into an error:
    A process flow package can be deployed to a specification file. But a deployment from that specification file fails with the error: " OMB05623: Cannot deploy specification from file. Exception follows. nulll"
    ### SETUP
    set CONN_DESIGN "xxx"
    set CONN_TARGET_DESIGN "yyy"
    set CONN_TARGET_RT "xxx'"
    set DIR "D:\\tmp"
    set RELEASE "V0_2"
    set file "$DIR\\$RELEASE"
    set plan "FILE_DEPLOY_$RELEASE"
    ### Deployment via control center: works!
    OMBCONNECT $CONN_DESIGN
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
    OMBCC '/KLINGEL_DWH'
    OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
    OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
    OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan'
    OMBDISCONNECT CONTROL_CENTER
    OMBCOMMIT
    OMBDISCONNECT
    ### Deployment via specificatin file: fails!
    OMBCONNECT $CONN_DESIGN
    OMBCONNECT CONTROL_CENTER $CONN_DESIGN
    OMBCC '/KLINGEL_DWH'
    OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN '$plan'
    OMBALTER DEPLOYMENT_ACTION_PLAN '$plan' ADD ACTION 'PF_TEST' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE '/KLINGEL_DWH/WF_DWH/PF_TEST'
    OMBDEPLOY DEPLOYMENT_ACTION_PLAN '$plan' AS SPECIFICATION TO '$file.xml'
    OMBDROP DEPLOYMENT_ACTION_PLAN '$plan'
    OMBDISCONNECT CONTROL_CENTER
    OMBCOMMIT
    OMBDISCONNECT
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
    OMBDEPLOY SPECIFICATION FROM '$file.xml'
    ### OMB05623: Deployment von Spezifikation aus Datei nicht möglich. Exception folgt. null
    ###OMB05623: Cannot deploy specification from file. Exception follows. nullIf we use the operation DROP it works. But REPLACE and CREATE do not work.
    We get the error regardless whether the code is executed as an expert or on the command line at a windows client.
    Does anyone knows a workaround?
    Deployment via a specification file is a must due to license and architecture requirements.
    Thanks,
    Carsten.

    Its woked fine for me for OWB 10.2.0.4 .... some steps are missing from code like
    when you are connecting again it should be
    OMBDISCONNECT
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RT
    OMBDISCONNECT
    OMBCC '/KLINGEL_DWH'
    OMBCONNECT CONTROL_CENTER $CONN_TARGET_RTI think you can try the same on different system .
    Cheers
    Nawneet

  • Cannot deploy webdynpro project from SP11 of developer studio

    Hi All,
    I have recently upgraded was java from SP09 to SP11 of netweaver 2004s. I have also upgraded developer studio to SP11. Now I cannot deploy webdynpro project from upgraded developer studio. SP09 developer studio can still deploy webdynpro projects.
    Please help.
    Thanks in advance .
    Raktim

    Hi,
       R u trying to deploy an old DC in the upgraded studio? Is the same happening for deploying any newly created local webdynpro project? Create a simple local project and check if same problem occurs.
    Regards,
    Vijai

  • Cannot activate Dreamweaver MX 2004 on Windows 7 64 bit pc?

    Hello.
    Does anybody in here know how to activate Dreamweaver MX 2004 on a Windows 7 64 bit pc?
    I keep getting the message that there is an internet connection problem.
    I have deactivated my firewall etc., but it doesn't help me.
    Anybody got an idea? Adobe Chat does not have the answer for me!
    Regards Anders Fj

    Wow! Thank you. It Works! Clever!
    This is really helpful for those
    of us who are nore professionals. I only use Dreamweaver MX 2004 to
    maintain and repair my own small homepage with photos. And I know how to
    use Dreamweaver MX 2004 and I am not interested in learning new tools -
    not now
    ONE MORE QUESTION THOUGH: Where and how do I update my
    Dreamweaver MX 2004 now that I have installed Dreamweaver MX 2004 on my
    new Win 7 64 bit pc?
    Regards
    Anders Fjeldberg, Denmark
    Ken Binney
    skrev den 2014-05-04 00:01:
    CANNOT ACTIVATE DREAMWEAVER MX 2004 ON
    WINDOWS 7 64 BIT PC?
    created by Ken Binney  in _Dreamweaver
    support forum_ - View the full discussion 
    >

  • Java DC not deployed with WebDynPro DC

    Hi,
    I've been testing the DC functionality and I'm trying to create the following:
    1) WebDynPro DC (DCA)
    2) Java DC (DCB)
    DCB has code for reading data from a database table (three classes, one is set as a public part). This code is functioning ok in another WebDynpro project where I've used it as an external jar file located in the lib directory and added to classpath.
    DCA has a small table in the view that I'm filling (or trying to) with data from the database.
    DCB has one java class as a Public Part. DCA has this PP defined in the Used DC's (DC Metadata --> DC definition --> Used DC's). I can see the DCB code fine from the DCA's view (I can use the methods from the class).
    I see no code errors and everything compiles ok. I've built the DCA and DCB separately (Development Component --> Build) before doing the project build and deployment.
    When I deploy, I'm getting java.lang.NoClassDefFoundError for the DCB class (User.class) when the program starts. So it seems that the DCB is not deployed with the DCA. I've tried to look at the properties and java classpath but nothing I've done has helped.
    Purpose is set to compilation, and there is a
    <at-build-time/>
    tag in the .dcdef file.
    Deployment of normal (no DC) Webdynpro projects works fine and the jars in the lib directory are deployed to the server OK.
    Seems like I've tried everything but have found no solution yet. Refreshed every part, re-created everything, re-built, re-deployed etc...
    Shortly: how to get DCB to deploy ?
    Any help is appreciated here
    Kind Regards,
    Jari Pakarinen

    Hi,
    What is the Java DC for then ? If it cannot be used as a part of another DC (deployable unit) then how should it be used ? What is the use if it does not end up at the server with Webdynpro code ?
    The scenario I'm looking for is to include Java classes in a Webdynpro project as a part of the project (not jars done somewhere else, I can do that already) deployed to the server with the Webdynpro.
    Thank you for your help, I'm not blaming you or anything
    Regards,
    Jari

  • EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

    Hi All ,
               I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
    1 . 3 EJB3.0 session DCs
    2.  1 JPA DC
    I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
    --- Deploying file(s):
         D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
    --- Status:
         Deploy finished with warnings.
    --- Description:
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
         Name:erecapp
         Vendor:asianpaints.com
         Location:J2N_ERECTT_D
         Version:20090217100038
         Deploy status:Warning
         Version:HIGHER
         Description:
              1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
         at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
         at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Result
    Status:Warning

    You have to give an explicit data source in your persistence.xml to solve this error normaly.
    <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
         <persistence-unit name="YOUR_UNIT">
        <jta-data-source>DSNAME</jta-data-source>
    Frank

Maybe you are looking for

  • I cant get my itunes to work or get started at all in my computer?

    Hi my name is fabienne grotke i can get my itunes to work or even open and i have a movies and music i am not trying to get new one or spend more money in getting the same movies and music again so i was wondering if the is a way i can bring it in so

  • Insignia LCD HDTV region problem

    I just bought a 32" Insignia LCD TV at a Best Buy store in my trip to Orlando, Florida. I tested it at the hotel, and it was ok. The problem is that I came back to Brazil and now it is black and white only. Searching in the internet I realized that T

  • Writing on top of writing?

    There are certain websites where the titles or headers have writing on top of writing. Is this my Mac Air or is it the web site? Thank you.

  • Send email notification once published - cs4

    Hi all, In Contribute CS4, should contribute send an email to the user once I have published their file to let them know it is published? It looks like it goes through that process, something like 'sending notification to user' but no emails are ever

  • Unable to insert Unicode in Widget of CP 5.5

    Hi, I just submitted the bug report. And would like to confirm again in this forum to see if anybody has any update. To reproduce this issue is very simple. Open Widget Panel and insert TextArea.swf or CertificateWidget.swf, as an example. It's OK fo