Error in deploying VC iView on Portal

hi all,
i have created an applicaton which will fetch data from SAP R/3 and will be shown in an iView which is made in VC.
when i try to deploy that iView in Portal , i get an compilation error ,
the error is
"Error in executing a process for compilation, .\GUIMachine_Business_Packages\testbi_21811\com.autogen.guimachine.testbi.iView_TestBI\src.core\Iview_testbi_ctl.java:62: cannot resolve symbol
symbol : constructor BWQueryFunction (java.lang.String,com.sapportals.guimachine.ep5kit.Iview_testbi_ctl,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,int,java.lang.String)
location: class com.sap.portal.guimachine.bikit.runtime.BWQueryFunction
BWQueryFunction BWQGQR = new BWQueryFunction ("BWQGQR", this, profile.getProperty("System1"), "/sap/bw/xml/soap/queryview", "ZVC_CUBE", "VCQUERY1", "", 2, 500,"KEY");
^
1 error
how could i solve this problem.
please help me to solve this error
Regards
Naveen Gupta

Hi,
If you are using Ep 6.0 Sp 15 then you have to deploy the BIKIT for Sp 13 on the portal using SDM.
This will solve Your problem.
Regards,
Naveen Gupta

Similar Messages

Compilation error while deploying an iView containing BI Queries

Hi All,
I am trying to use a BW Query in my VC.
Using BI Query Wizard, i have selected my query. So, when I preview my output in VC, it is giving the output. But when I am deploying my iView into the portal, I am getting the following error:
Error in executing a process for compilation, .\GUIMachine_Business_Packages\testbi_21817\com.autogen.guimachine.testbi.iView_TestBI\src.core\Iview_testbi_ctl.java:46: cannot resolve symbol
symbol : constructor BWQueryFunction (java.lang.String,com.sapportals.guimachine.ep5kit.Iview_testbi_ctl,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,int,java.lang.String)
location: class com.sap.portal.guimachine.bikit.runtime.BWQueryFunction
BWQueryFunction BWQGTF = new BWQueryFunction ("BWQGTF", this, profile.getProperty ^
^
("System1"), "/sap/bw/xml/soap/queryview", "ZVC_CUBE", "VCQUERY1", "", 2, 500,"KEY");
1 error
The error says that symbol cannot be resolved, which symbol is it talking about?
Thanks in advance,
Deep.

Hi Norbert,
We add few addons on portal for visual composer.Till EP6.0 sp13 the addons had to be deployed separately onto portal,but since SP14 onwards these come with the portal patch itself and we don't have to deploy the .sda files explicitly for visual composer.
The constructor of BWQueryFunction class which is being generated by the guimachine of Visual composer corresponds to that present in com.sap.portal.guimachine.BIKITapi.jar file present in SP13 addons and hence you get a compile time error when trying to deploy onto sp15 or sp16 portal.
One solution to this problem is to deploy the visual composer addons corresponding to SP13.The jar file com.sap.portal.guimachine.BIKITapi.jar is present in com.sap.visualcomposer.BIKiT.sda file.
Hope this solves your problem.
Regards,
Pradeep

Error while creating webdynpro iview after portal upgrade to ehp1

Hello All
We have upgraded our portal from 7.0 sp 15   to portal 7.01 sp 3    .
After upgrade we can create iviews using portal components but we are not able to create iview using Iview template
We are getting following error while creating webdynpro java iview
java.lang.NoSuchMethodError: com.sapportals.portal.pcd.gl.PcdSearchControls.addExplicitAttributeCheck(Lcom/sapportals/portal/pcd/gl/IPcdAttribute;)V
     at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getPCDCatalog(TemplatesCacheSrv.java:184)
     at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.refresh(TemplatesCacheSrv.java:589)
     at com.sap.newpage.pagewizardpanes.PageTemplateSelection.initTemplates(PageTemplateSelection.java:229)
     at com.sap.newpage.pagewizardpanes.PageTemplateSelection.wdDoModifyView(PageTemplateSelection.java:172)
     at com.sap.newpage.pagewizardpanes.wdp.InternalPageTemplateSelection.wdDoModifyView(InternalPageTemplateSelection.java:305)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     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:319)
     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:860)
     at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1300)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869)
     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:319)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     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)
Regards
Rajendra

Hello Rajendra,
please can you tell me, if you finally get a Solution for this Problem about iviews creation with template Error after upgrade.
Thanks and take Care
Gedeon

Javascript error in Standard MDM IViews on portal

Hello Xperts,
I have deployed standard MDM IViews on my portal.
In standard Resultset IView, there is a provision of saving results by using My Bags option. When I click on My Bags option and then New Bag, it throws javascript error.
Details of systems are as below.
MDM API version 5.5
Portal Version EP 7 SP07.
Appreaciate any inputs for this.
Ashutosh

Hi Anu,
Thanks for the reply.
we are able to login to Data Manager with Mapped ID's and I even tried creating new IViews. Nothing worked.
As you suggested, will try restarting the portal server.
Thanks
Satish

Error while deploying gml files to portal through VC

Hi,
I am trying to deploy the models through VC to portal. The model are getting compiled correctly but error out while deploying with the error" No Valid iviews"
The same models are getting deployed on the Sandbox server but not on the development portal ?
Can some one point in right direction ?
Regards
Jayesh

Hi Jayesh
Can you please specify which version of VC are you working on?
Thanks,
Shai

GETTING ERROR WHILE DEPLOYING A COM.SAP.PORTAL.RUNTIME.LOGON.PAR FILE

Hi Experts,
I need to change the text in logon screen i.e,
2006-2007 SAP AG ALL RIGHTS RESERVED
for this i changed the copyright and deployed the par file
but it is giving error like this
operation failed:please make sure the server is running or check the log(sap-plugin.log)
what should i do plz suggest me na.....
i searched the file sap-plugin.log in program files -> sap>IDE>eclipse-->plugin but i couldnt find the
plz specify the directory na...
waiting for u r response.....
Regards,
Shilpa

HI SHILPA....really sorry for the late response.
here is the error log which i m getting...(its not 500 error)
[13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Startup in progress
[13.08.08 / 16:49] #DEBUG LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin > Factory initialized !
[13.08.08 / 16:50] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 502 for URL: http://hostname:50000/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=Administrator&j_password=EPDJ2EEADM&j_authscheme=default&uidPasswordLogon=Log%20on
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:808)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.invokeWizardInANewDialog(WizardInvokeAction.java:179)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.actions.WizardInvokeAction.run(WizardInvokeAction.java:84)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
     at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

Error while deploying BIKit.sda on Portal

Hello Masters,
When I select the system for BW from VC Data tab, I get the following error:
Error -21007:Search for table returned an error. Service not found:
com.sap.portal.guimachine.BIKit.CommandHandler.
However I am using VC 6.0 with Patch level 6.0 and EP 6.0 with SP14. So I tried to deploy the following sda files on the portal server:
BIUDISystems.sda
com.sap.visualcomposer.BIKit.sda
com.sap.visualcomposer.BIKitQV.ear
But I am not been able to deploy the last .ear file, the error message I am getting is as follows:
===========================================================================
Deployment started Tue Jan 24 17:18:23 IST 2006
===========================================================================
Starting Deployment of com.sap.visualcomposer.BIKitQV
Aborted: development component 'com.sap.visualcomposer.BIKitQV'/'sap.com'/'SAP AG'/'6.20.20050824171228.0000':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.visualcomposer.BIKitQV.. Reason: com.sap.engine.services.webservices.jaxrpc.wsdl2java.ServiceBase.setGlobalClientSettings(Lcom/sap/engine/interfaces/webservices/runtime/GlobalClientSettings;)V; nested exception is: java.lang.NoSuchMethodError: com.sap.engine.services.webservices.jaxrpc.wsdl2java.ServiceBase.setGlobalClientSettings(Lcom/sap/engine/interfaces/webservices/runtime/GlobalClientSettings;)V
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.visualcomposer.BIKitQV finished with Error (Duration 14312 ms)
Can any one tell me what configurations to do to create an application which will use BW Queries.
Thanks in advance,
Deep.

you need to set up FQDN fully qualified domain name.
instead of http://duetserver:8006/....you need to use
http://duetserver.domain.com:8006/...
check
1. whether WAS settings in system definition in portal is with FQDN
2. check whether ABAP system FQDN is done. (its in the profile parameter icm/host_name_full (you can run abap report RSPARAM and check this.)

Error after deploying JCA on EP6( Portal Applications with RFC)

Error
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
iView not found: ewParProject.JspPage.
Exception id: 06:22_23/03/07_0104_14574950
See the details for the exception ID in the log file
I have written code in java file for connection as follows
please help me.
package com.rr.JspPage;
import javax.resource.cci.MappedRecord;
import javax.resource.cci.RecordFactory;
import com.sap.security.api.umap.NoLogonDataAvailableException;
import com.sapportals.connector.ConnectorException;
import com.sapportals.connector.connection.IConnection;
import com.sapportals.connector.execution.functions.IInteraction;
import com.sapportals.connector.execution.functions.IInteractionSpec;
import com.sapportals.connector.execution.structures.IRecordMetaData;
import com.sapportals.connector.execution.structures.IRecordSet;
import com.sapportals.htmlb.page.DynPage;
import com.sapportals.htmlb.page.PageException;
import com.sapportals.portal.htmlb.page.JSPDynPage;
import com.sapportals.portal.htmlb.page.PageProcessorComponent;
import com.sapportals.portal.ivs.cg.ConnectionProperties;
import com.sapportals.portal.ivs.cg.IConnectorGatewayService;
import com.sapportals.portal.ivs.cg.IConnectorService;
import com.sapportals.portal.prt.component.IPortalComponentRequest;
import com.sapportals.portal.prt.runtime.PortalRuntime;
@author laxmikant.pathak
To change the template for this generated type comment go to
Window>Preferences>Java>Code Generation>Code and Comments
public class JspPage extends PageProcessorComponent {
public DynPage getPage(){
 return new JspPageDynPage();
public static class JspPageDynPage extends JSPDynPage{
 /* (non-Javadoc)
@see com.sapportals.htmlb.page.DynPage#doInitialization()
 public void doInitialization() {
 try {
 IConnectorGatewayService cgService =(IConnectorGatewayService)
 PortalRuntime.getRuntimeResources().getService(IConnectorService.KEY);
 IPortalComponentRequest request=(IPortalComponentRequest) this.getRequest();
 ConnectionProperties cp = new ConnectionProperties(request.getLocale(),request.getUser());
 IConnection connection = cgService.getConnection("P35",cp);
 IInteraction ix = connection.createInteractionEx();
 IInteractionSpec ixspec = ix.getInteractionSpec();
 // Put Function Name into interaction Properties.
 ixspec.setPropertyValue("Name","ZHRESS_ESEPARATION_DETAILS");
 RecordFactory rf = ix.getRecordFactory();
 // create input MappedRecord from
 MappedRecord input;
 input = rf.createMappedRecord("input");
 input.put("YYMOD","DIS");
 input.put("YYUSR","EMP");
 MappedRecord output = (MappedRecord)ix.execute(ixspec, input);
 IRecordSet rs = null;
 Object result = output.get("T_P9100");
 if (result instanceof IRecordSet)
 rs = (IRecordSet) result;
 IRecordMetaData rsmd = null;
 try
 rsmd = rs.retrieveMetaData();
 } catch (Exception ex)
 ex.getStackTrace() ;
 // Do something with the Metadata
 finally
 if (connection != null)
 try
 connection.close();
 //logMsg("* Iview: Closing connection ok.");
 connection = null;
 catch (Exception e)
 //logMsg("* Iview: Error closing connection.");
 } catch (ConnectorException e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
 } catch (NoLogonDataAvailableException e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
 } catch (javax.resource.ResourceException e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
 public void doProcessAfterInput() throws PageException {
 public void doProcessBeforeOutput() throws PageException {
 this.setJspName("JspPageFile.jsp");
My Jsp file
hbj:content id="myContext" >
<hbj:page title="PageTitle">
 <hbj:form id="myFormId" >
 Test
 </hbj:form>
</hbj:page>
</hbj:content>
XML File
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
 <property name="PrivateSharingReference" value="com.sap.portal.htmlb"/>
 <property name="ServicesReference" value="com.sap.portal.ivs.connectorservice"/>
</application-config>
<components>
 <component name="JspPage">
 <component-config>
 <property name="ClassName" value="com.rr.JspPage.JspPage"/>
 <property name="ComponentType" value="jspnative"/>
 <property name="JSP" value="pagelet/JspPageFile.jsp"/>
 <property name="ServicesReference" value="com.sap.portal.ivs.connectorservice"/>
 </component-config>
 <component-profile/>
 </component>
</components>
<services/>
</application>
Error
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
iView not found: ewParProject.JspPage.
Exception id: 06:22_23/03/07_0104_14574950
See the details for the exception ID in the log file

Hi Laxmi,
this is a portal application problem - nothing to do with this forum. Anyway - you can try by changing your component-config portion in portalapp.xml and see whether it works or not.
Your current component config is like below
<component-config>
<property name="ClassName" value="com.rr.JspPage.JspPage"/>
<property name="ComponentType" value="jspnative"/>
<property name="JSP" value="pagelet/JspPageFile.jsp"/>
<property name="ServicesReference" value="com.sap.portal.ivs.connectorservice"/>
</component-config>
Try replaing the same with below:
<component-config>
<property name="ClassName" value="com.rr.JspPage.JspPage"/>
<property name="SecurityZone" value="com.sap.portal.pdk/low_safety"/>
</component-config>
Check once and let me know...
regards,
Shubho

Error while deploying WDA application on portal.

hello Friends,
i am getting this error when eevr i try to check my WDA application on portal.
can you please help me?
note:my its connection is not establishing.
is this the cause of error?
The URL http://duetserver:8006/sap/bc/webdynpro/sap/z57316_portal_event_send/ was not called due to an error.
Note
The following error text was processed in the system EC1 : Die URL enthält keine vollständige Domainangabe (duetserver statt duetserver.).
The error occurred on the application server DuetServer_EC1_06 and in the work process 1 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system EC1 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server DuetServer_EC1_06 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server DuetServer_EC1_06 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 100 -u: DEVECC -l: E -s: EC1 -i: DuetServer_EC1_06 -w: 1 -d: 20070614 -t: 142215 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
thanks,
Nutan.

you need to set up FQDN fully qualified domain name.
instead of http://duetserver:8006/....you need to use
http://duetserver.domain.com:8006/...
check
1. whether WAS settings in system definition in portal is with FQDN
2. check whether ABAP system FQDN is done. (its in the profile parameter icm/host_name_full (you can run abap report RSPARAM and check this.)

Error while deploying WebDynpro IViews

Hello All,
I am trying to deploy webdynpro application on the remote WAS server and I am getting following error.
Server serverName did not accept login request as admin on port XXXXX.
Details: ERROR: Could not establish connection to server serverName at port XXXXX:
No route to host: connect
I have checked following things that could cause me error.
1. There is an entry in the host file with IP address of the remote server.
2. The remote server name is spelled correctly in the NWDS settings.
3. The J2EE engine is running fine and shows green nodes when checked through J2EE engine perspective.
I am using SP14 on my system.
Could someone throw some light on what exactly is going wrong with my settings?
I would appreciate the helpfull responses.
Ashutosh Moharir

Hey Gowri,
I know the port number and it is correctly mentioned in the settings.
Regarding PING, it would anyway work once you put entry in hosts file.
Moreover, the same settings are working for other system located in the same network.
From my system, I am unable to access any WAS system (local and remote).
Any idea?
Ashutosh

LDAP users Faicng Error While Accessing the ESS Iviews in Portal

Hi,
My Portal is SAP EP 7.0 SP20 And ECC 6.0 SP16.
UME users able to access the ESS MSS Iviews.But only one LDAP User only access ESS/MSS Iviews Other getting the Below error.
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
Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
                at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:205)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:428)
                at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:570)
                at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:292)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
                at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:389)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:546)
                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.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:314)
                at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
                at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
                at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
                at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:278)
                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.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
                at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
                at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
                at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
                at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.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:782)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                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.wdDoInit(PageBuilder.java:193)
                at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
                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:782)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                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)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
                at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:171)
                at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
                ... 76 more
Thanks & Regrads,
Subba Rao

Hi,
Now every user facing the same error while accessing ESS Iviews from Portal.
in ST22 Dump is created.
What happened?                                                                                |
Error in the ABAP Application Program
The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_XSS_CAT_BUFFER=============CP " in include
"CL_XSS_CAT_BUFFER=============CM00C " in
line 50:
""L_CATSDB" and "L_CATSDBCOMM" are not mutually convertible. In Unicode"
" programs, "L_CATSDB" must have the same structure layout as "L_CATSDB"
"COMM", independent of the length of a Unicode character."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
terminated because it has
|    come across a statement that unfortunately cannot be executed.
What we need to resolve the above issue.
Thanks & Regards,
Subba Rao

Error while deploying models in VC

Hi Experts,
I am encountering the following error while deploying any model on Portal. The model compiles without any errors but while deployment it gives the below error:
Error in compiling Flex application: Error: Element type "vc:VCFormLabel" must be followed by either attribute specifications, ">" or "/>".
(D:\usr\sap\WEP\JC01\j2ee\cluster\server0\GUIMachine_Business_Packages\Test_Model_61468\FLEX_COMPILATION_FOLEDR\AAD1IXA.mxml:131)
Failed to compile AAD1IXA.mxml
Please help me out in fixing this issue.
Regards,
Arafat

Hi,
Please refer to note 1039898. This is the error it talks about. You should be on SP12 and up to fix this issue or use the form 's default layout
Regards,
Natty

Error - While deploying application in portal

Hi Friends..
I have developed applications using NWDS, after that I tried to deploy the applications using .ear files
into portal, at that moment I got the below error message
Apr 28, 2009 5:31:13 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[005]Deployment aborted
Settings
SDM host : xxxxxxxx
SDM port : yyyy
URL to deploy : file:/C:/DOCUME1/GOWRI1.SHA/LOCALS~1/Temp/temp25231CalculatorEar.ear
Result
=> deployment aborted : file:/C:/DOCUME1/GOWRI1.SHA/LOCALS~1/Temp/temp25231CalculatorEar.ear
Aborted: development component 'CalculatorEar'/'sap.com'/'localhost'/'2009.04.28.16.56.03'/'0':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
Deployment exception : The deployment of at least one item aborted
please let me know the solution for this.
Thanks
Gowrishankar

I developed my simple calculator app under NWDS, exported it as an EAR file, transferred the file from my laptop to my Unix Java host and deployed it using SDM.
When I build an iView I can't find it. It doesn't appear as an iView template (unlike a PAR file I deployed earlier) and if I follow the help in the link from the previous post then I get application exceptions indicating that the portal component is not valid. (I still have to trawl the log for details of the full error text.)
I don't understand the process behind the deployment. I know that the EAR file is a compressed archive of components required to run the application but what does the deployment process do with this? Where are the components stored? How does the portal's iView builder decide that it's looking in the right or wrong place? How does the portal (how do I) know what sort of iView to build and what object type to include?

Error - while deploying to Portal

Hi,
I get error while deploying ti portal from Visual Composer. The iView works fine in preview mode. In the log i find error like "com.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException
Cannot assign a zero-length byte array to host variable 18."
Please suggest.
Thanks
SA

hi,
Same problem has been dealt with the solution in this thread
Portal (EP6) deployment failed
Regards,
Ganesh N

Federated Portal Network - Unexpected Error - Unable to get IView

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

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

Error in deploying VC iView on Portal

Similar Messages

Maybe you are looking for