Upgrade Ep6 to NW04s portal - deploy error

I am upgrading our EP 6 system to NW04s w/Portal. Java AS only. No ABAP. In the DEPLOY_ONLINE phase it is stopping after about 2 hours.
When I restart it, from the logs it appears to be restarting from the beginning instead of where it stopped. But I can't find the true cause of why it's stopping in the first place.
My arch logs are not full and my tablespaces are ok, so the DB didn't fill up with anything more than it should.
The logs show that most items were deployed, even though with warnings.  2 errored out, although I can't find why in the detailed logs:
Aug 4, 2006 12:10:42 PM  Info: Summarizing the deployment results:
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/ADSSAP08_0-10003001.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIIBC06_0.SCA
Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/BIWEBAPP06_1.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIMMR08_0-10002782.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIUDI08_0-10002781.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5***03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUA03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUY02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5COM02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5DCO02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5ESS03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5HRA03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5INV02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MSS03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MTC02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PLA02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PRS02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PSS03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5QIN02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SAL02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SUP02_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAF08_0-10003464.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFKM08_0-10003478.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFUM08_0-10003472.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPPSERV08_0-10003474.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPWDC08_0-10003557.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPBC208_0-10003489.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/FSCMBD03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/ISHERCSS03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMKWJIKS08_0-10003021.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCBC08_0-10003491.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCM08_0-10003492.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCOLL08_0-10003493.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMPORTAL08_0-10003487.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMTOOLS08_0-10003486.SCA
Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/NETPDK08_0-10003351.SCA
Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/RTC08_0-10003494.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/RTCSTREAM08_0-10003488.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPCRMDIC03_0.sca
Aug 4, 2006 12:10:42 PM  Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPEU08_0-10003026.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPCUIGP03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPASR03_0.sca
Aug 4, 2006 12:10:42 PM  Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPESS03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPMSS03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPSS03_0.sca
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/UMEADMIN08_0-10003471.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/UWLJWF08_0-10003490.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCBASE08_0-10003602.SCA
Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCFLEX08_0-10003616.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCFRAMEWORK08_0-10003624.SCA
Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITGP08_0-10003617.SCA
Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITXX08_0-10003615.SCA
Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/WDEXTENSIONS08_0-10003618.SCA
Aug 4, 2006 12:10:42 PM  Error: Processing error. Return code: 4

Hello,
We are having the exact same issue when DEPLOY_ONLINE encounters WDEXTENSIONS08_0-10003618.SCA as part of the NW2004s upgrade process.
We just submitted an OSS message to SAP about it --- but I am wondering if you have received a solution already? 
Is this a bad support package that SAP released?

Similar Messages

  • Weblogic jsf portal deploy error

    Hello, I am trying to deploy a JSF Portlet. After some time i managed to reach where i get this error when i am loading the portlet in browser.
    >
    <28.02.2008 17:07:20 EET> <BEA-101214> <Included resource or file "/portal/framework/skeletons/portal
    al/gridlayout.jsp" not found from requested resource "/portal/Portal.portal".>

    Hello,
    We are having the exact same issue when DEPLOY_ONLINE encounters WDEXTENSIONS08_0-10003618.SCA as part of the NW2004s upgrade process.
    We just submitted an OSS message to SAP about it --- but I am wondering if you have received a solution already? 
    Is this a bad support package that SAP released?

  • Upgrade 306 to 307 portal main errors

    I've upgrade both my db (solaris 816 to 817) and portal (306 to 307). Portal and RDBMS are in separate ORACLE_HOMEs on the same machine. Now, when I try to access portal, I get the following errors:
    "Client Logon Failed with errorcode:28150
    Reset Session Call also failed with error-code:1008
    Error-Code:28150
    Error TimeStamp:Tue, 27 Feb 2001 13:47:49 GMT
    Database Log In Failed
    TNS is unable to connect to destination. Invalid TNS address supplied or destination is not listening. This error can also occur because of underlying network transport problems.
    Verify that the TNS name in the connectstring entry of the DAD for this URL is valid and the database listener is running. "
    If I monitor the listener, I see the connection occur with success, and I can connecct c/s from 9ias ORACLE_HOME to the 817 database no problem. Any clue?

    Hi,
    Upon inspection of the pupgrade script it was found that the
    script upg/307/wwv/wwvupd2.csh was using SQL Plus to connect to
    the portal demo schema (PORTAL_SCHEMA_NAME_DEMO). However, since
    we had upgraded to portal 306 from webdb 2.2 we don't have such a
    schema. The upgrade guide does not ask you to create the DEMO
    schema before starting the process. Therefore the script fails at
    this point.
    Rgds,
    Rupesh

  • Upgrading EP6 SP10(j2ee,portal,KMC)  to SP11

    Hi,
    I am trying to upgrade my EP6 SP10(with KMC) to SP11.
    I downloaded all the patch files for J2EE, Portal &
    KMC. I unzipped all the sar files in to a common folder
    (sp_directory) using sapcar tool, exactly the way it is
    listed in the documentation. As a result, there are
    two main folders created in the root folder, one for
    j2ee and the other for Portal & KMC. The document says,
    I need to patch all the 3 components using the same SAPInst file. But, whenever I run the SAPInst exe file,
    it is taking me through the same steps that is upgrading J2EE alone. After running SAPInst twice, I checked the versions of these 3 components in the portal and found that only J2EE is upgraded. Neither Portal platform nor the KMC has upgraded. Is there anything else that I need to do ?
    regards
    Sudheer

    Sudheer,
       You have to upgrade each component separately. Don't unsar everything together. This is what you do.
    1. Unsar all the files required for J2ee upgrade.
    3. run the sapinst to upgrade.
    4. Delete all the folder/files directory created by unsar
    5. Unsar all the files required for EP.
    6. run the sapinst to upgrade EP.
    7. Delete all the folder/files created by unsar.
    8. Unsar all the files required for KMC.
    9. run the sapinst to upgrade KMC.
    10. delete all the folder/files created by unsar

  • Portal Runtime Error after Upgrade 7.01 to 7.3

    Hi,
    i have a Problem after Upgrade a BW 7.01 to 7.3 SP5 the,
    abap works fine but the Java Portal bring up Error on many time by choosing any funktion
    for example:
    try to use Portalcontent -> Systemlandscape -> SAP_BW
    this error is shown.
    Portal Runtime Error
    Tracefile:
    2011 11 24 13:05:51:546#+0100#Error#com.sap.portal.prt.connection#
    #EP-PIN-PRT#tcepbcprtc~api#C0000A11295500740000000000E900F2#9281050000000004#sap.com/irj#com.sap.portal.prt.connection#FREYAD#3##8D780B5716941                             1E1C8790000008D9E1A#a6e61adf169411e1cab50000008d9e1a#a6e61adf169411e1cab50000008d9e1a#0#Thread[HTTP Worker [@904797166],5,Dedicated_Application_                             Thread]#Plain##
    Exception ID:01:05_24/11/11_0004_9281050
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Application name : com.sap.portal.appdesigner.framework
    Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.pcmEditor
    Component class : com.sap.portal.admin.propertyeditor.core_functionality.PCMEditor
    -all Funktions in NWA are working
    -Diagnose an Supporttool is Green !
    Thanks Steven

    Hi Raj,
    You need to redeploy the patches in the message from Alexandra.
    How to redeploy same component with JSPM?
    JSPM does not allow to deploy an SCA with the same version (release, SP-level, patch-level) as an already deployed component. However, in some special cases you may need to redeploy an SCA with the same version. Use command line:
    go "-config=/jspm/forceMode=true" "-config=/jspm/deployVersionRule=updateAll" to redeploy all SDAs. See note #1123333 for more options.
    regards
    Steven

  • SSO error message when publishing a BI 7.0 report to the NW04s Portal

    Please indicate how to resolve the following SSO error message received when publishing a BI 7.0 report from Query Designer to a PCD folder on a NW04s Portal:
    Java system error: call FM RSRD_X_MAP_TO_PRTL_USERS_PROXY to ProgId (server alias)_PORTAL_ABV on host (server alias) with SSO not authorized: Authentication f

    Hi,
    Please check if the integration and sso configuration did correctly
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a
    Hope it helps.
    Regards,
    Mona

  • EP6.0SP2: MSS teamviewer -  portal runtime error

    Hi all,
    could you provide me with information how to solve this problem:
    We implemented the BP MSS 60.1.2 . Now only a few iviews are working fine - he most of them occur this error:
    Portal Runtime Error - ... - tcom/sap/pct/hcm/orgmanagementeventing/CKey.
    The teamviewer is not working neither, here this error appears:
    Portal Runtime Error - ... -
    Component Name : null
    Page could not create the iView
    I have found some similar topics within the sdn forum, but the only solution mentioned there are to reimplement MSS 60.1.1 .
    Is this the only solution for this foreseen ??
    Thanks in advance for your help.
    Sandra

    1st question would be.. does that iview in that path actually exist.  If it does it may be worth delting it from the page and then adding it again.  if it doesn't, well that's your problem.
    If it does exit then try previewing it. Looking at the error (Component Name : null) it could be that the par file has not deployed properly, in which case it is basically pointing at java code that doesn't exist.  If that is the case look for any .err files at OS level, rename then to .par and restart j2ee.
    Paul

  • Sapinst: Portal Deployment Monitor has reached the timeout of 1800

    Hello All,
    I am installing SAP EP 6.0 and in the Step 11 of 13 its continuosly giving me the following message.
    "Portal Deployment(0 of 298 files done. 0 with errors .Time elapsed: xxxx seconds).Wait..."
    and after 1800 secs its gets time out.
    It is not giving me any erros .
    Please help.
    Anthony

    Hello Anja Kloetzer ,
    With you suggestion , i have upgraded the patch level of WE AS JAVA to 20 .
    But still when starting the portal its waiting in stage 2 (Deploy JDBC libaries) , with no errors.
    I have checked the SDM logs
    09/04/22 19:16:54 -  ***********************************************************
    09/04/22 19:16:54 -  Start deploying library JAR E:\usr\sap\MOS\JC00\SDM\root\origin\sap.com\com.sapportals.datadirect\SAP AG\1\609.20041012102246.0000\com.sapportals.datadirect.sda...
    09/04/22 19:16:56 -  Library E:\usr\sap\MOS\JC00\SDM\root\origin\sap.com\com.sapportals.datadirect\SAP AG\1\609.20041012102246.0000\com.sapportals.datadirect.sda successfully deployed on the server.
    Apr 22, 2009 7:16:56 PM  Info: End of log messages of the target system.
    Apr 22, 2009 7:16:56 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Apr 22, 2009 7:16:56 PM  Info: Finished successfully: development component 'com.sapportals.datadirect'/'sap.com'/'SAP AG'/'609.20041012102246.0000'/'1'
    Apr 22, 2009 7:16:56 PM  Info: Starting to save the repository
    Apr 22, 2009 7:16:57 PM  Info: Finished saving the repository
    Apr 22, 2009 7:16:57 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Apr 22, 2009 7:16:57 PM  Info: -
    Deployment was successful -
    Apr 22, 2009 7:16:57 PM  Info: Summarizing the deployment results:
    Apr 22, 2009 7:16:57 PM  Info: OK: E:\SAP EP AS 6.0\EP\Portal\51030723_6\DVD_NW_04_SR1_NetWeaver_Components\EP-KMC\PORTAL\JAVA-LIB\com.sapportals.datadirect.sda
    Apr 22, 2009 7:16:57 PM  Info: Successfully executed. Return code: 0
    Apr 22, 2009 7:16:59 PM  Info: Start logging to 'C:\Program Files\sapinst_instdir\NW04\EP\EP/callSdmViaSapinst.log'
    Apr 22, 2009 7:16:59 PM  Info: Start logging to console
    Apr 22, 2009 7:16:59 PM  Info:
    Apr 22, 2009 7:16:59 PM  Info: ==============================================
    Apr 22, 2009 7:16:59 PM  Info: =   Starting to execute command 'jstartup'   =
    Apr 22, 2009 7:16:59 PM  Info: ==============================================
    Apr 22, 2009 7:16:59 PM  Info: Starting SDM - Software Deployment Manager...
    Apr 22, 2009 7:17:00 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4020.00.0000.20070308110902.0000
    Apr 22, 2009 7:17:00 PM  Info: SDM operation mode successfully set to: Standalone
    Apr 22, 2009 7:17:01 PM  Info: Initializing Network Manager (50017)
    Apr 22, 2009 7:17:01 PM  Info: Checking if another SDM is running on port 50018
    Apr 22, 2009 7:17:01 PM  Info:
    Apr 22, 2009 7:17:01 PM  Info: SDM operation mode successfully set to: Integrated
    Apr 22, 2009 7:17:02 PM  Info: Operationmode for JStartupFramework set to "integrated".
    Apr 22, 2009 7:17:02 PM  Info: Successfully executed. Return code: 0
    The installation of Portal is wating in that phase , please suggest.
    Regards
    Anthony

  • Got a Portal runtime error while using JSPDynepage

    Hi,
    Please help me out in the this error which I got when I tried to run the component developed based on JSPDynePage. I developed the component in the Developer Studio (version 2.0.4) in my local machine, built the project and deployed in the remote server using the option "Quick PAR Upload".
    It says JSP file could not be found.
    Thanks in advance
    Sushma
    <b>Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Cannot find JSP file: JSPFileInfo :27242692 JSP File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\pagelet\BeanJsp.jsp Class Name: sapportalsjspBeanJsp Java File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\work\pagelet\_sapportalsjsp_BeanJsp.java Package Name : pagelet Class File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\work\pagelet\_sapportalsjsp_BeanJsp.class Is out dated : true.
    Exception id: 01:45_03/11/04_0004_37482850
    See the details for the exception ID in the log file</b>

    Hi,
    I am also facing the same problem.
    1) EP6 SP7
    2) As mentioned in the error message there is no work directory in the mentioned path.
    3) Please find beow portalapp.xml and log file.
    <B>
    <?xml version="1.0" encoding="utf-8"?>
    <application>
      <application-config>
        <property name="SharingReference" value="com.sap.portal.htmlb"/>
      </application-config>
      <components>
        <component name="default">
          <component-config>
            <property name="ClassName" value="Ex1"/>
            <property name="SecurityZone" value="Ex1/low_safety"/>
          </component-config>
          <component-profile>
          <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
          </component-profile>
        </component>
      </components>
      <services/>
    </application>
    </B>
    Exception:
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : Ex1.default
    Component class : Ex1
    User : Administrator
    at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
    at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
    at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
    at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:109)
    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)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:627)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
    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:337)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:315)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:815)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
    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:151)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Cannot find JSP file: JSPFileInfo :16447115
    JSP File : D:
    usr
    sap
    P66
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    Ex1
    pagelet
    Ex1.jsp
    Class Name: sapportalsjspEx1
    Java File : D:
    usr
    sap
    P66
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    Ex1
    work
    pagelet
    _sapportalsjsp_Ex1.java
    Package Name : pagelet
    Class File : D:
    usr
    sap
    P66
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    Ex1
    work
    pagelet
    _sapportalsjsp_Ex1.class
    Is out dated : true
    at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:96)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:931)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
    ... 38 more
    #1.5#000C76EEC65400440000000F000001E80003E8A8BBC24BD7#1100236331418#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#99#####SAPEngine_Application_Thread[impl:3]_26##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.system.hooks.ErrorComponent supports (*, *, *) #
    #1.5#000C76EEC654004400000010000001E80003E8A8BBC250B2#1100236331418#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#99#####SAPEngine_Application_Thread[impl:3]_26##0#0#Info##Plain###------PRT AbstractPortalComponent: calling doContent for portal component: com.sap.portal.runtime.system.hooks.ErrorComponent#
    #1.5#000C76EEC654005B00000005000001E80003E8A8BC0E32CF#1100236336397#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#96#####SAPEngine_Application_Thread[impl:3]_2##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.admin.logviewer.default supports (*, *, *) #
    #1.5#000C76EEC654004D0000000C000001E80003E8A8C46CFCDD#1100236476698#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#96#####SAPEngine_Application_Thread[impl:3]_0##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.admin.logviewer.default supports (*, *, *) #

  • Export/import content from EP6 into NW04

    We are upgrading from SRM3.0/EP6 SP2 (source) to SRM5.0/Portal NW2004s (target).
    The only thing we need to preserve from the source portal are the users and roles. We plan to re-apply the business package for SRM 5.0 after the migration is completed. We are not using any Collaboration Rooms.
    I know there is a migration path from EP6 SP2->EP6 SP9(NW04), followed by an upgrade from NW04->NW04s.
    My question is:
    - is it possible to export content from EP6SP2 and import it into NW04/MW04s?  this will eliminate the complicated migration path from EP6 SP2 to NW04.

    Hi,
    As long as you only need to transport PCD content, I would recommend using normal PCD transport (just did an upgrade from EP6 SP2 to NW04 SP13 and used normal PCD transport without any problems. Will do the same for another upgrade to NW04s). Only if you have KM content you are forced to use the migration tools.
    I am not quite sure about users and role migration since I've only use LDAP as a user store (we manually repeated the AD group to portal role mapping since there were very few)
    There was a conf call on this, but the only reference I can find now is https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/supplemental_docs/prtl204.pdf
    Dagfinn

  • Portal runtime error : com.sap.portal.pcm.Title

    Hi All
    I have  the problem in the Portal , in time  whe I open the portal y all tabs there are  this message:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 12:29_12/02/09_2357150
    Refer to the log file for details about this exception.
    And I found this information  in the logs
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.navigation.CollaborationNavTree of Portal Component com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation because: Could not instantiate implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 35 more
    Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.activityreportingframework
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:415)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:507)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 39 more
    And in this time  I have a problem  in deployment the EP server SP16.
    I don't Know  What's the problem exactly??
    thanks
    Danny

    Hi Shrikant thanks for your answer
    I solved this problem with these  notes:
    Activity Data Collector on NW04
    SAP Note Number: 1178889
    Activity Data Collector stops generating files
    SAP Note Number: 1251041
    Thanks  I will hope this help someone
    Danny

  • Upgrade 6.40 to 7.01 Error

    Hi,
    I am running a SAP Netweaver upgrade from 6.40 to 7.01. I have made the preparation and now running the upgrade part. But I keep getting an error.
    The steps that fails is "Deploy_Online". With this error:
    Feb 13, 2010 11:19:11... Info: Starting the process server0
    Feb 13, 2010 11:48:52... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Feb 13, 2010 11:48:52... Error: Aborted: development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0103.20081105085346.0000'/'11', grouped by :
    SDM could not start the J2EE cluster on the host chpsqld01! The online deployment is terminated.
    A timeout has occured while ensuring that process server0 is in final state.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    As I can read from the error, the cluster is not getting started, so I have checked SAP MMC, along with the upgrade and the step that hangs is "STARTING APPS", so I have tried fixing this, but no luck.
    I have applied note 891905.
    I have changed the MaxApplicationThreadCount to 100.
    The first error I got were related to the component ADSSAP, so I tried removing this component from deploy list, and when the upgrade is complete, I will deploy this component. BUT now I am getting error on another component.
    Do I have the possibility to set a parameter, saying that the cluster should not start the app?
    Or is there another possibility?
    BR
    Kim Kjelgaard

    Hello Kim,
    Its by design that SDM either expects the server to be in completely started state ('Running' status) or completely stopped state.
    Anything in between, SDM will hang indefinitely for the server to go up. So in a case like yours, you could give it a try to redeploy the offline components first by shutting down the server. For the online deployments, SDM will try to restart the server. If it still hangs in 'Starting applications', the best way is to take threaddumps as per note 710154 and check using the threaddump viewer what is causing the hang. Is it exhaustion of the threads or thread blockage waiting on some action! You can find more info about threaddumpviewer @
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2015bb75-a9da-2910-e0b1-c5ba9fe90012?quicklink=index&overridelayout=true
    Also, one tip for SDM redeployment, its always good to select option 3 on the deployment screen which says 'upgrade regardless of sca/sda version'
    SafeMode means the applicaitons are not started during the server startup. This is done during the upgrade when the engine is put in the safemode to avoid long startups. So, the application start forbidden is just indicating that the application was not started due to that mode. Doesn't indicate any error with the application as such.
    To check for the startup errors, please check std_server* from <j2ee engine>/work & defaultrace file in server<n>log always. You can get hints from here.
    Hope the above helps.
    Regards,
    Snehal Bhaidasna
    SAP Labs, Palo Alto, CA(USA)

  • Portal runtime error while selecting page layout in WPC editor

    Hello,
    in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
    The logfile shows the following :
    #1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
    [EXCEPTION]
    #1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
    usr
    sap
    EPD
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.netweaver.bc.util
    lib
    bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
    (source unavailable)
    1 error
    I have the same by clicking on "check assignments"
    Any help ?
    Thanks

    Hello Jego.
    We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
    As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
    Best regards,
    Aliaksandr Zhukau

  • BI Admin Cockpit - Portal Runtime Error

    Hi,
    We have BI 7.0 (NW 7.0 with EHP1) BI_CONT 704. It is a dual stack (ABAP+JAVA) installation.
    We have deployed "BI Administration 1.0" on the java stack. All the configurations are done as per notes.
    Error is faced when trying to access BI Admin cockpit from portal.
    When we click on BI Administration -> Data Load Status it should load two selector iViews in the left hand pane but it gives error.
    Error message is given below:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 03:02_06/08/10_0022_406159550
    Refer to the log file for details about this exception.
    Please help.
    Regards,
    Yaitn

    Default trace is attached herewith:
    #1.5 #001A64594CA200360000001100000CEC00048D20941D9F94#1281070970280#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#A100678#8809##GLBWI741_BC1_406159550#A100678#5c89db70a11711df87a4001a64594ca2#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception ID:03:02_06/08/10_0022_406159550
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : com.sap.portal.layouts.framework.dynNavArea
    Component class : com.sapportals.portal.pb.layout.PageLayout
    User : A100678
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:680)
         at com.sapportals.portal.pb.layout.PageLayout.doContent(PageLayout.java:82)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
         at com.sapportals.portal.pb.PageBuilder.includeLayout(PageBuilder.java:1038)
         at com.sapportals.portal.pb.PageBuilder.doContent(PageBuilder.java:517)
         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.component.CachablePortalComponent.service(CachablePortalComponent.java:273)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
         at com.sapportals.portal.navigation.DynamicNavigationArea.doContent(DynamicNavigationArea.java:65)
         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(Native Method)
         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:534)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:116)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 31 more
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2215)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
         ... 34 more
    #1.5 #001A64594CA200360000001300000CEC00048D20941DA66C#1281070970280#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#A100678#8809##GLBWI741_BC1_406159550#A100678#5c89db70a11711df87a4001a64594ca2#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error##Java###03:02_06/08/10_0022_406159550
    [EXCEPTION]
    #1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2215)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:680)
         at com.sapportals.portal.pb.layout.PageLayout.doContent(PageLayout.java:82)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
         at com.sapportals.portal.pb.PageBuilder.includeLayout(PageBuilder.java:1038)
         at com.sapportals.portal.pb.PageBuilder.doContent(PageBuilder.java:517)
         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.component.CachablePortalComponent.service(CachablePortalComponent.java:273)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
         at com.sapportals.portal.navigation.DynamicNavigationArea.doContent(DynamicNavigationArea.java:65)
         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(Native Method)
         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:534)
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2206)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:680)
         at com.sapportals.portal.pb.layout.PageLayout.doContent(PageLayout.java:82)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
         at com.sapportals.portal.pb.PageBuilder.includeLayout(PageBuilder.java:1038)
         at com.sapportals.portal.pb.PageBuilder.doContent(PageBuilder.java:517)
         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.component.CachablePortalComponent.service(CachablePortalComponent.java:273)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
         at com.sapportals.portal.navigation.DynamicNavigationArea.doContent(DynamicNavigationArea.java:65)
         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(Native Method)
         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:534)

  • Portal Runtime Error while checking the Transaction in Portal

    Hi all,
    We r in the phase of setting the configuration of Portal. We did the the template installer but when iam checking the transactions in Portal ( System Administration--> Support--->SAP Apllication) , it is throwing me the following error.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Missing Property 'ClassName' in property file for layer'Transaction/WinguiSSOLayer'..
    See the details for the exception ID in the log file
    Can anybody help me in this regard.
    Thank in Advance.

    Hi Niyati,
    I guess check through -->
    Under "Personalize > User Profile" the checkbox "Activate Accessibility Feature" must be unchecked!
    as, people earlier also faced this issue and SAP provided this solution.
    Also an alternative solution for this is like --
    Go to:
    <Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\property\Transaction
    and see the content of the 'WebGuiSSOLayer.properties' file.
    One of the entries is ''ClassName'. The value on a 'valid' portal is: com.sapportals.portal.sapapplication.itsdetection.ITSDetectionLayer
    If it's not the case, then go to:
    <Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
    rename the file 'com.sap.portal.appintegrator.sap.par.bak' to 'com.sap.portal.appintegrator.sap.par' open the par file and edit the file ''WebGuiSSOLayer.properties' (add the relevant entry for ClassName).
    Save the file (still with the par extension)
    Restart the portal (if everything is OK then the bak extension will be added to the filename).
    Just try this, hope it works.
    Reward points if helpful
    Regards,
    Shailesh Nagar
    Edited by: Shailesh Kumar Nagar on Jan 22, 2008 7:16 AM

Maybe you are looking for

  • How do i get my recordings and pictures back...? help..!!

    previously had sucess with soft start up... but it is done for this time... i plug it in, it shows me the motorola icon, then shows my battery percentage... no matter how long it has charged from a wall charger... it quickly goes to five, ten and str

  • ABAP dump when running an ALV report in a portal

    Hi,   I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.   When the report is run in the portal, I get a runtime

  • HT4818 I have a new IMac with an external disk drive, it won't instal bootcamp

    I have a new IMac with an external disk drive, it won't instal bootcamp because the windows 7 disk in the mac drive is the wrong format.. how do I instal bootcamp with windows 7 from the disk I have?

  • Cannot access precision editor in iMovie 10.0.5

    I am using iMovie 10.0.5 and am in the timeline of a new project and would like to preserve the length of my movie after adding transitions. I hace double clicked on the space between each clip and there is a visual change and the option to close pre

  • Xs engine throws "No successful authentication possible"

    Hi, I'm a new to HANA & SAP platform, I've launched my HANA instance in AWS and i'm trying to create xsjs application, I've built the application and it's deployed in HANA box. i've followed the procedure specified in below URL. https://help.hana.ond