Error on exporting a PAR file to portal

I am trying to export a portal application (java code) to PAR file in the NWDS. i am getting the following error;-
<b>PAR Upload failed:Please make sure that portal server is running.
HTTPS is not supported ,please ensure the server is not using HTTPS</b>
The PAR file is to be uploaded to the portal later.
Note:The portal application has compiled successfully.
Is it not supported in this version of the portal?
Please help
Regards
Navneet
Message was edited by:
        Navneet Giria

Hello Navneet,
Check these threads:
Problems deploying par file via Netweaver Developer Studio
Unable to Upload  portal application from NWDS
If this does not help, try deploying from
System Administration-> Support-> Portal Runtime-> Administration Console.
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.
Greetings,
Praveen Gudapati
p.s. Points are always welcome for helpful answers

Similar Messages

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

  • Exporting a .par file from portal

    hello, help me please
    I have a standard iview in a business package employee self-service
    I need find the .par file to download this iview then import with Netweaver developer studio, I think is not created, I try in
    "System Administration"==>"Support"==>"Support Desk"==>"Portal Runtime"==>"Browse deployment"==>"ROOT"==>"WEB-INF"==>"deployment"==>"pcd
    but is not in there.
    anyone can help me please.
    Thanks.

    Hi,
    ESS content is developped in PAR... Basically these are more of Development Components(DCs)... In order to customize them , you should have NWDI...
    Below blog explains how to customize....
    ESS/MSS Customization – Make it Simple
    If in case your customisation is minor like customizing the text, hiding/un hiding the links, then
    go to the location whrere your ESS iViews are stored, click on Preview.
    It will open the iView.
    Then do a (Cntrl+Right Click) on the link/image which you want to hide/unhide.... u will get the options...
    Regards,
    Srinivas.

  • Error while uploading a PAR file

    Hi All,
    I'm having an error when i try to upload a PAR file from Portal>Java Development>Development
    The strange is that i am having the error in QA environment, in development environment i can upload it without any problem, and also it is not the first time that I upload a PAR to QA.
    I hope someone can help me, i really don't know what to do...
    Regards,
    Nicolás.-
    Here is the error:
    May 8, 2009 11:46:34 AM # Client_Thread_17     Fatal           Application upload failed: InvoiceTool.par
    com.sapportals.portal.prt.runtime.PortalException: archive: InvoiceTool.par
    at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:309)
    at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:700)
    at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:396)
    at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:285)
    at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:115)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
    at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:250)
    at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:351)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:628)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:229)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:555)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
    at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
    at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
    at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
    at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
    at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
    at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
    at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
    at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: java.util.zip.ZipException: error in opening zip file
    at java.util.zip.ZipFile.open(Native Method)
    at java.util.zip.ZipFile.(ZipFile.java:121)
    at com.sapportals.portal.prt.deployment.ArchiveIntrospector.getDeploymentDescriptor(ArchiveIntrospector.java:54)
    at com.sapportals.portal.prt.deployment.DeploymentManager.getDeploymentDescriptor(DeploymentManager.java:942)
    at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:273)
    at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:700)
    at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:396)
    at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:285)
    at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:115)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
    at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:250)
    at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:351)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:628)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:229)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:555)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
    at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
    at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
    at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
    at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
    at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
    at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
    at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
    at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)

    Hi Nicolas,
    In you development server,
    1. Create a new iview  (With new from PAR file option). The iView wizard gives you the option to choose the PAR file available on your development portal.
    2. Now create a Transport Package. Navigate to System Administration - Transport - Export.
    Navigate to your Transport Folder in PCD.
    Now Create a new Transport Package and add the iView to the package (iView created earlier from PAR file).
    3. Now go to Transport Package properties and Make sure, you are changing the property id prefix to * .
    This will include every object associated with the iView while manually exporting.
    4. Now click on the EXPORT button. This will export the required PAR file with. This in turn create an EPA file. save it to your desktop.
    5. Now in Quality server,
    Do the manual Import.
    Navigate to System Administration - Transport - Import.
    Browse the EPA file on your desktop and say IMPORT.
    This way, you will be able to get your PAR file as well as your required portal object (here the iView) in quality server.
    Hope this helps,
    Cheers!!!!!
    Biroj...
    Points for useful answer will be appreciated.
    Edited by: Biroj Patro on May 12, 2009 8:40 PM

  • 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

  • Deploye par file into portal

    When I tried to deploye the par file into portal using file->Export->PAR file, I am getting an error says "unfortunately the upload of your PAR was not sucessfule. ....
    Error message: Upload seems to have faild" ... Because of this I am not able to upload the PAR file to portal. Any Idea? Please help
    Pages: 1    Back to Thread List 
    Threads: [ Previous | Next ]

    I tryied to do it manaulay and able to upload it. but when I run it, I am getting some error says
    An exception occurred while processing a request for :
    iView : com.flightsafety.hr.EmployeeAddressChange.EmployeeAddressChangenew
    Component Name : com.flightsafety.hr.EmployeeAddressChange.EmployeeAddressChangenew
    Internal error: empty page context.
    Exception id: 10:14_10/01/07_0214_6394050
    See the details for the exception ID in the log file
    Have any Idea?

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

  • Problem during uploading of .par file in Portal

    Hi,
    I am downloading a properly working .par file from portal in my local system. But whenever I am uploading the same par file back into the portal through NWDS, the .par file is not running properly and its Giving error.
    Here is the error:
    "Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.tmobile.compSumm.CompSumm of Portal Component com.tmobile.CompSumm.CompSumm because: Could not find implementation class "
    Any Idea what is the problem?????

    Hi,
    I have unzipped the .jar file from the .par file. Then I imported the .par file into NWDS. After that I have added the extacted .jar file as external jar into the project(Proerties->Java Build Path->Libraries->Add External Jars). After that I had uploaded the project into the portal.
    But still its showing the same error:
    "Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.ibm.test of Portal Component testing.test because: Could not find implementation class"
    Any solution.....
    Message was edited by: Debasish Sarkar

  • 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

  • Accessing PAR files though Portal

    Hi All,
    I want to access the PAR file through Portal itself. So I go to the foll path
    System Administration --> Support --> Portal Runtime --> Browse Deployment --> portalapps.
    I am able to find  the com.sap.portal.navigation.masthead
    But when I try to download this file then it is trying to download  com.sap.portal.support.browse.zip and not com.sap.portal.navigation.masthead
    My intention is to download the PAR file from Portal itself, do some customizations and then upload the same through Portal. I don't want to use NWDS for this purpose.
    Please help
    Regards
    Nikhil Bansal

    Hi everybody,
    just some additional remarks:
    - download the PAR from /WEB-INF/deployment/temp as described by Daniel in the thread referred
    - if you download it by using the "View" button, Praveen is right, you have just to rename the file; if you download it by using the "Download" button, the PAR is inside the ZIP
    - if importing the PAR as a project into NWDS, be aware to add the JARs manually into the /lib and the /private/lib directories, respectively; NWDS does not import the JARs automatically, and if you don't import them, deploying the PAR on the portal will lead to massive problem as then the JARs are missing...
    Hope it helps
    Detlev

  • Download PAR file from portal or Service marketplace

    Hi,
    Can you tell me that how we can download the par file from portal 7.3 or from marketplace.
    give me the path also.
    Regards,
    Shashank

    Hi
    Please check the process :
    http://scn.sap.com/community/netweaver-portal/blog/2012/05/10/customizing-logon-page-on-portal-73

  • 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

  • Portal Run time error after deploying custom logon page par file in portal

    Hi Experts,
       We have customized the standard portal logon par file for client XYZ and imported it with the same name (com.sap.portal.runtime.logon.par)  in portal.
       It is working fine for XYZ . And another client ABC wants the same customization for them also. So we took the par file from XYZ and imported it in ABC system. But in ABC system, we are getting Portal Run time Error. When we checked the logs, it is showing error in LogonBean class.Wwe have included the necesary jar files. Could anyone help us in identifying what is missing?
    Thanks
    VJ

    Hello Vijay,
    Please paste or attach the error log.
    Regards,
    Haseena

  • Portal runtime error after modifying masthead par file

    Hi experts,
    i tried to upload com.sap.portal.navigation.masthead.par in the portal (productive system) after modifying tooltip text of u201CHelpu201D link. i used Archive uploader.
    After upload, status messages are correct.
    But now in the masthead area, i have red message :
    "Portal runtime error"
    "An exception occurred while processing your request"
    I cannot also access the Browse Deploymentu2026
    So now i cannot log off from the portal (except by restart computer)
    In development system where I used the same procedure, everything is OK.
    Please help!

    Dev,
    Please ensure that the changes are correct by to upload the orignial par.
    The other way of modifying the par is as below,
    *Upload the PAR into NWDS and add the jars htmlb.jar, com.sap.portal.htmlb_api.jar and servlet.jar through java build path of your par project and add the jar com.sap.portal.navigation.masthead_core.jar (you can get this by extracting your par and navigate to the folder PORTAL-INF -> lib) in PORTAL-INF -> lib folder of your project.
    Make changes
    Build project
    Export into portal
    Ram

  • 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