Federated Portal Network - Unexpected Error - Unable to get IView

[Former Member]

Hallo.

I have this problem: I have two portal federated.

When I create an iView BI7.0 from the consumer portal , that points to the producer portal , when I execute it I obtain the error :

500 Internal Server Error

BEx Web Application

Failed to process request; contact your system administrator

Error Summary

Exception occured while processing the current request; this exception cannot be handled by the application or framework

If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator

To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)

Root Cause

The initial exception that caused the request to fail was:

Unexpected error - Unable to get IView: fpn:consumer_ABC/pcd:portal_content/com.abc.AbcFolder/zcitbi70/worksetBI70/Prova/sottoprova/BI7ReportProgetti:lQ9fUQ0dfID4PPyUU4cpZg%3D%3D:1:

Note that I am able to see the iview, role etc from consumer to producer, so the Federated Portal Network seems to work.

What could I do ?

Thanks for your help

Mario

[Former Member · Accepted solution]

Please check if the permissions are defined correctly on the Producer Portal content.

Kiran

[anja_engelhardt2]

Hi Mario,

yes, ms_server is the correct type if you like to use the message server port. This is also documented:

http://help.sap.com/saphelp_nw70/helpdata/EN/43/222fc40bb93fece10000000a11466f/frameset.htm

At the end of the side you'll see a part telling about P4 connection types.

Cheers,

Anja

[Former Member]

Hi Experts,

I am getting below error in logs. Some of the reports working and some of the are not working. I can see below error in BW system logs. Any inputs to solve this issue is much appreciated.

java.io.IOException: Cannot establish connection with any of the profiles.

ID 011006:Rmi_P4 Dispatcher: Can't open socket

Error while processing the request in a BI application; see SAP Notes 937697 and 948490

Exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException: Unexpected error - Unable to get IView: fpn:PP2_IS_CONSUMER_FOR_PB1/pcd:portal_content/com.sw1.intranet.staff/com.sw1.intranet.staff.bi/com.sw1.intranet.staff.bi.roles/com.sw1.intranet.staff.bi.hr.roles.headcount_reports/com.sw1.intranet.staff.srm.worksets.reports/com.sw1.intranet.staff.bi.hr.parentws.headcount_reports/com.sw1.intranet.staff.bi.hr.ws.headcount_reports/com.sw1.intranet.staff.bi.hr.iviews.headcount:hNsfu%2FSQ7LTdTmfpBwd7qQ%3D%3D:1:

com.sapportals.portal.prt.runtime.PortalRuntimeException: Unexpected error - Unable to get IView: fpn:PP2_IS_CONSUMER_FOR_PB1/pcd:portal_content/com.sw1.intranet.staff/com.sw1.intranet.staff.bi/com.sw1.intranet.staff.bi.roles/com.sw1.intranet.staff.bi.hr.roles.headcount_reports/com.sw1.intranet.staff.srm.worksets.reports/com.sw1.intranet.staff.bi.hr.parentws.headcount_reports/com.sw1.intranet.staff.bi.hr.ws.headcount_reports/com.sw1.intranet.staff.bi.hr.iviews.headcount:hNsfu%2FSQ7LTdTmfpBwd7qQ%3D%3D:1:

at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1960)

at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:234)

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.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._createRequestParameters(BIRuntimeService.java:397)

at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.createRequestParameters(BIRuntimeService.java:379)

at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:303)

at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:250)

at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)

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(AccessController.java:246)

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: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(AccessController.java:219)

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.sap.portal.fpn.exception.base.unchecked.FpnCommunicationException: Could not retrieve the bean / access service to connect with consumer 'PP2_IS_CONSUMER_FOR_PB1'

at com.sap.portal.fpn.entrypoint.FederatedPersistanceUtils.getAccessServiceByConsumerName(FederatedPersistanceUtils.java:169)

at com.sap.portal.fpn.entrypoint.RuntimeFederatedPersistance.retrieveDLRemoteState(RuntimeFederatedPersistance.java:92)

at com.sap.portal.fpn.FpnRuntimeService.bringRemoteState(FpnRuntimeService.java:134)

at com.sap.portal.fpn.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:97)

at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:49)

at javax.naming.InitialContext.lookup(InitialContext.java:361)

at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1919)

... 40 more

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances

Nested exceptions are:

com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Cannot open connection on host: and port: ] at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455) at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65) at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46) at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675) at com.sapportals.portal.prt.jndisupport.NamingManager.getInitialContext(NamingManager.java:50) at com.sapportals.portal.prt.jndisupport.InitialContext.getDefaultInitCtx(InitialContext.java:39) at javax.naming.InitialContext.init(InitialContext.java:233) at javax.naming.InitialContext.<init>(InitialContext.java:209) at com.sapportals.portal.prt.jndisupport.InitialContext.<init>(InitialContext.java:24) at com.sap.portal.fpn.entrypoint.FederatedPersistanceUtils.getAccessServiceByConsumerName(FederatedPersistanceUtils.java:159) ... 46 more Caused by: com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances Nested exceptions are: com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Cannot open connection on host: and port:

at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:55)

at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:35)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:340)

... 56 more

[anja_engelhardt2]

Seeing the objects of BI in the consumer does not mean that FPN is configured correctly. Please test the trust:

login to the consumer and change the URL to the one of the producer

If you are automatically logged into the producer also trust works fine.

If this is possible please check both default traces - consumer and producer for P4 Exceptions. I assume there will be one there. P4 Exception means that there is some problem in the P4 communication between both machines and/or both J2EE Engines. In this case test if P4 is possible at OS level. If this also does not help check out note 845302.

Cheers, Anja

[Former Member]

Hallo Anja,

thanks for your help.

I tried what you asked me.

I am able to login to the producer when I logged into the consumer (I changed the url and it works without lo login).

Default trace on the producer is :

Error while processing the request in a BI application; see SAP Notes 937697 and 948490

n/a com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService sap.com/irj SBJHVIVV01 Server 1 0_19290

error 2009-04-09 15:14:38:460 Exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException: Unexpected error - Unable to get IView: fpn:consumer_EPP/pcd:portal_content/com.vimar.VimarFolder/zcitbi70/worksetBI70/Prova/sottoprova/BI7ReportProgetti:lQ9fUQ0dfID4PPyUU4cpZg%3D%3D:1:

com.sapportals.portal.prt.runtime.PortalRuntimeException:... [see details]

n/a com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService sap.com/irj SBJHVIVV01 Server 1 0_19290

error 2009-04-09 15:14:38:444 java.io.IOException: Cannot establish connection with any of the profiles.

ID 011006:Rmi_P4 Dispatcher: Can't open socket

n/a com.sap.engine.services.rmi_p4 n/a SBJHVIVV01 Dispatcher 0 0_19290

error 2009-04-09 15:14:37:085 Naming exception from the pcd when trying to access the principal ROLE.PCD_ROLE_PERSISTENCE.YEaWaiBxXMnE3kjX3nccxXFJGmM=

[EXCEPTION]

javax.naming.NameNotFoundException: Child not found: ZprovaReport at portal_content/vimarfolder [Root exception is javax.naming.NameNotFoundException: Child not found:... [see details]

n/a com.sap.security.portal.service.usermanagement.[cf=com.sapportals.portal.prt.service.usermanagement.persistence.pcd.GLRolePersistence][md=populatePrincipalDatabag][cl=171406] sap.com/irj SBJHVIVV01 Server 1 0_19290

error 2009-04-09 15:14:36:850 Naming exception from the pcd when trying to access the principal ROLE.PCD_ROLE_PERSISTENCE.YEaWaiBxXMnE3kjX3nccxXFJGmM=

[EXCEPTION]

javax.naming.NameNotFoundException: Child not found: ZprovaReport at portal_content/vimarfolder [Root exception is javax.naming.NameNotFoundException: Child not found:... [see details]

n/a com.sap.security.portal.service.usermanagement.[cf=com.sapportals.portal.prt.service.usermanagement.persistence.pcd.GLRolePersistence][md=populatePrincipalDatabag][cl=171406] sap.com/irj SBJHVIVV01 Server 1 0_19290

error 2009-04-09 15:14:33:132 Naming exception from the pcd when trying to access the principal ROLE.PCD_ROLE_PERSISTENCE.YEaWaiBxXMnE3kjX3nccxXFJGmM=

[EXCEPTION]

javax.naming.NameNotFoundException: Child not found: ZprovaReport at portal_content/vimarfolder [Root exception is javax.naming.NameNotFoundException: Child not found:... [see details]

n/a com.sap.security.portal.service.usermanagement.[cf=com.sapportals.portal.prt.service.usermanagement.persistence.pcd.GLRolePersistence][md=populatePrincipalDatabag][cl=171406] sap.com/irj SBJHVIVV01 Server 1 0_19290

error 2009-04-09 15:14:33:100 Naming exception from the pcd when trying to access the principal ROLE.PCD_ROLE_PERSISTENCE.YEaWaiBxXMnE3kjX3nccxXFJGmM=

[EXCEPTION]

javax.naming.NameNotFoundException: Child not found: ZprovaReport at portal_content/vimarfolder [Root exception is javax.naming.NameNotFoundException: Child not found:... [see details]

n/a com.sap.security.portal.service.usermanagement.[cf=com.sapportals.portal.prt.service.usermanagement.persistence.pcd.GLRolePersistence][md=populatePrincipalDatabag][cl=171406] sap.com/irj SBJHVIVV01 Server 1 0_19290

error 2009-04-09 15:14:33:069 Naming exception from the pcd when trying to access the principal ROLE.PCD_ROLE_PERSISTENCE.YEaWaiBxXMnE3kjX3nccxXFJGmM=

[EXCEPTION]

javax.naming.NameNotFoundException: Child not found: ZprovaReport at portal_content/vimarfolder [Root exception is javax.naming.NameNotFoundException: Child not found:... [see details]

n/a com.sap.security.portal.service.usermanagement.[cf=com.sapportals.portal.prt.service.usermanagement.persistence.pcd.GLRolePersistence][md=populatePrincipalDatabag][cl=171406] sap.com/irj SBJHVIVV01 Server 1 0_19290

error 2009-04-09 15:14:33:022 Naming exception from the pcd when trying to access the principal ROLE.PCD_ROLE_PERSISTENCE.YEaWaiBxXMnE3kjX3nccxXFJGmM=

[EXCEPTION]

javax.naming.NameNotFoundException: Child not found: ZprovaReport at portal_content/vimarfolder [Root exception is javax.naming.NameNotFoundException: Child not found:... [see details]

So, I see an entry of P4 type.

I checked the oss note that you mentioned on P4 problem but I haven't the problem on brokerID (They are different from consumer and producer)

What could I check ?

[Former Member]

Hallo,

my consumer is a cluster with 2 instances ABAP+Java.

I set

com.sap.portal.remotePortal.P4Connection=direct

com.sap.portal.remotePortal.P4PortConsumer=8101

but I have a doubt : 8101 is the SCS message server http port so, have I to set

com.sap.portal.remotePortal.P4Connection on a different value from "direct" ?

Thanks.

Mario

[Former Member]

Hallo,

my consumer is a cluster with 2 instances ABAP+Java.

I set

com.sap.portal.remotePortal.P4Connection=direct

com.sap.portal.remotePortal.P4PortConsumer=8101

but I have a doubt : 8101 is the SCS message server http port so, have I to set

com.sap.portal.remotePortal.P4Connection on a different value from "direct" ?

I tried to set :

com.sap.portal.remotePortal.P4ConnectionConsumer=Message Server but when I save and I register, it is set to "direct"

So, what have I to do?

Thanks.

Mario

[Former Member]

Now I am able to set :

com.sap.portal.remotePortal.P4ConnectionConsumer=Ms_server

com.sap.portal.remotePortal.P4PortConsumer=8101

com.sap.portal.remotePortal.P4Connection=Ms_server

com.sap.portal.remotePortal.P4Port=8101

and now it seems to work !!!

Thanks.

Mario

[anja_engelhardt2]

Hi Mario,

have you ever been able to view any BI iView within your federated portal? If yes - what did you do in the meantime? Any upgrade of any of those 2 systems?

Sometimes after upgrades it happens that BI iViews are not working through FPN as on BI side there have beens some changes. In this case just recreate the FPN connection and try again.

If it has never been working in the past for you please check your FPN configuration. Check trust especially.

Cheers,

Anja

[Former Member]

Hallo.

I have the right permission on the BI portal (producer)

I am able to see the BI object (iViews, Roles) from the Consumer (from Content Administrator->Portal Content->NetWeaver Content Producer->"Name of the producer"->Portal Content ...)

I have the problem only when I execute the iview on the Consumer, that points to the producer BI report.

We didn't upgraded nothing in the meantime.

Thanks.

Mario

[Former Member]

Hi,

The iview works in consumer portal?

Regards

Grilo