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

Similar Messages

  • 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,

  • Regarding  exporting a  Par file from  NWDS.

    HII...
    I have a problem regarding the exporting a par file from NWDS. when i created any projectt my project is succesfully deployed but . it is not visible when i create any iview from par.
    pls check this steps , perhaps i am missing any steps , or i m deploying it in wrong manner.
    suppose i have to change the masthead brand image.
    steps r .
    1. download a par file.
    2. do the changes in headerview.jsp file.
    3. add the image in img folder.
    4. add the jar file in lib folder.
    5. save and  quick par upload.
    MY server settings r correct . but i dont know why  my project is not in the list.
    thanks..

    Hi,
    You will have the par file directly under your project folder where also your .classpath and .project files exist. Also check them from windows explorer.
    Without a par file, you cannot deploy your project on the server.
    To create par file check this:
    http://help.sap.com/saphelp_nw70/helpdata/EN/96/df7f409cd50a1ae10000000a155106/frameset.htm
    Once you export the par file, you should see this par directly under your project folder.
    If this is not there, then it is a problem in your NWDS.
    Let me know the version of NWDS you are using.
    Regards,
    Praveen Gudapati

  • 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.

  • Unable to deploy the PAR file after the first successfully deploy.

    Hi, my gurus.
    I found a problem when I developed the JspDynPage.
    That is after  first deploy the PAR file successfully,I found there is a miss in portalapp.xml, so I correct the miss and then do a second delpoy.But it didn't work.
    I goto the Server's file system to find the portalapp.xml,
    the content of xml was still the old one.
    Anyone can help me, I don't want restart the J2EE Engine,
    because the restart will last for 15mintues.
    Thanks.

    Hi,
    I dont think there is no need to restart your J2EE Engine.
    Becuase i dont think you have a requirement to create an iview from that PAR File
    If it is so delete the previous iview and create a new iview.
    From the updated PAR File in ur System
    Every Time when you uplaod the PAR the old instance will be lost.and new changes will come into effect on each upload done by you.
    There is no question of restarting ur J2EE Engine.
    Whenever there is a change in you PAR.
    Hope this Helps you.
    Thanks & Regards,
    Lokesh.
    Reward Points if helpfull

  • PAR file from NWDS

    Hello,
        I'm attempting to change a couple of the images on the log on page by adding them into the PAR file using a project in NWDS. After making the changes, which I believe I have done correctly, in order to create the new par file I've used the export PAR file option. I then rename the new file to our our existing filename and pass it to our BASIS team who have tried to deploy it using SDM. For some reason it won't load. (I have manually added the 2 JAR files so that is not the problem). Any ideas about what is wrong ? Any help would be appreciated.
    Much obliged,
         Phil.

    Hello
    Check while creating the PAR file again after uploading the images,
    is the par file created correctly or not?
    is there any custom jar files added previously when the login par has created.
    make sure all jar files added in PAR file while building PAR.
    If PAR file generated successfully then try to deploy from System Admin as mentioned by above reply.
    Cheers
    Chinmaya
    reward for Helpful answers.

  • Problem uploading a PAR file from NWDS

    I am having trouble uploading to one of my portal servers- I have always been able to upload to this server until last week when a database conversion and a change to the way SSO works (they implemented the spnego method of authentication) and now I can't upload to this server any longer.  Here is the log from the sap-plugin.log file.  Any ideas would be greatly appreciated.
    Thanks,
    Dana
    [12.02.07 / 10:25] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > No privateArchive.properties file is defined.
    [12.02.07 / 10:25] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Missing file plugin.header.properties in /UMERefresh/src.config/install/meta/expanded/cm/services/schedulertasks
    [12.02.07 / 10:25] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Config archive successfully created (time to export 1266 ms)
    [12.02.07 / 10:49] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > No privateArchive.properties file is defined.
    [12.02.07 / 10:49] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Missing file plugin.header.properties in /UMERefresh/src.config/install/meta/expanded/cm/services/schedulertasks
    [12.02.07 / 10:49] #ERROR LEVEL# com.sap.portal.plugins.ConfigFrameworkArchiver > Config archive successfully created (time to export 1016 ms)
    [12.02.07 / 10:50] #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://tewk-eptst.global.avidww.com:54200/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=dboisver&j_password=newman12&j_authscheme=default&uidpasswordlogon=log%20on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
         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: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.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:185)
         at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:86)
         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:286)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:795)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:602)

    Hi Dana,
    Try opening the url in the error trace directly and see what happens:
    http://tewk-eptst.global.avidww.com:54200/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=dboisver&j_password=newman12&j_authscheme=default&uidpasswordlogon=log%20on
    You can see from the url that it tries to call the archiveuploader application directly, and that it passes your logon credentials (maybe you should change your password now ) and uses "default" authentication. The spnego authentication you mentioned, is it the default authentication method for the portal?
    Johan

  • 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

  • Import .par file into NWDS and Rum it without deploying ?

    Hello All,
    I'm new to the NWDS and the Portal.
    I've many Qns on my Requirement. Hope u guys can help me out in resolving my Issues.
    Is this  the right forum to place my Query ?
    If not then please let me know the right forum .
    My Requirement is like this :-
    1. I need to create a Portal Application which calls an URL.
    2. But before developing this, my Client gave me one 2 options :
         a. He gave me a par file and asked me to make  changes in it.
         b. Create a new Portal Project which calls the URL ( Predefined ).
    3. I wanted to check the 1rst option i.e  " a ".
    4. I tried to Import the .par file into NWDS like this :
    * Windows --> Open Perspective --> Enterprise Portal .
    * File --> Import --> Par FIle.
    * I gave the name of the Project as PortalLogon.
    5. I searched in the forum on this scenario and I found that the libraries for this project are not automatically imported.
    <b>A .Can any one tell me how to import the libraries and which are all the libraries to be imported ?</b>
    <b>B. How to test my PortalLogon Project without deploying ?</b>
    Is it possible to test this Project without deploying ?
    If yes can anyone tell me hoe to do this ?
    Regards,
    Deepu.K

    Hi Deepu,
    Usually Server will be having all the jar files and If you want to deploy your par file using NWDS you need to give a path to your Jar file location.
    So better download all the jar files from your server and keep it in your local desktop.
    Create a new folder called "JarFiles" in your desktop and keep all of your jar files inside.
    Download Jar finder from IBM Site ( search for "Resolving Java Classpath Issues" in SDN ,you will get a pdf and follow it.).Add it as a plugin to your NWDS path.
    Restart NWDS.
    Now you can resolve the jar file issues.there are many weblogs /articles/forum QAs regarding this.
    If u need more clarification,please let me know.
    Thank you.
    Regards,
    Karthick Eswaran

  • 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,

  • Uploading par files in nwds and deploying back

    Hi all,
    I wanted to work with the masthead iview in nwds, so found it on the server as the par file and imported it into NWDS. Changed the headeriview jsp and deployed it back to the portal. But it is not working. Saw in another sdn thread that when you create the project in nwds, it does not bring up all the components from the par file as required and some class files are missing. I think this is the problem in my case. The solution to it was not given in that thread.
    Would anybody help please.
    thanks.
    Lm

    Hi
    the following are the steps to modify a masthead.
    1.Find the PAR file and copied to a temporary directory and renamed to the customer namespace taking off .bak extension.
    2.Import the PAR file now using File->import option.
    3.make necessary modifications.
    4.once the JSP is edited, the PAR file needs to be created ans uploaded to the portal.If JDK is installed just login into portal and deploy the pAR file otherwise use PortalAnywhere to deploy it.
    5.Now goto Content Administration->Portal Content->right click the folder you wish to create the mastheadiView.Select New from Portal Archive-?iView from the context menu.Select new masthead.
    6. select poratal component Default and choose next.
    7.enter the properties for masthead and next.
    8.edit the Iview and saved it.
    9.add the iView to Framework Page in portal catalog and edit page layout.
    10.select iView from catalog and add it as Delta link and position it accordin to your need.
    Hope this helps you to modify the masthead.
    Regards
    Victoria

  • Import .par file into NWDS and Run without deployment ?

    Hello All,
          I'm new to the NWDS and the Portal.
    I've many Qns on my Requirement. Hope u guys can help me out in resolving my Issues.
    My Requirement is like this :-
    1. I need to create a Portal Application which calls an URL.
    2. But before developing this, my Client gave me one 2 options :
         a. He gave me a par file and asked me to make  changes in it.
         b. Create a new Portal Project which calls the URL ( Predefined ).
    3. I wanted to check the 1rst option i.e  " a ".
    4. I tried to Import the .par file into NWDS like this :
    * Windows --> Open Perspective --> Enterprise Portal .
    * File --> Import --> Par FIle.
    * I gave the name of the Project as PortalLogon.
    5. I searched in the forum on this scenario and I found that the libraries for this project are not automatically imported.
    <b>A .Can any one tell me how to import the libraries and which are all the libraries to be imported ?</b>
    <b>B. How to test my PortalLogon Project without deploying ?</b>
    Is it possible to test this Project without deploying ?
    If yes can anyone tell me hoe to do this ?
    Regards,
    Deepu.K

    hi Deepu,
    for simply displaying a URL, you can use the commonly available URL iView.
    your folder->new->create iView->iView from template->URL iView and then enter your URL
    for the other think.......
    you can create an iView from PAR file.
    your folder->new->create iView->Iview from PAR->then select your PAR and create an iView for that.
    and the last one.......to see the effect without deploying it on the portal......refer the link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
    and the usual libraries to be associated are
    <b>htmlb.jar</b>  and
    <b>com.sap.portal.htmlbbridge.zip</b>
    Cheers........

  • Problem while deploying new logon screen par file via NWDS

    hi
    i have a problem with deploying .par files out of the NWDS.
    i want to change the look of the logon screen in our EP Portal (SAP NetWeaver 2004s).
    when i just import the (working one) par file into NWDS and deploy it without ANY changes i get then an error when trying to call the portal:
    instead of the logonscreen i get some IView error (like IView: N/A).
    if i just copy the par file, and put it back to the pcd, everything works fine.
    my problem seems to be the "compiling/deploying" via NWDS.
    any suggestions?
    i followed the guide:
    http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
    i followed also the BLOG:
    Modifying The Logon Par(or customising the Logon Screen)
    and the help:
    http://help.sap.com/saphelp_nw04/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
    thanks for your help.
    markus

    Markus,
    If you import the par file using NWDS, most likely you wouldn't import the associated jar files (I think 2 jars) that are originally part of the par file. So, when you make changes and update your custom jar, it would lack the two jars and your application would fail. Try downloading the par file using System Administration -> Support -> PCD Administration -> Browse Deployment..
    Save the jar file on desktop and then import it to NWDS.
    Hope this helps,
    Kiran

  • Error while importing logon par file into NWDS.

    Dear Friends ,
    I m trying to customise the logon screen for my project. For this I have downloaded the "com.sap.portal.runtime.logon.par.bak" from portal server instance with the help of basis team. I have locally saved this file on my desktop[. I have renamed the file as .par and removed the .bak extension. Now I have tried to import the file onto NWDS in EP perspective by following File>Import>Par file. But its giving me this error:
    error in opening zip file
    Reason: Sorry, an error occured creating the new project.
    The plugin "com.sap.portal.plugins.config-archiver caused an exception during the
    "Unpack" Operation See log for more details.
    In some of the solutions provided in SDN saying that after renaming the file to par open with zip if i done it is again showing the error as "Start of the central directory not found .Zip file corrupt.Possible cause :file transfer error."
    Kindly suggest me the solution.
    Thanks and regards.

    Hi,
    I think you have taken this file from a wrong path and hence this issue.
    Pls download the par file from the below path and try importing it into EP perspective..
    System admin> Support>Portal Runtime > Browse Deployment>
    Browse through the following to find the com.sap.portal.runtime.logon.par.bak file:
    WEB-INF u2013> deployment u2013> pcd
    Root>WEB-INF>Portal>Portalapps> temp--> download the com.sap.portal.runtime.logon.par.bak
    Regards,
    Vijay.
    Edited by: VijayKPappala on Sep 7, 2011 8:46 AM

  • Error while deplye logon par file in NWDS

    Hello Everybody,
    Here I am using EP 7 and SP 14. I have to change my Portal Logon PAR file as I have to add some hyperlinks in my par file.
    Now problem is , after importing par file in NWDS i made some changes.Then at the time of exporting file, it ask for deployement. When i deploye par file it is throwing error:
    Operation Faliled:please make sure server is running or check log for more details.
    so i checked the logs.  It is like :
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://epdev:50000/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=&j_password=null&j_authscheme=default&uidPasswordLogon=Log%20on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
         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)
    Kindly help me out. i'll be really very thankfull.
    Thanks & Regards
    Nivedita

    Hi Nivedita,
    You could try to delete the entry from the NWDS preferences and set the data there again. Set all the needed information like the portal host name, port, user name. And try not to select the option to save the passwords and check if NWDS does ask for a password then. (Also restart NWDS, I learnt that restart sometimes works wonders :P )
    If it yet doesnt work, build the par file and then logon to the portal as administrator and go to tab System Administration->Support->Portal Runtime->Administration Console. Browse to your par file and click on upload.
    Good Luck!
    GLM

Maybe you are looking for