Error deploying PAR file from Developer Studio (NW04)

Hello,
i've got a problem while trying to deploy a PAR file from NW Developer Studio.
The PAR Export function says
"Unable to connect to the Portal",
the portal itself gives the following response:
"ERROR: Upload failed - exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException: Invalid content type submitted - no multipart data"
Deploying the PAR file manually using the Administration Console (system administration tab) of the portal works fine, but why doesn't the PAR Export function of NWDS?
Thanks in advance for any help!
Regards,
Jörg

Hi Jörg,
as a general advise, use the NWDS version corresponding to the Servers version, so in this case, upgrade (or better: install new) NWDS 2.0.14. The main reason is WebDynpro compatibility, but the deploy mechanism may need this too.
At least, give it a try and report if you have success (or not).
Hope it helps
Detlev

Similar Messages

  • Error Deploying Sample Portal from Development Guide

    I am going through creating a New Portal from WebLogic Portal 7 Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot Deploy the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.

    That's great, Mike, you're welcome. I'm glad it's working for you. Thanks for letting me know.
    -Scott
    Mike Friesen wrote:
    I'm sorry you were right.. I tried it and everything works... thanks..
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I hear what you are saying and I believe you. But the error you describedis the known issue related to Internet access
    (down to the exact line numbers in the stack trace). Is it possible yourconnection was down last time you attempted
    hot-deploy?
    If you are sure your Internet connection is up, I would recommend tryinghot-deploy again. If it still does not work,
    something very strange is going on. At that point I would recommendtrying the workaround anyway or escalating the issue
    to BEA Support.
    Now my curiosity is piqued so I hope you'll let me know either way.
    Best Regards,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    yes..
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Can you please try something for me? Paste the following URL into abrowser:
    http://java.sun.com/dtd/application_1_3.dtd
    Does it come up?
    Thanks,
    Scott
    Mike Friesen wrote:
    Actually, my computer does have internet access, so I don't think that
    is
    the problem.
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I would bet that you are working on a machine that doesn't have
    Internet
    access, correct?
    The problem is that the EBCC is trying and failing to access the J2EEapplication descriptor
    dtd from Sun's website.
    If you can't get Internet access, here is the workaround:
    - save the attached file to your harddrive (just save it to c:\)
    - edit the application.xml file for your project as follows:
    - first copy the entire DOCTYPE declaration and save it somewhere
    in
    a
    separate text file (in case want to revert back to it later)
    - edit the DOCTYPE declaration so that it looks like this:
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN' 'file:///application_1_3.dtd'>
    ( notice that the java.sun.com web address is replaced with the URI
    to
    the file on your harddrive)
    - save your changes and hotdeploy will work with or without Internetaccess
    Thanks,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    I am going through creating a New Portal from WebLogic Portal 7
    Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot
    Deploy
    the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.
    <!--
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, U.S.A.
    All rights reserved.
    Sun Microsystems, Inc. has intellectual property rights relating to
    technology embodied in the product that is described in this document.
    In particular, and without limitation, these intellectual property
    rights may include one or more of the U.S. patents listed at
    http://www.sun.com/patents and one or more additional patents or
    pending patent applications in the U.S. and in other countries.
    This document and the product to which it pertains are distributed
    under licenses restricting their use, copying, distribution, and
    decompilation. This document may be reproduced and distributed but
    may
    not be changed without prior written authorization of Sun and its
    licensors, if any.
    Third-party software, including font technology, is copyrighted and
    licensed from Sun suppliers.
    Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail and and
    Enterprise JavaBeans are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries.
    Federal Acquisitions: Commercial Software - Government Users Subjectto
    Standard License Terms and Conditions.
    DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
    CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
    WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
    NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
    DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, E'tats-Unis.
    Tous droits re'serve's.
    Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
    relatants a` la technologie incorpore'e dans le produit qui est
    de'crit
    dans ce document. En particulier, et sans la limitation, ces droits de
    proprie'te' intellectuels peuvent inclure un ou plus des brevets
    ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
    brevets plus supple'mentaires ou les applications de brevet en attente
    dans les E'tats-Unis et dans les autres pays.
    Ce produit ou document est prote'ge' par un copyright et distribue'
    avec des licences qui en restreignent l'utilisation, la copie, la
    distribution, et la de'compilation. Ce documention associe n peut
    e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
    l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
    licence, le cas e'che'ant.
    Le logiciel de'tenu par des tiers, et qui comprend la technologie
    relative aux polices de caracte`res, est prote'ge' par un copyright et
    licencie' par des fournisseurs de Sun.
    Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail et and
    Enterprise JavaBeans sont des marques de fabrique ou des marques
    de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
    pays.
    LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
    DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
    EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
    NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
    L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
    CONTREFAC,ON.
    -->
    <!--
    This is the XML DTD for the J2EE 1.3 application deployment
    descriptor. All J2EE 1.3 application deployment descriptors
    must include a DOCTYPE of the following form:
    <!DOCTYPE application PUBLIC
    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
    "http://java.sun.com/dtd/application_1_3.dtd">
    -->
    <!--
    The following conventions apply to all J2EE deployment descriptor
    elements unless indicated otherwise.
    - In elements that contain PCDATA, leading and trailing whitespace
    in the data may be ignored.
    - In elements whose value is an "enumerated type", the value is
    case sensitive.
    - In elements that specify a pathname to a file within the same
    JAR file, relative filenames (i.e., those not starting with "/")
    are considered relative to the root of the JAR file's namespace.
    Absolute filenames (i.e., those starting with "/") also specify
    names in the root of the JAR file's namespace. In general, relative
    names are preferred. The exception is .war files where absolute
    names are preferred for consistency with the servlet API.
    -->
    <!--
    The application element is the root element of a J2EE application
    deployment descriptor.
    -->
    <!ELEMENT application (icon?, display-name, description?, module+,
    security-role*)>
    <!--
    The alt-dd element specifies an optional URI to the post-assembly
    version of the deployment descriptor file for a particular J2EEmodule.
    The URI must specify the full pathname of the deployment descriptor
    file relative to the application's root directory. If alt-dd is not
    specified, the deployer must read the deployment descriptor from the
    default location and file name required by the respective component
    specification.
    Used in: module
    -->
    <!ELEMENT alt-dd (#PCDATA)>
    <!--
    The connector element specifies the URI of a resource adapter archive
    file, relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT connector (#PCDATA)>
    <!--
    The context-root element specifies the context root of a web
    application.
    Used in: web
    -->
    <!ELEMENT context-root (#PCDATA)>
    <!--
    The description element is used to provide text describing the parent
    element. The description element should include any information that
    the application ear file producer wants to provide to the consumer of
    the application ear file (i.e., to the Deployer). Typically, the tools
    used by the application ear file consumer will display the description
    when processing the parent element that contains the description.
    Used in: application, security-role
    -->
    <!ELEMENT description (#PCDATA)>
    <!--
    The display-name element contains a short name that is intended to be
    displayed by tools. The display name need not be unique.
    Used in: application
    Example:
    <display-name>Employee Self Service</display-name>
    -->
    <!ELEMENT display-name (#PCDATA)>
    <!--
    The ejb element specifies the URI of an ejb-jar, relative to the top
    level of the application package.
    Used in: module
    -->
    <!ELEMENT ejb (#PCDATA)>
    <!--
    The icon element contains small-icon and large-icon elements that
    specify the file names for small and a large GIF or JPEG icon images
    used to represent the parent element in a GUI tool.
    Used in: application
    -->
    <!ELEMENT icon (small-icon?, large-icon?)>
    <!--
    The java element specifies the URI of a java application clientmodule,
    relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT java (#PCDATA)>
    <!--
    The large-icon element contains the name of a file
    containing a large (32 x 32) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <large-icon>employee-service-icon32x32.jpg</large-icon>
    -->
    <!ELEMENT large-icon (#PCDATA)>
    <!--
    The module element represents a single J2EE module and contains a
    connector, ejb, java, or web element, which indicates the module type
    and contains a path to the module file, and an optional alt-ddelement,
    which specifies an optional URI to the post-assembly version of the
    deployment descriptor.
    The application deployment descriptor must have one module element for
    each J2EE module in the application package.
    Used in: application
    -->
    <!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
    <!--
    The role-name element contains the name of a security role.
    The name must conform to the lexical rules for an NMTOKEN.
    Used in: security-role
    -->
    <!ELEMENT role-name (#PCDATA)>
    <!--
    The security-role element contains the definition of a security
    role. The definition consists of an optional description of the
    security role, and the security role name.
    Used in: application
    Example:
    <security-role>
    <description>
    This role includes all employees who are authorized
    to access the employee service application.
    </description>
    <role-name>employee</role-name>
    </security-role>
    -->
    <!ELEMENT security-role (description?, role-name)>
    <!--
    The small-icon element contains the name of a file
    containing a small (16 x 16) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <small-icon>employee-service-icon16x16.jpg</small-icon>
    -->
    <!ELEMENT small-icon (#PCDATA)>
    <!--
    The web element contains the web-uri and context-root of a web
    application module.
    Used in: module
    -->
    <!ELEMENT web (web-uri, context-root)>
    <!--
    The web-uri element specifies the URI of a web application file,
    relative to the top level of the application package.
    Used in: web
    -->
    <!ELEMENT web-uri (#PCDATA)>
    <!--
    The ID mechanism is to allow tools that produce additional deployment
    information (i.e., information beyond the standard deployment
    descriptor information) to store the non-standard information in a
    separate file, and easily refer from these tool-specific files to the
    information in the standard deployment descriptor.
    Tools are not allowed to add the non-standard information into the
    standard deployment descriptor.
    -->
    <!ATTLIST alt-dd id ID #IMPLIED>
    <!ATTLIST application id ID #IMPLIED>
    <!ATTLIST connector id ID #IMPLIED>
    <!ATTLIST context-root id ID #IMPLIED>
    <!ATTLIST description id ID #IMPLIED>
    <!ATTLIST display-name id ID #IMPLIED>
    <!ATTLIST ejb id ID #IMPLIED>
    <!ATTLIST icon id ID #IMPLIED>
    <!ATTLIST java id ID #IMPLIED>
    <!ATTLIST large-icon id ID #IMPLIED>
    <!ATTLIST module id ID #IMPLIED>
    <!ATTLIST role-name id ID #IMPLIED>
    <!ATTLIST security-role id ID #IMPLIED>
    <!ATTLIST small-icon id ID #IMPLIED>
    <!ATTLIST web id ID #IMPLIED>
    <!ATTLIST web-uri id ID #IMPLIED>

  • NWDS - Error deploying .par file to portal (EP 7)

    I am unable to deploy a par file to our portal (EP7 SP12) using NWDS (7.0.06).
    I can use the Administration Console to upload par files, but when using the deployment option in NWDS it gives me the following error message:
    Operation failed: Please make sure the server 'ALIAS' (SERVER:PORT) is running or check the log (sap-plugin.log) for more detail.
    My user id has the "super_admin_role", the "ContentManager" role, and the "Administrator" role assigned.
    The log file shows that the upload is getting an HTML 401 error (Unauthorized), but if I paste the link below into my web browser, it takes me to the file upload page.
    sap-plugin.log
    [04.02.08 / 15:13] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.IOException: Server returned HTTP response code: 401 for URL: http://SERVER:PORT/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=***********&j_password=********&j_authscheme=default&uidPasswordLogon=Log%20on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:361)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:433)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:220)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
         at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
         at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
         at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:519)
         at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:112)
         at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
         at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
         at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         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 com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

    Dhruv...
    Thanks for your response.  I checked the settings for the Server Message Port.  I have the default values enabled.  "SAP J2EE engine is installed on remote host" is selected with "Message Server Host" set to "localhost" and the "Message Server Port" set to 3601.
    When I change the Message Server Port to 3901, I get an additional error regarding HTTPS protocal not being supported.  When I change the proxy settings, I still get the same error message that I was receiving before.
    I have verified that my account is not locked, and I have already re-installed NWDS twice, which did not fix the problem.
    Thanks...
    Bill

  • Error importing result file from Visual Studio Online load test - Incorrect Syntax near ')'

    We are seeing the exact same issue as reported in:
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/4a338992-1a46-47ae-9f13-10a53a6264b5/error-downloading-load-test-report-from-visual-studio-service-load-test-incorrect-syntax-near?forum=TFService#cb43383b-c60d-4dcc-a353-352ac6908b35
    When clicking on the "Download report" after running a load test using Visual Studio Online an error occurs.  The download completes, but the import fails at 15% with the following:
    This is happening for 2 different users on 2 different systems.  
    Any assistance in resolving this would be greatly appreciated!
    Let me know if additional information is needed.
    Thanks!

    Hi,
    We are researching your issue. Please clarify my question with detailed information:
    1. Do you get the error in your first post when you click ‘Download report’ after you run load test from
    Visual Studio 2013 on
    team foundation service?
    2 You said that ‘I am trying to import the test results into a Visual Studio 2012 (Update 3) on-prem instance’, what and where is
    your load test result repository? A SQL Server database or the default database:LoadTest2010 in SQL Express on the same machine with Visual Studio 2013?
    3 Whether you specify the load test result repository under Load Test->Manage Test Controller?
    4. What error do you get? Please provide us more detailed information about the error message or share us with a screenshot.
    5 Whether you can run the load test successfully locally and get the load test result with the same load test result database?
    6 You said that your co-worker can work fine. Please check whether your account has enough permissions for load test result database and download load test result from TFS to load test result database based on the account
    permission of your co-work.
    Thanks,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Bad Magic Number error trying to deploy WAR file from Netweaver Studio

    We hae an application that runs fine as a WAR in both Tomcat and Weblogic and we are trying to deploy it on Netweaver.  I tried both to use the External deployment archives and the Workspace Deployable Archives.  In both cases, the deployment fails with error:
    Bad magic number, found 0x80CCF1C3, expected 0xCAFEBABE.
    I know the server is working because I can deploy a very simple test application with no errors.  The server is a new installation of 7.1.
    Any help on how to get past this error or how to troubleshoot further is appreciated.

    Looks like it's complaining about a missing shared library. Check weblogic.xml for library-ref elements and make sure the domain you are deploying to has those libraries deployed.

  • Problems deploying par file via Netweaver Developer Studio

    Hello,
    I have problems deploying a par file using the SAP Netweaver Developer Studio.
    In the SNWDS i configure the following:
    Window -> Preferences -> SAP Enterprise Portal
    Alias: IEP
    Host: khz059
    Port: 52900
    Login: Administrator
    Description: Testportal
    The logon Url of the portal is http://khz059:5290052900/irj/portal
    If i try to upload a par file via "Quick PAR Upload" i get the error messages:
    "Unable to connect to the portal
    Operation failed: Please make sure the server 'IEP' (khz059:52900) is running or check the log (sap-plugin.log) for more detail."
    Am I using the proper settings? Am I using the wrong port?
    I don't know whats wrong.
    Can anyone help me?
    The logfile shows:
    [12.09.05 / 14:53] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.IOException: Error writing to server
         at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:302)
         at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:314)
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:634)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:361)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:433)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:220)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:404)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:338)
         at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
         at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
         at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:519)
         at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.portal.developmentTools.general.uploader.QuickPARUploader.run(QuickPARUploader.java:146)
         at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
         at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
         at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         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 com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Best regards,
    Nils Kloth

    Hi Nils,
    I think you must have selected the defualt checkbox (Try and uncheck that). Also uncheck the checkbox for "<i>Yes, I want to remeber the password for deployment</i>" if it is also selected. When you deploy the par file now enter the password and try to deploy. I think this will solve your problem.
    Apart from this, try this methos of deploying the Par file.
    1) Save you project. Right click it and "Quick par Upload".
    2) On your browser type
    "http://<your_server_name>:50000/irj/servlet/prt/portal/"
    Your case:
    <i>http://khz059:52900/irj/servlet/prt/portal/</i>
    or same page you can get by navigating:
    System Administration-> Support-> Portal Runtime-> Administration Console.
    3) At the option "Please specify a Portal Archive file (PAR) and press "upload" to store it into the PCD." Deploy your par file by giving the path.
    Now you file is deployed on the server. If you want to create an Iview from this deployed .par file then :
    1) On your portal. Follow the path: Content Administrator-> Portal Content -> Portal Content(sub-option). Right click -> New from par ->iView.
    2) Here in the list you will find the par file which you have uploaded. Proceed as said.
    3) You will finally have an iView. Right click it and preview it.
    I hope this solves your problem.
    Regards
    Pravesh
    PS: Please consider rewarding points if helpful.

  • Error while deploying a PAR file from NWDS into an ECC.

    Hi all,
    I am getting this error while deploying a PAR file from NWDS into an ECC.
    Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
    more detail.
    My server is running properly
    1 - Where is sap-plugin.log file? I don´t find it. 
    2 - Could there be another file with another name with information about the error?
    3 - Is there another way to deploy the file directly from the ECC?
    Regards,

    Hi,
    Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
    Windows/ Prefereces / SAP Enterprise Portal
    Check the following enteries
    Alias
    Host
    Port
    Login etc.
    Regards,

  • Unable to deploy a par file from NWDS

    Hi experts ,
    Im getting the below error on deploying a par file from my nwds studio ,
    please suggest a solution
    createDeployArchive:
          [copy] Copying 1 file to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local
    Error: E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\logs\build.xml:341: Failed to copy E:\sap_ep_prog\dc\.dtc\1\t\7FEDA11250B7CF9AB991A30B09B76536\com.***.par to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par due to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    at org.apache.tools.ant.taskdefs.Copy.doFileOperations(Copy.java:628)
    at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:421)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:116)
    at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:58)
    at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
    at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
    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 com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
    at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.dcutils.DCBuildWrapper.run(DCBuildWrapper.java:49)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:252)
    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
    at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
    at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
    at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
    at org.eclipse.jface.window.Window.open(Window.java:563)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:179)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:84)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
    at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
    at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    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 com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
    at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
    at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: java.io.FileNotFoundException: E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:628)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:309)
    at org.apache.tools.ant.taskdefs.Copy.doFileOperations(Copy.java:617)
    ... 62 more
    --- Nested Exception ---
    java.io.FileNotFoundException: E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:628)
    at org.apache.tools.ant.util.FileUtils.copyFile(FileUtils.java:309)
    at org.apache.tools.ant.taskdefs.Copy.doFileOperations(Copy.java:617)
    at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:421)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    at org.apache.tools.ant.Task.perform(Task.java:364)
    at org.apache.tools.ant.Target.execute(Target.java:341)
    at org.apache.tools.ant.Target.performTasks(Target.java:369)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:116)
    at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:58)
    at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
    at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
    at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
    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 com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
    at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
    at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
    at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.dcutils.DCBuildWrapper.run(DCBuildWrapper.java:49)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:252)
    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
    at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
    at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
    at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
    at org.eclipse.jface.window.Window.open(Window.java:563)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:179)
    at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:84)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
    at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
    at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    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 com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
    at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
    at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Ant runtime 8.863 seconds
    Ant build finished with ERRORS
    Failed to copy E:\sap_ep_prog\dc\.dtc\1\t\7FEDA11250B7CF9AB991A30B09B76536\com.***.par to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par due to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    Error: Build stopped due to an error: Failed to copy E:\sap_ep_prog\dc\.dtc\1\t\7FEDA11250B7CF9AB991A30B09B76536\com.***.par to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par due to E:\sap_ep_prog\dc\.dtc\1\DCs\***\portal_dev\***_logon\_comp\gen\default\local\com.***.par (Access is denied)
    Build plugin finished at 2014-07-15 18:36:07 GMT+05:30 (IST)
    Total build plugin runtime: 9.113 seconds
    Build finished with ERROR
    Regards
    Govardan

    Hi Talviv ,
       The folder where Par file is residing  has read only property i.e
    gen->local .
    but we should not change this property of a DC folder i guess , im getting this error sometimes and some times im able to deploy with out any error.
    Regards
    Govardan

  • Deploy par file error using NWDS

    Hi
    I developed a portal service for activity report. After i deploy the service i get an Java Iview Runtime error in portal and our portal is down. I found the error which is a null reference in portal service i wrote.I fixed the problem, but i can't deploy par file using neither NWDS. Is there any other ways to deploy the par file. Please help.
    Thanks
    Edited by: Ozkan Onay on Jan 31, 2008 8:11 PM
    Edited by: Ozkan Onay on Jan 31, 2008 8:16 PM

    Hi,
      To deploy the application, you can without NWDS but not without server running. Server should be up for deploying any application. Go to Drive:\usr\sap\J2E\JCXX\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
    and ..\deployment\temp folders. Delete your project. It will be cleaned from the portal. Now restart the server. It will be up.
    Regards,
    Harini S

  • Error 500 when trying to upload PAR file from NWDS

    Since few weeks now, I'm not able to directly upload a par file from NWDS. I'm always getting a operation failed error. In the sap-plugin.log file I've found the following trace:
    [21.04.09 / 17:51] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://myserver.com:50500/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=mylogin&j_password=mypwd&j_authscheme=default&uidpasswordlogon=log%20on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1170)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
         at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
         at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
         at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
         at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.portal.developmentTools.general.uploader.QuickPARUploader.run(QuickPARUploader.java:146)
         at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
         at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
         at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         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:585)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

    Developing for iphone can be amazingly complicated and frustrating.  (even before you start coding).  The process of having to create a Certificate, to approving the Certificate, to Assigning the deviceIDs to the certificate, to creating the AppIDs, to creating the provisioning profiles and then creating the .p12 file... is just too tedious. 
    I solved the problem of the "Entitlements are not valid".   The AppID i had set in the iPhone Developer Portal did not match that of the AppID i had set in the Adobe Flash CS5 -> Publish Settings.  (ie. com.yourdomainname.yourappname).  After I re-entered my AppID and compile, i was able to sync the .ipa file into my ipad. 
    I wish the error message had been a little more descriptive.  Could have saved me a whole day.
    I hope this helps others.  But my guess is, if you don't set the 40 character device ID correctly, or the email in the signingcertificate correctly, you'll get this same generic error message.

  • Error while exporting a par file from NWDSVersion: 7.0.19 to portal7.0

    Hi,
    When i tried to export a par file from NWDS to portal. I am getting the following error. Please can any one help me to trace out this error.
    21.08.09 / 15:09] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.FileNotFoundException: http://sgcsapeps:50200/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=XXXXX&j_password=YYYYYYt&j_authscheme=default&uidPasswordLogon=Log%20on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:792)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
         at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
         at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
         at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
         at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
         at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:112)
         at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
         at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
         at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         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 com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Thanks in Advance.
    Regards
    Basha

    Hi,
    Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
    Windows/ Prefereces / SAP Enterprise Portal
    Check the following enteries
    Alias
    Host
    Port
    Login etc.
    Regards,

  • Error when using a plugin from Developer Studio

    Hi,
    When trying to use VSS plugin from Developer Studio v2.0.14, I receive the error: "800401f3: Invalid class string".
    Does anyone received the same error in a similar situation and know how to fix it?
    Thank you in advance,
    Janina

    Hi Janina,
    First check whether you have the correct version of the plugin for the NWDS. Reason is, different versions of plugins exist for different versions of Eclipse. I wasn't able to find a version for Eclipse 2.0, may be it is hidden somewhere in the internet
    If you couldn't find the correct version then you need to manually Check-in and check-out the files from the VSS client outside the Eclipse IDE.
    Best regards,
    Guru.
    PS: Award points for replies.

  • How to create a .par file from console apart from tools like eclipse,studio

    Plz reply me if any body knows how to create .par file from Console i.e command prompt.just like creation of .jar & .war file in java.I have created some iViews and making .par files from tool Eclipse/Netweave rstudio etc..I waqnt to create from console..How it is possible?
    Regards
    Sridhar Raju

    Hi Sridhar,
    I'm unsure for what you'd need this, but in general there are at least two possibilities:
    - manually pack everything into the dir structure needed (documented here: http://help.sap.com/saphelp_nw04/helpdata/en/f9/561140d72dc442e10000000a1550b0/frameset.htm ), than create a ZIP with some command line tool (e.g. JAR), naming it to .par.
    - use ANT to do this; with this, you can even deploy the file, see PAR-File deployment with ANT (EP6)
    Hope it helps
    Detlev

  • How to create a PAR file from EAR file

    Hi,
       I have created an Web Dynpro Application . When i deploy it in Remote J2EE Engine, it will deploy as EAR file. It then runs as normal Web Application in Web browser. My requirement is to create an iView for my Web dynpro appn in EP. That is possible only by creating a PAR file. so How to create an PAR file from EAR in NWDS(NetWeaver Developer Studio).
    How to access the EAR file in NWDS or J2EE ?
    Thanks in Advance ,
    By
    Saravanan

    Hi,
    To create a iview,
    log on to portal, New iView and select SAP webdynpro iview.
    It will ask for namespace which is usually , local/Project Name
    and application name is the name of the application.
    We dont have to create par file for this requirement

  • Runtime exeception after deploying PAR file in portal

    Hi ,
    I am facing an issue during the deployment of PAR file in our  Quality portal. I have download the PAR file from the system-->import to the NWDS--> did the modification (only to the properties files as part of my requirement) -->Export as PAR file. I then undeploy the previous earlier PAR file and then upload the modified PAR file in portal. When i test the application , i received portal runtime error.
    I have also tried by downloading the PAR file for the same application from the production portal and tried importing to Quality system without making any modification to the PAR. I still face the same issue.
    Due to this issue, i am not able to bring the application back as its not getting deployed properly. Can anyone help me on this.
    Regards
    Ray

    Hi Ray,
    Are you sure your file is getting deployed properly. Can you verify if the time stamp of the PAR file is getting updated on each deployment or after you upload it through Portal.
    Also, please check the PAR file (size and it's contents by unzipping the PAR file) that you've downloaded from PROD and deploying on QAS to ensure that the file is not corrupted by any means during downloading.
    You can also ask your BASIS team to provide the PAR file directly from PROD server and try to upload it on QAS instead of you downloading it from PROD portal.
    Also, you can follow the below steps to download the PAR file yourself from PROD portal with Administrator ID:
    Browse to the following location : System administration->Support->Portal Runtime->Browse deployment->ROOT/WEB-INF/deployment/temp
    1. Find and Identify the PAR file and Copy the name of PAR file.
    2. Click on view instead of download link to save the PAR file. Keep the name of PAR file same while saving with .par extension.
    3. Deploy this file on QAS Portal.
    Please let us know the results.
    BR,
    Anurag

Maybe you are looking for

  • Is there a way to delete multiple emails at one time?

    I did a search but didn't find anything on this. I just got the new 3G and when I setup one of my email accounts (not .mac) it downloaded 700 emails from that account even though about 600 had been previously deleted. Is there a way to select multipl

  • Keyboard problem-sudden refusal to properly record key strokes

    My wife's iMac 1.6 (running 10.4.3) has suddenly refused to properly reflect keystrokes for the 3, e, d, c, 6, y, h, n, -, [ and n keys (a partial list, there may be more, I stopped counting but most of the rest seem to still work ok). It has also st

  • Creating a PDF from an image using Adobe Reader 9.0

    Hi, I've converted a bitmap image to Adobe PDF using Adobe Reader 9.0. I was able to open and read the file but not to modify it. The resulting file ended up being password protected. I do not have a password. I am using Adobe Acrobat X. Can you help

  • IP SLA stats - one-way latency / MOS score 4.34 not updating

    I'm trying to use Cisco IP SLA to bench mark voice traffic peformance before and after I apply QoS to the network.  *  I've setup IP SLA in both directions over a DSL connection between a 7600, and an 1801 *  I've setup IP SLA in both directions over

  • Download CS5 to re-install?

    My company bought CS5 last year and I installed it on my computer. Now I'm changing computer and need to install it on that computer instead. Unfortunately my boss have lost the DVD with the software. Question 1 is how I can get a new DVD with CS5 or