Hello,

We are working with EP 7.4 SP 11

Our requirement is, if user was not logged into his portal account within 60 days then account should locked automatically .

I done the changes in UME Properties(please find an attachment) from system administrator-->System Configuration-->UME Configuration-->Security Policy Tab.

In attachment, I set “Password Maximum idle time=1” for testing purpose but I am not successful to lock user account after 1 day.

Please suggest, if any other changes is require.

After changing the UME property, is it compulsory to restart the server?

Thanks,

Dhara

All,   To fix another issue, I must change from Generic Application Integrator iview I have ben using,  to a Web Dynpro iview created from remote source.

In current iview, I am passing sap-language and also the screen id as dynamic parameters whose value comes in on the URL to the SAP portal.  and then is passed to back end system. 

Using new iview,  we have made that work successfully with the screen id, as the web dynpro application did not automatically include that as an application parameter.  

but for the language, the iview that was "created" from the source is already including language parameter, and so, even though it will pass the one I put in as dynamic, since it is the second value, it does not use it.  (We see if listed twice in the Fiddler trace.)
.

How can I tell it not to pass the application parameter it has or derives some how, and instead to pass what I give it.

we have tried putting the field in the property of the iview:   Do Not Forward These Parameters to Web Dynpro but it still did not work.  but perhaps we did not enter it in correctly.

our portal is NW 7.4

Ruth Jones

We are receiving an error in our SAP Enterprise Portal 7.4 (NWA) log.    Its says

Fail to add Node to HistoryService

[Exception]

java.lang.RuntimeException: Secuirty error: failed to validate parameter window ID :

at com.sapportals.portal.navigation.HistoryService.validatewindowID(HistoryService.java:464)

at com.sapportals.portal.navigation.HistoryService.addNavNode(HistoryService.java:291)

at com.sapportals.portal.navigation.HistoryService.addNavNode(HistoryService.java:391)

etc.

I don't know what this means.

Or what we should do to stop it "trying" to make a HistoryService..

Or what security to add to allow it to have a HistoryService?

We are running a single node in the portal. And it is in a DMZ part of the network, so lots of restrictions around it, but this message still means nothing to me.

Ruth Jones

Hi!

If we delete a user from Active Directory it supposly should be delete automatically from Portal UME isn't?

We're getting so many errors with the same description,

User wgomez has been deleted from AD but Portal keeps looking for it.

We're using SAP Netweaver Portal 7.3 SP09.

Help would be highly appreciated

Thanks,

Ariana Barrera

Hi All,

Our portal is taking 20 secs to display the home page. We are using EP 7.31 SP 7 version. I have checked the thread dumps. Everything is fine.We don't know the exact cause of this portal slowness. Is there any solutions to bring back the portal to normal stage?

Thanks and regards,

Karthik.S

Dear experts.

I need know the roles that I need to Transporting portal content (epa-files) and The development portals using Charm?

Should I use the webdynpro ABAP application cts_browser ?

I have read this, however I need more help

How to use CTS+ Transport method in portal | SCN

Regards

Hi,

I'm trying to integrate SAP Portal and Fiori for SSO purposes.  I've created the system and iview and all the connection tests etc are successful.

We've been using SAP Portal for ESS and MSS for sometime now and I did see this exact error when I was setting up ESS but it was to do with a user group not having end user access, but it doesn't appear to be the same issue with Fiori.

Please see my settings below -

No errors found.

But when I preview I get the following error -

Thanks for looking!

Regards

Amanda

Hello ,

we did last week a BW upgrade from 7.0 to 7.4 , ABAP and JAVA , splitted stacks. After the upgrade the BW portal doesn't work anymore. When calling the portal link in browser , following error comes up:

Error: Application error occurred during the request processing.

SAP Technology Troubleshooting Guide

Details:     WebApplicationException log ID is [C0000A017823004100000000000051F9].

The log in detail ( /usr/sap/SID/J03/j2ee/cluster/server0/log/ )

#2.#2016 02 03 09:53:51:724#+0100#Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#

com.sap.ASJ.web.000137#EP-PIN-PRT#sap.com/irj#C0000A017823004100000002000051F9#33154850000000004#sap.com/irj#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_ADMIN#1##0A217D33CA4F11E5933B000001F9E722#80989fbdca5311e5b6a3000001f9e722##0#Thread[HTTP Worker [@412233480],5,Dedicated_Application_Thread]#Plain##

Cannot process an HTTP request to servlet [prt] in [irj] web application.

For more details on the problem please check traces searching by logId: C0000A017823004100000000000051F9#

#2.#2016 02 03 09:53:51:726#+0100#Error#com.sap.engine.services.servlets_jsp.ISE500#

com.sap.ASJ.web.000500#EP-PIN-PRT#sap.com/irj#C0000A017823004100000003000051F9#33154850000000004#sap.com/irj#com.sap.engine.services.servlets_jsp.ISE500#J2EE_ADMIN#1##0A217D33CA4F11E5933B000001F9E722#80989fbdca5311e5b6a3000001f9e722##0#Thread[HTTP Worker [@412233480],5,Dedicated_Application_Thread]#Plain##

500 Internal Server Error is returned for HTTP request [http://ltgvlbd1.ltg-sap.os.itelligence.de:50300/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fEmil_Loeffelhardt!2fcom.loeffelhardt.dektop!2fcustomizedDesktop!2fframeworkPages!2fframeworkpage!2fcom.sap.portal.innerpage]:

  component [prt],

  web module [irj],

  application [sap.com/irj],

  DC name [sap.com/irj],

  CSN component[EP-PIN-PRT],

  problem categorization [com.sap.ASJ.web.000137],

  internal categorization [1449841995].

[EXCEPTION]

java.lang.NoSuchMethodError: com.sapportals.portal.navigation.NavigationEventsHelperService.getFrameworkPage(Lcom/sapportals/portal/prt/component/IPortalComponentRequest;)Lcom/sap/portal/pcm/page/IPage;

        at com.sap.portal.navigation.LightDetailedNavigationTree.doOnNodeReady(LightDetailedNavigationTree.java:83)

        at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:390)

        at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)

        at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)

        at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)

        at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)

        at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:341)

        at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:349)

        at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:198)

        at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:470)

        at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:281)

        at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:712)

        at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:390)

        at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:890)

        at com.sap.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:407)

        at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)

        at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)

        at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)

        at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)

        at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:341)

        at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:349)

        at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:465)

        at com.sapportals.portal.prt.connection.ServletConnection._handleRequest(ServletConnection.java:224)

        at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:101)

        at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

        at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)

        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

        at com.sap.portal.prt.dispatcher.CustomHeaderFilter.doFilter(CustomHeaderFilter.java:58)

        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

        at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)

        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)

        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

        at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

        at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

        at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

        at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

        at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

        at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

        at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

We applied note 2002334 , 1840877 and 2146087 so far but with no success. Any thoughts on this error ?

Thanks

Here are the issues I am facing when my portal is upgraded from 7.0 to 7.4

1. Log off is not working

2. Ajax famework page is empty

3. FLP framework page is also empty (using OOB content for testing FLP).

Thanks for the xpers for the help.

Hello colleagues, I have a problem with the button in the POWL in the SRM - Portal. The button in the POWL / SRM are not active and the links of SC`s are not active. In the Log Viewer I get the warning: uwl_uwl_erp2005_prodspvr.zip:com.sap.netweaver.bc.uwl.UWLException: Tue February 16 09:02:04 CET 2016 (Configuration): org.xml.sax.SAXException: The content of element type "UWLConfiguration" must match"(Principals?,UWLLauncherLocations?,DescriptionBundles?,CompoundExpressions?,Actions?,ItemTypes?,Views?,GlobalDisplayAttributes?,NavigationNode?)". and Reading configuration Failed for: (uwl_erp2005_prodspvr). Exception is The content of element type "UWLConfiguration" must match"(Principals?,UWLLauncherLocations?,DescriptionBundles?,CompoundExpressions?,Actions?,ItemTypes?,Views?,GlobalDisplayAttributes?,NavigationNode?)". How do I get the button in the POWL active set? Best wishes Olli

Hi Experts. We had a domain change so my SLD and J2EE Engine for dev changes to new path. I did re-placed the new SLD and J2EE Runtime links in the NWDS. After that config I tried to sue any existing projects to import or remove from client It is pointing to old DTR. I don't see any where to configure new DTR in the NWDS. But have new DTR and it was setup in CMS  landscape directory. SLD will directly pointing to new DTR correct? Thanks rag

Hi SAP People

I need to know if one can upgrade directly to NW7.4 SP13 from SP5 & SP7 or NW 7.5 SP2.  We need the 2 Portals to be Fiori functional.

HR & SAP Core backend = ECC6 EHP7.

EP NW 7.4 SP7 = connected to - HR, Core & PPM 6.0

FED NW 7.4 SP5 = connected to - BW ASE, BW Hana & BO.

BW Backend = NW 7.4 SP5

BW Hana Backend  = NW 7.4 SP10.  In process to be upgraded to SP12.

Please advice which SP will be the best for the Portals (ASE too) & BW servers.  SP11 / SP12 / SP13, NW 7.5 SP2.

Are there any Tips & Tricks to share?

Are there any known risks?

Please advice.

Thank you

Regards

Wynand

Hi All,

Im trying to use the broadcast messaging functionality in SAP Portal 7.4

I have followed all the steps as per the link - http://scn.sap.com/community/enterprise-portal/blog/2014/08/29/broadcast-messages-in-sap-enterprise-portal-bcm

but for some reason, the message is not broadcasted.  On the broadcast message editor,the status is shown as green.

I have tried various things - Cleared IE cache, Start/Stop Broadcast service in NWA, but still no luck.

Can anyone please suggest the resolution for this issue?

Regards,

PK

Hi,

I deployed customized masterhead war file. But i cant see deployed war in portal application location.

Anyone help me for customizing and masterhead page and how to create iView for customized master head...

Hi,

Do we have any way to hide the highlighted(red) part from the portal screen? either by configuration or enhancement?

Thanks and Regards,

Gabriel

Hi,

We have Outstanding Task displayed on home page of our consumer Portal, which display no of pending UWL task and Attendance management task. When user clicks on Attendance management task user get the log off screen on the portal body. But when we clear the Role delta link Cache from Our consumer it works. Again after some time it stops working and we have to clear the cache. Attendance management iview belongs to MSS role which we have deployed in Producer portal and we are using it as Remote delta link in consumer.

Hello Team,

While I am accessing the MSS appraisal job service in UWL am getting below error. Could please anyone help me to resolve this error.

Log file:

10:58_17/02/16_0042_7206750
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    'SAP_LocalSystem',
Attribute: 'client'.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
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:223)
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:1064)
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)
---------------------------------------------------

Hi Experts,

We did BI JAVA configuration between 740 ABAP system and 740 JAVA system.

When we do user mapping from: User Administration -> Identity Management, it throws one error message:

"Verification of user mapping data for system "EnterprisePortal:SAP_BW" failed; check the credentials for mistakes."

Please help here to resolve this issue.

Kindly find the screenshot of error message.

Thanks and Regard,

Ashish

Hi,

   In Portal , When the user tries to approve the Travel Request from the UWL Worklist, it opens a  new window with all the details and attachment link.

When we clicks the attachment link it opens the new tab in the browser which displays the pdf form.

The issue is  the pdf form display with menu bar(command bar) which it make user to access the ECC system.

      How to hide/remove the menu bar from that screen.

Dear Experts,

During the EP configurations we encountered on error.

ERROR: Extract  CKMINIAPP does not exists (termination ERROR_MESSAGE_STATE).

Does anyone encountered this error before? Please share the resolution.

Regards,

Vipul Patil.