Weather magnet PAR File Export Error

I have created a weather application PAR File following this blog:  Create a weather magnet  using xml feed from weather.com
As far as I can tell I have followed everything correctly however when I select Export to create the file I get the following error:
Nov 11, 2008 11:32:54 AM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[main,5,main]] ERROR: ep_wa: Build failed for myl.com/ep_wa(myl.com_MYLAN_1) in variant "default": The Build terminated with errors
Build log -
Development Component Build (2008-11-11 11:32:54)
  Component name: ep_wa
  Component vendor: myl.com
  SC compartment: myl.com_MYLAN_1
  Configuration: JP1_EPPHASE1_D
  Location: JP1_EPPHASE1_D
  Source code location: http://max-sap50:50000/dtr/ws/EPPHASE1/myl.com_MYLAN/dev/inactive/DCs/myl.com/ep_wa/_comp/
  DC root folder: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_comp
  DC type: Enterprise Portal
  DC subtype: Portal Application Module
  Host: 03-M100236
DC Model check:
   All used DCs are available locally
   validating dependency to build plugin "sap.com/tc/bi/bp/portalapplication"
   validating dependency to  public part "default" of DC "sap.com/webservices_lib"
   validating dependency to  public part "default" of DC "sap.com/sapxmltoolkit"
   validating dependency to  public part "default" of DC "sap.com/com.sapportals.htmlb"
   validating dependency to  public part "default" of DC "sap.com/epbc.prtapi._api"
   validating dependency to  public part "default" of DC "sap.com/epbc.prtpars._htmlb"
   validating dependency to  public part "default" of DC "sap.com/epbc.prtpars._soap"
   validating dependency to  public part "default" of DC "sap.com/epbc.prtapi._test"
   validating dependency to  public part "default" of DC "sap.com/servlet"
   validating dependency to  public part "default" of DC "sap.com/jaxm"
   DC model check OK
Start build plugin:
   using build plugin: sap.com/tc/bi/bp/portalapplication
   starting build plugin from : C:Documents and Settingsm100236.dtc3DCssap.com     c i pportalapplication\_compgendefaultpublicdef
Build Plugin 'PortalAppPlugin', Version 7.00 SP 15 (645_VAL_REL, built on 2008-02-16 08:47:10 CET, CL76043)
   development component:  ep_wa (myl.com)
      software component:  MYLAN (myl.com)
                location:  JP1_EPPHASE1_D
                    type:  Enterprise Portal, subtype Portal Application Module
           build variant:  default
         output location:  C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefault
       generation folder:  C:Documents and Settingsm100236.dtc3     EBC1BF499DA88943638C12CB3AD23D86
       plugin start time:  2008-11-11 11:32:54 GMT-05:00 (EST)
                 Java VM:  Java HotSpot(TM) Client VM, 1.5.0_07-b03 (Sun Microsystems Inc.)
General options:
  convert *.xlf to *.properties: yes
  include sources for debugging: yes
Warning: Package folder "src.api" exists but is empty and will be ignored.
Checking path lengths for sources
Path length checks finished in 0.015 seconds
Preparing data context..
No public part descriptor found for component "webservices_lib" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "sapxmltoolkit" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sapportals.htmlb" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtapi._api" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtpars._htmlb" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtpars._soap" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "epbc.prtapi._test" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "servlet" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "jaxm" (vendor "sap.com"), public part "default", using legacy mode.
No 'default' JDK defined, will use running VM.
Data context preparation finished in 0.032 seconds
Creating Ant build file..
  Creating output file: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefaultlogs uild.xml
  [Velocity] Error: VM #CreateConfigArchive: error : too few arguments to macro. Wanted 3 got 0
  Using macro file:     C:Documents and Settingsm100236.dtc3DCssap.com     c i pportalapplication\_compgendefaultpublicdefmacros uild.vm
DC specific options:
  Portal Application file name:   ep_wa.par
  Include sources in application: no
  Deploy type:                    online
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Warning: Internal warning: IComponentDependency#getPublicPartPurpose(String) should no longer be used.
Build file creation finished in 0.078 seconds
Starting Ant..
  Using build file:     C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefaultlogs uild.xml
  Using build target:   build
  Using Ant version:    1.6.2
compile:
      [echo] Compiling Java sources in src.core
      [echo] Starting Java compiler
      [echo] Settings:
      [echo]         debug: on
      [echo]      optimize: off
      [echo]   deprecation: default
      [echo]       verbose: default
      [echo]      encoding: UTF8
      [echo]        source: default
      [echo]        target: default
      [echo]   source path: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compsrc.core
      [echo]    class path:
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjava oot.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjavaiq-lib.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjava     c_sec_wssec_lib.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjavautil.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comwebservices_lib\_compgendefaultpublicdefaultlibjavawebservices_lib.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtapi._test\_compgendefaultpublicdefaultlibjavaprttest.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtpars._soap\_compgendefaultpublicdefaultlibjavacom.sap.portal.runtime.application.soap_api.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtpars._soap\_compgendefaultpublicdefaultlibjavacom.sap.portal.runtime.application.soap_core.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtapi._api\_compgendefaultpublicdefaultlibjavaprtapi.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comepbc.prtpars._htmlb\_compgendefaultpublicdefaultlibjavacom.sap.portal.htmlb_api.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comjaxm\_compgendefaultpublicdefaultlibjavajaxm-api.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comjaxm\_compgendefaultpublicdefaultlibjavasaaj-api.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comservlet\_compgendefaultpublicdefaultlibjavaservlet.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comsapxmltoolkit\_compgendefaultpublicdefaultlibjavasapxmltoolkit.jar
      [echo]       C:Documents and Settingsm100236.dtc3DCssap.comcom.sapportals.htmlb\_compgendefaultpublicdefaultlibjavahtmlb.jar
      [echo]    output dir: C:Documents and Settingsm100236.dtc3     EBC1BF499DA88943638C12CB3AD23D86classessrc.core
     [javac] Compiling 1 source file to C:Documents and Settingsm100236.dtc3     EBC1BF499DA88943638C12CB3AD23D86classessrc.core
     [javac] ERROR: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compsrc.corecommylwadisplay.java:23: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier
     [javac] ERROR: (try -source 1.4 or lower to use 'enum' as an identifier)
     [javac] ERROR: import com.sapportals.htmlb.enum.CellHAlign;
     [javac] ERROR:                             ^
     [javac] ERROR: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compsrc.corecommylwadisplay.java:24: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier
     [javac] ERROR: (try -source 1.4 or lower to use 'enum' as an identifier)
     [javac] ERROR: import com.sapportals.htmlb.enum.DropdownListBoxDesign;
     [javac] ERROR:                             ^
     [javac] 2 errors
Error: C:Documents and Settingsm100236.dtc3DCsmyl.comep_wa\_compgendefaultlogs uild.xml:104: Compile failed; see the compiler error output for details.
     at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:938)
     at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
     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:585)
     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 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: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)
Ant runtime 0.047 seconds
Ant build finished with ERRORS
Compile failed; see the compiler error output for details.
Error: Build stopped due to an error: Compile failed; see the compiler error output for details.
Build plugin finished at 2008-11-11 11:32:54 GMT-05:00 (EST)
Total build plugin runtime: 0.267 seconds
Build finished with ERROR

Thanks Harini,  That solved my Export error, however I am still having issues withthe Weather Magnet Application.  After uploading it and creating a PAR File iView I am getting lots of errors that I can't figure out.  (I haven't quite gotten the hang of reading the error logs yet). 
#1.5 #C28BB00110020073000004F70015D02200045C10645C2F09#1227125379836#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#m100236#18970##n/a##b52d80f0b67511dd8f12c28bb0011002#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#/System/Server#Java###Exception ID:03:09_19/11/08_0083_9333450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : ep_wa.display
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:242)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.myl.wa.display of Portal Component ep_wa.display because: Could not instantiate implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 26 more
Caused by: java.lang.UnsupportedClassVersionError: (com/myl/wa/display) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:224)
at com.sapportals.portal.prt.util.AutoClassLoader.findClassInternal(AutoClassLoader.java:880)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClassLocally(AutoClassLoader.java:1250)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1388)
at com.sapportals.portal.prt.util.AutoClassLoader$2.run(AutoClassLoader.java:1465)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1461)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 30 more
#1.5 #C28BB00110020073000004F90015D02200045C10645C633D#1227125379850#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#m100236#18970##n/a##b52d80f0b67511dd8f12c28bb0011002#SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Java###03:09_19/11/08_0083_9333450
[EXCEPTION]
#1#java.lang.UnsupportedClassVersionError: (com/myl/wa/display) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:224)
at com.sapportals.portal.prt.util.AutoClassLoader.findClassInternal(AutoClassLoader.java:880)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClassLocally(AutoClassLoader.java:1250)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1388)
at com.sapportals.portal.prt.util.AutoClassLoader$2.run(AutoClassLoader.java:1465)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sapportals.portal.prt.util.AutoClassLoader.loadClass(AutoClassLoader.java:1461)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:242)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #C28BB00110020070000006010015D02200045C1064C8BAFB#1227125386951#com.sap.portal.SOAPLogger#sap.com/irj#com.sap.portal.SOAPLogger#m100236#18970##n/a##b52d80f0b67511dd8f12c28bb0011002#SAPEngine_Application_Thread[impl:3]_17##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
#1#SOAP Fault Exception [Actor [max-sap55] com.sapportals.portal.prt.service.soap.exception.SoapFaultHandler] : The User Authentification is not correct to access to the Portal Service com.sap.portal.prt.soap.Bridge or the service was not found.
<type>java.lang.IllegalAccessError</type>

Similar Messages

  • PAR File Export

    I have a Development Component it is an Enterprise Portal Application Standalone.  It is a simple application for a weather magnet using RSS Feeds.
    It was created by another developer and his instructions for deployment were to Right Click the project and choose Quick PAR Upload->however this option is greyed out to me.  I tried to do a simple export (which is what we do with the Enterprise Portal Application Module DCs) but the project is not listed in the options of projects to select.
    I have tried to create a new Enterprise Portal Application Module DC and copied this code into the new DC and it exported fine only when I tried to run the iView containing the application I received errors - I assumed the application was broken but the developer who created the application said it must be Standalone to work so I am just trying to figure out why I cannot deploy a Standalone App

    Please read this:
    http://help.sap.com/saphelp_nw04/helpdata/en/00/ef0942364ec417e10000000a155106/frameset.htm
    Standalone application build should result in SDA file, which has PAR file inside.
    SDA file, once you get it, can be deployed via SDM.
    Trgards,
    Slava

  • Par file deployment error

    Hi
    I am trying to deploy the par file from NWDS. First time i was able to deploy with out any error. But after that i get the following error (Taken from sap-plugin.log)
    [30.05.06 / 11:05] #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://xxxx:50100/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=xxxxxxxx&j_password=xxxxxxxxx&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: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)
    I am using the administrator user id for deploying the par. I am using NWDS Version: 7.0.07 (NW 2004s)
    Any help on this
    Regards
    NagaKishore V

    Hi
    Try upload from portal
    Login to Portal using Administrator id or any account having super_admin role.(admin /admin)
    Navigate through System Administrator>>Support>>Portal runtime>>"Portal Anywhere" Admin Tools>>Administrator Console
    You will see a link for uploadin the par file from there
    Cheers
    Jawahar Govindaraj

  • Layer Comps To Files - Export error: Could not complete this operation. There are no user slices

    I have been using the Export Layer Comps To Files scrips that ships with Adobe Photoshop CS5 for a while and found it very useful, apart from the numbers it automatically adds as a prefix to the layercomp name.
    A friend pointed me in the direction of a altered version of this scrips which removes the numbers and only exports the layer comp name, gerat I thought. Not great! After using this successfully for a while the scrip started to throw up errors whenever I attempted to export. Either "No layer comps found" or "Adobe Save for Web & Devices Error: Could not complete this operation. There are no user slices." As I knew there were layercomps for the first error and knew that I had not created any slices for the second error I was pretty miffed. Fortunately I had the foresight to make a copy of the original script from the Photoshop presets library.
    I have since deleted the offending script out of my presets folder and copied the original script back in however the error still persists. I constantly receive Adobe Save for Web & Devices Error: Could not complete this operation. There are no user slices. I have searched the forums and around the net to try and find a solution for this problem but none seem to present themselves. I am perplex how this error can persist when the original script is now being used.
    If there's is anyone out there who can help me resolve this I'd be most grateful. As I say I've tried to resolve this myself and am pretty computer savvy but this one has defeated me
    Thanks in advance

    The problem seems to be already solved, but I'm commenting this for future reference.
    This has happened to me too and I think I know what causes it.
    It happens when you...
    1) Do "Save for Web" with the "All User Slices" selected in the dropdown menu "Slices".
    (This can only be done with a file that has a user slice)
    2) Then try to use the "Layer Comp to Files" script to a file that doesn't have any slices.
    To avoid this you need to once open a file that "has" a user slice and save with
    the "All Slices" option in the "Slices" menu and then go back to the file you want
    to run the script to.
    When you run the script, the saved "Slices" option from the previous export seems to
    be used and causes an error when there are no user slice.
    I also found a fix to the script to avoid this error to come out.
    This can be also applied to the fix to "remove the numbers" added to the head of the
    exported file names.
    The number removal script goes something like this...
    var fileNameBody = exportInfo.fileNamePrefix;
    if (fileNameBody != "") fileNameBody += "_";
    fileNameBody += compRef.name;
    this should replace the "Layer Comps to Files.jsx" lines 188-190.
    In addition to that, the script below needs to be added below line 818 and line 863.
    (This line numbers are those before any alterations to the "Layer Comps to Files.jsx" script)
    var idSWsl = charIDToTypeID( "SWsl" );
    var idSTsl = charIDToTypeID( "STsl" );
    var idSLAl = charIDToTypeID( "SLAl" );
    desc4.putEnumerated( idSWsl, idSTsl, idSLAl );
    The line right above where the above script should be inserted should read as the following...
    desc4.putPath( id44, new File( exportInfo.destination + "/" + fileNameBody + ".png") );
    Actually it can be added any where after the "desc4" variable is declared but I specified just
    to make it simple.
    This sets the "Save for Web" "Slices" settings to "All User Slices".

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

  • NWDS 7.0 Error during Quick PAR Upload and while trying Exporting PAR-File

    Hello,
    I am trying to use the functions "Export as PAR-File" and "Quick PAR Upload" in NWDS 7.0.
    Unfortunately I got an error every time when I am trying to use this functions. I am using the package explorer in the Java perspectiv in NWDS for starting this functions. The error tells me the following:
    "Unable to connect to the Portal"
    "Operation failed: Please make sure the server "XY" is running or check the log (sap-plugin.log) for more detail"
    Thats all.
    When I am looking in the log-file I can read the following messages:
    "ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: GET_VIEW:ALL]"
    "ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: IS_VIEW_EXISTS:ALL]"
    "ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: SIZE_OF_VIEW:ALL]"
    "ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: READ_ENTRY:ALL]"
    LOGIN.ERROR|null|| Login Method=[default] UserID=[user_Admin] IP Address=[192.168.xxx] Reason=[Cannot authenticate the user]
    I have tried this with several users and their passwords. All of the users have admin-rights at least in the portal. One of them even in the SDM.
    I can sucessfully deploy webdynpros from NWDS into the same Portal with this users.
    We are using SAP Logon Tickets and SSO is configured working fine between Portal and backend.
    We have imported Key Store File in NWDS unter Window --> Preferences --> Java Development Infrastructure.
    And we are not using the NWDI.
    Who knows why I cannot even export par-files? Are their any configurations missing?
    Best regards,
    Iris

    It is mentioning about authentication.
    check whether you have access to deploy directly or not ? maybe direct deployment into portal disabled .
    I think you have to follow the procedure of checkout and activate procedure.
    Can you clarify few things
    1) Are you using NWDI Based Transports in your landscape?
    Login Method=default UserID=user_Admin IP Address=http://192.168.xxx Reason=Cannot authenticate the user
    http://192.168.xxx  is it your development portal?
    Did you clarify with admin people whether direct deployment disabled?
    Koti Redd

  • Error while exporting PAR file

    Hi,
    I am getting an error "Build of project failed" while exporting a PAR file to the project folder and it is showing that "The project was not built due to classpath errors (incomplete or involved in cycle)." I am very new to this technology, so please help me in this.

    Check if the required JAR files under /dist/lib or /dist/private/lib are added in the project structure.
    Refer http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d58bb490-0201-0010-64a1-9e5165e5dbac?QuickLink=index&overridelayout=true
    ~ Dhanz

  • 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

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

  • 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

  • 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 uploading a PAR file

    Hello,
    an upload of a new PARFile ends with the foll. error.
    Anybody seen before?
    com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.updateObject(ApplicationRepositoryService.java:717)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeApplication(ApplicationRepositoryService.java:389)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:306)
         ... 34 more
    Caused by: com.sap.sql.log.OpenSQLException: Cannot assign a java.io.ByteArrayInputStream object of length 0 to host variable 18.
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setBinaryStream(CommonPreparedStatement.java:838)
         at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setBinaryStream(PreparedStatementWrapper.java:401)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.storeAttribute(AttributeHeadersTable.java:431)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.insert(AttributeHeadersTable.java:248)
         at com.sapportals.portal.pcd.pl.PlObject.save(PlObject.java:541)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:616)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:640)
         ... 54 more

    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

  • 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

  • Error while deploying PAR files for JSPDynPage & HTMLB

    Hi,
    I am facing following error while exporting the PAR file.
    PAR upload failed:
    *Please make sure the server ***** is running. HTTPS protocol is not supported, please ensure this server is not using HTTPS.*
    I checked with the server. It is running fine.
    Please help..
    Regards,
    Niraj

    hi niraj,
    Login into portal System Administration->support->portal runtime->Browse Deployment
    select web-inf (Browse)-deployment(Browse) check you par file...
    Other way around...
    go to portal content -> create iveiw ->using Par (not using template)->select ur par file....and done..
    Regards
    parth

Maybe you are looking for

  • Only one user at a time can log in per client

    Server: 10.6.2 Client: 10.5.8 The share point on the server is the default of /Users. Home directories are configured as /Network/Severs/hostname/Users/username. In the "Home" tab of each user, the home directory shows up as "afp://hostname/Users", w

  • How to XI error message will mapped to the SOAP faul message-SOAP(Axis)

    Hi,   Receiver end I am using SOAP (Axis) adapter and I am getting the system error and I am not getting the payload in SXMB_MONI. What ever the error message how do MAP as a SOAP Fault message in SXMB_MONI. I found the Solution from OSS note 1039369

  • BAPI to create a billing document with reference to delivery or sales order

    Hi, Does anyone know any BAPI or function module that allows the creation of a billing document with reference to a sales order or to a delivery. Maybe the BAPI_BILLINGDOC_CREATEFROMDATA may be used to create a billing document with reference to a sa

  • Screen turns bright white while display freezes? Any one know why?

    The screen freezes and gets brighter and brighter until it becomes all white. If I move the screen of the laptop the display returns to normal for a brief second then starts turning white all over again. Anyone know what the problem could be? I have

  • Data flowing to top of second page

    Hello everyone I have a report which has a logo on the top. There is typically about 300 pages but (1 per customer). But if there is more detail than can fit on one page then the remainder is just placed over the logo on the next page even though it'