Error in Webdynpro deployment in Portal

Dear All,
I have created one model in VC and compiled it using webdynpro compiler. I have deployed in it portal. when i view this iveiw in portal, it shows it is not an webdynpro object. What could be the problem? can any one help me it resolve this error?
Should i create any JCo for the R/3 communication in VC?
With Regards,
Balachander

Hi Balachander,
  If you want communicate with R/3 in VC you need to create the portal system so that you can able to access BAPI's or RFC's
/people/marcel.salein/blog/2007/03/14/how-to-create-a-portal-system-for-using-it-in-visual-composer
Above link will helpout you, for creating the portal system.
Regards
Srikanth

Similar Messages

  • Error in WebDynPro Iview in portal.

    Hello All,
    I have to create WebDynPro ABAB Iview to display the Application created in the same.
    I have followed this Blog
    Creating WD-ABAP iView and the WD Namespace
    and steps taken are.
    1) Created System with R/3 Credentials and System is Up and running.
    System Name:: CoP
    System_Aliase:: CoP_Aliase
    2) Now i have created one WebDynPro Iview and on the Application Parameter Page which is in the wizard of Iview creation i have done thease entries.
    System:: Cop_Aliase
    Namespace:: sap
    Application Name ZRAH_TUTORIAL2
    and created Iview now When i see Preview of this Iview am getting this Error.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Application URL ':///sap/bc/webdynpro/sap/ZRAH_TUTORIAL2/;sap-ext-sid=CiOljEJTkrTNS5ZSeEZtwA%3D%3DY3EU8GM3SofqGxk%2B6%2BWHWg%3D%3D' is not valid! Please check the protocol and host entries for system 'CoP_Aliase'..
    See the details for the exception ID in the log file
    What can be the cause of it and how can i get rid of it.
    Any help  will be highly Appretiated and will be rewarded for sure.
    Thanks and Regards.
    Vinit

    Hi Vinit,
    It seems that there should have been issue with the connection from portal to your ECC system.
    Can you please close the thread and also post the solution so that it is useful for others.
    Regards
    Mukesh

  • Error - while deploying to Portal

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

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

  • Error Deploying Sample Portal from Development Guide

    I am going through creating a New Portal from WebLogic Portal 7 Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot Deploy the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.

    That's great, Mike, you're welcome. I'm glad it's working for you. Thanks for letting me know.
    -Scott
    Mike Friesen wrote:
    I'm sorry you were right.. I tried it and everything works... thanks..
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I hear what you are saying and I believe you. But the error you describedis the known issue related to Internet access
    (down to the exact line numbers in the stack trace). Is it possible yourconnection was down last time you attempted
    hot-deploy?
    If you are sure your Internet connection is up, I would recommend tryinghot-deploy again. If it still does not work,
    something very strange is going on. At that point I would recommendtrying the workaround anyway or escalating the issue
    to BEA Support.
    Now my curiosity is piqued so I hope you'll let me know either way.
    Best Regards,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    yes..
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Can you please try something for me? Paste the following URL into abrowser:
    http://java.sun.com/dtd/application_1_3.dtd
    Does it come up?
    Thanks,
    Scott
    Mike Friesen wrote:
    Actually, my computer does have internet access, so I don't think that
    is
    the problem.
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I would bet that you are working on a machine that doesn't have
    Internet
    access, correct?
    The problem is that the EBCC is trying and failing to access the J2EEapplication descriptor
    dtd from Sun's website.
    If you can't get Internet access, here is the workaround:
    - save the attached file to your harddrive (just save it to c:\)
    - edit the application.xml file for your project as follows:
    - first copy the entire DOCTYPE declaration and save it somewhere
    in
    a
    separate text file (in case want to revert back to it later)
    - edit the DOCTYPE declaration so that it looks like this:
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN' 'file:///application_1_3.dtd'>
    ( notice that the java.sun.com web address is replaced with the URI
    to
    the file on your harddrive)
    - save your changes and hotdeploy will work with or without Internetaccess
    Thanks,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    I am going through creating a New Portal from WebLogic Portal 7
    Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot
    Deploy
    the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.
    <!--
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, U.S.A.
    All rights reserved.
    Sun Microsystems, Inc. has intellectual property rights relating to
    technology embodied in the product that is described in this document.
    In particular, and without limitation, these intellectual property
    rights may include one or more of the U.S. patents listed at
    http://www.sun.com/patents and one or more additional patents or
    pending patent applications in the U.S. and in other countries.
    This document and the product to which it pertains are distributed
    under licenses restricting their use, copying, distribution, and
    decompilation. This document may be reproduced and distributed but
    may
    not be changed without prior written authorization of Sun and its
    licensors, if any.
    Third-party software, including font technology, is copyrighted and
    licensed from Sun suppliers.
    Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail and and
    Enterprise JavaBeans are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries.
    Federal Acquisitions: Commercial Software - Government Users Subjectto
    Standard License Terms and Conditions.
    DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
    CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
    WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
    NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
    DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, E'tats-Unis.
    Tous droits re'serve's.
    Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
    relatants a` la technologie incorpore'e dans le produit qui est
    de'crit
    dans ce document. En particulier, et sans la limitation, ces droits de
    proprie'te' intellectuels peuvent inclure un ou plus des brevets
    ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
    brevets plus supple'mentaires ou les applications de brevet en attente
    dans les E'tats-Unis et dans les autres pays.
    Ce produit ou document est prote'ge' par un copyright et distribue'
    avec des licences qui en restreignent l'utilisation, la copie, la
    distribution, et la de'compilation. Ce documention associe n peut
    e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
    l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
    licence, le cas e'che'ant.
    Le logiciel de'tenu par des tiers, et qui comprend la technologie
    relative aux polices de caracte`res, est prote'ge' par un copyright et
    licencie' par des fournisseurs de Sun.
    Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail et and
    Enterprise JavaBeans sont des marques de fabrique ou des marques
    de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
    pays.
    LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
    DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
    EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
    NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
    L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
    CONTREFAC,ON.
    -->
    <!--
    This is the XML DTD for the J2EE 1.3 application deployment
    descriptor. All J2EE 1.3 application deployment descriptors
    must include a DOCTYPE of the following form:
    <!DOCTYPE application PUBLIC
    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
    "http://java.sun.com/dtd/application_1_3.dtd">
    -->
    <!--
    The following conventions apply to all J2EE deployment descriptor
    elements unless indicated otherwise.
    - In elements that contain PCDATA, leading and trailing whitespace
    in the data may be ignored.
    - In elements whose value is an "enumerated type", the value is
    case sensitive.
    - In elements that specify a pathname to a file within the same
    JAR file, relative filenames (i.e., those not starting with "/")
    are considered relative to the root of the JAR file's namespace.
    Absolute filenames (i.e., those starting with "/") also specify
    names in the root of the JAR file's namespace. In general, relative
    names are preferred. The exception is .war files where absolute
    names are preferred for consistency with the servlet API.
    -->
    <!--
    The application element is the root element of a J2EE application
    deployment descriptor.
    -->
    <!ELEMENT application (icon?, display-name, description?, module+,
    security-role*)>
    <!--
    The alt-dd element specifies an optional URI to the post-assembly
    version of the deployment descriptor file for a particular J2EEmodule.
    The URI must specify the full pathname of the deployment descriptor
    file relative to the application's root directory. If alt-dd is not
    specified, the deployer must read the deployment descriptor from the
    default location and file name required by the respective component
    specification.
    Used in: module
    -->
    <!ELEMENT alt-dd (#PCDATA)>
    <!--
    The connector element specifies the URI of a resource adapter archive
    file, relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT connector (#PCDATA)>
    <!--
    The context-root element specifies the context root of a web
    application.
    Used in: web
    -->
    <!ELEMENT context-root (#PCDATA)>
    <!--
    The description element is used to provide text describing the parent
    element. The description element should include any information that
    the application ear file producer wants to provide to the consumer of
    the application ear file (i.e., to the Deployer). Typically, the tools
    used by the application ear file consumer will display the description
    when processing the parent element that contains the description.
    Used in: application, security-role
    -->
    <!ELEMENT description (#PCDATA)>
    <!--
    The display-name element contains a short name that is intended to be
    displayed by tools. The display name need not be unique.
    Used in: application
    Example:
    <display-name>Employee Self Service</display-name>
    -->
    <!ELEMENT display-name (#PCDATA)>
    <!--
    The ejb element specifies the URI of an ejb-jar, relative to the top
    level of the application package.
    Used in: module
    -->
    <!ELEMENT ejb (#PCDATA)>
    <!--
    The icon element contains small-icon and large-icon elements that
    specify the file names for small and a large GIF or JPEG icon images
    used to represent the parent element in a GUI tool.
    Used in: application
    -->
    <!ELEMENT icon (small-icon?, large-icon?)>
    <!--
    The java element specifies the URI of a java application clientmodule,
    relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT java (#PCDATA)>
    <!--
    The large-icon element contains the name of a file
    containing a large (32 x 32) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <large-icon>employee-service-icon32x32.jpg</large-icon>
    -->
    <!ELEMENT large-icon (#PCDATA)>
    <!--
    The module element represents a single J2EE module and contains a
    connector, ejb, java, or web element, which indicates the module type
    and contains a path to the module file, and an optional alt-ddelement,
    which specifies an optional URI to the post-assembly version of the
    deployment descriptor.
    The application deployment descriptor must have one module element for
    each J2EE module in the application package.
    Used in: application
    -->
    <!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
    <!--
    The role-name element contains the name of a security role.
    The name must conform to the lexical rules for an NMTOKEN.
    Used in: security-role
    -->
    <!ELEMENT role-name (#PCDATA)>
    <!--
    The security-role element contains the definition of a security
    role. The definition consists of an optional description of the
    security role, and the security role name.
    Used in: application
    Example:
    <security-role>
    <description>
    This role includes all employees who are authorized
    to access the employee service application.
    </description>
    <role-name>employee</role-name>
    </security-role>
    -->
    <!ELEMENT security-role (description?, role-name)>
    <!--
    The small-icon element contains the name of a file
    containing a small (16 x 16) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <small-icon>employee-service-icon16x16.jpg</small-icon>
    -->
    <!ELEMENT small-icon (#PCDATA)>
    <!--
    The web element contains the web-uri and context-root of a web
    application module.
    Used in: module
    -->
    <!ELEMENT web (web-uri, context-root)>
    <!--
    The web-uri element specifies the URI of a web application file,
    relative to the top level of the application package.
    Used in: web
    -->
    <!ELEMENT web-uri (#PCDATA)>
    <!--
    The ID mechanism is to allow tools that produce additional deployment
    information (i.e., information beyond the standard deployment
    descriptor information) to store the non-standard information in a
    separate file, and easily refer from these tool-specific files to the
    information in the standard deployment descriptor.
    Tools are not allowed to add the non-standard information into the
    standard deployment descriptor.
    -->
    <!ATTLIST alt-dd id ID #IMPLIED>
    <!ATTLIST application id ID #IMPLIED>
    <!ATTLIST connector id ID #IMPLIED>
    <!ATTLIST context-root id ID #IMPLIED>
    <!ATTLIST description id ID #IMPLIED>
    <!ATTLIST display-name id ID #IMPLIED>
    <!ATTLIST ejb id ID #IMPLIED>
    <!ATTLIST icon id ID #IMPLIED>
    <!ATTLIST java id ID #IMPLIED>
    <!ATTLIST large-icon id ID #IMPLIED>
    <!ATTLIST module id ID #IMPLIED>
    <!ATTLIST role-name id ID #IMPLIED>
    <!ATTLIST security-role id ID #IMPLIED>
    <!ATTLIST small-icon id ID #IMPLIED>
    <!ATTLIST web id ID #IMPLIED>
    <!ATTLIST web-uri id ID #IMPLIED>

  • Getting portal server name using webdynpro deployed in different server.

    Hi All,
      I have a question on accessing the servername where my portal is running which has an iview created for a webdynpro which is deployed in other server.I have J2ee server1 on which portal is installed and running, now i have developed webdynpro with authentication and deployed to another J2ee server2. In server1 i want to create the iview through which i can access the webdynpro deployed in server2, now in my webdynpro i used NavigationTarget with LinkToURL element where user can navigate to the one of portal page which requires the servername of portal, so how can i get the servername where portal is running(server1) if my webdynpro is deployed in server2.please provide what are the steps rerquired to get this scenario running and also for i used the target propery of linktourl to _self  and _top but its opening in new browser, i want link to open  in same window.Please give your valuable suggestions.
    Thanks,
    Pkv.

    Hi..
    try {
         InetAddress ina = InetAddress.getLocalHost();
          wdComponentAPI.getMessageManager().reportSuccess("Host name is "ina.getHostName()"..Host address "ina.getHostAddress()"...CanonicalHostName   "ina.getCanonicalHostName()"...by name    "+ina.getByName(ina.getHostName()));
         } catch (UnknownHostException e) {
         // TODO Auto-generated catch block
         wdComponentAPI.getMessageManager().reportSuccess(""+e);
    this is the small peice of to know  and tell me ur requirment is on Development Server or Production,for development above code is enough if not than need to do more
    Regards
    Rajesh

  • How to deploy WebDynpro application from Portal

    Hi Friends,
    when we develop WebDynpro applications, we deploy and run the applications from IDE NWDS studio..
    Is there any way to deploy it from portal?

    Hi,
    Wat do you mean by deploying it from the portal?
    It is possible to integrate webdynpro apps in Portal
    Follow this link
    https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/2fffe990-0201-0010-aab0-e61c3250bcf3
    Regards,
    Santhosh

  • Error in WebDynpro with WebServices

    Hi all,
    I’m getting some errors using applications deployed in WEB AS SP9 that runs as a WebDynpro IView in EP.
    Running the application as standalone (out of EP) this works fine.
    NetWeaver Developer Studio 2.0.9
    WebDynpro application using WebServices that access Oracle 8i database in the follow sequence:
    WebServices -> Session Bean stateless -> Entity Bean CMP (manage connections; generate sql code, etc.)
    In WebDynpro application we import WebService Model by the follow sequence:
    New Model - Import Web Service Model - Local Server for WSDL Source - <WebService deployed>
    In each WebServices we have created these methods:
    findByID(ID);
    getAll();
    insert(parameters);
    remove(ID);
    update(parameters);
    We guess that the error is generated in Entity Bean because all WebServices generate these errors.
    <b>Error 1 - Application with WebServices Model</b>
    Error stacktrace:
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Repository Object br.com.xxx.fluxo.Fluxo/ComponentInterface:FluxoInterface/InterfaceViews:CadastroSituacaoFluxoInterfaceView/InboundPlugs:Default associated via relation RepositoryObjectRelation(br.com.xxx.fluxo.application.CadastroSituacaoFluxoApp, StartupPlug) does not exist.
         at com.sap.tc.webdynpro.repository.RelationToOne.resolveTargets(RelationToOne.java:124)
         at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:108)
         at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:72)
         at com.sap.tc.webdynpro.repository.RelationToOne.getTarget(RelationToOne.java:174)
         at com.sap.tc.webdynpro.repository.RepositoryObject.getRelatedModelObject(RepositoryObject.java:349)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getStartupPlugInternal(IWDApplicationInfo.java:319)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:355)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         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:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    -- end --
    <b>Error 2 - Application with WebServices Model</b>
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
    Web Dynpro code generators of DC local/Apontamentos:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: (unknown)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87037.313
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller NotProductiveEventController
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
         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.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         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:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    <b>Error 3 - Application with RFC Model</b>
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
    Web Dynpro code generators of DC local/Apontamentos:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: (unknown)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87037.313
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller ZMANPP012Controller
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
         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.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         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:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

    Hi,
    I feel this error is nothing to do with webservice model.
    Please check your application properties like startupPlug,Interface View etc. Set the properties correctly and deploy once again.
    Regards, VIP

  • Error in executing new webcenter portal application

    Hi
    i am getting error in executing new webcenter portal application, even while executing existing webcenter portal application.Installed all necessary bundles.And my installation is under OR_MW_1 folder.
    [Running application SmartSystems on Server Instance IntegratedWebLogicServer...]
    [11:29:32 AM] ---- Deployment started. ----
    [11:29:32 AM] Target platform is (Weblogic 10.3).
    [11:29:33 AM] Retrieving existing application information
    [11:29:33 AM] Running dependency analysis...
    [11:29:33 AM] Deploying 3 profiles...
    [11:29:33 AM] Wrote MAR file to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\SmartSystems\AutoGeneratedMar
    [11:29:34 AM] Wrote Web Application Module to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\SmartSystems\PortalWebApp.war
    [11:29:34 AM] Info: Namespace '/oracle/adf/share/prefs' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/lifecycle/importexport' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/lock' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/rc' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/persdef' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/shared/oracle/wcps' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/xliffBundles' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/search/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/framework/scope/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/page/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/pageDefs' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/adf/portlet' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/adf/portletappscope' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/doclib/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/portalapp' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/security/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/siteresources/shared' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Namespace '/oracle/webcenter/quicklinks/scopedMD' is mapped to deploy-target metadata-store-usage 'WebCenterFileMetadataStore' in adf-config.xml but no metadata from the namespace is included in the MAR.
    [11:29:34 AM] Info: Any customizations created while running the application will be written to 'C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.mds.dt\adrs\SmartSystems\AutoGeneratedMar\mds_adrs_writedir'.
    [11:29:35 AM] Wrote Enterprise Application Module to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\SmartSystems
    [11:29:35 AM] Deploying Application...
    <May 6, 2013 11:29:36 AM IST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.apps.common.resource, referenced from: C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\tmp\_WL_user\oracle.webcenter.framework\owur7d]. Make sure the referenced optional package has been deployed as a library.>
    <May 6, 2013 11:29:37 AM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1367819975651' for task '2'. Error is: 'weblogic.management.DeploymentException: '
    weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
         at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.webcenter.lifecycle.listener.FeatureMetricApplicationListener
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
         Truncated. see log file for complete stacktrace
    >
    <May 6, 2013 11:29:37 AM IST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <May 6, 2013 11:29:37 AM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00003. Log messages will continue to be logged in C:\Users\Kavipriya_g01\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
    <May 6, 2013 11:29:37 AM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'SmartSystems [Version=V2.0]'.>
    <May 6, 2013 11:29:37 AM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
         at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.webcenter.lifecycle.listener.FeatureMetricApplicationListener
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
         Truncated. see log file for complete stacktrace
    >
    [11:29:37 AM] #### Deployment incomplete. ####
    [11:29:37 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    #### Cannot run application SmartSystems due to error deploying to IntegratedWebLogicServer.
    [Application SmartSystems stopped and undeployed from Server Instance IntegratedWebLogicServer]

    Have you included libraries for this ?
    java.lang.ClassNotFoundException: oracle.webcenter.lifecycle.listener.FeatureMetricApplicationListener

  • Gettin error while starting the weblogic portal server

    Hi ,
    This is Kalyan. I had installed weblogic portal 10.3 in my system.After installing i had tried for the sample portal web application. I had selected the portal web project-->given the project name and selected the necessary things .I had create sample portal when iam trying to run this portal on the server it showing me the error.
    Error(s) found in module 'ProData'. Publish was cancelled. See "Problems" view for details.
    A WebLogic Portal web application project should be added as a J2EE module to a WebLogic Portal EAR project for proper deployment at ProData
    The associated EAR "ProDataEAR" is not a Portal Application Services EAR at ProData
    A Portal Application Services web application should be associated with a Portal Application Services EAR for proper deployment at ProData
    Here ProData is the my project name can anybody tell me the solution i will be grate ful to them
    Thanks & Regards

    Hi Kalyan
    1. First you need to create the portal ear project by selecting the portal project facets. Then create the portal web project with portal facets and make sure it is added to first create portal ear project. By default it will show in the list. Then portal data sync project is optional. Since this is your first time you can skip for now. Later on you can add data sync project also to the same portal ear. Once you have this, then you can deploy the portal ear project on the portal domain. Remember that you need to create the portal domain with portal facets.
    Delete the project you already created and start from fresh. If you already created any portlets or pageflows or jsps etc, copy those files as backup. Once you create portal ear and web projects, copy them into your new application.
    Here is the link for details: http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/quickstart/newproject.html
    HTH
    Ravi Jegga

  • JCO Connection error in webdynpro

    Hi
    I  have Ep 7.0, ECC 6.0 (NW2004s)
    I am  trying to establish JCo connection but we are getting the
    following error
    "com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect
    to message server host failed Connect_PM TYPE=B MSHOST=*****
    GROUP=SPACE R3NAME=HEI MSSERV=sapmsHEI PCS=1 ERROR
    service 'sapmsHEI' unknown TIME Fri May 30 16:19:20 2008
    RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -
    3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2:
    service 'sapmsHEI' not found SYSTEM CALL getservbyname_r COUNTER 2"
    Already i have created TechnicalSystems in the Portal and
    I have entered the sevice file in the location of c:\WINDOWS\system32\drivers\etc as "sapms<SID> 3600/tcp" in EnterprisePortal Server.
    after that we have restarted the server
    Still i am getting same error.
    Could you please help us.
    Regards
    Srinivas

    Hi,
    First You Configure SLD Correctly.If You Have ECC And BW.You Maintaing Two WEBAS ABAP Systems.
    You Create WEB AS ABAP System In SLD And Maintain Connection Properties Of ECC.And
    Similarly For BW Also.
    The Given Below Links To Help You SLD Cofiguration For J2EE
    http://www.*********************/solution_manager/solution_manager_sld.html
    SLD Configuration
    3.If You Want To Create JCO Destinations.You Go To Login Portal
    Content Administration->Webdynpro->Create JCO Destinatiion
    A.General Data -> Specify Model Name,Client And JCO Pool Configuration
    B.Specify J2EEE Cluster
    C.Destination type
    Data Type-> Application DataModel,Dictionary MetaDataMetadata
    Destination Type->Load Balancing Or Single Server
    D.Specify Either Application Server Or Message Server
    E.SecurityUsername,password,confirm password,language
    F.SummaryWhole Information
    Similarly Metadata Created Follow Same Steps As Above
    After Creating JCO Destinations, Go For Maintain JCO Destination And test The JCO Destinations Works Fine Or Not you Con Test.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/webdynpro/wd%20java/portal%20integration/how%20to%20use%20the%20web%20dynpro%20content%20administrator.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
    http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm
    It's Useful Rewards Points
    Bye
    Thanks
    SubbaRao

  • Time out error in webdynpro

    Hi all,
    We are facing a time out error uisng webdynpro.
    The webdynpro application is mapped to the enterprise portal for the users.
    When ever the users loads the application and first click on the link then again loads the application and click any link(as clicked previously) then the application returs time out error.
    I am little confused as not known the error is a portal one or webdynpro error.
    Requesting experts for a say on this.
    thanks

    Hi,
    You can try this...
    Re: TimeOut
    Cheers,
    Kris.

  • Deploying BEA Portal App in Managed Server problems....

    Hello,
    I have a BEA portal application (exploded EAR) that I want to deploy in a managed server. I first created a regular portal domain (8.1 SP4). I then created a managed server via the console. When I went to deploy my portal application (in the console), I received an error indicating that the application was a Split Development Directory and that I would have to run the wlpackage Ant task against the application first. I ran the wlpackage ant task and it seemingly worked.
    I then used the wldeploy Ant task to deploy it in the managed server but got an error indicating that it could not find a JNDI name from one of the data sources. I went back to the console and targeted/deployed all of the default Connection Pools & Data Sources to the managed server thinking that was the reason the deploy failed.
    When I ran the wldeploy again I got the following error:
    Module: content.jar Error: Exception activating module: EJBModule(content.jar, status=PREPARED)
    Unable to deploy EJB: ValueBean from content.jar
    java.sql.SQLException: javax.naming.NameNotFoundException: While trying to lookup 'portalFrameworkPool; contentDataSource;weblogic.jdbc.jts.commercialPool' didn't find subcontext 'portalFrameworkPool;contentDataSource;weblogic' Resolved ; remaining name 'portalFrameworkPool;contentDataSource;weblogic/jdbc/jts/commercialPool'
    Has anyone run into this? Am I not suppose to deploy a portal application in a managed server?
    Any help would be greatly appreciated.
    Thanks - Peter Len

    Problem solved.......
    After targeting all the data sources and poolers to the managed server, I restarted the main domain but did not restart the managed server. After restarting the managed server all was well.
    Thanks - Peter

  • Error in distributed installation of portal

    Hi,
    We are having a distributed installation of EP 7.0 Including EHP1 on
    RedHat Linux 5.4 with Oracle. Currently our installation is struck in
    the installation of Central Instance. Install Java Engine.
    IT starts at erroring out here:
    Error: Target system of development
    component 'DocumentServicesSupportFiles'/'com.adobe'/'Adobe
    Systems'/'802.20080424033707.465503'/'0' reported the following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/com.adobe/DocumentServicesSupportFiles/Adobe
    Systems/0/802.20080424033707.465503/work/META-INF/null (No such file or
    directory)
    Target system of development
    component 'com.sap.engine.configtool'/'sap.com'/'SAP
    AG'/'7.0103.20081111105857.0000'/'0' reported the
    following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.configtool/SAP
    AG/0/7.0103.20081111105857.0000/work/META-INF/null (No such file or
    directory)
    This error is repeated at least 15 times for other SDA's as well.
    Please let me know any workaround.
    Thanks,
    Antarpreet

    Hello Fan,
    Firstly, thanks for your help.
    We are currently installing Portal and we are currently in phase Install Java Engine.
    I can not see any SDM processes running at this stage.
    Following is the log of sapinst.
    Info: Update strategy: UpdateSameAndLowerVersions
    Info: Starting deployment prerequisites:
    Info: Check sync archives:
    Info: Selected archives successfully loaded.
    Info: Actions per selected component:
    Info: Update: Selected development component 'com.sap.engine.visualadmin'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0' updates currently deployed development component 'com.sap.engine.visualadmin'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
    Info: Update: Selected development component 'tc/sapinst/fs'/'sap.com'/'SAP AG'/'7.0103.20081111152535.0000'/'0' updates currently deployed development component 'tc/sapinst/fs'/'sap.com'/'SAP AG'/'7.0103.20081111152535.0000'/'0'.
    Info: Update: Selected development component 'com.sap.engine.deploy.online'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0' updates currently deployed development component 'com.sap.engine.deploy.online'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
    Info: Update: Selected development component 'com.sap.engine.client'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0' updates currently deployed development component 'com.sap.engine.client'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
    Info: Update: Selected development component 'tc/sdt/app/jspm/bootstrap'/'sap.com'/'SAP AG'/'7.0103.20081127075715.0000'/'0' updates currently deployed development component 'tc/sdt/app/jspm/bootstrap'/'sap.com'/'SAP AG'/'7.0103.20081127075715.0000'/'0'.
    Info: Update: Selected development component 'com.sap.engine.configtool'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0' updates currently deployed development component 'com.sap.engine.configtool'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
    Info: Update: Selected development component 'sapjra'/'sap.com'/'SAP AG'/'7.0103.20081105085923.0000'/'0' updates currently deployed development component 'sapjra'/'sap.com'/'SAP AG'/'7.0103.20081105085923.0000'/'0'.
    Info: Update: Selected development component 'com.sapportals.supportplatformSDA'/'sap.com'/'SAP AG'/'7.0103.20081105090112.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatformSDA'/'sap.com'/'SAP AG'/'7.0103.20081105090112.0000'/'0'.
    Info: Update: Selected development component 'tc/monitoring/logviewer-standalone'/'sap.com'/'SAP AG'/'7.0103.20081127075758.0000'/'0' updates currently deployed development component 'tc/monitoring/logviewer-standalone'/'sap.com'/'SAP AG'/'7.0103.20081127075758.0000'/'0'.
    Info: Update: Selected development component 'tc/template_config_tool'/'sap.com'/'SAP AG'/'7.0103.20081105084616.0000'/'0' updates currently deployed development component 'tc/template_config_tool'/'sap.com'/'SAP AG'/'7.0103.20081105084616.0000'/'0'.
    Info: Update: Selected development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0103.20081105085706.0000'/'0' updates currently deployed development component 'IAIKSecurityFS'/'sap.com'/'SAP AG'/'7.0103.20081105085706.0000'/'0'.
    Info: Update: Selected development component 'com.sap.engine.deploytool'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0' updates currently deployed development component 'com.sap.engine.deploytool'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0'.
    Info: Update: Selected development component 'DocumentServicesSupportFiles'/'com.adobe'/'Adobe Systems'/'802.20080424033707.465503'/'0' updates currently deployed development component 'DocumentServicesSupportFiles'/'com.adobe'/'Adobe Systems'/'802.20080424033707.465503'/'0'.
    Info: Update: Selected development component 'tc/ads/lib'/'sap.com'/'SAP AG'/'7.0103.20081105083713.0000'/'0' updates currently deployed development component 'tc/ads/lib'/'sap.com'/'SAP AG'/'7.0103.20081105083713.0000'/'0'.
    Info: Update: Selected development component 'tc/sdt/app/jspm/ext'/'sap.com'/'SAP AG'/'7.0103.20081127075715.0000'/'0' updates currently deployed development component 'tc/sdt/app/jspm/ext'/'sap.com'/'SAP AG'/'7.0103.20081127075715.0000'/'0'.
    Info: Update: Selected development component 'tc/lm/ctc/offline_ctc'/'sap.com'/'MAIN_NW701P03_C'/'2901714'/'0' updates currently deployed development component 'tc/lm/ctc/offline_ctc'/'sap.com'/'MAIN_NW701P03_C'/'2901714'/'0'.
    Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'7.0103.20081105085525.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'7.0103.20081105085525.0000'/'0'.
    Info: Update: Selected development component 'tc/sdt/app/jspm'/'sap.com'/'SAP AG'/'7.0103.20081127075715.0000'/'0' updates currently deployed development component 'tc/sdt/app/jspm'/'sap.com'/'SAP AG'/'7.0103.20081127075715.0000'/'0'.
    Error: Target system of development component 'DocumentServicesSupportFiles'/'com.adobe'/'Adobe Systems'/'802.20080424033707.465503'/'0' reported the following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/com.adobe/DocumentServicesSupportFiles/Adobe Systems/0/802.20080424033707.465503/work/META-INF/null (No such file or directory)
    Target system of development component 'com.sap.engine.configtool'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0' reported the following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.configtool/SAP AG/0/7.0103.20081111105857.0000/work/META-INF/null (No such file or directory)
    Target system of development component 'com.sap.engine.deploy.online'/'sap.com'/'SAP AG'/'7.0103.20081111105857.0000'/'0' reported the following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.deploy.online/SAP AG/0/7.0103.20081111105857.0000/work/META-INF/null (No such file or directory)
    Target system of development component 'tc/ads/lib'/'sap.com'/'SAP AG'/'7.0103.20081105083713.0000'/'0' reported the following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/ads/lib/SAP AG/0/7.0103.20081105083713.0000/work/META-INF/null (No such file or directory)
    Target system of development component 'tc/sapinst/fs'/'sap.com'/'SAP AG'/'7.0103.20081111152535.0000'/'0' reported the following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/sapinst/fs/SAP AG/0/7.0103.20081111152535.0000/work/META-INF/null (No such file or directory)
    Target system of development component 'tc/sdt/app/jspm/bootstrap'/'sap.com'/'SAP AG'/'7.0103.20081127075715.0000'/'0' reported the following error:
    com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Cannot parse XML document.
    Additional error message is:
    java.io.FileNotFoundException: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/sdt/app/jspm/bootstrap/SAP AG/0/7.0103.20081127075715.0000/work/META-INF/null (No such file or directory)
    Error: Prerequisites were aborted.
    Error: Error while creating deployment actions.
    Info: Summarizing the deployment results:
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/sdt/app/jspm/ext/SAP AG/0/7.0103.20081127075715.0000/sap.comtcsdtappjspm~ext.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/sld/data/SAP AG/0/7.0103.20081105085525.0000/lcrwork.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.client/SAP AG/0/7.0103.20081111105857.0000/sapj2eeclient.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/monitoring/logviewer-standalone/SAP AG/0/7.0103.20081127075758.0000/logviewer-standalone-fs.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sapportals.supportplatformSDA/SAP AG/0/7.0103.20081105090112.0000/com.sapportals.supportplatform.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/com.adobe/DocumentServicesSupportFiles/Adobe Systems/0/802.20080424033707.465503/DocumentServicesSupportFiles.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/IAIKSecurityFS/SAP AG/0/7.0103.20081105085706.0000/tc_sec_java_crypto_fs_lib.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.deploy.online/SAP AG/0/7.0103.20081111105857.0000/sapj2eenginedeploy.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/template_config_tool/SAP AG/0/7.0103.20081105084616.0000/TemplateConfigTool.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.visualadmin/SAP AG/0/7.0103.20081111105857.0000/visual-admin.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.deploytool/SAP AG/0/7.0103.20081111105857.0000/deploy-tool.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/sapinst/fs/SAP AG/0/7.0103.20081111152535.0000/sltools.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/ads/lib/SAP AG/0/7.0103.20081105083713.0000/adobe-LibFiles.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/sapjra/SAP AG/0/7.0103.20081105085923.0000/sapjra.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/sdt/app/jspm/bootstrap/SAP AG/0/7.0103.20081127075715.0000/sap.comtcsdtappjspm~bootstrap.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/com.sap.engine.configtool/SAP AG/0/7.0103.20081111105857.0000/configtool.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/sdt/app/jspm/SAP AG/0/7.0103.20081127075715.0000/sap.comtcsdtappjspm.sda
    Error: Precondition violated: /usr/sap/SUD/JC00/SDM/root/origin/sap.com/tc/lm/ctc/offline_ctc/MAIN_NW701P03_C/0/2901714/tclmctc~offline_ctc.sda
    Processing error. Return code: 4
    Error: Processing error. Return code: 4
    ERROR      2010-05-19 20:19:45.338 [iaxxinscbk.cpp:260]
    MUT-02041  SDM call of deploy ends with returncode 4
    TRACE      2010-05-19 20:19:45.338 [iaxxejsbas.hpp:408]
               handleException<ESAPinstException>()
    Converting exception into JS Exception Exception.
    TRACE      2010-05-19 20:19:45.338
    Function setMessageIdOfExceptionMessage: modlib.jslib.caughtException
    ERROR      2010-05-19 20:19:45.339
               CJSlibModule::writeError_impl()
    MUT-03025  Caught ESAPinstException in Modulecall: SDM call of deploy ends with returncode 4.
    TRACE      2010-05-19 20:19:45.339 [iaxxejsbas.hpp:483]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    TRACE      2010-05-19 20:19:45.347 [syuxctask.cpp:1382]
               CSyTaskImpl::start(bool)
    A child process has been started. Pid = 26175
    TRACE      2010-05-19 20:19:45.360 [syuxctask.cpp:1382]
               CSyTaskImpl::start(bool)
    A child process has been started. Pid = 26176
    ERROR      2010-05-19 20:19:45.369 [sixxcstepexecute.cpp:950]
    FCO-00011  The step redeployFS with step key |NW_Java_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|12|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|5|0|redeployFS was executed with status ERROR ( Last error reported by the step :Caught ESAPinstException in Modulecall: SDM call of deploy ends with returncode 4.).
    TRACE      2010-05-19 20:19:45.385 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    Can you confirm to me whether SDM interacts with the file system on the database instance.
    thanks,
    antarpreet

  • Error in service call of Portal Component while accessing CRM iview

    Hi Experts,
    When I'm trying to open the iview, i'm getting portal runtime error.  Below is the log I found.  I check the permissions and everything looks fine.  We have migrated from EP6 to EP7 EHP1 SP8.  This iview is working properly in EP6 but throwing error in EP7.  Kindly let me know how to resolve this issue.
    Exception ID:02:43_05/09/11_0009_109976350
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.scc.scc/vcr/com.ids.scc.vcr.crm_link/com.ids.scc.vcr.crm_link.Roles/com.scc.sapbpe.salesrep/myApplications_dlren_0/CRM/quotations/com.sap.pct.crm.sal.my_favorites_sales_documents
    Component class : com.sap.pct.crm.core.favorites.list.ListPortalComponent
    User : TESTUSER
    at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
    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.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
    at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
    at com.sapportals.portal.navigation.workAreaiView.doContent(workAreaiView.java:293)
    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:375)
    at java.security.AccessController.doPrivileged(AccessController.java:246)
    at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:388)
    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:770)
    Caused by: java.lang.NoClassDefFoundError: com.sap.pct.crm.core.objectlinks.ObjectLinkGenerator (initialization failure)
    at java.lang.J9VMInternals.initialize(J9VMInternals.java:134)
    at com.sap.pct.crm.core.favorites.list.ListDynPage.onContainerCreate(ListDynPage.java:547)
    at com.sapportals.pct.util.pdv.PDVDynPage.doProcessBeforeOutput(PDVDynPage.java:171)
    at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:127)
    at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
    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)
    ... 15 more
    Thanks in advance,
    VV.

    Hi,
    check whether note 1291058 applies for you.
    Check whether your Stacks and SPs / Business Packages matched correctly with maintenance optimizer.
    Got this error only once while implementing a new portal, it was due to a corrupted deployment, so probably some of the XSS JAVA Components got corrupted.
    EDIT: "Caused by: java.lang.NoClassDefFoundError: com.sap.pct.crm.core.objectlinks.ObjectLinkGenerator" really looks like something with the JAVA deployment went wrong. Java Stack can't find a class definition in PBO... you haven't modified anything with NWDS/NWDI or have you?
    regards, Lukas
    Edited by: Lukas Weigelt on Sep 7, 2011 1:22 PM

  • Error in MSS Deployment in SDM

    Hi,
         I am new to Portal. I am facing an issue while redeploying the MSS package in SDM. Due to some Problems I need to redeploy the MSS package in SDM ,For that first I have undeployed the existing package from SDM.All the Components have been undeployed properly.Again I try to deploy the BPMSS Package 10.
    It gives an Error that,
    Starting Deployment of mss/bp_mss
    Aborted: development component 'mss/bp_mss'/'sap.com'/'MAIN_ERP05VAL_C'/'1251615':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/mssbp_mss.. Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: Failed to deploy archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197297170562\sap.commss~bp_mss.epa
    The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
    com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: Failed to deploy archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197297170562\sap.commssbp_mss.epa
    The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:227)
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchives(PackageDeployServiceImpl.java:369)
    Caused by:
    com.sapportals.portal.transport.app.TransportApplicationLockingException: The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
         at com.sapportals.portal.transport.app.TransportUtils.setAllLocks(TransportUtils.java:644)
         at com.sapportals.portal.transport.app.TransportApplicationImpl.importList(TransportApplicationImpl.java:945)
         at com.sapportals.portal.transport.app.TransportApplicationImpl.importPackage(TransportApplicationImpl.java:819)
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: Failed to deploy archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197297170562\sap.commssbp_mss.epa
    The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
    com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: Failed to deploy archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197297170562\sap.commssbp_mss.epa
    The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:227)
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchives(PackageDeployServiceImpl.java:369)
    Caused by:
    com.sapportals.portal.transport.app.TransportApplicationLockingException: The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
         at com.sapportals.portal.transport.app.TransportUtils.setAllLocks(TransportUtils.java:644)
         at com.sapportals.portal.transport.app.TransportApplicationImpl.importList(TransportApplicationImpl.java:945)
         at com.sapportals.portal.transport.app.TransportApplicationImpl.importPackage(TransportApplicationImpl.java:819)
    ; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: Failed to deploy archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197297170562\sap.commssbp_mss.epa
    The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
    com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: Failed to deploy archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197297170562\sap.commssbp_mss.epa
    The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:227)
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchives(PackageDeployServiceImpl.java:369)
    Caused by:
    com.sapportals.portal.transport.app.TransportApplicationLockingException: The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
         at com.sapportals.portal.transport.app.TransportUtils.setAllLocks(TransportUtils.java:644)
         at com.sapportals.portal.transport.app.TransportApplicationImpl.importList(TransportApplicationImpl.java:945)
         at com.sapportals.portal.transport.app.TransportApplicationImpl.importPackage(TransportApplicationImpl.java:819)
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: Failed to deploy archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197297170562\sap.commssbp_mss.epa
    The following objects could not be locked: [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service|INTEG-NEHA]
    INTEG-NEHA is the Portal UserId having the administration rights.
    It would be more helpful for me if anyone bring me the solution for this Issue.
    Regards,
    Thenmalar v

    Hi,
               I have removed all the Locked Objects under that User Id(Integ-Neha). After that I am getting an error like this,
    Aborted: development component 'mss/bp_mss'/'sap.com'/'MAIN_ERP05VAL_C'/'1251615':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/mssbp_mss.. Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commss~bp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
    com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commssbp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:285)
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commssbp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
    com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commssbp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:285)
    ; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commssbp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
    com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commssbp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:285)
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commssbp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
    com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive D:\usr\sap\EP7\JC20\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1197345222062\sap.commssbp_mss.epa could not be deployed completely. Import failed for 2 of 268 objects. [pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service: Import failed.
    Did not find attribute name to attribute number 170000, pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.worksets/com.sap.pct.erp.mss.team: Import failed.
    Did not find attribute name to attribute number 170000, ]
         at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:285)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of mss/bp_mss finished with Error (Duration 141375 ms)
    Please it would be help ful if anyone bring me the Solution to this Issue.
    Regards,
    Thenmalar

Maybe you are looking for