Error deploying logon.par

Hi Experts,
I am trying to change the portal logon screen. I followed the insstructions in the documentation to modify the com.sap.portal.runtime.logon.par.bak
I exported an par file from nwds and copied to the apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd and apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp directory
Also i modified the authschemes.xml and set the corrext value in com.sap.security.core.ume.service via configtool.
The problem is when i restart the server the created .par file changes to .p.err and the following error log is created:
2007-05-16_14-54-15
Application upload failed: com.sap.test.logon.par
com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: com.sap.test.logon.par
     at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
     at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
     at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchives(DeploymentManager.java:599)
     at com.sapportals.portal.prt.deployment.DeploymentManager.populateRuntimeRepository(DeploymentManager.java:582)
     at com.sapportals.portal.prt.deployment.DeploymentManager.runtimeRepositoryDeployment(DeploymentManager.java:310)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:404)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException when calling OpenSQLServices.isTransientSQLError()
Invalid connection type com.sap.engine.services.dbpool.cci.ConnectionHandle.
     at com.sapportals.portal.pcd.pl.BasicObjectsTable.isTransientSQLError(BasicObjectsTable.java:281)
     at com.sapportals.portal.pcd.pl.PlFactory.checkDeadlockResolution(PlFactory.java:2433)
     at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1158)
     at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1100)
     at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:856)
     at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:190)
     at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:190)
     at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:253)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:145)
     at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:440)
     at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:369)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:469)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebindInt(PcdProxyContext.java:489)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:508)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:494)
     at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:549)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:736)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:741)
     at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeArchive(ApplicationRepositoryService.java:373)
     at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:299)
     ... 20 more
Caused by: com.sap.sql.log.OpenSQLException: Invalid connection type com.sap.engine.services.dbpool.cci.ConnectionHandle.
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
     at com.sap.sql.services.OpenSQLServices.isTransientSQLError(OpenSQLServices.java:742)
     at com.sapportals.portal.pcd.pl.BasicObjectsTable.isTransientSQLError(BasicObjectsTable.java:277)
     ... 40 more
looks like a problem with openSQL. In fact I have defined an <b>additional</b> <b>vendor data source</b> in visual admin that works properly with my application. Is my problem related to that?
Thanks in advance

Hi,
   Before cheking the entire steps at one shot, try step by step procedure.
First just edit the changes and try to deploy and run the new par from portalapp.xml. If the output is correct, then go ahead changing the actual logon page with your new page. Else it will be difficult to find the exact problem. Also make sure the logon par which u have taken for modiifcation comes from the server u r deploying and u use NWDS of same patch. Otherwise there can be mismatches.
Regards,
Vijai

Similar Messages

  • GETTING ERROR WHILE DEPLOYING A COM.SAP.PORTAL.RUNTIME.LOGON.PAR FILE

    Hi Experts,
    I need to change the text in logon screen i.e,
    2006-2007 SAP AG ALL RIGHTS RESERVED
    for this i changed the copyright and deployed the par file
    but it is giving error like this
    operation failed:please make sure the server is running or check the log(sap-plugin.log)
    what should i do plz suggest me na.....
    i searched the file sap-plugin.log in program files -> sap>IDE>eclipse-->plugin but i couldnt find the
    plz specify the directory na...
    waiting for u r response.....
    Regards,
    Shilpa

    HI SHILPA....really sorry for the late response.
    here is the error log which i m getting...(its not 500 error)
    [13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Startup in progress
    [13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Factory initialized !
    [13.08.08 / 16:50] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.IOException: Server returned HTTP response code: 502 for URL: http://hostname:50000/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=Administrator&j_password=EPDJ2EEADM&j_authscheme=default&uidPasswordLogon=Log%20on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:808)
         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.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)

  • 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

  • Error deploying new portal logon page

    Hi Gurus,
    I'm getting an error deploying my new portal logon page. I've made teh necessary changes to the portal.logon.par.bak file. I've rename it and made the necessary changes in config tool. i've created a new autoscheme_test.xml file and have assigned it accordingly. After restarting the portal, i'm getting the error message below trying to launch the portal :-
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    The exception was logged. Inform your system administrator..
    See the details for the exception ID in the log file
    Any ideas? Are there any other setting that i need to do aside from teh autosceme file. thanks

    Hi Johan,
    There are two lib files which you need to paste while you import the file in the NWDS.Just check for the steps through this weblog
    the jar files name are
    com.sap.portal.runtime.logon_api.par
    umelogonbase.jar
    (when you unzip you can find the files at PORTAL-INFlib)
    Modifying The Logon Par(or customising the Logon Screen)
    Thanks
    Pankaj

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

  • Error in deploying the par from NWDS

    Hello,
    I am not able to deploy a par file from my NWDS, whereas I am able to deploy the same par from another machine which is in the same network. The error thrown in my machine in the file sap-plugin.log is given below. Kindly help to solve this issue
    [17.01.06 / 14:04] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
    java.io.IOException: Server returned HTTP response code: 407 for URL: http://212.140.143.165:57100/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.archiveuploader?login_submit=on&j_user=administrator&j_password=admin123&j_authscheme=default&uidpasswordlogon=log on
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
         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)
    Regards,
    Rukmani

    Hi Rukmani,
    407 is "Proxy Authentication Required", which sounds like you are using a proxy and on the other machine, the network access to the portal works in fact different or the authentication mechanism is different.
    This is hard to elaborate remotely...
    Hope it helps
    Detlev

  • 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

  • Error while importing logon par file

    Hi
    I have to do logon page customisation for that i have taken com.sap.portal.runtime.logon.par.bak file from basis team and i saved it to my desktop .Now i have renamed it to com.sap.portal.runtime.logon.par and trying to import to my NWDS.
    So i opend EP perspective file->import->browsed the par file in place of Archive file name when i click on finish it is showing the error "invalid END header(bad central directory offset).
    "The plugin com.sap.portal.plugins.config-archiver"caused an exception during the unpack operation.see log for more details"
    Can anybody please let me know the reason for this error .
    Thanks in advance.

    Hi,
    After renaming com.sap.portal.runtime.logon.par.bak to com.sap.portal.runtime.logon.par. Try opening the file with winrar/winzip to see if you have a right par file structure. On some portal versions, when you open com.sap.portal.runtime.logon.par file, you have again a com.sap.portal.runtime.logon.par file inside it.
    So if you find com.sap.portal.runtime.logon.par file inside com.sap.portal.runtime.logon.par. Then just extract it again and try importing it into NWDS.
    Please refer to [link|NWDS Log - PAR import error;
    Hope this helps!!
    Thanks & Regards
    Vijay

  • Error while deploying the par file

    while deploying  an application in NWDS we are getting the error as"operation failed,please make sure that the server is running or check the log."
    we have ensured that the server is running,but the deployment is getting failed.
    Please suggest tips to deploy the PAR file successfully.
    Thanks.

    Hi,
    We are using NWDS to create a small application to develop ( for ex jspdynpage)
    .while deploying the par file or exporting it to the server,we are getting the error as "please make sure that the server running.HTTPS protocol is not supported,please ensure that this server is not using HTTPS.
    the server is running and is shown in green.
    we have also  disabled the proxy settings.
    we have also tried by specifiing the IP of the server in the proxy settings.
    the above steps didnt work.please suggest the things to do to make this working.
    thanks,
    rajani.

  • 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 in the Portal Logon par

    Hi All
    i got the error  in the logon par customization i have the followed the steps based on the weblog from the following link
    Modifying The Logon Par(or customising the Logon Screen)
    after done everything i restarted the portal then i got the following error
    <b> Servlet [prt] will be unavailable for undefined time.
      Details:   javax.servlet.UnavailableException: Initialization of Dispatcher failed
    Exception id: [001731424EAC006700000029000013100004346F05987ABE]
    </b>
    please help me on this as early as posible
    Regards
    Sunil

    Hi Sunil,
    First of all, put back the original par file and restart the portal. If you have the same problem, it has nothing to do with your changes (unless you changed the authschemes.xml as well).
    Download the standard logon par file and compare the structure with your par file. Find the problem (create an iview where you can test your component). If it works, you can try again.
    cheers,
    Noë

  • Portal Runtime error when modifying: com.sap.portal.runtime.logon.par

    Hello,
    We need some help because we get 'Portal Runtime error: iView: N/A Component Name:N/A' error when trying to access portal logon screen.
    This is what we've done:
    We've modified com.sap.portal.runtime.logon.par file and we've uploaded it but it doesn't work. Because of the error, we've overwritten this file with the original one but now it's imposible to access portal.
    The situation it seems to be like before the modification of the .par file but we get the same error and can't access portal.
    Please, do you know what could be the problem?
    Thanks in advance

    Hi Belen,
    Here are the steps you would need to take
    1. import the original par file into the NWDS and name the project as  
        com.sap.portal.runtime.logon
    2. Make sure the project name is com.sap.portal.runtime.logon
    3. use winzip/winrar to extract the com.sap.portal.runtime.logon.par file in
        a local directory
    4.Under the lib you would find two jar files copy them and paste them in your project
       under dist>PORTAL-INF>lib directory
    5.move the files cert....till umResetPass....jsp into the  PORTAL-INF directory
    6. export the par to the server in question
    7. restart your server
    This should solve your problem..
    Thanks,
    Gokul

  • Error after deploying backup PAR

    Hello guys,
    we updated a PAR-File in our Portal. The PAR-File that was changed is com.sap.portal.appintegrator.sap.par. And now iViews with Codelink
    com.sap.portal.appintegrator.sap.bwc.BSP show Message:
    "SAPApplication Backward Compatibility Component".
    After reverting back to old Par-File (was backed up local before
    changing) and reloading it (even after restarting the whole server) the
    Problem still persists.
    When executing a iView of that type following errors are located in log-File:
    Time , Category , Date , Message , Severity , Location , Application , User
    11:36:23:272 , /System/Server , 11/21/2006 , Failed to get application
    IPropertyContentProvider:
    pcd:com.sap.portal.system/applications/com.sap.portal.appintegrator.sap/components/BSP
    , Error , com.sap.portal.ivs.semantic.iViewService , sap.com/irj , horn
    11:36:23:270 , /System/Server , 11/21/2006 , Failed to get application
    IPropertyContentProvider: com.sap.portal.appintegrator.sap.BSP , Error ,com.sap.portal.ivs.semantic.iViewService , sap.com/irj , horn
    I further saw, that portalapp.xml in pcd (browse over pcd-browser) after deploying, only has 409 bytes.
    "portalapp.xml view, download 409 Tue Nov 21 17:54:08 CET 2006"
    The content of this file is:
    " <?xml version="1.0" encoding="iso-8859-1" ?>
    - <application>
    - <!-- THIS FILE IS A COPY OF THE ORIGINAL VERSION STORED IN THE PCD. PLEASE DO NOT CHANGE IT!
    -->
    - <application-config>
    <property name="ClassLoadingPolicy" value="5.0" />
    <property name="DeploymentPolicy" value="5.0" />
    <property name="AuthenticationPolicy" value="5.0" />
    </application-config>
    <components />
    <services />
    </application>"
    So there must be an error when I deploy the backup-PAR to server. But after deploying I get the message:
    "Messages:
    INFO: Detected Portal Archive File: com.sap.portal.appintegrator.sap.parINFO: Application successfully stored in the PCD
    Messages from Server ID 7805250
    INFO: com.sap.portal.appintegrator.sap has been successfully updated. "
    additionally it seems that services that are defined in portalapp.xml aren't deployed, if I redeploy the backup of com.sap.portal.appintegrator.sap.par. The names of this services are IViewURLGenerator and Transaction_Configuration under com.sap.portal.appintegrator.sap in service tree.
    The portalapp.xml component aren't attached to the corresponding security zones, too. For example in Portal Content Browser I see:
    ara:/security/sap.com/NetWeaver.Portal/low_safety/com.sap.portal.appintegrator.sap/components/BSP
    If I select Where-Used on this Element, there is the message:
    "No component is bound to this security zone"
    and
    "No service is bound to this security zone"
    I have no further idea how I can deploy this par-File that it works correctly. Hope you can help me!
    Thanks in advance.
    Best regards,
    Daniel

    Hi,
    now I searched the directories again and I found under ROOT/WEB-INF/deployment/pcd
    three files with name "com.sap.portal.appintegrator.sap.par" but three file-extensions:
    -log
    -err
    -bak
    In log-File there is shown an error while deploying...perhaps that helps analysing.
    Here I list the content of the log-File:
    2006-11-21_10-22-16
    Application upload failed: com.sap.portal.appintegrator.sap.par
    java.lang.InternalError: jzentry == 0,
    jzfile = 4333072224,
    total = 94,
    name = /usr/sap/TEP/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.sap.portal.appintegrator.sap.par,
    i = 1,
    message = invalid LOC header (bad signature)
         at java.util.zip.ZipFile$2.nextElement(ZipFile.java:322)
         at com.sapportals.portal.prt.deployment.ArchiveIterator.iterate(ArchiveIterator.java:46)
         at com.sapportals.portal.prt.deployment.UploadProcess.upload(UploadProcess.java:60)
         at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:835)
         at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)
         at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)
         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.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:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Best regards,
    Daniel

  • Error While uploading PAR File into NWDS

    Hi Experts,
    I have been to this location:
    Server(D)\usr\sap\P64(SID)\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
    I have copied this file com.sap.portal.runtime.logon.par.bak and pasted on my desktop.
    Changed the name to com.mycompany.portal.runtime.logon.par
    I tried to upload the file to NWDS(File --> Import --> Par file) and I am getting the fallowing error.
    http://imageshack.us/photo/my-images/853/error1un.png/
    and when i click OK on above Error
    i get this errors : http://imageshack.us/photo/my-images/571/error2v.png/
    I am unable to upload the Par file did i miss something?
    Regards,
    Siva

    Dear Siva,
    that is indeed strange.
    Still don't know if this could be an issue with your NWDS or the PAR itself.
    So let's do 2 tests
    ===============================================
    TEST NR. 1
    Let's try and check the NWDS first by creating a custom PAR.
    Don't worry, it's easy.
    Just open your NWDS and go to the top menu
    File > New > Project
    Inside the popup window that will open please choose
    Portal Application (on the left) and Create a Portal Application Project (on the right)
    Then give any name you would like (no spaces or dots, etc...)
    You now have a Portal project created on NWDS ( you will see a folder on the left side with your project name)
    Click on that folder with your LEFT mouse button and choose EXPORT
    Choose PAR File
    Choose your Project
    Choose a path where you want your PAR file to be saved. (uncheck the deploy PAR file, but check the include the source code).
    And click Finish.
    Now delete the project you have created (by clicking on the folder with your LEFT mouse button again, but chose DELETE project)
    Now you're ready to re-import the PAR file.
    ===============================================
    TEST NR. 2
    Maybe your standard PAR file that you've downloaded doesn't have the source code included or is corrupted.
    Please try to open it with a ZIP program and check what type of structure/files you have there.
    Have you also checked your NWDS log ?
    You could also share here that log, so that I can better help you.
    Kindest Regards
    /Ricardo

Maybe you are looking for

  • HT1349 I have i tunes on two computers using the same apple id but each library is not showing the same songs

    I have i tunes on the computer with over 1000 songs on it and i also have loaded i tunes on my laptop as i want to get rid of the computer but the library on the laptop is not showing the same songs how can i transfer the songs from the computer to t

  • Problem launching Campaign from UI

    Hi All We have a problem launching campaign from UI screen,as when we try and launch the campaign from the screen following error is coming: Cannot display view BSPWD_BASICS/WorkAreaHostViewSet of UI Component CRM_UI_FRAME An exception has occurred E

  • Error in oc4j standalone & JAX-WS 2.0

    Hi!! I'm trying to generate a SOAP Message with this code: MessageFactory factory = MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL); response = factory.createMessage(); SOAPPart parte = response.getSOAPPart(); parte.setContent(xmlSource);

  • PO Value exceeded the ION Budget Value

    We are able to add more value to the PO than the budgeted ION value attached to the PO .This is a standard SAP  functionality that it should not allow the PO value to be more than the ION budget .Not able to arrive  how this can happen .If some one c

  • 802.1x Wireless - Enforce user AND machine authentication

    I am using ACS v5.6 and I'd like to confirm that it is not possible to enforce both user and machine authentication against AD before allowing wireless access to Windows 7 clients, using PEAP/MSCHAPv2 and the built-in 802.1x supplicant. The only work