Content repository FD does not exist :user agent sap web application server
Hi All
i am using 3rd party software(dms SERVER) and connecting it using archive link interface SAP HTTP 4.5 AL
i have created a new repository with name FD using tcode OAC0.when i give inputs in OACO and click on test connection it gives me information Content repository FD does not exist
here is my HTTP trace at receiver content server side
TRACE:(5) - GET /Default.aspx?serverInfo&pVersion=0045&contRep=FD HTTP/1.0
TRACE:(5) - user-agent: SAP Web Application Server (1.0;700)
TRACE:(5) - host: SERVERIP:PORT
TRACE:(5) - accept-encoding: gzip
TRACE:(5) -
--> C05 --> S06 ==== (15.583) Request <GET /Default.aspx?serverInfo&pVersion=0045&contRep=FD HTTP/1.0>
--> C05 --> S06 GET /Default.aspx?serverInfo&pVersion=0045&contRep=FD HTTP/1.0
--> C05 --> S06 user-agent: SAP Web Application Server (1.0;700)
--> C05 --> S06 host: SERVERIP:PORT
--> C05 --> S06 accept-encoding: gzip
--> C05 --> S06 ==== Body 0 bytes
--> C05 --> S06 Body =>
Sockets 6 of 4,5,6 need checking ####
TRACE:(6) - HTTP/1.1 200 OK
TRACE:(6) - Cache-Control: private
TRACE:(6) - Content-Length: 189
TRACE:(6) - Content-Type: text/plain; charset=utf-8
TRACE:(6) - Server: Microsoft-IIS/7.5
TRACE:(6) - X-AspNet-Version: 2.0.50727
TRACE:(6) - boundary:
TRACE:(6) - X-dateC: 2010-10-22
TRACE:(6) - X-timeC: 07:07:23
TRACE:(6) - X-dateM: 2010-10-22
TRACE:(6) - X-timeM: 07:07:23
TRACE:(6) - X-contentRep: FD
TRACE:(6) - X-numberComps: 1
TRACE:(6) - X-docId: 0
TRACE:(6) - X-docStatus: online
TRACE:(6) - X-pVersion: 0045
TRACE:(6) - X-ContentServer: contentServer=Server ip;contentServerPort='9025;pVersion='0045';id='DMSSRV1'
TRACE:(6) - X-Powered-By: ASP.NET
TRACE:(6) - Date: Fri, 22 Oct 2010 13:37:23 GMT
TRACE:(6) - Connection: close
TRACE:(6) -
TRACE:(6) - serverType='DMSSRV1';1;serverVersion=12;serverPatch=0;serverBuild=180;pVersion='0045';serverStatus=running;serverStatusDescription=;serverDate='2010-10-22';serverTime='07:07:23';startUpDate='2010-10-22';startUpTime='07:07:23';lastAccessDate='2010-10-22';lastAccessTime='07:07:23';contRep='FD';contRepStatus=defined;contRepStatusDescription=;contRepDescription=Content-Repository Test;contentStorageHost=localhost;contentStorageName=FD;secKeyVerification=y;defaultDocProt=rucd;
one change which i have observed in this trace is .. this trace is showing trace agent as SAP Web application server ... ideally it should show user agent :SAP HTTP
Please suggest me some solution.
Thanks
sandeep
Dear all,
my issue is resolved.I solved my issue myself
solution: SAP sends HTTP request in the form of URL like
http://serverip:port/GET /Default.aspx?serverInfo&pVersion=0045&contRep=FD HTTP/1.0
Now your response should contain string contRep="FD"
dont forget double quotes on repository name coz SAP program matches string with double quotes. if you will return value like this contRep=FD
this will through error.
Thanks
sandeep sharma
Similar Messages
-
Not able to install SAP Web Application Server -6.40
iam running on SAP NETWEAVER Studio 6.0.21 in Windows XP operating System , not able to install SAP Web Apllication Software -6.40 .
iam not sure what to choose(while Installation) central system or distributed System ,i have tried in either way but
still not able to install the software .
If i go with Sap System Installtion>Java System >Distributed system>Java Central Instance installation ,it throws me getJavaHome was executed with status error ......
then ,
what is the version of Sap Web Application Server to be installed if my system runs on
SAP NETWEAVER Studio 6.0.21 or 6.0.11
cheers
SundarHello,
What do you want to do exactly?
You speak about SAP Netweaver Studio? I suppose you mean Netweaver Developer Studio?
Do you want to install a complete SAP System on your windows XP?? or only the Java part?
Thanks to give us more info
Olivier -
Hi All,
I am currently trying to setup a standard PCR and have gone through the steps for configuration, and I am going to run my Personnel Change Request, but it throws and exeptions and bombs. One of the key lines I could piece together from the Stack Trace is the follow:
<b>Caused by: java.io.IOException: Executable does not exist: F:\usr\sap\PD1\JC01\j2ee\os_libs\adssap\XMLFormService\bin\XMLForm.exe
at com.adobe.service.ProcessResource.startProcess(ProcessResource.java:252)
... 42 more
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:374)
... 51 more</b>
This would lead me to believe that ADS or XMLForms was not installed, or installed correctly.
Could anyone provide any clarity to this situation?Hello,
fist make sure you use a supported plattform for ADS:
http://service.sap.com/PAM
If it it supported try the following:
If these files are not exist, it might be caused by deployment or
synchronizing binaries (bootstrap). In order to force synchronize
os native module, please try follows:
Stop J2EE engine
rename version.bin to version.bin.old
this file can be found under /usr/sap/<SID>/JCxx/j2ee/cluster
Start J2EE engine
If deployment is correctly done, native files will be downloaded.
Best regards,
Dezso -
Not able to change password in SAP WEB application server for BI 7 EHP 1.
Hi all,
I'm currently upgrading from BW 3.5 to BI 7 EHP 1.
When logging to SAP WEB application server to execute a WEB report, it's not possible to change password. Even when a initial password has been set, the user are not forced or able to change it.
Also to logon dialogue is more like a Windows pop-up than the Web based in 3.5.
Anyone having a clue?
Best regards
KentHi Eriki,
My problem is related to the WEB application server (WAS), not the Netweaver Portal.
BR
Kent -
SAP Web Application Server Java 6.40 download is not working
SAP Web Application Server Java 6.40 is not working. There seems to be an issue with the server hosting the binaries.
Antoine Voirytry this site
The SAP WAS 6.40 SP9 is in for of a zip file "WebAS640SP9.zip" it is about 1 GB
https://www.sdn.sap.com/sdn/downloads.sdn?page=webas640_sp9_maxdb_download.htm
Also you can go to the site
https://www.sdn.sap.com/sdn/downloadarea.sdn
and select "SAP NetWeaver Enterprise Portal on MaxDB, Developer Edition Sneak Preview"
to download it
Cheers
Sai -
'Screen does not exist' error after transported to Quality server.
I have a report program which is working fine in development server. It is transported to quality server and when executed it throws dump. There is a CALL SCREEN statement in the program and the dump shows screen 1001 does not exists. I checked the program on quality server and when i double clicked on the screen number, it tells screen 1001 does not exist and do you want to create??. I rechecked the program in Development server and confirmed everything is active and have been catched in the transport request. When I checked with the basis guy, he said there was a component conflict error with the request while transporting and he overrided it.
Please tel me what should I do to solve this issue. Its very urgent. Please help.
Thanks
JohanHi
You seem to have run into some trouble with transports. Did someone perhaps develop this report in the QA server?
I would suggest this:
In SE80. display your report. Then in the hierarchy on the left, right click on your report and select 'write transport entry' . This option will ask you to create a new transport for your report and all objects inside it. Take that transport to the QA server. It should include the entire report, including screens.
If you have trouble importing into the QA server, please provide the transport logs here. -
SDA hdbsdautil does not exist in /usr/sap/ SID /home
I am looking to test ODBC connections for SDA per this document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/706d9725-7087-3110-6d9e-91be8ad377d6?QuickLink=index&overridelayout=true&59064390315971
But hdbsdautil does not exist in my home folder.
I am able to see that program under exe:
/sapmnt/<SID>/exe/linuxx86_64/HDB_1.00.70.00.386119_1342680
But when I execute there I see the following error:
error while loading shared libraries: libhdbrskernel.so: cannot open shared object file: No such file or directory
Any thoughts?Hi Sebastian,
Of course the program hdbsdautil is not in the home directory, as it resides in the exe directory of the SAP HANA software.
server:/usr/sap/HBW/HDB10> which hdbsdautil
/usr/sap/HBW/HDB10/exe/hdbsdautil
server:/usr/sap/HBW/HDB10>
It seems it was not included in the initial SP07 release of HANA 1.0 and an update to the latest version on SP07, which is Rev. 73 is anyway recommended.
Best Regards Roland -
Class DbwsProxy does not exist when connecting to WEB SERVICE
Hi,
I am trying to connect to the OC4J sample web service using the Oracle supplied method specified in this document.
http://www.oracle.com/technology/sample_code/tech/java/jsp/callout_users_guide.htm
We of course use a 10g DB.
The DBWS Callout Utilities were successfully installed by our systems team.
When I run the sample script for the PL/SQL Dynamic Invocation Interface (DII)
I get this error:
ORA-29540: class oracle/jpub/runtime/dbws/DbwsProxy does not exist
ORA-06512: at "SYS.UTL_DBWS", line 178
ORA-06512: at "ABS.CHANNA_TEST_PLSQL_DII", line 14
ORA-06512: at line 1
Why is this??
Any help would be grately appreciated?
Is there any grans/permissions we have to give?
Thanks & Regards,
Channa.Be certain to "propagate permissions" for the shared volume. Under Manage Devices, look for hardware, "Server" then the tab on the right, storage, gear icon at bottom.
This will change the permissions for all files, folders and sub folders. -
I am living in Iran...I have made an apple ID about 10 months ago to use free Apps available in ITunes and Application Store...But I always get a message which says your Apple ID does not exist in iTunes and Application Store...Please guide me how to use iTunes and Application Store for downloading free Apps and music...
It sounds like you haven't yet setup iCloud with that account and you need to do that on a Mac or iOS device. Once setup, you can enable iCloud on a PC, but it needs to be setup first.
See Creating an iCloud account: Frequently Asked Questions
Which says in part:
You can sign up for iCloud on an iPhone, iPad, or iPod touch with iOS 5 or later, or through System Preferences on a Mac with OS X Lion v10.7.4 or later. Just follow the setup instructions for your iOS device or Mac.
ivan -
This is an old app to a server that will have no software updates. I can get logged in but when I try to go to any other page within the app it displays about 8 lines of WWWWWWW along the left side of the window followed by my username and message "Please wait page is loading". It never loads. App works with IE7 or older but have never successfully gotten Firefox 3 or 4 to work. Have had some success with User Agent Switcher Add On with some other apps in the past but it now doesn't show browser versions going back far enough to try them.
I can't guarantee anything, but there's a website that offers old versions of Firefox back to 0.8, so it should have what you need. :-)
http //www oldapps com/firefox php
Good luck!
edit: This is a unofficial download site and not safe. No need for it as Mozilla hosts all since beginning for public access. -
SAP Web Application Server is not running.
Hi All,
I have successfully installed the SAP Netweaver 04 SP15 trial version.
Using SAPMMC i have started the application server
but when i try to access http://localhost:50000
iam getting the following message:
Application stopped.
Details: You have requested an application that is currently stopped
also i rebooted all Dispatcher and Server using the Visual Administrator but still iam getting the same message:
My configuration is :
Windows XP Professional sp2
RAM - 1GB
Hard Disk : 150GB
Pentium 4.
if any one come across the same kindly reply to this message.
its highly apreciated.
Thanks in Advance,
VijayWelcome to SDN.
J2EE engine takes almost 10 to 15 minutes to start up. (check whether the system icon is full Green in SAPMMC). the message you are describing comes up when you try to login when the system is not fully up.
start SAPMMC->J2EE wait till it turns full green and then access localhost:50000
Regards
Raja -
User "Administrator" does not exist
Hello everybody,
i implemented SP Stack 13 in our Java Instance! Now we got some Problems in our Portal.
1) Selfgenerated IViews cannot be accessed. We got the a Portal runtimeerror. In the Tracefile we found the following message:
#1.5 #0011258C7044006100000253000003EC0004418B74EB8814#1197967124597#com.sap.portal.sapapplication#sap.com/irj#com.sap.portal.sapapplication#TESTUSER1#36624##srv053_BWT_18713950#Guest#95ba2ce0ad4411dcbf910011258c7044#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Content pass of Application Integrator failed.
Component Name: 'com.sap.portal.appintegrator.sap.BWReport',
Context Name (iView): 'pcd:portal_content/every_user/general/ARB/ARB-FI/AR_FI_Role/ARB_QM_REP_0/AR_FI_SY_WEB_KONZUMS_RW_S',
Top Layer: 'BWReport/TopLayer',
Producer ID (FPN): 'null',
System Alias: 'BWTCLNT001',
[EXCEPTION]
#1#com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>'; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:455)
at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
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(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.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: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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template '<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>'; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:167)
at com.sapportals.portal.appintegrator.template_processor.compiler.TemplateCompiler.processWholeTagExpression(TemplateCompiler.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseSimpleExpression(TemplateParser.java:234)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:188)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTagExpression(TemplateParser.java:170)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTemplateExpressionPart(TemplateParser.java:97)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:89)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:83)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processImpl(TemplateProcessor.java:407)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:374)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:386)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:107)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:441)
... 30 more
Caused by: java.lang.ClassCastException
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.getProducerByAlias(AppIntegratorInformationService.java:126)
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.buildFPNLocatorForShortcut(AppIntegratorInformationService.java:142)
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.transformURL(AppIntegratorInformationService.java:204)
at com.sapportals.portal.appintegrator.template_processor.context.FPNWrapper.getTerminal(FPNWrapper.java:69)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:152)
... 45 more
#1.5 #0011258C7044006100000255000003EC0004418B74EC9CB6#1197967124690#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#TESTUSER1#36624##srv053_BWT_18713950#Guest#95ba2ce0ad4411dcbf910011258c7044#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Exception ID:09:38_18/12/07_0005_18713950
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/every_user/general/ARB/ARB-FI/AR_FI_Role/ARB_QM_REP_0/AR_FI_SY_WEB_KONZUMS_RW_S
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : TESTUSER1
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
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(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.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: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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>&\#39;; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
#1.5 #0011258C7044006100000257000003EC0004418B74EEE9EF#1197967124894#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#TESTUSER1#36624##srv053_BWT_18713950#Guest#95ba2ce0ad4411dcbf910011258c7044#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Java###09:38_18/12/07_0005_18713950
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>&\#39;; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
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(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.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: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(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)
2) In the Trace file all the Time occurs the following message:
#1.5 #0011258C7044006F0000027A000003EC0004418B678FE974#1197966900571#com.sap.workflow#sap.com/irj#com.sap.workflow#J2EE_GUEST#0####8f2fa3e0aa4d11dcb0150011258c7044#Thread[ThreadPool.Worker4,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/Applications/Workflow/General#Plain###TaskSchedulerDeadline.run()#
#1.5 #0011258C7044006F0000027B000003EC0004418B678FEBD8#1197966900571#com.sap.workflow#sap.com/irj#com.sap.workflow.#J2EE_GUEST#0####8f2fa3e0aa4d11dcb0150011258c7044#Thread[ThreadPool.Worker4,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###com.sap.security.api.NoSuchUserException: User "Administrator" does not exist.
at com.sap.security.core.imp.UserFactory.getUserByUniqueName(UserFactory.java:1635)
at com.sap.security.core.imp.UserFactory.getUserByUniqueName(UserFactory.java:1574)
at com.sap.security.core.imp.UserFactory.getUserByUniqueName(UserFactory.java:1560)
at com.sap.workflow.es.scheduler.TaskSchedulerDeadline.run(TaskSchedulerDeadline.java:90)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:174)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:108)
at java.lang.Thread.run(Thread.java:534)
Can somebody tell me what is going on here?
Thanks so long
Edited by: Oliver Heinzelmann on Jan 11, 2008 2:17 PM
Problem #1 resolved: Ask me for solutionHi Oliver,
A contact at SAP has indicated that in the KM Task Scheduler Deadline (com.sap.workflow.es.scheduler.TaskScheduler.Deadline.run) that the user "Administrator" is hard coded in the SPS13 release.
Depending on what you are using the KM for you could reduce the frequency of the alert by changing the scheduling of this task which by default is every five minutes.
Although the release notes of the following patches didn't formerly address the hard coding issue, I decided to apply them anyway as I thought that a later release may have fixed the issue. However it is not fixed with these interim patches.
KMCBC13P_1-10003491.SCA Patch for KMC BASE COMPONENTS 7.00 SP13
KMCCM13P_1-10003492.SCA Patch for KMC CONTENT MANAGEMENT 7.00 SP13
I guess we will need to wait for a further patch to be released and ignore the error in the meantime.
Regards
Craig -
User does not exist in this period / ESS does not work anymore ;-(
Hello experts,
starting any ess application on portal side (leave request), I get the follwoing error code:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User TESTUSER does not exist in this period
Starting application personal data I get the message: "There are no services in the area."
I know, that this error has often been discussed in this forum. So I check the hints I found, but I could not solve my problem.
The HR user TESTUSER is assigned to the portal user TESTUSER in IT0105 and the user is not exceeded.
TESTUSER got SAP_ALL on HR side.
The error appears for all users, that worked propably a few days before.
Login on portal side and HR works. ESS overview is shown for TESTUSER. For a user that has not a login to HR system it does not appear. So the single singn on (SSO) between portal and HR system seems to work.
The ESS applications worked fine until two days ago. Portal guys said, they had not done any changes on portal side.
Where could the error occure on HR side? How can I recognize if any changes have been made on HR side?
Thank you for your help.TX HRUSER seems not working.
Using the function 'Set Up and Maintain ESS User (Overview)' in TX HRUSER with my test-PERNR it is shown under 'Employees with deleted users'.
Clicking on it I got the Information:
PERS.NO: 12345678 (i.e.) NAME: Test User FROM: 01.01.2011 TO: 31.12.9999 USER: Name: FROM: TO: User does not exist.
But in IT0105 the PERNR is assigned to user TESTUSER in that period.
When I try to assign PERNR to TESTUSER with TX HRUSER under 'Assign Employees to Existing Users' I read the follwing information:
USER: TESTUSER Name: FROM: 01.01.2011 TO: 31.12.9999 USER GROUP: IT PERS.NO.: NAME: FROM: TO: no employee assigned.
Trying to 'assign employees' I get the message 'Error occurred when creating relationship for user ESSUSER-B to employee'.
Please create the appropriate assignment manually in HR master data.
But I have assigned it manualy in IT 0105.
Concurrent employment (CCURE PAUIX) is not activated. -
Hi there,
same Thread I post in "Portal Developement". Now I try my luck in ths category...
we implement ESS (ERP2004 with WebDynpros) in our testsystem, but we got an error and don´t know what to do...
System Landscape:
- mySAP Enterprise Portal 6.0 SP17
- Java Application Server (excluding from HR)
- mySAP ERP2004 HR-System
The Connections from the portal runs to the Java-App-Server, not direct to the HR-System (HR-System has no Java Installation and our Customer don´t want a installation, because it could be a bad performance)
We implement the Jco´s and fill out the usermapping. If we want to call the firstpage of the new ESS-Role we get this error.
Can anyone help us? Do we need some installations?
Best regards
Christian
Error
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
... 54 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
J2EE Engine No information available
Java VM Classic VM, version:1.4.2, vendor: IBM Corporation
Operating system AIX, version: 5.2, architecture: ppc64
Other
Session Locale de
Time of Failure Thu Jan 11 16:14:11 GMT+00:00 2007 (Java Time: 1168532051021)
Web Dynpro Code Generation Infos
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
sap.com/tcwddispwda
No information available
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.xss.ser.xssmenu.model.types.P_Pernr could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:314)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:669)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:855)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:158)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:143)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:135)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:628)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:773)
at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeader.onInit(VcXssMenuHeader.java:196)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeader.onInit(InternalVcXssMenuHeader.java:225)
at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeaderInterface.onInit(VcXssMenuHeaderInterface.java:162)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface.onInit(InternalVcXssMenuHeaderInterface.java:144)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface$External.onInit(InternalVcXssMenuHeaderInterface.java:220)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 52 moreHi,
uhm... good question, long time ago...
Error should be in the JCO-Destinations, where you can choose a targetsystem for each Jco-Destination.
Since them we installed a java on the abap-system, so we have a doublestack.
In the Jco Destiantions must be the ABAP-System.
Application via SAPTicket and MetaData via fix User like DDIC.
Regards
Christian -
PRTMessageListenerException: The listener does not exist
Hi All,
We are running EP 7.0 NWO4s on Windows 2003. When the user log on to the portal with the valid qualified URL geting an " 500 Internal Server error with java.lang.null pointer exception message" Before the restart of the server every user able to access the portal properly. But after the restart of the server we are facing this problem. Few months back also we faced the same problem but it is fixed automitically in our next restart of our server. But this time even though how many times we are restarting of the server still the problem exists.
1. The Server is up and running
2. All the J2EE process are running properly
3. Oracle database is up and running
On the Defaulttrace file we noticed few exceptions
com.sap.portal.prt.sapj2ee.api.clustercommunication.exceptions.PRTMessageListenerException: The listener does not exist !
com.sap.engine.services.servlets_jsp.server.exceptions.WebUnavailableException: Servlet prt is currently unavailable.
Timeout Service Synchronous Internal Thread: javax.management.InstanceNotFoundException
Processing HTTP request to servlet gateway finished with error.The error is: java.lang.NullPointerException: null
Caused by: javax.servlet.UnavailableException: Initialization of Dispatcher failed
Defaulttrace file Information:
#1.5#00188B874AFD002100000505000023E80004474C5F840A13#1204293252562#
com.sap.engine.services.monitor.common.Template##com.sap.engine.services.monitor.common.Template######
a68a3f70e4d411dcc2e100188b874afd#Timeout Service Synchronous Internal Thread##0#0#Warning##Plain###
javax.management.InstanceNotFoundException: com.sap.default:name=ComponentRuntimeMBean,
SAP_J2EEApplicationPerNode=sap.com/com.sap.netweaver.bc.rf.moni,j2eeType=SAP_ApplicationResourcePerNode,
SAP_J2EEClusterNode=18025994,SAP_J2EECluster=ANV not in repository
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1291)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.monitor.mbeans.Template.pollDynamicData(Template.java:891)
at com.sap.engine.services.monitor.mbeans.Template.handleNotification(Template.java:847)
at com.sap.engine.services.jmx.server.AscynchronousProxyListener.handleNotification(AscynchronousProxyListener.java:51)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:94)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:61)
at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification(Timer.java:432)
at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)
at com.sap.engine.services.timeout.TimeoutNode.synchronousRun(TimeoutNode.java:72)
at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun(TimeoutManagerImpl.java:632)
at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:18)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#00188B874AFD00610000000A000023E80004474C946ED4C0#1204294140410#com.sap.engine.services.prtbridge##
com.sap.engine.services.prtbridge######b8f36600e65511dc9d3000188b874afd#SAPEngine_System_Threadimpl:5
_105##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
EXCEPTION
#1#
com.sap.portal.prt.sapj2ee.api.clustercommunication.exceptions.PRTMessageListenerException: The listener does not exist !
(NotificationSAPJ2EE630)
at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.distributeMessage(MessageContextWrapper.java:373)
at com.sap.portal.prt.sapj2ee.bridge.PRTBridgeAccessor.distributeMessage(PRTBridgeAccessor.java:228)
at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.receive(PRTBridgeCommunicationManager.java:568)
at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:126)
at com.sap.engine.core.cluster.impl6.ms.MSMessageQueue.process(MSMessageQueue.java:77)
at com.sap.engine.core.cluster.impl6.ms.MSMessageThread.run(MSMessageThread.java:37)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#00188B874AFD003500000030000023E8000447700BC25D6F#1204446466108#
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
sap.com/irj#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
Guest#2####8920f6c0e83211dc960400188b874afd#SAPEngine_Application_Threadimpl:3_4
##0#0#Error#1#/System/Server/WebRequests#Plain###
Processing HTTP request to servlet gateway finished with error.
The error is: java.lang.NullPointerException: null
Exception id: 00188B874AFD00350000002E000023E8000447700BC25C4C#
#1.5#00188B874AFD00560000003E000023E8000447700C764EBA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain###com.sapportals.portal.prt.dispatcher.DispatcherException: Previous dispatcher initialization failed. Check logs for details.#
#1.5#00188B874AFD00560000003F000023E8000447700C76505A#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:257)#
#1.5#00188B874AFD005600000040000023E8000447700C76509D#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:213)#
#1.5#00188B874AFD005600000041000023E8000447700C7650DA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.access$300(Dispatcher.java:42)#
#1.5#00188B874AFD005600000042000023E8000447700C765116#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:437)#
#1.5#00188B874AFD005600000043000023E8000447700C765151#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#00188B874AFD005600000044000023E8000447700C765192#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
#1.5#00188B874AFD005600000045000023E8000447700C7651CE#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#00188B874AFD005600000046000023E8000447700C765209#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
#1.5#00188B874AFD005600000047000023E8000447700C765247#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#00188B874AFD005600000048000023E8000447700C765282#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
#1.5#00188B874AFD005600000049000023E8000447700C7652BF#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
#1.5#00188B874AFD00560000004A000023E8000447700C7652FB#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
#1.5#00188B874AFD00560000004B000023E8000447700C765338#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
#1.5#00188B874AFD00560000004C000023E8000447700C765374#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
#1.5#00188B874AFD00560000004D000023E8000447700C7653B6#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
#1.5#00188B874AFD00560000004E000023E8000447700C7653F3#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
#1.5#00188B874AFD00560000004F000023E8000447700C76542E#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
#1.5#00188B874AFD005600000050000023E8000447700C76546A#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.5#00188B874AFD005600000051000023E8000447700C7654AA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
#1.5#00188B874AFD005600000052000023E8000447700C7654E8#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5#00188B874AFD005600000053000023E8000447700C765522#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#00188B874AFD005600000054000023E8000447700C76555C#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
#1.5#00188B874AFD005600000055000023E8000447700C765598#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
#1.5#00188B874AFD005600000056000023E8000447700C765C20#1204446477905#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/irj#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2####90290b10e83211dccc4800188b874afd#
SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain###
Processing HTTP request to servlet invoker finished with error.
The error is:
com.sap.engine.services.servlets_jsp.server.exceptions.WebUnavailableException: Servlet prt is currently unavailable.
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:174)
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)
Caused by: javax.servlet.UnavailableException: Initialization of Dispatcher failed
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:371)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:213)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$300(Dispatcher.java:42)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:437)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
Please help us to resolve this issue. Its a bit urgent for us. Your suggestions and views would be highly appreciable.
Thanks
RaviHi Ravi,
can you check if you see any more relevnt information in the std_serverx.out files? or in the dev_server/dev_dispatcher files.?
cheers,
Shantanu
Maybe you are looking for
-
Exception while deploying webservice to weblogic 10.3.6
Hi i am facing following exception while deploying ear file to weblogic. the same ear files was working in weblogic 9.2 bundle of thanks for your help <Error> <Deployer> <BEA-149265> <Failure occ urred in the execution of deployment request with ID '
-
IPhone 4 with 5.0.1 not recognised by iTunes. Forcing me to restore.
I upgraded to iOS 5.0.1 last week now my phone is not recognised by iTunes. It it telling me to set up a new phone or restore from back up. Problem is the last back up is the the day I updated. I don't want to lose all me purchases and stuff on my iP
-
I am not able to redeem my redemption code
i purchased the adobe cloud because my upgrade to elements 12 never worked despite endless hours talking to would be experts, so i decided to lose the 67 gbp and try creative cloud for ligfhtroom 5 and photoshop cc however i am having the same proble
-
I am trying to recover or restore my phone but it either says, error has occurred or it says they cannot find my iphone. It is stuck on the loading apple logo. Please help! I dropped it hard, maybe thats why it is not working.. and i put a new screen
-
Hey guys, i just noticed there's a black patch on my screen. Bottom right has bigger patch and its obvious on the grey loading screen or any bright backgrounds. Is it something i should worry about be it dirt or burnt? Im using Macbook White Unibody