RFC_ERROR_PROGRAM: 'mshost' missing

Hi people,
when I use the BI>Bex on enterprise portal I get the ne
com.sap.ip.bi.base.service.connection.ConnectionException: No connection possible to BI master system SAP_BW
     at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:71)
     at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:463)
     at com.sap.ip.bi.base.application.impl.Application.getProperty(Application.java:715)
     at com.sap.ip.bi.base.application.impl.Application.startApplicationStep(Application.java:283)
     at com.sap.ip.bi.base.application.impl.Application.initialization(Application.java:263)
     at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:172)
     at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:65)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.createApplication(Page.java:1029)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.constructPage(Page.java:911)
     at com.sap.ip.bi.webapplications.runtime.impl.Page.<init>(Page.java:750)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.createPage(Controller.java:547)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:919)
     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:816)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:328)
     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(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java: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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.ip.bi.base.service.connection.ConnectionException: No connection exists for system "SAP_BW"
     at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:206)
     at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:67)
     ... 46 more
Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mshost' missing
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
     at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)
     at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
     at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:429)
     at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.establishInitialConnection(SAPCFConnectorManagedConnection.java:204)
     at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:183)
     at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:129)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:267)
     at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:156)
     at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:295)
     at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:256)
     at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:446)
     at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:84)
     at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:170)
     ... 47 more
xt message error:
What can I do?

I fill the message server, and the error have changed, now it´s this:
The initial exception that caused the request to fail was: 
Connect to message server host failed
Connect_PM  TYPE=B MSHOST=host GROUP=PUBLIC R3NAME=SID MSSERV=3200 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       The message received isn't from a message server.
            Are you really connected to the message server?
            Please check your connection parameters.
            (host / 3200)
TIME        Wed Jan 28 10:16:35 2009
RELEASE     700
COMPONENT   MS (message handling interface, multithreaded)
VERSION     4
RC          -29
MODULE      msxxi.c
LINE        2543
COUNTER     1
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed
Connect_PM  TYPE=B MSHOST=host GROUP=PUBLIC R3NAME=SID MSSERV=3200 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       The message received isn't from a message server.
            Are you really connected to the message server?
            Please check your connection parameters.

Similar Messages

  • Error in GRC AC 5.3--ERM-mshost missing

    Dears,
    We are using SAP GRC 5.3 on AIX,Oracle 10g.
    In Enterprise Role Management,We are facing one issue:
    We created a role,Now we try to change it and try to add new tcode by option searching tcodes in Available system it shows error:
    "mshost missing"
    Please suggest,Where I need to maintain this setting.
    Regards,
    Shivam
    Edited by: Shivam Mittal on Nov 17, 2009 4:38 PM

    Hi Shivam,
    In the ERM>>COnfiguration>>system....have you maintained the MS server name???
    If NOt please maintain....
    Check for the test connection..
    Regards
    Gangadhar

  • (101) RFC_ERROR_PROGRAM: 'password' missing at com.sap.mw.jco.Middlewar

    All,
    I am trying to set up a simple demo about Payer direct with our 46C system. I have the R3 system defined in the system landscape. In user management, I have assigned UIDPW as logon method. I have maintained the User mapping where it is successfully saved but then when I go for the actual execution of the payer direct package, I get following error:
    com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:413) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:823) at com.sap.mw.jco.JCO$Client.connect(JCO.java:2922) at com.sapportals.portal.prt.service.jco.JCOClientService.getJCOClientPoolEntry(JCOClientService.java:1290) at com.sapportals.portal.prt.service.jco.JCOClientService.getJCOClientPoolEntry(JCOClientService.java:1059) at com.sap.pct.fin.suss.PortalJcoService.getClientFromPortalJCOService(PortalJcoService.java:71) at com.sap.pct.fin.suss.PortalJcoService.getFunctionFromPortalJCOService(PortalJcoService.java:85) at com.sap.pct.fin.suss.R3UserAccountService.getUserAccounts(R3UserAccountService.java:37) at com.sap.pct.fin.suss.PortalBusinessPartnerService.loadBusObjects(PortalBusinessPartnerService.java:150) at com.sap.pct.fin.suss.FrontController.createBillerDirectUser(FrontController.java:244) at com.sap.pct.fin.suss.FrontController.createNewModelManager(FrontController.java:207) at com.sap.pct.fin.suss.FrontController.prepare(FrontController.java:168) at com.sap.pct.fin.suss.FrontController.doContent(FrontController.java:94) 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.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377) at java.security.AccessController.doPrivileged(Native Method) at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390) at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729) at java.lang.Thread.run(Thread.java:534) .
    Exception id: 05:45_29/07/05_0026_3897050
    See the details for the exception ID in the log file
    Any help will be greatly appreciated.
    Regards,
    Abhijeet

    Hi Abhijeet,
    Can you tell us on what version of EP you are working?
    Did u try out other R/3 transaction codes using the same system. you can test in Sys Admin--> support --> SAP Application --> SAP Transaction for EP6 SP2 .Check to see whether you can access and have no error. For EP6 SP9, you can test connection after you create the system.
    there are few sAP notes with reference to EP5.0 on RFC_ERROR_PROGRAM - SAP note - 458082, 543870, 516636.
    Hope this helps,
    Thanks,
    Praveen
    PS.Dont forget to reward points for useful/solved answers

  • RFC_ERROR_PROGRAM: 'password' missing

    HI all,I had the ess/mss system on EP7.0,When I logon the system ,give me the error:
    The initial exception that caused the request to fail, was:
    com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
    at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
    at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:123)
    ... 72 more
    See full exception chain for details.
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException: failed to create provider: 'password' missing
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:449)
    at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:378)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:181)
    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:219)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1288)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
    at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:592)
    at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:864)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(AccessController.java:215)
    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.dictionary.runtime.DdException: failed to create provider: 'password' missing
    at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:254)
    at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
    at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
    at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
    ... 60 more
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:44)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:315)
    at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:229)
    ... 67 more
    Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
    at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
    at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:123)
    ... 72 more
    I check the sld and JCo Destination,it's all ok.
    who can help me?

    Hi Joecui,
    Refer this link [JCo Exceptions|http://help.sap.com/saphelp_erp2005/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm]
    With Regards,
    Laksh.

  • SSO Between EP  and R/3 6.4

    Hi,
    I am trying to implement SSO between SAP EP 6.0 and SAP R/3 6.4 using logon tickets.
    I've downloaded the .pse and .der files from Portal,uploaded the .pse in the backend system,added it to the ACL,but when i tried to test the connection in portal using system admin->system configuration->UM configuration->SAP system
    i am getting an error----
    (System ID): com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mshost' missing
    (System ID & System Number): com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=ctsgvcsap3 SYSNR=03 GWHOST=ctsgvcsap3 GWSERV=sapgw03 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service '?' unknown TIME Thu Feb 23 16:24:39 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 2
    Where am i going wrong?Please help.
    If anyone is having detailed documentation please forward the same.
    Thanks in advance
    SwarnaDeepika.
    Message was edited by: SwarnaDeepika

    Hi Swarna
    the procedure for importing portal certificate in r3 system i already mentioned
    u have a  authorization for strustsso2 on r3 system
    ask for that to basis person or done with their id
    after importing portal certificate into r3 system u have to restart the r3 system no need to restart the portal system
    and make sure for SSO  both portal and R3 system are in same domain.
    i.e
    sapr3.mydomain.com
    portal.mydomain.com
    if not u have to specify the DNS entry for that by creating alias.
    regards,
    kaushal

  • Error while changing UME data Source of EP.

    Hi All,
    I am trying to change the UM Congifuration for my EP.
    Currently EP is using ECC System as UME data source, Now I am trying to change it from ECC to SCM.
    For that I have done SSO between EP and SCM, also I have created SAPJSF id on SCM with roles
    SAP_BC_JSF_COMMUNICATION, SAP_BC_JSF_COMMUNICATION_RO, SAP_BC_USR_CUA_CLIENT_RFC and maintained same id on EP under Um Configuration- SAP System.
    After doing this while checking the test connection it is giving me following error.
    (System ID): com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mshost' missing
    (System ID & System Number): com.sap.mw.jco.JCO$Exception: (102)
    RFC_ERROR_COMMUNICATION: Connect from SAP gateway to RFC server failed
    Connect_PM TYPE=A ASHOST=mmscmsaptst SYSNR=00
    GWHOST=mmscmsaptst GWSERV=sapgw00 PCS=1
    LOCATION SAP-Gateway on host mmscmsaptst / sapgw00
    ERROR Return codes ( function=STIAsRcvFromGw / CPIC-RC=CM_PARAMETER_ERROR / SAP-RC=C_NIHOSTTOADDR )
    TIME Tue Sep 23 10:55:04 2008 RELEASE 640 COMPONENT CPIC (TCP/IP) with Unicode VERSION 3
    RC 772 MODULE r3cpic.c LINE 5079 COUNTER 2
    Pl help to resolve above issue.
    Thanks & Regards,
    Aditya

    Aditya,
    This RFC error is encountered when there is no message server host name in this file.
    C:/windows/system32/drivers/etc/services
    make an entry like this sapmsPBI     3600/tcp
    3600 is the port number , try to figure out the correct port number for SCM and update this.
    These changes are to be done on your Portal side.
    Good Luck.
    Sandeep Tudumu
    Edited by: Sandeep Tudumu on Sep 23, 2008 11:17 AM

  • UME using SAP R/3 as Data Source

    Hi,
    We are trying to set User authentication to SAP R/3 system, not load balanced system, on the User Management Configuration values: Client=501, Userid=sapjsf, Password=pwd, sys id=RS1, Group and Message server= blank, Application server= server.company.com, Sys. number=00, Max pool=10, Max wait=300000.
    When testing connection, I get this message:
    (System ID): com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mshost' missing
    (System ID & System Number): OK
    Is this an error? since our SAP R/3 is not a load balanced system.
    Did we miss any item for the setup, in dataSourceConfiguration_r3.xml? The SAPJSF "communication user" got the right sap role and authorizations.
    Portal version : EP6 SR1
    Regards
    Huzaifah

    Hi,
    If u want to Use The SAP R3 System as Data source u may
    do it from config tool if u got following message.
    WARNING! You are not allowed to select dataSourceConfiguration_r3.xml as active configuration file.
    (For Portal Patch less than SP13 u must download two data source file which is attached with note - 718383
    and upload it to portal which is described in the note)
    the following are the procedure which i apply ,
    Go to System Administration -> System Configuration ->UM  Configuration
    Now Do not change Data source from Here.
    Make sure  your data source is "Database Only"
    (dataSourceConfiguration_database_only.xml)
    Now enter the following value under SAP System Tab.
    Client : - Your sap system client
    User:-  Sap user
    password: - password
    System language:- your system language
    Application server: - Host name or IP of sap system
    System Number : -  SAP instance number
    Maximum Size of Connection Pool : -  As per req.
    Maximum Wait Time in Milliseconds :- 10000
    Now, save the changes and shutdown the portal server.
    Using Config Tool change the data source. Run the following
    <drive:\> usr\sap\<sid>\JC<instance number>\J2EE\configtool\configtool.bat
    (Make sure the portal system is shutdown)
    Under Cluster Data -> Global Server Configuration -> services -> com.sap.security.core.ume.services
    Now find the key: -  ume.persistence.data_source_configuration     
    The default was : - dataSourceConfiguration_database_only.xml
    change the value to :- dataSourceConfiguration_r3.xml     
    click on set and from flie-> apply
    Now restart the portal server ur data source changer to SAP R3 System
    Regards,
    Kaushal

  • RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets

    hello again,
    i manage to restart my server and applications
    but now when i try to start :
    http://host:port/b2b/b2b/init.do
    and i can't
    the logs show these line which i don't understand :
    1}#2#parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
    Properties: {lang=en, passwd=?, sysnr=01, client=300, user=$MYSAPSSO2$, ashost=192.168.1.14, jco.client.type=A, maxcon=0, jco.client.trace=1, codepage=1100}
    Client not connected#com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mysapsso2' missing
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
         at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:922)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3171)
         at com.sap.isa.core.eai.sp.jco.JCoConnectionStateless.getInternalJCoClient(JCoConnectionStateless.java:118)
         at com.sap.isa.core.eai.sp.jco.JCoConnectionStateless.isValid(JCoConnectionStateless.java:479)
         at com.sap.isa.user.backend.crm.IsaUserBaseCRM.loginViaTicket(IsaUserBaseCRM.java:1677)
         at com.sap.isa.user.backend.crm.IsaUserBaseCRM.loginForBPRole(IsaUserBaseCRM.java:127)
         at com.sap.isa.user.backend.crm.UserBaseCRM.login(UserBaseCRM.java:248)
         at com.sap.isa.user.businessobject.UserBase.login(UserBase.java:308)
    #1.5#000423A6E1B400640000002E0000169C00041D66DC92778B#1158227531375#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_17##0#0#Debug##Plain###[actionxecution]='end' [actionclass]='com.sap.isa.user.action.LoginBaseAction' [path]='/login' [forward]='/base/error_ume.jsp' [exectime]='32'#
    #1.5#000423A6E1B400480000000F0000169C00041D66DCE4AE38#1158227536750#tracing.advisor.method#sap.com/crm~b2b#tracing.advisor.method#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###AdvisorBusinessObjectManager:<constructor>#
    #1.5#000423A6E1B40048000000120000169C00041D66DCE4B676#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='begin' [actionclass]='com.sap.isa.isacore.action.IsaCoreInitAction' [path]='/b2b/coreinit'#
    #1.5#000423A6E1B40048000000130000169C00041D66DCE4C261#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='end' [actionclass]='com.sap.isa.isacore.action.IsaCoreInitAction' [path]='/b2b/coreinit' [forward]='/user/performLogin.do' [exectime]='0'#
    #1.5#000423A6E1B40048000000140000169C00041D66DCE4C607#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='begin' [actionclass]='com.sap.isa.core.action.SetReloginCookieAction' [path]='/relogin/setcookie'#
    #1.5#000423A6E1B4004800000
    many thnx if you can help me

    it doesn't work ..
    i need to understand the meaning of SSO ticket in  sap logon..
    i still have the error :
    parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
    Properties: <u>{lang=en, passwd=?, sysnr=01, client=300, user=$MYSAPSSO2$, ashost=192.168.1.14, jco.client.type=A, maxcon=0, jco.client.trace=1, codepage=1100}</u>Client not connected#com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mysapsso2' missing
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
    why does it replace the user i mapped in XCM JCO setting with the user 'mysapsso2' ?
    plz help me

  • SSO (SNC) for BEx applications

    In our testing environment, we use SSO(SNC) through the SAP GUI for Windows to access our backend systems:
    *SSO file gx64ntlm on the server side
    *SSO file sncgss32.dll on the client side
    *User mapping (SNC tab) mapped to active directory user
    and everything works fine.
    However, when launch BEx Analyzer, Query Designer, etc, we get the following error when accessing the SSO logon options in the SAP Logon Control tool:
    Error Group
    RFC_ERROR_PROGRAM
    Message
    Missing SNC_LIB=... in connect_param in RfcOpenEx
    How does the logon control need to be configured in order to connect to the backend system via SSO?

    Almost there....AFter that setting, I get the following:
    Error Group
    RFC_ERROR_COMMUNICATION
    Message
    SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
    Connect_PM  GWHOST=xxx.xx.x.xxx, GWSERV=sapgw00s, SYSNR=00
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner xxx.xx.x.xxx:4800' not reached
    TIME        Thu Jan 15 14:42:56 2009
    RELEASE     710
    COMPONENT   NI (network interface)
    VERSION     39
    RC          -10
    MODULE      nixxi.cpp
    LINE        3139
    DETAIL      NiPConnect2: xxx.xx.x.xxx:4800
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     2
    SNC is set to accept insecure RFC (value =1)...

  • Error while deploying my application

    Hi,
    I am getting the following error while deploying my application.
    com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
        at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
        at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
        at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
        at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:319)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    Thanks ,
    nadh

    Hi Nadh,
    This is the code to execute RFCst
    Z_Notification_Create_Input input = new Z_Notification_Create_Input();
    wdContext.nodeZ_Notification_Create_Input().bind(input);
    wdContext.currentZ_Notification_Create_InputElement().modelObject().addFlines(longText);
    wdContext.currentZ_Notification_Create_InputElement().modelObject().execute();
    Best regards,
    Chinnu

  • Error while Role Upload

    Hello,
    We have Enterprise Portal connected to the Backend SRM System and while trying to do a Role Upload from SRM to Portal ,I get the following error as below:
    com.sap.portal.pcd.rolemigration.RoleMigrationConnectionException: Connection Failed: Nested Exception. Physical connection was not initialized. - message at com.sap.portal.pcd.rolemigration.util.Connector.callFunction(System,en,userid,TWPN_GET_URL,SERVICE_TABLE,{ENABLE_LOGGING= , ROLENAME=<Rolename>OBJECT_ID=00000102}): Connection not available for system ''Connection Failed: Nested Exception. Physical connection was not initialized. at com.sap.portal.pcd.rolemigration.util.Connector.callFunction(Connector.java:114) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1328) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.doDependentObjects(RoleMigrationObject.java:4974) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:4734) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:4303) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1497) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:686) at com.sap.portal.pcd.rolemigration.RoleMigrationThread.run(RoleMigrationThread.java:525) Original exception: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: Nested Exception. Physical connection was not initialized. at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedException(SAPConnectorException.java:107) at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:133) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:371) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:262) at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:156) at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:295) at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:256) at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:446) at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:84) at com.sap.portal.pcd.rolemigration.util.Connector.callFunction(Connector.java:79) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1328) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.doDependentObjects(RoleMigrationObject.java:4974) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:4734) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.save(RoleMigrationObject.java:4303) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1497) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:686) at com.sap.portal.pcd.rolemigration.RoleMigrationThread.run(RoleMigrationThread.java:525) Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: Nested Exception. Failed in creating the JCO Connection. at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedException(SAPConnectorException.java:107) at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:456) at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.establishInitialConnection(SAPCFConnectorManagedConnection.java:204) at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:183) at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:129) ... 15 more Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3296) at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:429) ... 18 more
    Any help would be highly Appreciated.
    Thanks

    Hi,
    Please check the SRM system object connection in the SAP Portal. GO to system administration > system configuration > system landscape and search for SRM system object and test the connection. If connection test successful then try to upload the roles.
    Hope it will helps
    Best Regards
    Arun Jaiswal

  • I have error while testing the system created from a sap business objects template in SAP portal

    I have error while testing the system created from a sap business objects template in SAP portal. Error text:
    com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not initialize physical connection. Connection Failed: A nested exception occurred. Could not create JCO connection. 'mshost' missing
    I configure integration SAP portal and SAP BW system. All system requirements are complied.
    Environment
    SAP Business Objects 4.0
    SAP BW 7.31
    1.     I configure SSSO between SAP BW and SAP Business Objects Enterprise 4.0
    2.     Next I setting integration SAP PORTAL with SAP BW system
    3.     I download certificate from portal. Select Certificates and key (http://sapserver:port/nwa) – See scren_
    4.     In next window selected Ticketkeystore and Saplogonticketpair-cert( near part window form)
    5. Select Export entry button and binary format file certificate for download. Press download.
    6.     Save certificate file in local PC folder
    In next step need export certificate file to SAP system. Sequence of step:
    1.       Run STRUSTSS02 transaction .
    2.       Chose certificate ->import.
    3.       Select downloaded certificate file
    4.       Select Add to certificate list button and Add to ACL button
    5.       Inter System ID and Client(000)
    6.       In next I download iview sap business objects template into sap portal: System administration->transport->Import. And select and download sap business Objects iview template in .epa format into sap portal.
    7.       Result – downloaded iview.
    8.       In next step I create system from template. System administration->system landscape.
    9. In next step I input parameters for my system in Connector category, Sap business objects and user management categories: See screen _2
    10.   When I created the system and test the connection error occurred: See screen_3
    This issue is important enough. I would be grateful for opinions and ideas. Thanks in advance.

    Did you find a solution?

  • Error while setting up BI and EP

    Hi
    I have followed the 12 steps to configure BI and EP as described in this doc:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a
    I then run into some errors so I loaded the SAP NetWeaver BI Diagnostics & Support Desk Tool.
    I followed on some of the errors and managed to solve most.
    But I still have 4 errors left:
    BI Mastersystem
    Deployed Components
    Registered RFC listeners
    Webdynpro JCO Destinations
    See the details errors below.
    Thanks
    Edan
    BI Mastersystem
    Error while connecting to BI mastersystem via RFC: com.sap.mw.jco.JCO$Exception:'mshost' missing Check connection properties in Portal Systemlandscape for the property category 'Connector' (BID)
    Deployed Components
    The required SCA 'BI-BASE-S' is not deployed Make sure the usage types AS Java, EP and BI-Java are deployed on your system -
      RED
    The required SCA 'BI-IBC' is not deployed Make sure the usage types AS Java, EP and BI-Java are deployed on your system -
      RED
    The required SCA 'BI-REPPLAN' is not deployed Make sure the usage types AS Java, EP and BI-Java are deployed on your system -
      RED
    The required SCA 'BIWEBAPP' is not deployed Make sure the usage types AS Java, EP and BI-Java are deployed on your system
    Registered RFC listeners
    No RFC listener registered for function module BICS_CONS_GET_VIEW_DEF_J_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSDAS_X_PROV_DESCRIBE_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSDAS_X_PROV_OBJECT_DET_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSDAS_X_PROV_PROCESS_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSOBJS_GET_PORTAL_VIEWS_RFC Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSOD_MIGRATE_DOCUMENT_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSPOR_NODES_READ Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSPOR_NODES_SAVE Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSPOR_PORTAL_CALL Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSPOR_SHORT_TO_URL_CONVERT Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSPOR_URL_TO_SHORT_CONVERT Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_BROADCASTING_KM_RFC Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_FOLDER_WRITABLE Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_GET_PORTAL_USERS Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_MAP_TO_PORTAL_USERS Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_STORE_ONLINE_LINK Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_X_DISTRIBUTE_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_X_GET_INFO_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_X_GET_PORTAL_INFO_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_X_MAP_TO_PRTL_USERS_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSRD_X_PRODUCE_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_ABAP_EXCEPTION_TEST Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_BINARY_CONTENT_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_CACHE_INVALIDATE_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_CLUSTER_INFO_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_FOLDER_CONTENT_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_JAVA_VERSION_INFO_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_LOGGER_CONFIG_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_LOGGER_CONFIG_SET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_PREEXECUTION_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_RFC_SERVICE_LISTENERS_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_RFC_SERVICE_TEST Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_RFC_VERSION_INFO_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_ROOT_FOLDER_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_SAP_ROOT_FOLDER_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_SERVICE_DISPATCHER_TEST Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_STRING_CONTENT_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_SYSTEM_ALIAS_CHECK_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_TEMPLATE_PROCESS_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_TIME_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_URL_QUERY_COMPRESS_PROXY Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module RSWR_ZIP_STREAM_GET Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
      RED
    No RFC listener registered for function module SALV_WD_EXPORT_PDF Check that the J2EE rfc service (com.sap.portal.runtime.application.rfcengine.RFCEngine) is running. Check that all necessary BI archives are deployed. -
    Webdynpro JCO Destinations
    Webdynpro JCO destination WD_ALV_METADATA_DEST does not exist.  Planning modeller will not work. Create the destination.See J2EE start page->web dynpro tools->content administrator->maintain jco destinations -
      RED
    Webdynpro JCO destination WD_ALV_MODELDATA_DEST does not exist.  Planning modeller will not work. Create the destination.See J2EE start page->web dynpro tools->content administrator->maintain jco destinations -
      RED
    Webdynpro JCO destination BI_METADATA does not exist.  Planning modeller will not work. Create the destination.See J2EE start page->web dynpro tools->content administrator->maintain jco destinations -
      RED
    Webdynpro JCO destination BI_MODELDATA does not exist.  Planning modeller will not work. Create the destination.See J2EE start page->web dynpro tools->content administrator->maintain jco destinations

    Hi
    First of all, try to login the support desktop tool with a user that have administrative rights.
    And regarding errors, I faced the same issues.
    BI Mastersystem
    -check master system is assigned to the system you want to connect.
    Deployed Components
    -deploy components that are asked and reload configuration
    Registered RFC listeners
    -Restart the Java server. That would resolve the error.
    Webdynpro JCO Destinations
    -Make sure that your JCO rfcs are working fine.
    Thanks,
    Rathnakar.

  • Problem Create System Object in the Portal for connecting CRM abap

    Hi, i creating system in the portal (JCX) for connecting system ABAP CRM (CRX), after create system try run test connection and show messages error:
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    In the logs the portal (NWA) show messages:
    Failed in creating the JCO Connection.
    The logs operation system (log Security_audit.log)
    Error> occured  >Thu Jun 23 11:34:41,278<RfcException: message: 'mshost' missing  Return code: RFC_INVALID_PARAMETER(19  Return code: RFC_INVALID_PARAMETER(19)    error group: 101 key: FC_ERROR_PROGRAM
         at com.sap.mw.rfc.api.RfcOptions.checkParameters(RfcOptions.java:438)
         at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:688)
         at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1079)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3256)
    Plase help, any idea?

    message: 'mshost' missing Return
    During the System Object Creating in System Landscape, there is any entry as Message Server Host: CRM MS HOST
    and Message Server Port : sapmsSID and add this entry in etc/services --> bottom samsSID 36NN/tcp where NN is instance number.
    Try this and let me know.
    Thanks
    SM

  • Error when create connection in Xcelcius 2008 SP3 to BW EHP 1 SPS 6

    Dear All,
    Last week there is no problem in this connection, buat since today this error happen.
    We found error when trying to connect Xcelcius and and BW,below the error:
    com.sap.ip.bi.bics.remote.impl.rmi.ApplicationCreationException: Could not to create the application. This is probably due to a misconfigured Abap/Java connection.
    at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.getApplication(AbstractConnectionContext.java:195)
    at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.createBicsRemoteMessageProducer(AbstractConnectionContext.java:387)
    at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.getMessageProducer(AbstractConnectionContext.java:209)
    at com.sap.ip.bi.bics.remote.BicsRemoteImpl.getDesignTimeInfo(BicsRemoteImpl.java:156)
    at com.sap.ip.bi.bics.remote.BicsRemoteBean.getDesignTimeInfo(BicsRemoteBean.java:109)
    at com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(BicsRemoteObjectImpl0_0.java:379)
    at com.sap.ip.bi.bics.remote.BicsRemote_Stub.getDesignTimeInfo(BicsRemote_Stub.java:328)
    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:331)
    at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
    at SoapServlet.doPost(SoapServlet.java:51)
    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.ip.bi.base.service.connection.ConnectionException: No connection possible to BI master system BD1CLNT500
    at com.sap.ip.bi.base.portal.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:71)
    at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:568)
    at com.sap.ip.bi.base.application.impl.Application.getMasterSystemService(Application.java:1027)
    at com.sap.ip.bi.base.application.impl.Application.getProperty(Application.java:829)
    at com.sap.ip.bi.base.application.impl.Application.startApplicationStep(Application.java:346)
    at com.sap.ip.bi.base.application.impl.Application.initialization(Application.java:326)
    at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:63)
    at com.sap.ip.bi.bics.remote.impl.rmi.cc.ConnectionContextStateless.createApplication(ConnectionContextStateless.java:72)
    at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.getApplication(AbstractConnectionContext.java:172)
    ... 31 more
    Caused by: com.sap.ip.bi.base.service.connection.ConnectionException: No connection exists for system "BD1CLNT500"
    at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:206)
    at com.sap.ip.bi.base.portal.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:67)
    ... 39 more
    Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086)
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3256)
    at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:429)
    at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.establishInitialConnection(SAPCFConnectorManagedConnection.java:204)
    at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:183)
    at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:129)
    at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
    at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:262)
    at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:156)
    at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:295)
    at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:256)
    at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:446)
    at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:84)
    at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:170)
    Please your help and solution on this,
    Thanks and Best Regards,
    Widi

    Hi Mustafa,
    Yes, we are able to resolve the issue.
    This issue happen because we change the configuration in
    System Admin -> System Configuration -> Portal Content -> Systemlandscape -> (your system landscape)
    - Display = Object
    - Property Category = User Management
    - Authentication Ticket Type = SAP Assertion  TIcket
    - Logon Method = SAPLOGONTICKET
    - User Mapping type = admin,user
    After we change this configuration, our we can connect with our Xcelcius to SAP BW.
    Please kindly check your User Management configuration.
    Regards,
    Widi

Maybe you are looking for