Com.sap.sdb.tools.databasemanagement.DM_Exception: Runtime environment erro
Hi,
using Database Studio when i click on Analyzer tab of Administration tool i get follow error:
19/05/2009 22:12:05
ERROR Runtime environment error
1,OS error: 'No such file or directory'
Component : UIDBM
Detail Message: com.sap.sdb.tools.databasemanagement.DM_Exception: Runtime environment error
1,OS error: 'No such file or directory'
at com.sap.sdb.tools.databasemanagement.internal.DM_Session.execute(DM_Session.java:150)
at com.sap.sdb.tools.databasemanagement.internal.commands.DM_BaseCommand.doExecute(DM_BaseCommand.java:130)
at com.sap.sdb.tools.databasemanagement.internal.commands.DM_DatabaseCommand.doExecute(DM_DatabaseCommand.java:53)
at com.sap.sdb.tools.databasemanagement.internal.commands.DM_BaseCommand.execute(DM_BaseCommand.java:69)
at com.sap.sdb.tools.databasemanagement.internal.DM_AnalyzerLog.open(DM_AnalyzerLog.java:66)
at com.sap.sdb.tools.databasemanagement.internal.DM_AnalyzerLogItems.readItems(DM_AnalyzerLogItems.java:99)
at com.sap.sdb.tools.databasemanagement.internal.DM_AnalyzerLogItems.refresh(DM_AnalyzerLogItems.java:89)
at com.sap.sdb.tools.ui.dbm.model.AnalyzerLogAdapter.fetchDeferredChildren(AnalyzerLogAdapter.java:82)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:207)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
is something wrong in my configurations or Analyzer tab cant check analyzer files from a remote server?
regards
Clóvis
Hi Lars,
file_getfirst ANALYZER#/20090520 returns:
0
END
2339 2339
keyname,mode,size,date,time,comment,filename
ANALYZER#/20090520/DBAN.prt UNKNOWN 1080209 20090520 220608 DB Analyzer File DBAN.prt
ANALYZER#/20090520/DBAN_LOGGING.csv UNKNOWN 6670 20090520 220608 DB Analyzer File DBAN_LOGGING.csv
ANALYZER#/20090520/DBAN_CACHES.csv UNKNOWN 9686 20090520 220608 DB Analyzer File DBAN_CACHES.csv
ANALYZER#/20090520/DBAN_FILLING.csv UNKNOWN 7335 20090520 220608 DB Analyzer File DBAN_FILLING.csv
ANALYZER#/20090520/DBAN_GC.csv UNKNOWN 5392 20090520 220608 DB Analyzer File DBAN_GC.csv
ANALYZER#/20090520/DBAN_TASK_IO.csv UNKNOWN 7026 20090520 220608 DB Analyzer File DBAN_TASK_IO.csv
ANALYZER#/20090520/DBAN_IO.csv UNKNOWN 9976 20090520 220608 DB Analyzer File DBAN_IO.csv
ANALYZER#/20090520/DBAN_TRANSACTIONS.csv UNKNOWN 7319 20090520 220608 DB Analyzer File DBAN_TRANSACTIONS.csv
ANALYZER#/20090520/DBAN_TASK_ACTIVITIES.csv UNKNOWN 9721 20090520 220608 DB Analyzer File DBAN_TASK_ACTIVITIES.csv
ANALYZER#/20090520/DBAN_LOAD.csv UNKNOWN 8867 20090520 220608 DB Analyzer File DBAN_LOAD.csv
ANALYZER#/20090520/DBAN_SHARED_SQL.csv UNKNOWN 9370 20090520 220608 DB Analyzer File DBAN_SHARED_SQL.csv
ANALYZER#/20090520/DBAN_STRATEGY_PRIMKEY.csv UNKNOWN 5612 20090520 220608 DB Analyzer File DBAN_STRATEGY_PRIMKEY.csv
ANALYZER#/20090520/DBAN_STRATEGY_INDEX.csv UNKNOWN 10043 20090520 220608 DB Analyzer File DBAN_STRATEGY_INDEX.csv
ANALYZER#/20090520/DBAN_STRATEGY_SCANS.csv UNKNOWN 6193 20090520 220608 DB Analyzer File DBAN_STRATEGY_SCANS.csv
ANALYZER#/20090520/DBAN_BACKUP.csv UNKNOWN 4740 20090520 220608 DB Analyzer File DBAN_BACKUP.csv
ANALYZER#/20090520/DBAN_TASK_STATES.csv UNKNOWN 6088 20090520 220608 DB Analyzer File DBAN_TASK_STATES.csv
ANALYZER#/20090520/DBAN_OVERVIEW.csv UNKNOWN 6759 20090520 220608 DB Analyzer File DBAN_OVERVIEW.csv
ANALYZER#/20090520/DBAN_REGIONS.csv UNKNOWN 5552 20090520 220608 DB Analyzer File DBAN_REGIONS.csv
ANALYZER#/20090520/DBAN_RW_LOCKS.csv UNKNOWN 5379 20090520 220608 DB Analyzer File DBAN_RW_LOCKS.csv
ANALYZER#/20090520/DBAN_SPINLOCKS.csv UNKNOWN 4720 20090520 220608 DB Analyzer File DBAN_SPINLOCKS.csv
ANALYZER#/20090520/DBAN_IOTHREADS.csv UNKNOWN 5073 20090520 220608 DB Analyzer File DBAN_IOTHREADS.csv
ANALYZER#/20090520/DBAN_CPU_UTILIZATION.csv UNKNOWN 8835 20090520 220608 DB Analyzer File DBAN_CPU_UTILIZATION.csv
file_getfirst ANALYZER#/20090520/DBAN.prt returns:
1
CONTINUE
1080209 15917
===== #0 at 2009-05-20 09:05:30
* I Number of CPU's 4, processor type: x86_64
CON: NUM_PHYSICAL_CPU > 1
VAL: 4 > 1
* I Physical memory 3943 MB, virtual memory 6000 MB, memory allocated from instance: 3246 MB
CON: NUM_PHYSICAL_CPU > 1
VAL: 4 > 1
* I Operating system: Linux 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006
CON: 1
VAL: 1
* I Kernel version: Kernel 7.6.03 Build 007-123-157-515
CON: 1
VAL: 1
* I Instance SUNDOWN (dcpr0136n) is up since 2009-05-18 21:45:40
CON: 1
VAL: 1
* I Configuration: number of CPUs (MAXCPU): 4, max user tasks: 500
CON: 1
VAL: 1
* I Size of data cache 2045.56 MB
CON: DATA_CACHE_SIZE > 1
VAL: 2094656 > 1
* I Number of data volumes: 5
CON: 1
VAL: 1
* I PACKET_SIZE is 131072
CON: ENV_PACKET_SIZE
VAL: 131072
* I SQL commands executed: 12921239
CON: SQL_Cmds > 0
VAL: 12921239 > 0
===== #1 at 2009-05-20 09:06:20
* I SQL commands executed: 6346, avg. 97 per second
CON: PureSQL_Cmds > INTERVAL * 5
VAL: 6346 > 68 * 5
* W3 69 command cache cleanups! 6 commands reloaded, 40960 execution plans and 188 commands deleted
CON: CmdCacheCleanups > INTERVAL
VAL: 69 > 68
* W3 Task 120 (appl. 0) is waiting for lock 'row_exclusive' on table TITULOPAGAMENTO since 68s, locked 'tab_share' from task 429 (appl. 0, state Vwait)
CON: LOCK_REQUESTOR_TID[" 2898305"] == last(LOCK_REQUESTOR_TID[" 2898305"]) && LOCK_WAITER_TRANS[" 2898305"] == last(LOCK_WAITER_TRANS[" 2898305"])
VAL: 120 == 120 && 2898305 == 2898305
* W3 Task 429 (appl. 0) is waiting for lock 'tab_share' on table TITULOCOBRANCA since 68s, locked 'row_exclusive' from task 348 (appl. 0, state Vwait)
CON: LOCK_REQUESTOR_TID[" 2880370"] == last(LOCK_REQUESTOR_TID[" 2880370"]) && LOCK_WAITER_TRANS[" 2880370"] == last(LOCK_WAITER_TRANS[" 2880370"])
VAL: 429 == 429 && 2880370 == 2880370
* W3 Task 361 (appl. 0) is waiting for lock 'row_exclusive' on table TITULOPAGAMENTO since 68s, locked 'tab_share' from task 429 (appl. 0, state Vwait)
CON: LOCK_REQUESTOR_TID[" 2921405"] == last(LOCK_REQUESTOR_TID[" 2921405"]) && LOCK_WAITER_TRANS[" 2921405"] == last(LOCK_WAITER_TRANS[" 2921405"])
VAL: 361 == 361 && 2921405 == 2921405
* W3 Task 313 (appl. 0) is waiting for lock 'row_exclusive' on table TITULOPAGAMENTO since 68s, locked 'tab_share' from task 429 (appl. 0, state Vwait)
CON: LOCK_REQUESTOR_TID[" 2913185"] == last(LOCK_REQUESTOR_TID[" 2913185"]) && LOCK_WAITER_TRANS[" 2913185"] == last(LOCK_WAITER_TRANS[" 2913185"])
VAL: 313 == 313 && 2913185 == 2913185
* W3 Task 135 (appl. 0) is waiting for lock 'row_exclusive' on table TITULOPAGAMENTO since 68s, locked 'tab_share' from task 429 (appl. 0, state Vwait)
CON: LOCK_REQUESTOR_TID[" 2918713"] == last(LOCK_REQUESTOR_TID[" 2918713"]) && LOCK_WAITER_TRANS[" 2918713"] == last(LOCK_WAITER_TRANS[" 2918713"])
VAL: 135 == 135 && 2918713 == 2918713
* W3 Task 563 (appl. 0) is waiting for lock 'row_exclusive' on table TITULOPAGAMENTO since 68s, locked 'tab_share' from task 429 (appl. 0, state Vwait)
CON: LOCK_REQUESTOR_TID[" 2911020"] == last(LOCK_REQUESTOR_TID[" 2911020"]) && LOCK_WAITER_TRANS[" 2911020"] == last(LOCK_WAITER_TRANS[" 2911020"])
VAL: 563 == 563 && 2911020 == 2911020
Similar Messages
-
When I try running my web application from browser after deploying succesfully, I get following error.I checked web.xml & config.xml..they are welformed.
Application cannot be started!
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application sap.com/crm.b2b_hsp.
at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:101)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.prepareStart(WebContainer.java:383)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:323)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:358)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:116)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:217)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4350)
at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:520)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:341)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:161)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:135)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:349)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:116)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:217)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4350)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2466)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2339)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:41)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:141)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:101)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Cannot get a naming context or initialize the application's naming environment.
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.createNamingContexts(WebApplicationConfig.java:630)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.parse(WebApplicationConfig.java:101)
at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:579)
at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.createContext(WebContainerHelper.java:541)
at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:50)
... 24 morekinldy let me know what was the solution to this problem
-
Hi All,
Iam getting this error while trying to change "com.sap.portal.navigation.masthead.par" within portal. I have updated the HeaderiView.jsp and then saved the PAR file and uploaded the file. It was successful upload from Administration console. But after I logged into portal again, I got this error and even though I tried to revert back the changes, it still gives the same error. Has any one faced similar issue? We faced this during the IE8 (Internet explorer 8) upgrade to SP 27 in sap portal.
Thanks.
#1.#0003BA4D72F200540000000300003DEA00049C4FAA821F4E#1297765883836#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#O000001496#192##n/a##bbf9eef438ee11e08722000035d6a152#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error##Java###10:31_15/02/11_903258450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component :
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.pb.PageBuilder.createIviewProfile(PageBuilder.java:418)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:372)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:706)
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.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.navigation.PortalLauncher.doOnNodeReady(PortalLauncher.java:218)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
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.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:547)
at java.security.AccessController.doPrivileged(Native Method)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.sap.portal.navigation.Gateway.service(Gateway.java:101)
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:1060)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getDeploymentDescriptor(PortalApplicationItem.java:1622)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getConfiguration(PortalComponentItem.java:1022)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.refresh(PortalComponentItem.java:274)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:729)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 42 moreThanks Raghu.
I have tried that option as well. But, when I uploaded the PAR file from DEV to Sandbox environment, the header did not work, but I identified that the "portalapp.xml" file is only partially deployed (even though the PAR that is used for Upload (using Admin Console) contained all parameters. I could not understand why the portalapp.xml is only partially deployed.
After deployment the portalapp.xml has only 3 properties within it : ClassLoadingPolicy, value 5.0, DeploymentPolicy, value 5.0 and AuthenticationPolicy, value 5.0,
and all other attributes that are part of the uploaded par file are not present after deployment within "PAR directory within portalapps directory".
Edited by: jakk on Feb 16, 2011 5:17 PM
Edited by: jakk on Feb 16, 2011 5:19 PM -
Hi Subhra/ Asit,
The following is the main information form the log file and attched logfile with full info for your reference.
#1.5#00188B874AFD00320000000A000007B4000447710E97B363#1204450808802#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
usr
sap
SPP
JC01
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.portal.layouts.default
jsp
fullWidth.jsp [email protected]a6d4d7#
#1.5#00188B874AFD00320000000B000007B4000447710E97BD23#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]a6d4d7#
#1.5#00188B874AFD00200000000B000007B4000447710E97C15A#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
usr
sap
SPP
JC01
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.portal.layouts.framework
jsp
WAandNavPanel.jsp [email protected]16c192#
#1.5#00188B874AFD00200000000C000007B4000447710E97CCCC#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]16c192#
#1.5#00188B874AFD002900000049000007B4000447710EA4FBF8#1204450809677#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.
[EXCEPTION]
#2#fonterra.com/cmtuwlcmir~dispform/CMIRCreateNotificationDisplay#java.lang.NullPointerException
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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(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)
#1.5#00188B874AFD00290000004A000007B4000447710EA7E5F6#1204450809865#com.tssap.dtr.client.lib.protocol.session.Cookies#sap.com/tcwddispwda#com.tssap.dtr.client.lib.protocol.session.Cookies.setCookie(Cookie)#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Java###rejecting invalid cookie for domain "": #2#.fonterra.com#JSESSIONID#
#1.5#00188B874AFD00290000004B000007B4000447710EA8000D#1204450809880#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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(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)
#1.5#00188B874AFD00290000004D000007B4000447710EA803B8#1204450809880#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: java.lang.NullPointerException: null
Exception id: [00188B874AFD00290000004B000007B4000447710EA8000D]#
#1.5#00188B874AFD00290000004E000007B4000447710EA82DD2#1204450809896#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:168)
at javax.servlet.ServletOutputStream.print(ServletOutputStream.java:135)
at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendBodyText(HttpServletResponseFacade.java:957)
at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:948)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
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:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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(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)
#1.5#00188B874AFD002900000050000007B4000447710EA82F56#1204450809896#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)].The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
Exception id: [00188B874AFD00290000004E000007B4000447710EA82DD2]#
Regards
Krishna Kkinldy let me know what was the solution to this problem
-
Com.sap.kw java.lang.NullPointerException: FATAL ERROR:
We are getting a bunch of errors around cop.sap.kw in our J2EE defaultTrace log file.
Here is an example:
Apr 1, 2008 7:36:33 PM com.sap.kw.framework.FrontController [SAPEngine_Application_Thread[impl:3]_56] Path: Caught java.lang.NullPointerException: FATAL ERROR: Could not load E:\usr\sap\QAA\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\tc~kw_tc\servlet_jsp\SAPIKS2\root\WEB-INF\ApplConfig.xml
at com.sap.kw.framework.XMLConfiguration.<init>(XMLConfiguration.java:53)
at com.sap.kw.actions.ApplConfig.init(ApplConfig.java:83)
at com.sap.kw.framework.FrontController.init(FrontController.java:222)
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)
Has anyone ran into this before?Hi,
that file you mentioned exists in file system?
it seems somebody has changed incorrectly something in the file system.
regards.
roberti -
Hi,
We have just finish apply/update our SAP Netweaver WebAS 6.40 (Java) with the support package (SP25). When we test our application, we encountered the following exception
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
This exception seems to be intermittent. After some time, when we try again, we did not encountered this exception. But after we restart, the error appear again.
Please help.Hi,
On checking the trace log file, I noticed some security exception 'com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.'.
before the 'com.sap.engine.services.jndi.persistent.exceptions.NamingException : Error getting the server-side naming service functionality during getInitialContext operation. '
What could be the cause for 'BaseSecurityException: Caller not authorized' exception?
#1.5 #0003BA7B25C0002B000000000000394600048F300D41A62A#1283336450450#System.err#sap.com/CRRSRatingEAR#System.err#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.#
#1.5 #0003BA7B25C0002B000000010000394600048F300D437AAE#1283336450570#System.err#sap.com/CRRSRatingEAR#System.err#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.#
#1.5 #0003BA7B25C0002B000000030000394600048F300D47CA6E#1283336450850#com.sap.engine.services.security.authentication.logincontext#sap.com/CRRSRatingEAR#com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Java###Caller not authorized.
[EXCEPTION]
#1#com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:119)
at com.sap.engine.services.security.server.AuthenticationContextImpl.getSessionPool(AuthenticationContextImpl.java:395)
at com.sap.engine.services.security.server.AuthenticationContextImpl.getLoginContextFactory(AuthenticationContextImpl.java:740)
at com.sap.engine.services.security.server.AuthenticationContextImpl.getLoginContext(AuthenticationContextImpl.java:254)
at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:59)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.mbb.crrs.business.common.InitialContextFactory$SapWasContext.getInitialContext(InitialContextFactory.java:139)
at com.mbb.crrs.business.common.InitialContextFactory.getInitalContext(InitialContextFactory.java:81)
at com.mbb.crrs.business.common.ServiceLocator.<init>(ServiceLocator.java:286)
at com.mbb.crrs.business.common.ServiceLocator.getInstance(ServiceLocator.java:308)
at com.mbb.crrs.web.common.dao.ParamCacheDAO.<init>(ParamCacheDAO.java:56)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:182)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:166)
at com.mbb.crrs.common.CRRSInitServlet.init(CRRSInitServlet.java:33)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #0003BA7B25C0002B000000040000394600048F300D499B25#1283336450972#com.sap.engine.services.servlets_jsp.Deploy#sap.com/CRRSRatingEAR#com.sap.engine.services.servlets_jsp.Deploy#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Warning##Plain###application [CRRSWeb] Initialization of servlet <CRRSInitServlet> failed! The error is: com.mbb.crrs.common.exceptions.ApplicationConfigurationException: Unable to connect to WAS at 172.31.40.10:52004: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
at com.mbb.crrs.business.common.InitialContextFactory$SapWasContext.getInitialContext(InitialContextFactory.java:143)
at com.mbb.crrs.business.common.InitialContextFactory.getInitalContext(InitialContextFactory.java:81)
at com.mbb.crrs.business.common.ServiceLocator.<init>(ServiceLocator.java:286)
at com.mbb.crrs.business.common.ServiceLocator.getInstance(ServiceLocator.java:308)
at com.mbb.crrs.web.common.dao.ParamCacheDAO.<init>(ParamCacheDAO.java:56)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:182)
at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:166)
at com.mbb.crrs.common.CRRSInitServlet.init(CRRSInitServlet.java:33)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Thanks. -
Does anyone know what this error might be?
Details for 'Is the Adapter Engine running?'
==== Events on Server 19010950 ====
Adapter Engine, message: Fatal RecoverJob (Default Recover Job) failed.
(Details: Code: MS.JOB.RECOVER, Location: com.sap.aii.af.ra.ms.impl.core.archiving.executor.RecoverExecutor, Reason: java.lang.Exception: Failed to restart message ddc46f41-bdad-7cf1-b918-001b7832810c(INBOUND) remotely on cluster node 19011150. Reason: Could not execute cluster event, due to: Service"com.sap.aii.af.ms.svc"on cluster element 19,011,150 thrown an exception in receiveWait(), invoked by a request by cluster element 19,010,950., Time: 07.12.2008 10:00:00)
==== Events on Server 15965050 ====
Adapter Engine, message: Fatal Message listener localejbs/CIDXMessageListener could not be created for connection CIDXAdapter after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 07.12.2008 08:34:49)
Adapter Engine, message: Fatal Message listener localejbs/RNIFMessageListener could not be created for connection RNIFAdapter after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 07.12.2008 08:34:49)
Adapter Engine, message: Fatal Message listener localejbs/RNIF11MessageListener could not be created for connection RNIF11Adapter after 60 attempts.
(Details: Code: MS.APP.LISTENER.NOTFOUND, Location: com.sap.aii.af.ra.ms.runtime.ListenerFinder, Reason: Unknown, Time: 07.12.2008 08:34:49)
Reset event protocol:http://nytsappip.nyhq.nytint.com:50100/MessagingSystem/performance?resetSystemMatrixInClusterResolved in thread: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol ha
-
Hi all,
Kindly be informed that I get the following error while logging on to the B2B webshop from the B2B portal.
Your thoughts on this would be greatly appreciated.
com.sap.isa.businessobject.BORuntimeException: No entry for User Business Object found
at com.sap.isa.businessobject.BusinessObjectHelper.splitException(BusinessObjectHelper.java:78)
at com.sap.isa.user.businessobject.UserBase.isUmeLogonEnabled(UserBase.java:541)
at com.sap.isa.user.action.UserActions.isUmeLogonEnabled(UserActions.java:579)
at com.sap.isa.user.action.UserActions.performUmeLogin(UserActions.java:443)
at com.sap.isa.user.action.UserBaseAction.performUMELogin(UserBaseAction.java:89)
at com.sap.isa.user.action.PrepareLoginBaseAction.ecomPerform(PrepareLoginBaseAction.java:138)
at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:353)
at com.sap.isa.core.BaseAction.execute(BaseAction.java:211)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:674)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.internalModuleRelativeForward(RequestProcessor.java:1012)
at com.sap.isa.core.RequestProcessor.processForward(RequestProcessor.java:643)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:260)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.tealeaf.capture.LiteFilter.doFilter(LiteFilter.java:98)
at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Awaiting your earliest reply
Thanks
Mutu...Its a late response... but if someone gets the same issue here is the solution.
When you register try uppercase password . That should take care of that issue.
The problem is with function module CRM_ISA_IUSER_SWITCH , Note 946536.
Although the note says 5.0 the problem exists with ISA 4.0 too -
Cannot install SAP JVM tools in Eclipse
I get this message:
Cannot complete the install because one or more required items could not be found.
Software being installed: SAP HANA Cloud Platform Tools for Connecting to SAP HANA Systems 1.11.0 (com.sap.cloud.tools.eclipse.hana.feature.feature.group 1.11.0)
Missing requirement: SAP HANA Cloud Platform Tools for Connecting to SAP HANA Systems 1.11.0 (com.sap.cloud.tools.eclipse.hana.tunnel 1.11.0) requires 'bundle com.google.gson 2.1.0' but it could not be found
Cannot satisfy dependency:
From: SAP HANA Cloud Platform Tools for Connecting to SAP HANA Systems 1.11.0 (com.sap.cloud.tools.eclipse.hana.feature.feature.group 1.11.0)
To: com.sap.cloud.tools.eclipse.hana.tunnel [1.11.0]
I have checked the box to Contact all update sites during install per the note, but keep getting the same message. Some of the components have installed.I have downloaded eclipse 4.3.2 and restarted eclipse. When I try again to install SAP JVM tools, I get new error messages:
Cannot complete the install because one or more required items could not be found.
Software being installed: SAP HANA Studio Application Development (Developer Edition) 1.0.7400 (com.sap.ndb.studio.appdev.feature.devedition.feature.group 1.0.7400)
Missing requirement: SAP HANA Studio - AFL Connector 1.0.7400 (com.sap.ndb.studio.aflconnector 1.0.7400) requires 'bundle org.eclipse.graphiti 0.0.0' but it could not be found
Cannot satisfy dependency:
From: SAP HANA Studio - AFL Connector Feature 1.0.7400 (com.sap.ndb.studio.aflconnector.feature.feature.group 1.0.7400)
To: com.sap.ndb.studio.aflconnector [1.0.7400]
Cannot satisfy dependency:
From: SAP HANA Studio Application Development (Developer Edition) 1.0.7400 (com.sap.ndb.studio.appdev.feature.devedition.feature.group 1.0.7400)
To: com.sap.ndb.studio.appdev.feature.feature.group [1.0.7400]
Cannot satisfy dependency:
From: SAP HANA Studio Application Development 1.0.7400 (com.sap.ndb.studio.appdev.feature.feature.group 1.0.7400)
To: com.sap.ndb.studio.dbdev.feature.feature.group 1.0.0
Cannot satisfy dependency:
From: SAP HANA Studio Database Development 1.0.7400 (com.sap.ndb.studio.dbdev.feature.feature.group 1.0.7400)
To: com.sap.ndb.studio.aflconnector.feature.feature.group 1.0.0 -
Hi
We running windows server with ERP 6.0 and this was coppied from another server.
The JSPM fails with the following error.
Trouble Ticket Report
Java Support Package Manager for SAP NetWeaver'04s
SID................: $(/J2EE/StandardSystem/SAPSystemName)
Hostname...........: $(/J2EE/SAPGlobalHost)
Install directory..: $(/J2EE/StandardSystem/SAPSIDDirectory)
Database...........: $(/J2EE/DBSystem/DBInfoName)
Operating System...: $(/J2EE/StandardSystem/CentralInstance/J2EEEngineInstanceHost/OpSysType)
JDK version........: $(/SystemProperties/JavaVersion) $(/SystemProperties/JavaVendor)
JSPM version.......: $(/MAIN_VERSION)
System release.....: $(/J2EE/StandardSystem/Version)
ABAP stack present.: $(/J2EE/StandardSystem/BCSystemPresent)
The execution ended in error.
Could not load data model com.sap.sdt.jspm.model.JspmDataModel. See previous messages.
Class with name com.sap.sdt.j2ee.model.NWDISystemRole not found.
More information can be found in the log file .
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.tools.model.LoadException
Could not load data model com.sap.sdt.jspm.model.JspmDataModel. See previous messages.
JSPM_MAIN
JSPMPhases
NetWeaver Upgrade
SAPJup
Java Upgrade
SAPJup.LOG
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:
usr
sap
ERP
DVEBMGS10
j2ee
JSPM
log
log_2008_11_17_12_39_25
SAPJup.LOG]/>
<!PATTERN[SAPJup.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
#1.5 #C0000A0A0A3D00000000000F010E329300045BE031D40CA8#1226918373625#/System/Server/Upgrade/Jump##com.sap.sdt.ucp.pce.build.BuilderDirector.extractElements(BuilderDirector.java:132)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.pce.build.BuilderDirector.extractElements(BuilderDirector.java:132)#Java###Tag with name found.#2#ControlUnit#JSPM#
#1.5 #C0000A0A0A3D000000000010010E329300045BE031D577F0#1226918373718#/System/Server/Upgrade/Jump##com.sap.sdt.ucp.pce.build.BuilderDirector.createUnits(BuilderDirector.java:186)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.pce.build.BuilderDirector.createUnits(BuilderDirector.java:186)#Java###Creating control unit .#1#JSPM#
#1.5 #C0000A0A0A3D000000000011010E329300045BE031D6E720#1226918373812#/System/Server/Upgrade/Jump##com.sap.sdt.ucp.pce.ctrl.ExecutionDialog.showWelcomeDialog(ExecutionDialog.java:421)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.pce.ctrl.ExecutionDialog.showWelcomeDialog(ExecutionDialog.java:421)#Java###Could not process dialog because execution dialogs have been suppressed.#1#JspmWelcomeDialog#
#1.5 #C0000A0A0A3D000000000012010E329300045BE031D6E720#1226918373812#/System/Server/Upgrade/Jump##com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:103)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:103)#Java###Starting execution of action with name and type .#2#Unit#JSPM#
#1.5 #C0000A0A0A3D000000000013010E329300045BE032541218#1226918382015#/System/Server/Upgrade/Jump##com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:103)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:103)#Java###Starting execution of action with name and type .#2#Modul#JSPMPhases#
#1.5 #C0000A0A0A3D000000000014010E329300045BE032541218#1226918382015#/System/Server/Upgrade/Jump##com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:103)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:103)#Java###Starting execution of action with name and type .#2#Phase#JSPM_MAIN#
#1.5 #C0000A0A0A3D000000000015010E329300045BE0333D02E8#1226918397281#/System/Server/Upgrade/Jump##com.sap.sdt.tools.model.AbstractDataModelElement.getClassByName(AbstractDataModelElement.java:743)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.model.AbstractDataModelElement.getClassByName(AbstractDataModelElement.java:743)#Java###Class with name com.sap.sdt.j2ee.model.NWDISystemRole not found.##
#1.5 #C0000A0A0A3D000000000016010E329300045BE0333D3D80#1226918397296#/System/Server/Upgrade/Jump##com.sap.sdt.tools.model.DataModel.load(DataModel.java:89)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.model.DataModel.load(DataModel.java:89)#Java###Could not load data model com.sap.sdt.jspm.model.JspmDataModel. See previous messages.##Hi Patrick ,
What user did you use to start JSPM? Was it <sid>adm? Also based on the error it seems there is something wrong with DataModel.xml JSPM uses. And you've mentioned it was copied from another system if I get it right.
So as a quick workaround you could try removing:
- Jspm.DataModel.xml
- Jspm.J2EE.DataModel.xml
- Jspm.JSPM.DataModel.xml
from ../j2ee/JSPM/data/variables directory and give JSPM another try.
Please make sure the rest of the XMLs are in place otherwise JSPM won't start.
Regards,
Vasil -
Error during server runtime installation - com.sap.js.jpaas.sdk
When adding the Runtime Enviroment for SAP HANA Cloud:
From which location the SAP HANA Cloud Platform SDK can be found?
On-screen help tells, that the location must contain com.sap.js.jpaas.sdk, but none of my downloads from "Getting Started" does contain a file with that name.
The validation of Server "SAP HANA Cloud Platform" was error free when assigning C:\...\neo-java-web-sdk-2.3.3, but with Runtime Environment this SDK is not working.neo-java-web-sdk-2.x is to be used with Java Web Tomcat 7 (Beta) runtime. For SAP HANA Cloud runtime, either neo-java-web 1.x or neo-javaee6-wp 2.x should be used. This will be handled better with the next update of the Platform tools. Sorry for the confusion.
-
Hello Portal gurus,
I am trying to customize the Portal logon page by modifying the com.sap.portal.runtime.logon.par file. I modified the par file. But after this change, I wanted to change the authschemes.xml file to reflect the par file changes.
When I downloaded the .xml file, I only found occurences of <b><frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget></b>, <b><frontendtarget>com.sap.portal.runtime.logon.basicauthentication</frontendtarget></b> and <b><frontendtarget>com.sap.portal.runtime.logon.header</frontendtarget></b>
Could anybody confirm, whether I have to rename these occurrences of com.sap.portal.runtime.logon with my customized logon .par file name between <frontendtarget> and </frontendtarget>?
Points will be awarded for correct answers and useful suggestions.
Thanks,
~~LBHi
Here is the procedure
1. Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.
2. Navigate to cluster_data>server>persistent>com.sap.security.core.ume.service.
3. Switch to edit mode by clicking on the pencil which is at the upper right area.
4. In the tree, select authschemes.xml and choose Download. Save the file to your local directory
5. Edit the local file: To select the new PAR file as the Logon page change the occurrence of all substrings com.sap.portal.runtime.logon to your
project/PAR file name. All com.sap.portal.runtime.logon should be substituted with something like com.company.portal.runtime.logon (or whatever you project name is). Dont remove the part behind it.
(These are the profiles in the portalapp.xml and have the names default, certlogon, basicauthentication, header, and anonymous).
6. Create a new node in the configuration tree in the Config-Tool for the edited file as follows:
a.Select the node com.sap.security.core.ume.service.
b. Choose the symbol for Creating a node below the selected node.
c. Select the type File-entry.
d. Choose Upload and select the custom file from your local directory.
e. Enter a name for the entry, for example, authschemes_myHR.xml. By default, the name of the uploaded file is used.
f. Choose Create.
g. Choose Close window.
h. The new node appears in the configuration tree.
i. Go to Global server configuration>services> com.sap.security.core.ume.service and edit the property login.authschemes.definition.file.
The value needs to be changed from authschemes.xml to authschemes_myHR.xml
j. Restart the Portal. That is often not done and the changes will not appear.
Rgds
Srikanth -
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,
ShilpaHI 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) -
Hi Gurus,
This is the error I am getting when I open WebDynpro Page of Content Administration.
<b>The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.repository.RepositoryException: Did not find application 'com.sap.tc.webdynpro.tools.explorer.Explorer' in repository.</b>
Can any one suggest a better solution for this.
Thanks,
Akella.Hi Gurus,
Please take a look onto this problem.I have tried many ways.I dont want to reinstall the portal.If any body has this application please give me.
Thanks,
Akella. -
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 advanceHi 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
Maybe you are looking for
-
How do I fix the error: Terminating app due to uncaught exception 'NSInvalidArgumentException'
Help! I have a 3rd party application that used to work perfectly until this morning. The problem is not do to an update of that program nor of updating the Mac OS. This came out of the blue. When I try to open the application, it won't open and I get
-
Hi, I am new to JSF, we recently decided to move from JSF, as part of a rewrite.I have struts background. I have skimmed many JSF books including Core JSF, JSF inAction and many online resources. But i still have not been able to get any recommendati
-
Oddly, my Toolbox pod opens just fine, only it's totally empty (no tools listed). Naturally, I need to a multi-file find and replace...any ideas? Thanks in advance!
-
Why PSE 10 works fine while PSE 11 crashes?
I have used PhotoShop Elements (and Premiere) since 2003 (version 2). I recently was lured into upgrading from version 10 to 11 by a couple of new features, but I had trouble from the beginning. The first download would not start until I repeatedly a
-
How do I delete the db files manually to drop a database in an ASM environment?