Customization of Portal Logon problem

Hi
I am Trying to change the Logon Screen for my Portal but cannot find the file specified by SAP . . .
<J2EE_Engine_Instance>\j2ee\cluster\server<X>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
I get to WEB-INF and there is no deployment folder?
is this a rights issue?
any help appreciated
tom

Thomas,
You can download same PAR file as:
Logon to portal as admiistrator:
Navigate to System Admiistration --> Support --> Portal Runtime --> Browse Deployment --> portalapps --> com.sap.portal.runtime.logon
download the file.
Thanks,
Yogesh

Similar Messages

Portal Logon Problem

Hi,
     I installed EP 6.0 .
     The logon page is appearing , when I enter the user as administrator and enter the password the page just refreshes and the fields gets blank.There is not message displayed. I am not able to logon to the portal.
    Again if I give wrong password then it gives and error message "User authenticatoin failed".
    Please can any one help me to find out why on giving the right password I am not able to logon,and there is not message displayed.
Thnx,
Pravesh Puria.

Hi Puria,
This is the case with the UME (User Management Engine).
Check out your UME settings and adjust accordingly in the configtool.
Regards,
Ravi.

Portal Logon Problem E-Mails

Hi all,
does anybody know the application that sends the notification E-Mails from the Logon Page?
I have to change the template of the notification.
Thank you for help,
Erik

Check the below thread that will help you.
Re: sending password via sms instead of email
Raghu

Different portal logon pages with same url.

Hi all,
Im doing portal logon page customization . My requirement is when a user give the portal link in his browser he should get the portal logon page according to the country language..for example if he opens the portal from india he should get English text and if he opens the portal from japan he should get the japanese text in the portal logon page.
thanks
Rajeev B

Rajeev,
Its possible to have the different logon pages for the same portal.
Its also possible for the same ulr but different parameters.
You can do customization on portal logon page.
For example:
Consider that the url http://myep:50000/irj/portal is currently using to access the portal.
You can pass addintional parameter on this url and fetch them into logon page, display the pages based on the values that you have fetched.
for example http://myep:50000/irj/portal/myparam
Have a lot at this link,
Displaying Different Login Pages Based On The Sales Organization
Ram

Customizing portal logon screen

Hi all
We are working with SP16 EP6.0.
Is the procedure the same as SP9 to customize the portal logon screen?
Is there any configurations need to be done for SP16 specifically?
Thanks in advance.
Regards
Yoga

Hi Yoga,
It's the same procedure, there are not changes in the procedure till portal 7.1
Best Regards,
Luis

Logon Problems? Get support is not working in Portal logon Page

Hi Experts,
I have created A Role and assigned Logon_help action to it and assigned the Role to Anonymous group.
So i have Logon Problem? Get Support link on Portal Logon Screen. When i click on it, i was asked to provide userid and email id.
I have entered them. i got a message the my userid is reset and sent to my mail. but havent received any mail, and the password is changed which have to log in as admin and reset the password.
Help me this regards.
Thank you
Siva

you might not have correctly configured your mail servers....
refer below link
http://help.sap.com/saphelp_nw70/helpdata/en/89/c5fd430b63c74bbdfaa5f2ec9bb20b/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/44/0761cea5c610b3e10000000a11466f/frameset.htm

Problems redeploying portal logon par file

Hi,
We customized the portal logon page within a custom par file and modified the authschemes.xml to make it work.
Once it worked on our DEV portal we moved the par file to the QA environment.
At this point the par file is having problems and doesn't execute. When we change the Authschemes.xml the portal even crashes because it tries to execute the custom par file and it fills up the log files.
The only difference in the deployement I could get from the log files it that it doesn't create a "work" directory during the deployement in QA while it does in DEV.
Any reasons why the par file would work in DEV and not in QA?
the portal releases and patch levels are exactly the same.
Thanks,
Johnny

Hi,
1. create ur custom parfile
2. change all occurences of the the old par file name with the new custom parfile name in authschemes.xml.
3. delete or rename com.sap.portal.navigation.masthead.par.bak
3. move the new custom parfile to the PCD location
4. delete the .bak file of new parfile or old parfiles if any
5. restart the portal.
check whether there are any discrepancies in authschemes.xml while changing the name of old parfile.
Hope this helps
Thanks,
Praveen
PS. Dont forget to reward point if useful/solved.

Activating Security Policy at Portal Logon Page

Hi @ll,
Iu2019m not able to activate the password security policy check at portal logon page. For this purpose, I have already checked the Enforce Password Security Policy at Logon (System Administration->System Configuration->UME Configuration->Security Policy) and restarted the server too. But it is failed to appear at logon page.
Plesae suggest me to resolve this problem.
Thanks
Gautam Singh

Hi Gautam Singh,
You say you are customizing the portal logon screen. Are you doing a simple modification by just changing UME properties as described in [Logon Screen Customization|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/fc3ae22adb025fe10000000a1553f7/frameset.htm] or are you actually changing .par files and creating your own logon application?
Are you using config tool, the user management configuration Web Dynpro UI, or visual admin to change the properties?
Have you assigned the UME actions Logon_Help and Selfregister_User to the Anonymous Users group?
-Michael

Customizing logon problems page

Hi,
I'm working on EP 7.0 ,my logon problems page is not enabled ,plz help me how to configure it

HI
authschemes.xml file change the com.sap.poratl.runtime.logon with your par file name
This blog explains step by step procedure for Custumzing the Portal Logon Screen
Modifying The Logon Par(or customising the Logon Screen)
A fast and easy Portal logon page customizing
Portal Customizations Intro - Login Part 2
Portal Customizations Intro - Login Part 1
http://help.sap.com/saphelp_nw2004s/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
Hope this helps,
Regards,
Arun

Error on Portal Logon Page

Hi Experts,
We are getting exception while calling the Portal URL.
Recently, we changed the password policy and made some customizations on the com.sap.portal.runtime.logon.par file.
After that when I tried to access the Logon page, it gave an exception.
I even replaced the customized logon par file with the original one but it did not help.
Please note that I deployed the logon par file with the same name, so I did not have to make any changes in the authschemes.xml file.
So ideally when I replaced the customized PAR file with the original one, it should have worked out.
Can it be because of some UME property "Password Policy change" or something like that which has been changed by our Basis team in the Config tool and which is creating issues now.
Is there any connection between the UME property and the Portal Logon page? I know that UME comes into picture once the user clicks on Login button after entering the login credentials but does it also come in picture at the portal logon page call?
We are not able to trace out the root cause as both Password Policy Change and deployment of PAR was done parallely due to which we are confused about the cause of the issue.
Please find below the trace against the exception ID:
#1.5 #5CF3FC5B7E1C00670000000300001B400004ACA7F25E4315#1315737232519#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##8b1ef68fdc6111e0a5840000061bff66#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###04:03_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
#1.5 #5CF3FC5B7E1C00660000000100001B400004ACA7F2896FC1#1315737235348#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###Shutting down Application Brokerage...#
#1.5 #5CF3FC5B7E1C00660000000800001B400004ACA7F2940472#1315737236039#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error#1#/System/Server#Java###[PortalServiceItem.release] exception caught releasing com.sap.netweaver.coll.appl.rtc|RTCClientPollingService
[EXCEPTION]
#1#java.lang.NullPointerException
 at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.unsubscribe(RTMFMessaging.java:1040)
 at com.sap.ip.collaboration.core.api.rtmf.core.cluster.ClusterSystemManager.unsubscribe(ClusterSystemManager.java:133)
 at com.sap.ip.collaboration.core.api.semantic.services.RTCBaseService.destroy(RTCBaseService.java:146)
 at com.sapportals.portal.prt.core.broker.PortalServiceItem.release(PortalServiceItem.java:389)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1159)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:575)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:680)
 at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)
 at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:731)
 at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #5CF3FC5B7E1C006F00000002000016140004ACA819F31491#1315737896495#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##1647a148dc6311e0aaaa0000061bff66#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Java###04:14_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
#1.5 #5CF3FC5B7E1C007000000000000016140004ACA81A149C1D#1315737898689#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0##n/a##18319b2cdc6311e092af0000061bff66#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server#Java###An error occured during authscheme computation.
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.runtime.logon.certlogon
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
 at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.java:233)
 at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:177)
 at com.sapportals.portal.prt.connection.PortalHook.doNodeHook(PortalHook.java:469)
 at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:138)
 at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:50)
 at com.sapportals.portal.prt.pom.PortalNode.createComponentNode(PortalNode.java:275)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:617)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sap.portal.navigation.Gateway.service(Gateway.java:117)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component com.sap.portal.runtime.logon.certlogon because: Linkage error while loading implementation class
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
 at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
 ... 33 more
Caused by: java.lang.NoClassDefFoundError: com/sap/security/core/logonadmin/IAccessToLogic
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:219)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
 ... 37 more
Thanks & Regards.
Anurag

Hi,
Check if your portalapp.xml has an entry "<property name="ClassName" value="com.sapportals.portal.ume.component.logon.SAPMLogonComponent"/>"
If it is there, then I feel that this is an issue with jar files not getting imported properly.
Just try including these two jars (umlogonbase.jar and com.sap.portal.runtime.logon_api.jar) from
usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.logon\lib
and copy manually to the lib folder under PORTAL-INF in your project.
Regards,
Vijay.

Portal Logon page repeating/ redirecting to itself on first attempt

All,
Apologies in advance if this is not the appropriate forum. We are in the process of migrating a NW7.0SPS13/EP7.0SPS13 installation from a remote site to a local site with a database only UME and SSO to an ECC6.0 backend. The new target installation has picked up a rather odd behavior. When loggin onto the portal, the logon page repeats/refreshes/redirects to itself with valid ID and password with no error message. The only apparent action is the clearing of the password field.
My only clue so far is the absence of this script in the http trace on the initial logon attempt which shows up on the second attempt:
http://<host>:51100/irj/portalapps/com.sap.portal.httpconnectivity.httpauthentication/scripts/CAManagerScript.js
I did find this related thread and attempted the suggestions with no luck:
Re: portal logon page coming again
I felt this might be the best place to post question since this may be an authentication/connectivity issue.
Thanks in advance,
Lee

You are correct, we are not implementing SPNego but at this point I will take any suggestions that might be conceptually related...
We are attempting to migrate/clone the entire server (OS,J2EE,MSSQL05...) from a remote hosted environment to a local network environment.
I checked the Everyone, Authenticated, and Anonymous groups for the correct roles/Java permissions and all seems to be in-line with the correctly functioning remote system with correct user assignment.
With some further log filtering I was able to where find this error:
The default keystore view [TicketKeystore] does not exist. Authentication stack: [ticket]. The possible reasons for that problem are: keystore does not exist or the user has no permission to read from the keystore view. You can delete the TicketKeystore and restart the engine so that the engine automatically re-creates it.
I suspect the SAPLogonTicketKeystore was recreated incorrectly... I will have the migration team recreate it again. FWIW, I am unfamiliar with the process of assigning user access to this object as the error suggests.
Thanks for the suggestions...

Error when connecting to Portal logon screen...

Hi,
We have a problem logging on to our portal system.
We changed the logon screen par file to add a graphic, this worked ok but we found a cosmetic error.
We changed the logon screen par file again and now we get the error below.
We have put back the original par file but are still getting the same error.
We have changed the par file on other systems without any problem in the past.
Could anybody point us in the right direction as to what we have done wrong?
Portal Runtime Error
An exception occurred while processing a request for :
iView : uk.gov.manchester.portal.logon.default
Component Name : uk.gov.manchester.portal.logon.default
Error occurs during the rendering of jsp component.
Exception id: 10:22_11/09/08_0018_88399250
See the details for the exception ID in the log file
The contents of the log file are as follows:-
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[10, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.9.trc]/>
<!NEXTFILE[defaultTrace.11.trc]/>
<!LOGHEADER[END]/>
#1.5 #C0000A70EC200057000000230000630D0004568DD104FFD3#1221067003980#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0####3da7f8807f5c11dda4fad9a60a70ec20#SAPEngine_Application_Thread[impl:3]_8##0#0#Error#1#/System/Server#Java###Exception ID:06:16_10/09/08_0171_88399250
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Access is denied: com.sap.portal.heartbeats.PortalHeartbeat - user: Guest,
 at com.sapportals.portal.prt.deployment.DeploymentManager.checkPermissions(DeploymentManager.java:2009)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:247)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
 at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java: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:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): com.sap.portal.system/security/sap.com/NetWeaver.Portal/high_safety/com.sap.portal.heartbeats/components/PortalHeartbeat)
 at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:417)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1227)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1233)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1233)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1233)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1233)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1233)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1233)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1233)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1332)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1279)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1046)
 at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)
 at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.sapportals.portal.prt.deployment.DeploymentManager.checkPermissions(DeploymentManager.java:2004)
 ... 26 more

Memory problems on the Server.
Closed a spare system and all ok.

7.01 to 7.3 Upgrade - Logon Screen - "Logon Problems? Get Support" occuring

Hi
We have upgrade our ABAP and JAVA stacks from NW 7.01 to NW 7.3.
After the upgrade is the "Logon Problems? Get Support" occuring on our portals logon screen. In 7.01 this was controlled with the parameter ume.logon.logon_help - however after the upgrade we do not see this parameter anymore.
Screen dump (requires a couple of clicks)
http://www.filefactory.com/file/c26d20b/n/Portal_Logon_Page_Issue.jpg
Any idea about how we remove the "Logon Problems? Get Support" part?
Thanks and kind regards,
Torben

Hi Torben,
On my fresh 7.3 installation, everything is clean and ... fresh ...
So, for example, the built in group AnonUsers only has the user Guest as it's solely relation (no parent, no child groups); the guest user has the Guest role, which has (via it's groups) roles Everyone and Guest; onbly the role Everyone as got UME actions.
All together, this sounds much like an upgrade issue (on my fresh 7.3, there is no group "J2EE_GUEST" at all).
Two possibilities to go:
- Open an OSS message (should be done in any case probably, to report this issue to SAP, so that this can be fixed);
- Check the UME consistenty by yourself (http://help.sap.com/saphelp_nw73/helpdata/en/44/aecb4253217037e10000000a422035/frameset.htm)
Maybe the second point already will fix some things; would be great for you, anyhow, I still would advise to report this issue officially to SAP.
Hope it helps
Detlev

Portal Logon image not changing

Hi Experts,
I am performing the branding of the portal login screen and have changed the branding-image.jpg and branding-text.gif files to the custom files i nthe Visual Admin - UME provider properties.
I restarted the instance but still the logon screen images are still not changed.
Can some one advise. I do not want to go the par file deployment way as I do not have anytime left in the project. Any ideas?
Regards,
Shobhit

Hi
Logon Screen Customization in EP7.0
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/fc3ae22adb025fe10000000a1553f7/frameset.htm
use config tool to change the image
http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/content.htm
refer this thread for more
Re: Portal Logon Page
Regards
Ganesan S

Portal Session Problem

Hello all!
I am trying to log-on to my portal with two different users parallel.
Example:
1. Open Internet Explorer -> Portal -> Logon as Administrator
2. Open Internet Explorer once again (NOT String-N) -> Portal -> Logon as another user
The problem is, that if I am opening the second Internet Explorer, he automatically logs-on as the Administrator. He is using the first portal session.
I also tried this with the moziall firefox. Same problem.
Does anybody know how to solve this problem?
Thank you in advance.
Best regards, Patrick.

Hi Patrick,
Logon with the admininstrator and open the personalize option in the masthead.
Check the option WorkProtect Mode and ensure that the option Use default portal setting is selected.
Thanks,
Trikanth

Customization of Portal Logon problem

Similar Messages

Maybe you are looking for