Employee Self Service ESS User username does not exist in this period

Hi,
1. I have created portal user and mapped to ECC6 user.
2. I have linked the ECC6 user in PA30 in 105 infotype/subtype 001.
3. the Begin Date / End Date is right.
but still,
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
 User <username> does not exist in this period 
Please let me know if there is anything i have to do.
Thank you,
Boobalan

Hi,
I have assigned the PA30 infotype and also checked the validity of the employee and the R/3 user. but still i get the same error.
i have also went to the administrator console /webdynpro/welcome/welcome.jsp
I have also given the new username in the JCo Connection which has been created tempority. It shows the same error. I could find that it is not related to PA30, as the new user was not assigned while testing.
Before and after changing of the personalize of the user also it is showing the same error.
Please let me know is there anything.
I have cheked in R/3 by typing the Transaction Code PZ01, it shows the same error.
Regards,
Boobalan
Message was edited by:
Boobalan S

Similar Messages

ESS Error- User Username Does Not Exist in this Period

Hi all,
I am getting the error as follows when I tried to get into any of the Sub iview like Address, Change Own Data etc
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
User <Username> does not exist in this period
I saw a thread but it doesn't resolve that error.
Actually I didnt assign my user to any employee.Is it mandatory to assign an employee to the user in PA30 because my user is a test user.
Then in the logon ticket the name should be same as my userid in portal and ECC.
Please this is very important gimme some good suggestion.

Hi Jayesh,
Thank you. It was solved but while tried to access 'Change Own Data'. I am getting the error like
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
Please give me some suggestion.
Thank you.

User does not exist in this period

Hi ,
 I am facing the problem when i access Overview -> Who's who
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User <Username> does not exist in this period
 at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
 at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
 at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:267)
 at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:222)
 at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:249)
 at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
 at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183)
 at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
 at com.sap.xss.hr.wiw.FcWiwBusinessLogicComp.onInit(FcWiwBusinessLogicComp.java:217)
 at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicComp.onInit(InternalFcWiwBusinessLogicComp.java:414)
 at com.sap.xss.hr.wiw.FcWiwBusinessLogicCompInterface.onInit(FcWiwBusinessLogicCompInterface.java:115)
 at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface.onInit(InternalFcWiwBusinessLogicCompInterface.java:298)
 at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface$External.onInit(InternalFcWiwBusinessLogicCompInterface.java:358)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
 at com.sap.xss.hr.wiw.selection.VcWiwSelectionComp.onInit(VcWiwSelectionComp.java:212)
 at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionComp.onInit(InternalVcWiwSelectionComp.java:206)
 at com.sap.xss.hr.wiw.selection.VcWiwSelectionCompInterface.onInit(VcWiwSelectionCompInterface.java:162)
 at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface.onInit(InternalVcWiwSelectionCompInterface.java:144)
 at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface$External.onInit(InternalVcWiwSelectionCompInterface.java:220)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
 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:430)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
 at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
 at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
 at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
 at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
 at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 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:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(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)
Kindly help me to solve this problem.
Thanks
Jibin

Hi,
you have to map the EP user to an employee at the backend for the ESS services to work.
Go to transaction HRUSER and check whether an employee is connected to this USER_ID. If it is not there, go to transaction pa30,select an employee and create a new record for the infotype 105 ( subtype 0001) with the USER_ID.
may be the dates were correct but the user maintained incorrect entry in IT0105...wrong username...
This should solve your issue.

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.

Web Service error: User [oc4jadmin] does not exist in system

Attempting to create a HelloWorld Web Service (WS) using JDeveloper 10.1.3 and deploying to OAS10g 10.1.3. Create the WS, deploy to OAS10g, test the Service from OAS10g - not a problem!
Then enable WS-Security and specify a cleartext password - ONLY. Then when test it from OAS10g I get the following output (HTTP Analyzer): User [oc4jadmin] does not exist in system.
Which is patently false as I login with oc4jadmin!
Anyone have an idea what is going on here???????
THANKS - Casey
P.S. Thanks in advance for any help

Casey, see if either of these help:
Securing a Web Service Client Using WS-Security (viewlet)
http://www.oracle.com/technology/products/jdev/101/viewlets/101/xesecureunitedloanclient_viewlet_swf.html
Securing Web Services using JDeveloper and WS-Security
http://www.oracle.com/technology/products/jdev/101/howtos/securews/index.html
Oracle JDeveloper 10g (10.1.3) Documentation: Working with Web Services
http://www.oracle.com/webapps/online-help/jdeveloper/10.1.3/state/content/navId.4/navSetId._/vtAnchor.CJAEHFJD/vtTopicFile.adfdevguide%7Cweb_services%7Ehtm/

Employee Self-Service Shopping Area (POWL) does not show any documents

Hello gurus,
My client has upgraded to SRM 7.0 and are configuring portal and SRM to meet the needs. The Shopping Area of the Employee Self-Service is being displayed; however we have some problems:
1) No Shopping Cart documents are being shown in the table query (even though there are SC created in the SRM system which you can see in BBP_PD)
2) When you go to the Shop functionality to create the SC, you can't select any Goods/Services because no Product Categories / Product IDs are being displayed (here also they are created in the SRM and backend systems).
Does anyone know if there is a feature or custo that I have to set so that the documents are displayed?
I don't know if this is a Portal config or SRM customizing issue, so I will post this thread to both forums.
Many thanks!
Adi

Hi Adi,
Have you tried using the POWL under Purchasing tab rather than the one in ESS?
Does this only affect your user or is no-one able to see POWL data?
Are the carts visible under the advanced search or not there also?
Regards,
Jason

IT105 warning message "user does not exist in this period"

Does anyone know if we can change the warning message on IT105 subtype 0001 to be an error message? This is causing an issue when HR are entering the User ID before it's been created in SU01, so sometimes there is a mismatch.
Hope you can help, thanks in advance!

This message is hardcoded as a warning in the method CHECK_USERID_EXISTENCE. Like it was suggested above, you will need an access key to change it into a message type 'E'. Other option is to do this validation via the AFTER_INPUT Method of the BAdI HRPAD00INFTY.
~Suresh

ESS Error - User id does not exist

Hi All,
When the user click on personal information - Emergency address link on the portal, user gets error "user XX does not exist in this period".
This proble is only for this particular user.
on the back end an abap dump with following error message is encountered.
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception              CX_SY_REF_IS_INITIAL
Error in the ABAP Application Program
The current ABAP program "SAPLHRXSS_PER_MAC" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
I checked the data is maintained in IT0105 an IT0002 correctly. Even the table V_T7XSSPERSUBTYP has value for IT0006 with correct usecase.
The user has a hiring date of 13.07.2009 and IT0105 also has the start date as 13.07.2009 can this be the reason? Since the validity is not for complete month?
Please advise what could be the possible reason for the above error. How to solve the problem
Regards,
Swati

Hi,
you have to map the EP user to an employee at the backend for the ESS services to work.
Go to transaction HRUSER and check whether an employee is connected to this USER_ID. If it is not there, go to transaction pa30,select an employee and create a new record for the infotype 105 ( subtype 0001) with the USER_ID.
This will solve the issue.

Pcuigp.xssfpm.java.FPMRuntimeException: User J2EE_ADMIN does not exist

Hi colleagues,
We are getting the following error in Personal Information of ESS(Employee Self Service)
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User J2EE_ADMIN does not exist in this period
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
     at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:267)
     at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:222)
     at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:249)
     at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
     at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183)
     at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
     at com.sap.xss.hr.per.us.address.overview.VcPerAddressUSOverview.onInit(VcPerAddressUSOverview.java:302)
     at com.sap.xss.hr.per.us.address.overview.wdp.InternalVcPerAddressUSOverview.onInit(InternalVcPerAddressUSOverview.java:287)
     at com.sap.xss.hr.per.us.address.overview.VcPerAddressUSOverviewInterface.onInit(VcPerAddressUSOverviewInterface.java:187)
     at com.sap.xss.hr.per.us.address.overview.wdp.InternalVcPerAddressUSOverviewInterface.onInit(InternalVcPerAddressUSOverviewInterface.java:152)
     at com.sap.xss.hr.per.us.address.overview.wdp.InternalVcPerAddressUSOverviewInterface$External.onInit(InternalVcPerAddressUSOverviewInterface.java:236)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     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:430)
System configuration is EP7, Oracle database.
Could you please assist me to resolve this issue.
Thanks & regards,
Pavan.

Hi,
you have to map the EP user to an employee at the backend for the ESS services to work.
Go to transaction HRUSER and check whether an employee is connected to this USER_ID.
If it is not there, go to transaction pa30,select an employee and create a new record for the infotype 105 ( subtype 0001) with the USER_ID.
Check the start DATE and the END date of the same PERNR of infotype 105 subtype 0001
This will solve the issue.

ESS mixed up users & ESS user not existing in this period

Hi all
I really hope you can help me in one way or an other. I am still quite new to SAP and SDN so have a bit leniency
At my company we have two demo system here and my job is right now to implement the ESS scenario. We have on the one side a EP 7.0 SP 09 and and on the other side an ERP 2005.
There have been allready the needed Business Packages for the ESS scenario deployed.
My job is right now to implement the ESS scenario between the EP and the ERP.
But I got nearly the same problems. Every time i am going to test some ESS- iViews, for example:
ESS->working time->leave request (iview)
or ESS->employee search ->change own data (iView)
the following Massage appears:
"User MISTRY does not exist in this period"
And now something really wired!
I am logging into the system with the user "stefan" (which is has the super admin role) but the user wihch is reffered in this message is an user from another admin (also super admin, but he was the person who deployed the Business Packages).
So now i don't get further... i searched already on SDN and service.sap.com , i found a JDI /NWDI Cook book...but all of these doesn't really help me out...
BTW: is that the ESS cook book you were talking about?
Perhaps one of You allready knows a solution or another purchase (starting point) i could investigate ...
Thanks very much for your efforts !!!
Kind and best regards
Stefan

And here is the Exception itself:
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
User MISTRY does not exist in this period
User MISTRY does not exist in this period:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User MISTRY does not exist in this period
 at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
 at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121)
 at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:257)
 at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:220)
 at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:249)
 at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
 at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183)
 at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
 at com.sap.xss.hr.cod.FcCodBusinessLogicComp.onInit(FcCodBusinessLogicComp.java:188)
 at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicComp.onInit(InternalFcCodBusinessLogicComp.java:355)
 at com.sap.xss.hr.cod.FcCodBusinessLogicCompInterface.onInit(FcCodBusinessLogicCompInterface.java:115)
 at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface.onInit(InternalFcCodBusinessLogicCompInterface.java:147)
 at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface$External.onInit(InternalFcCodBusinessLogicCompInterface.java:215)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
 at com.sap.xss.hr.cod.start.VcCodStartComp.onInit(VcCodStartComp.java:168)
 at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartComp.onInit(InternalVcCodStartComp.java:145)
 at com.sap.xss.hr.cod.start.VcCodStartCompInterface.onInit(VcCodStartCompInterface.java:161)
 at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartCompInterface.onInit(InternalVcCodStartCompInterface.java:144)
 at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartCompInterface$External.onInit(InternalVcCodStartCompInterface.java:220)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java(Inlined Compiled Code))
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java(Inlined Compiled Code))
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java(Compiled Code))
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
 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.doApplicationProcessingPortal(ClientSession.java:731)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:879)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
 at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)
 at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
 at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)
 at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:596)
 at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:827)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:683)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 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(Compiled Code))
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
 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))

Integrating Manager Self-Services(MSS), Employee Self-Services(ESS) in EP60

Hi,
I would like to integrate Manager Self-Services(MSS) and Employee Self-Services(ESS) into my Enterprise Portal EP6.0 SP2.
I have downloaded the business packages for the same and looking for a good document which can guide me to implement the integration.
Any quick response would be highly appreciated.

Hi,
the "connection" between iView and R3 System is done via the system definition. The ESS - iViews use a System alias SAP_R3_Human_Resources (and the other names I mentioned above).
If you have assigned this ESS role to a user the iView connects to the R3 system defined in the alias. If you chose single sign on the user id from the portal should be the same as in the R3. If it is different the easiest way would be to use usermapping.
The best way would be to assign this ESS role to your user and watch what is happening.
Regards,
Holger.

Connect-SPOService : The Application ID (AppID) for which the service ticket is requested does not exist on the system.

I am trying to connect to SharePoint in my Office 365 environment by following https://support.office.com/article/Set-up-the-SharePoint-Online-Management-Shell-environment-7b931221-63e2-45cc-9ebc-30e042f17e2c and I am getting:
Connect-SPOService : The Application ID (AppID) for which the service ticket is requested does not exist on the system.
Is there some setting I need to change on the O365 side? Thanks.

Hi,
Based on your description, my understanding is that you want connect SharePoint Online using PowerShell.
Please make sure that the following software is installed.
Windows Management Framework 3.0
SharePoint Online Management Shell
And then, open the SharePoint Online Management Shell and use the Script below to test
whether it works.
$User = "[username]@[tenant].onmicrosoft.com"
$Pass = "[password]"
$creds = New-Object System.Management.Automation.PSCredential($User,(ConvertTo-SecureString $Pass -AsPlainText -Force));
Connect-SPOService -Url https://[tenant]-admin.sharepoint.com -Credential $creds
Get-SPOSite
More information:
http://blog.falchionconsulting.com/index.php/2013/01/using-powershell-to-manage-sharepoint-2013-online/
Thanks,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Dennis Guo
TechNet Community Support

RDS Gateway + Smart Card Error [ The specified user name does not exist.]

I have the following Windows Server 2008 R2 servers:
addsdc.contoso.com, AD DS Domain Controller for contoso.com
adcsca.contoso.com, AD CS Enterprise CA, CDPs/AIAs published externally.
fileserver.contoso.com, RDS Session Host for Administration enabled
rdsgateway.contoso.com, RDS Gateway enabled
tmgserver.contoso.com, 'Publishing' rdsgateway.contoso.com but with pass-through authentication
And the following Windows 7 PCs:
internalclient.contoso.com
externalclient.fabrikam.com
There's no trust between the domains, the external client is completely separate on the internet but the CA certificate for contoso.com has been installed in the trusted Root CA store. All servers have certificates for secure RDP.
I enrolled for a custom 'Smart Card Authentication' certificate with Client Authentication and Smart Card Logon EKUs from the CA, stored on my new Gemalto smart card using the Microsoft Base Smart Card CSP.
From internalclient.contoso.com, I can RDP to fileserver.contoso.com
using the smart card just fine with no certificate errors.
From externalclient.fabrikam.com, I can RDP to fileserver.contoso.com
via rdsgateway.contoso.com using a username and password just fine with no certificate errors.
From externalclient.fabrikam.com, I can RDP to fileserver.contoso.com
via rdsgateway.contoso.com using the smart card to authenticate to the gateway, and a username and password to authenticate to the end server, just fine.
BUT from when using a smart card to authenticate to the end server via the gateway, it fails with:
The specified user name does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support.
When I move the client into the internal network and try the connection again (still via the RDS Gateway), it works fine - the only thing I can think of is being outside the network and not being able to contact the AD DS DC for Kerberos is causing the issue
- but I'm pretty sure this is a supported scenario?
The smart card works fine internally, the subject of the certificate is the user's common name (John Smith) and the only SAN is
[email protected] which matches the UPN of the user account as it was auto-enrolled.
Does anyone have any ideas?

I had a similar issue where I am using a smart card through a Remote Desktop Gateway. I had to disable Network Level Authentication (NLA) on the destination Remote Desktop Server. If anyone has another way around this, I'd appreciate hearing it. I'd prefer
to use NLA.

Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer

Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer, And when Installing network printers from the domain controller it reports it cannot connect to printer. I can ping all
network devices. I can connect to the internet.
On boot I get a netlogon 5719 error followed by service control manager errors 7023,7001 and a group policy error 1129.
Clients can connect to the remote application and RDP operates to connect to the server internally and externally.
The domain controller is another server 2008r2 box. I have scoured the internet but have not found any solutions that work yet.

Hi,
After referring to your post, it can be identified that the issue which you are facing is mostly due to some network issue in your environment. Please recheck your network connection issue between computer and domain controller.
Can you able to ping with IP address and also with fully qualified name of a domain controller in the users' and computers' domain. If it fails states that name resolution issue with computer and domain controller. Are you using MS DHCP Relay agent then there’s
available Hotfix for the particular Event ID. Please go through this KB 2459530 to fix the error event ID.
As per the net logon error 5719 which you are facing states that the client component of Netlogon was unable to locate a DC for the domain it was trying to perform an operation against. Below is one of the reason. If this is being logged on a DC and the event
refers to the DC's own domain, something might be preventing the client component of Netlogon from starting a network session (to itself or to another DC in the domain). The following event 7001 & 7023 states start & stop operation service. Please
go through beneath article for more details.
1. Event ID 5719 is logged when you start a computer
2. Netlogon 5719 and the Disappearing Domain [Controller]
3. Event ID 1129 — Microsoft-Windows-GroupPolicy
Hope it helps!
Regards.

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 solution

Hi 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

Employee Self Service ESS User username does not exist in this period

Similar Messages

Maybe you are looking for