MSS Iview problem

Hi,
I'm getting this 'No data available' message in the Attendance Overview iview even though the data is maintained in R/3. i'm using MSS 60.1.3
Any ideas?
Regards,
Raj

Is this the only iview this is happening on?  I had simular problems but it was related to having chief access and 105 in R/3.  Verify you have the HR system set up with an allias SAP_R3_HumanResources under System Administration/System Configuration/Systems (you have probably already done this but double check).  Also if you aren't using single sign on or something like that make sure you have usermapping under personalization set up for SAP_R3_HumanResources.
I know these are the basics and you have probably gone over this already.  But it has been the little stuff that has bit me every time.
Roy Richardson

Similar Messages

  • MSS Iview Problem -Any  Experts help please

    I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
    My System landscape :
    MSS BP Installed: BPMSS601_19-20001489
    R3- 4.6C
    Portal : EP6 Sp11
    WAS: 6.40
    ITS -  Standalone ( Not integrated)
    when i test  my System object  for ITS  ,it  is  working  fine , but  it  is  failed   for WAS Connection and Connector  test
    Any help will be highly appreciated.

    Hi Umair,
    Thanks for your  response, i am getting same  error  for all  iviews.I  pointed  that there  is  some problem with my System object, i tried to test connection for the  "Connection Test for Connectors" i am getting following  error.But Connection test is success  for the "ITS Connection"
    com.sap.mw.jco.JCO$Exceptionoccured->Connect to SAP gateway failed Connect_PM  TYPE=A ASHOST=XXXX SYSNR=00 GWHOST=XXXX GWSERV=sapgw00 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service '?' unknown TIME        Wed Aug 30 16:42:35 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 COUNTER     11
    my understand is , ESS  is  working  fine  for me because ,ESS  iviews  are IAC's  based  iviews  which  are running on ITS(ITS connection is  working fine for me),
    i think some  problem with connectors(jco).....could you please   suggest me.
    Thanks
    Aravinda

  • NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews

    We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
    ECC5.0
    Abap Stack
    EP6 SP13
    Java Stack
    latest versions of MSS and ESS BPs
    The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
    With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
    Any help on this will be greatly appreciated.
    Thanks in advance.
    Regards, Neeta

    Hi,
    Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
    http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
    The error message I get is (rather long....):
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
        ... 53 more
    See full exception chain for details.
    Correction Hints
    Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
    Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
    Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    Version 
    DOM version 
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
    J2EE Engine 6.40 patchlevel 95420.313
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system SunOS, version: 5.10, architecture: sparcv9
    Other
    Session Locale en_US
    Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwddispwda
    No information available
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwdcorecomp
    No information available
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         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)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         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:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         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:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 50 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
         ... 53 more
    Thanks, Neeta

  • MSS Iview error - Any  body  help me - Very urgent

    Hello All,
    I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
    My System landscape :
    MSS BP Installed: BPMSS601_19-20001489
    R3- 4.6C
    Portal : EP6 Sp11
    WAS: 6.40
    Any help will be highly appreciated.

    Hello All,
    I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
    My System landscape :
    MSS BP Installed: BPMSS601_19-20001489
    R3- 4.6C
    Portal : EP6 Sp11
    WAS: 6.40
    Any help will be highly appreciated.

  • Error in the Standard MSS iview?

    Hi,
    I am using "startprocess" mss iview from Content Provided By Sap,when click on preview it shows bellow error.But same iview is working in my Development System.
    Error
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name mss~hras
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
        at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
        at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)
        ... 40 more
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:528)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
         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:756)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: javax.naming.NamingException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name msshras [Root exception is com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name msshras]
         at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:51)
         at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:919)
         at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:692)
         at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:69)
         at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:526)
         ... 31 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name mss~hras
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
         at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
         at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)
         at com.sapportals.portal.prt.jndisupport.DirectoryManager.getObjectInstance(DirectoryManager.java:56)
         at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:47)
         ... 38 more
    Please guide me to solve the problem
    Thanks
    Srikanth

    No child found in WebDynproContext with name "mss~hras  "
    check the code where you define that.
    see the thhread below which is similar issue
    Description attribute of PCD element
    Points are welcome if it is helpful
    Koti Reddy

  • MSS iView Errors

    Hi all.  We're getting a Portal Runtime error in our production environment when trying to view certain MSS iviews, such as Absence Days, Personal Data, Detail View Attendances, Company Properties, Emergency Contact, etc.
    The error looks something like,
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 09:28_02/04/09_0155_2490650
    Refer to the log file for details about this exception.
    The error log gives such clues as:
    EXCEPTION
    #1#com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): com.sap.portal.system/security/com.sap.portal.ep50/ep50_safety)
    ErrorPage: com.sapportals.portal.prt.runtime.PortalRuntimeException: Access is denied: com.sap.pct.hcm.orgmanagementeventing.redirect
    EXCEPTION
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/state.la.portal.folder.global.State/state.la.portal.folder.EP5Development/state.la.portal.folder.roles/Z_PORTAL_LEOMSS/LEO_MSS/nf/state.la.portal.
       workset.attendance/state.la.portal.page.mss.absenseDetail/com.sap.pct.hcm.eeprofileabsencedays_0
    Component class : com.sap.pct.hcm.employeeprofile.absencedays.AbsenceDaysComponent
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Access is denied: com.sap.pct.hcm.hcm_util.error_page
    Caused by: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): com.sap.portal.system/security/com.sap.portal.ep50/ep50_safety
    All MSS iViews, working and not working, are inheriting from the same top level folder.  In their permissions is the Everyone group (Administrator=none, End User=checked) and the super_adminstrator_role (Administrator=owner, End User=checked).
    Any ideas on what our problem is?
    Edited by: Adam Tidwell on Apr 2, 2009 4:38 PM
    Edited by: Adam Tidwell on Apr 2, 2009 4:39 PM
    Edited by: Adam Tidwell on Apr 2, 2009 4:43 PM
    Edited by: Adam Tidwell on Apr 2, 2009 4:44 PM
    Edited by: Adam Tidwell on Apr 2, 2009 4:45 PM

    You need to check the permissions of that MSS Iview
    Go to the path  System Administration>Permisssions,
    Go to  "pcd:portal_content/com.sap.pct/srvconfig"
    Check whether you have valid permission or not.
    Also check the below thread that will help you.
    Re: Portal Runtime error
    PermissionControlException: Access denied
    Raghu
    Edited by: Raghavendranath Garlapati on Apr 2, 2009 4:52 PM

  • MSS Iview error -Could not connect to the R/3 System

    Hello All,
    I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
    My System landscape :
    MSS BP Installed: BPMSS601_19-20001489
    R3-  4.6C
    Portal : EP6 Sp11
    WAS: 6.40
    Any help will be highly appreciated.

    Hi Mahesh,
    Thanks for your repley, I am  using  the "SAP_R3_HumanResources" as a  default alias, The same  alias is  working fine  for my ESS  Configuration.
    I tried to test connection for the "Connection Test for Connectors" i am getting following error.But Connection test is success for the "ITS Connection"
    com.sap.mw.jco.JCO$Exceptionoccured->Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=XXXX SYSNR=00 GWHOST=XXXX GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service '?' unknown TIME Wed Aug 30 16:42:35 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 11
    my understand is , ESS is working fine for me because ,ESS iviews are IAC's based iviews which are running on ITS(ITS connection is working fine for me),
    i think some problem with connectors(jco).....could you please suggest me.
    Thanks
    Aravinda

  • No preview button or option for all ESS MSS iViews under portal content

    Hi All,
                We are doing a green field implementation for one of our clients, we have installed ECC 6.0 with EHP5 in R/3 system and SAP Netweaver Portal 7.02 with SP8. We have also deployed suitable ESS MSS business components from service market place.
    BP_ERP5ESS 1.41
    BPERPESSWDA  1.50
    BP_ERP5MSS 1.51
    As it is EHP5 in ECC all the Homepage framework, Areas, Sub areas, services are preconfigured for standard ESS MSS business areas.
    In Portal side under Portal content - Content Provided by SAP - End User Content - Employee Self Services -
    we are not able to preview any of the iViews. can anyone suggest whether what may be wrong...?

    Hi Sandeep,
    1. Yes we are accessing portal through FQDN
    2. IE 6.0
    3. I mentioned above, its SAP Netweaver 7.02 with SP8
    4. Yes, the user I am using has Super Administrator role
    5. There are roles for ESS in ECC 
    This problem of preview is for other iViews also. I mean other than ESS MSS iViews.
    Thanks,
    Kalam.

  • Empty MSS  iView

    Hi all,
    We are currently implementing portal project with EP7.0 (ESS Business package 50.4 and MSS Business package 60.1) connect to R/3 4.6c. The ESS iview and customised WDA iview are working fine without any problem. However, we stuck with the problem that the standard MSS iview display empty.
    Based on our understanding, this could be the issue that we are lack of EA and PI plugin in R/3. However, it seems that the EA and PI plugin are only available for 4.7 but not 4.6c.
    1) Any idea what could be causing the empty MSS iview?
    2) If R/3 plugin indeed is the issue, any idea what plugin should we use for 4.6c? 
    Appreciate for any feedback or idea!
    Thanks

    Is the iView empty when you preview it?  I had this problem and then assigned the iview to a role so it loaded when a user logged on and it worked.

  • Portal Runtime Error  for MSS Iviews

    Hi all,
    Though this topis has been discussed several times in our forum, i could not make anything from it.
    Portal Runtime Error
    <i>
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.ssmcehr.ssmcehr/com.ssmc.pct.ehr.mss.folder.mss/com.ssmc.pct.ehr.mss.folder.roles/com.ssmc.pct.ehr.mss.role.mss_mgrs/com.ssmc.pct.ehr.mss.workset.manager_self_service/manager_self_service/com.ssmc.pct.ehr.mss.worksets.employee_information/com.ssmc.pct.ehr.mss.page.employee_career/com.ssmc.pct.ehr.mss.iview.pay_actions
    Component Name : com.sap.pct.hcm.eeprofilegenericiviewtable.default
    The exception was logged. Inform your system administrator..
    Exception id: 09:51_08/12/06_0067_101532150
    See the details for the exception ID in the log file
    <i>
    <b>and  the error log file ...</b>
    <i>
    #1.5#00142216FF7C00640000003F000022F80004240E23838D08#1165543050906#com.sap.security#sap.com/irj#com.sap.security.logToFile#Guest#19####76b39fa0865f11db815c00142216ff7c#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Security/Audit#Plain###Guest | LOGIN.ERROR | NONE = null | | Login Method=[default], UserID=[jothi], IP Address=[137.55.161.180], Reason=[Access Denied.]#
    #1.5#00142216FF7C006100000031000022F80004240E23BE4303#1165543054765#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#Guest#19####790075d0865f11dba82400142216ff7c#SAPEngine_Application_Thread[impl:3]<b>_15##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##</b>
    <i>
    This occurs only for the LDAP users,if we create user in EP(manually) it's working fine..
    Thanks in Advance,
    Jothi.P

    It got resolved by itself after restarting the Java server.

  • Java.lang.NullPointerException in MSS iviews

    Hi,
    Can any one tell me the reasons for getting the below error? Only one user is getting this error while viewing all MSS Iviews.
    <b>Error:</b> java.lang.NullPointerException
    <b>Log Overview:</b>
    PortalComponentSession.putValue() failed
    [EXCEPTION]
    java.lang.NullPointerException
            at java.util.Hashtable.put(Hashtable.java(Compiled Code))
            at com.sapportals.portal.prt.component.PortalComponentSession.putValue(PortalComponentSession.java(Compiled Code))
            at com.sap.pct.hcm.employeeprofile.genericiviewtable.GenericIviewTablePage.beforePdvExecuteSource(GenericIviewTablePage.java:55)
            at com.sapportals.pct.util.pdv.PDVJspDynPage.doProcessBeforeOutput(PDVJspDynPage.java:128)
            at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java(Compiled Code))
            at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java(Compiled Code))
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java(Compiled Code))
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java(Compiled Code))
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java(Compiled Code))
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code))
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code))
            at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java(Compiled Code))
            at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java(Compiled Code))
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java(Compiled Code))
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code))
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java(Compiled Code))
            at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java(Compiled Code))
            at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java(Compiled Code))
            at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java(Compiled Code))
            at java.security.AccessController.doPrivileged1(Native Method)
            at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
            at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java(Compiled Code))
            at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
            at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java(Compiled Code))
            at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
            at java.security.AccessController.doPrivileged1(Native Method)
            at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    <b>Default trace:</b>
    #1.5#000255AF6E28002F00000526000C20B0000420A586EC226E#1161795212157#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#usera1#513560####58b79ca0644911dba4c5000255af6e28#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#/System/Server#Plain##
    #ErrorPage: java.lang.NullPointerException#
    #1.5#000255AF6E28001900000547000C20B0000420A586FDA259#1161795213304#System.err#sap.com/irj#System.err#usera1#513557##ri3023_UWP_108418750#usera1#585d6eb0644911dba163000255af6e28#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###     at com.sap.pct.hcm.teamviewer.TeamViewerPage.getJSCodeCheckCookie(TeamViewerPage.java(Compiled Code))#
    Thanks in Advance,
    Swapna.

    Hi ,
    One thing i can say is the Null Pointer Exceptin when ther is no value in the field which has been submiited .The code shd be written in the try and catch block so that u can know hwat is the error all about .
    just check in the Ui which u have made is the user having data reated to that .
    pls awrd pts if useful

  • JCo error while viewing MSS iviews

    Dear SDN Community,
       When I am trying to view any of the MSS iViews like photo, orgchart, personal data, I get the following error message.
      com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=sapdev GROUP=ED0LG R3NAME=ED0 MSSERV=sapmsED0 PCS=1 ERROR service 'sapmsED0' unknown TIME Fri Aug 03 11:59:07 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 4
    The JCo connections SAP_R3_HumanResources and SAP_R3_HumanResources_Metadata are tested successfully and I see the gree light for these 2 in the WebDynpro console.
    Can you please advice me here.
    Thanks,
    Vivek.

    Vivek,
    open the services file of your portal server box. This file will be in the location C:\WINDOWS or WINNT\system32\drivers\etc folder. In that enter an entry as below:
    sapmsED0   36XX/tcp
    where XX is the system no of your R/3 system. So if R/3 system number is 30 the line would be sapmsED0  3630/tcp.
    Save the file and then try accessing iView again. This error message would be going off.
    Regards,
    Shubhadip

  • Date seperator in MSS iViews

    hi all
    We have a requirement to change the format of date in MSS iViews from mm/dd/yyyy to mm.dd.yyyy. How can we achieve this in portal? Kindly advise.
    with thanks
    amit

    hi paul
    thanks a lot for the response...the note u have provided talks about changes specific toa country, but in my case the requirement is a bit more specific. we need to change the format to strictly dd.mm.yyyy
    i did not get from the note how do we achieve it. can u please elaborate on it???
    amit

  • Date Format in MSS iviews

    Hi,
    We have EP6 SP11 with the Manager Self Service Business Package. The dates on our MSS iviews are currently showing as MM/DD/YYYY. I have set the default country of the portal to GB but the language setting in the user profile is overriding this. If I set the language to "English (United Kingdom)" the date shows correctly as DD/MM/YYYY. But if I just set it to "English", the dates show as MM/DD/YYYY.
    However, we are using an R/3 system as our user store, so the language setting is coming from there (SU01 > Communication section) and there is no option for "English (United Kingdom)", only "English". How can I change the "English" option to default to en_gb rather than en_us? Or can I map the English setting in R/3 to English (United Kingdom) setting in the portal? Or is there something else I can do?
    Any help greatly appreciated!
    Thanks in advance,
    Jane

    Hi Jane,
    Try to change the language settings of the Internet Explorer and see if it is not being over-ridden from the user profile.
    Regards,
    Mohan

  • MSS iView Personalization

    Friends,
    We are not able to do Implicit Personalization for MSS iViews/Pages .When we open the iView in preview mode and set the property of a field to invisble mode then  click apply and OK the filed gets hidded.But when we open or refresh that iView the field appears again in that iview.So please help in resolving this issue.We are using EP7.0 SP09 with MSS BP1.0 and Self service components 600 SP09.
    Regards,
    Arun

    Arun,
    Although this is a portal related question,I suggest you to check whether the user which is used for personalisation has end user and super admin or not .
    Please post the questions in relevant forums
    Thanks
    Bala Duvvuri

Maybe you are looking for