Issue in portal after abap stack upgrade

Hi,
Except travel and expenditure, everything is working fine after abap stack upgrade.  we have restarted abap and portal 3-4 times, we use abap ume. we are  getting error:
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 18:57_27/02/12_0004_16184750
defaulttrace:
\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     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)
     ... 29 more
#1.5 #00144FF922BF006B00000028000021AF0004B9F256577D3A#1330350388639#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#J2EE_ADM_EDJ#73##ERPDEV_EDJ_16184750#J2EE_ADM_EDJ#d2df5090614511e1cbb100144ff922bf#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###07:16_27/02/12_0004_16184750
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #00144FF922BF006A0000001E000021AF0004B9F25959F274#1330350439133#com.sap.mw.jco#sap.com/tcwddispwda#com.sap.mw.jco#ESSEMP2#288##ERPDEV_EDJ_16184750#ESSEMP2#907dd803614911e1968500144ff922bf#SAPEngine_Application_Thread[impl:3]_6##0#0#Info##Plain###[WD JCO API] WebDynproExtension.addClientPool(SAP_R3_SelfServiceGenerics_ESSEMP2_EN_useSSO_(J2EE16184700)ID1578814350DB10044082816827940554End_9513223) with lang 'EN' and languages vector {EN,EN}#
#1.5 #00144FF922BF0062000016D7000021AF0004B9F26C7D264E#1330350760207#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Plain###Error! The following problem(s) occurred  during request processing:#
#1.5 #00144FF922BF0062000016D9000021AF0004B9F26C7D286A#1330350760208#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
#1.5 #00144FF922BF0062000016DB000021AF0004B9F26C7D2DAC#1330350760209#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
[EXCEPTION]
#1#Request failed due to failure of child requests
     at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
     at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
     at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
     at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
     at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
#1.5 #00144FF922BF006200001777000021AF0004B9F26FD235FC#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following problem(s) occurred  during request processing:#
#1.5 #00144FF922BF006200001779000021AF0004B9F26FD23863#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
Please check CBS service parameters against manual.#
#1.5 #00144FF922BF006600001720000021AF0004B9F26FFE4EC5#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following problem(s) occurred  during request processing:#
#1.5 #00144FF922BF006600001722000021AF0004B9F26FFE50DC#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
Please check CBS service parameters against manual.#
#1.5 #00144FF922BF005F0000179B000021AF0004B9F2714FA0E9#1330350841110#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Plain###Error! The following problem(s) occurred  during request processing:#
#1.5 #00144FF922BF005F0000179D000021AF0004B9F2714FA2FC#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
#1.5 #00144FF922BF005F0000179F000021AF0004B9F2714FA854#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
[EXCEPTION]
#1#Request failed due to failure of child requests
     at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
     at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
     at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
     at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
     at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
cbs.5:
#1.5 #00144FF922BF006E00009D0900000EEE0004B9E196C2E0E9#1330278454976#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF006E00009D1100000EEE0004B9E196C49580#1330278455088#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF006E00009D1900000EEE0004B9E196C664FD#1330278455207#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF006E00009D2100000EEE0004B9E196C81B65#1330278455319#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
#1.5 #00144FF922BF00310000000000000DA90004B9F0155B9416#1330340708455#/Applications/CBS/Administration##com.sap.tc.cbs.service.CBSFrame#######SAPEngine_System_Thread[impl:5]_82##0#0#Info#1#com.sap.tc.cbs.service.CBSFrame#Java###Starting CBS service on node ...#1#16184750#
Pls suggest

Hi James Bond
From the exception above, it can be seen that the AppIntegrator iView is trying to run on the "SAP_LocalSystem" where it should be running on a "real" backend system.
Please check what is the System alias in this iView and make sure it points on a backend system which has the same alias in the Portal System landscape.
Hope that helps,
Robin Hood.

Similar Messages

  • WebDynpro ABAP application issue from Portal after ECC 6 upgrade to SP14

    Hi,
       We have recently upgraded the Kernel, ABAP and Java stack of ECC 6.0 system to SP14. After the upgrade most of the WebDynpro ABAP applications doesn't load and just flickers when run from Portal as a WebDynpro iView, but they run perfectly fine when accessed directly using URL. These were running fine prior to the upgrade. Can someone suggest what can be going wrong.
       Will reward points for helpful answer.
    Regards
    Mukesh

    Hi Mukesh,
    As Gajendra said, restarting the service in SICF sometimes works for us, but not always.  We have also had to deactivate the entire Webdynpro node, and then reactivate it and all of the services below it.
    Obviously something changed in the SP, given that we now have to do this every time we create a new WDA application.
    Cheers,
    John

  • Dialogue instance not starting up after performing stack upgrade.

    Dear Experts,
    We have performed stack upgrade on ERP 6.0 EHP5 system. In configuration phase we have not got the option to update dialog instances.
    We proceeded without that option and completed the upgrade successfully but the dialog instance is not getting started.
    Kernel level got upgraded in all instance with the same level. Below  is the work process log content of dialog instance.
    Loading DB library '/usr/sap/MMD/D10/exe/dboraslib.so' ...
    M  *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/MMD/D10/exe/dborasli
    b.so") FAILED
      "I/O error mapping in '/usr/sap/MMD/D10/exe/dboraslib.so'."  [dlux.c       445
    B  *** ERROR => Couldn't load library '/usr/sap/MMD/D10/exe/dboraslib.so'
    [dbcon.c      5768]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 008192) [thxxhead.c   1519]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thx
    xhead.c   11532]
    As per SUM guide we need to uninstall the dialog instances before downtime and re-install the dialog instances after upgrade but we didn't uninstalled dialog instances before downtime.
    Kindly let me know if there is any other process start up the dialog instance with out going for re-installing it.
    Also suggest on re-installing the dialog instance since we didn't uninstalled dialog instances before downtime.
    Thanks,
    Bharath.

    Dear Divyanshu,
    Please find the work process log of dialog instance.
    trc file: "dev_w0", trc level: 1, release: "721"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      all, MJ
    M sysno      04
    M sid        MMD
    M systemid   274 (HP (IA-64) with HP-UX)
    M relno      7210
    M patchlevel 0
    M patchno    300
    M intno      20020600
    M make       single threaded, Unicode, 64 bit, optimized
    M profile    /sapmnt/MMD/profile/MMD_D10_msdprd
    M pid        266
    M
    M 
    M Fri Oct  3 02:46:33 2014
    M  kernel runs with dp version 139000(ext=121000) (@(#) DPLIB-INT-VERSION-139000-UC)
    M  length of sys_adm_ext is 592 bytes
    M  ThStart: taskhandler started
    M  ThTHPInit: thp initialized
    M  ThInit: initializing DIA work process W0
    M  ***LOG Q01=> ThInit, WPStart (Workp. 0 1 266) [thxxhead.c   1349]
    M  ThInit: running on host msdprd
    M  calling db_connect ...
    B  Loading DB library '/usr/sap/MMD/D10/exe/dboraslib.so' ...
    M  *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/MMD/D10/exe/dboraslib.so") FAILED
      "I/O error mapping in '/usr/sap/MMD/D10/exe/dboraslib.so'."  [dlux.c       445]
    B  *** ERROR => Couldn't load library '/usr/sap/MMD/D10/exe/dboraslib.so'
    [dbcon.c      5768]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 008192) [thxxhead.c   1519]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11532]
    M 
    M  Info for wp 0
    M 
    M    pid = 266
    M    severity = 0
    M    status = 0
    M    stat = WP_NEW
    M    waiting_for = NO_WAITING
    M    reqtype = DP_RQ_DIAWP
    M    act_reqtype = NO_REQTYPE
    M    req.req_info =
    M    req.tid = -1
    M    req.uid = 4294967295
    M    req.mode = 255
    M    req.len = 0
    M    req.rq_id = 65535
    M    req.rq_source =
    M    last_tid = 0
    M    last_uid = 0
    M    last_mode = 0
    M    locked semaphores (), locking ()
    M    act_cs_count = 1
    M    csTrack = 0
    M    csTrackRwExcl = 0
    M    csTrackRwShrd = 0
    M    mode_cleaned_counter = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    attachedVm = no VM
    M 
    M  ThIErrHandle: current request:
    M 
    M  -IN-- sender_id ?                 tid  -1    wp_ca_blk   -1      wp_id -1
    M  -IN-- action    -                 uid  -1    appc_ca_blk -1      type  -   
    M  -IN-- new_stat  NO_CHANGE         mode 255   len         0       rq_id -1
    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   867]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  302]
    sapcpe.log of dialog instance
    2014/10/03 02:45:39
    sapcpe version UC: @(#) $Id: //bas/721_REL/src/ccm/sapstart/sapxxcpe.c#21 $ SAP
    Command line:
      0: /usr/sap/MMD/SYS/exe/run/sapcpe
      1: pf=/sapmnt/MMD/profile/MMD_D10_msdprd
    Trace level (profile): 1
    ** INFO:    Try to find file table sapcpeft (default:sapcpeft)
    ** INFO:    Try to find file table in the central directory /usr/sap/MMD/SYS/exe/run/sapcpeft
    ** INFO:    Found file table: /usr/sap/MMD/SYS/exe/run/sapcpeft
    source: /usr/sap/MMD/SYS/exe/run
    target: /usr/sap/MMD/D10/exe
    Checking the files in the file table for copy type
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/db4cncl is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/dbdb2slib.so is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/dbdb2slib9.so is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/dbdb2slibx.so is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/dbdb4slib.so is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/dbinfslib.so is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/dbsldb4ccm.so is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/libsecude.so is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/setdb4pwd is not existing and status -copy when file exists- is set
    ** INFO:    file /usr/sap/MMD/SYS/exe/run/xdnxdaapi.so is not existing and status -copy when file exists- is set
    ** INFO:    no extern File-List defined. Look for the default File-List(s).
    Checking File-List(s).
    ** INFO:    File-List "/usr/sap/MMD/SYS/exe/run/instance.lst" exists.
    ** INFO:    File-List "/usr/sap/MMD/SYS/exe/run/instancedb.lst" exists.
    ** INFO:    File-List "/usr/sap/MMD/SYS/exe/run/tools.lst" does not exist.
    ** INFO:    File-List "/usr/sap/MMD/SYS/exe/run/inhouse.lst" does not exist.
    ** INFO:    File-List "/usr/sap/MMD/SYS/exe/run/dbclient.lst" does not exist.
    ** INFO:    File-List "/usr/sap/MMD/SYS/exe/run/igsexe.lst" exists.
    ** INFO:    File-List "/usr/sap/MMD/SYS/exe/run/sapcrypto.lst" does not exist.
    Current list file: see table below
    ActualizeLocalFileOrDir: instance.lst (FPM:0x0)
    ActualizeLocalFile: instance.lst
    ActualizeLocalFileOrDir: sapmanifest.mf (FPM:0x0)
    ActualizeLocalFile: sapmanifest.mf
    ActualizeLocalFileOrDir: saproot.sh (FPM:0x0)
    ActualizeLocalFile: saproot.sh
    ActualizeLocalFileOrDir: scsclient.lst (FPM:0x0)
    ActualizeLocalFile: scsclient.lst
    ActualizeLocalFileOrDir: j2eeinst.lst (FPM:0x0)
    ActualizeLocalFile: j2eeinst.lst
    ActualizeLocalFileOrDir: sapmanifestj2ee.mf (FPM:0x0)
    ActualizeLocalFile: sapmanifestj2ee.mf
    ActualizeLocalFileOrDir: scs.lst (FPM:0x0)
    ActualizeLocalFile: scs.lst
    ActualizeLocalFileOrDir: webdispinst.lst (FPM:0x0)
    ActualizeLocalFile: webdispinst.lst
    ActualizeLocalFileOrDir: gateway.lst (FPM:0x0)
    ActualizeLocalFile: gateway.lst
    ActualizeLocalFileOrDir: disp+work (FPM:0x1)
    ActualizeLocalFile: disp+work
    *** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/disp+work -> /usr/sap/MMD/D10/exe/disp+work (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: rsyn.bin (FPM:0x1)
    ActualizeLocalFile: rsyn.bin
    ActualizeLocalFileOrDir: ABAP.pad (FPM:0x1)
    ActualizeLocalFile: ABAP.pad
    ActualizeLocalFileOrDir: aci_ABAP.pad (FPM:0x1)
    ActualizeLocalFile: aci_ABAP.pad
    ActualizeLocalFileOrDir: aci_ABAP.gram (FPM:0x1)
    ActualizeLocalFile: aci_ABAP.gram
    ActualizeLocalFileOrDir: R3trans (FPM:0x1)
    ActualizeLocalFile: R3trans
    *** ERROR: CopyFile: write <dst> failed: -1 <> 1030984, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/R3trans -> /usr/sap/MMD/D10/exe/R3trans (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: R3ta (FPM:0x0)
    ActualizeLocalFile: R3ta
    *** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/R3ta -> /usr/sap/MMD/D10/exe/R3ta (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: R3check (FPM:0x0)
    ActualizeLocalFile: R3check
    *** ERROR: CopyFile: write <dst> failed: -1 <> 704256, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/R3check -> /usr/sap/MMD/D10/exe/R3check (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: tp (FPM:0x0)
    ActualizeLocalFile: tp
    ActualizeLocalFileOrDir: dipgntab (FPM:0x0)
    ActualizeLocalFile: dipgntab
    *** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/dipgntab -> /usr/sap/MMD/D10/exe/dipgntab (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: saplicense (FPM:0x1)
    ActualizeLocalFile: saplicense
    *** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/saplicense -> /usr/sap/MMD/D10/exe/saplicense (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: saplikey (FPM:0x1)
    ActualizeLocalFile: saplikey
    *** ERROR: CopyFile: write <dst> failed: -1 <> 620472, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/saplikey -> /usr/sap/MMD/D10/exe/saplikey (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: sapcpeft (FPM:0x0)
    ActualizeLocalFile: sapcpeft
    ActualizeLocalFileOrDir: startsap (FPM:0x0)
    ActualizeLocalFile: startsap
    *** ERROR: CopyFile: write <dst> failed: -1 <> 92600, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/startsap -> /usr/sap/MMD/D10/exe/startsap (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: stopsap (FPM:0x0)
    ActualizeLocalFile: stopsap
    *** ERROR: CopyFile: write <dst> failed: -1 <> 92600, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/stopsap -> /usr/sap/MMD/D10/exe/stopsap (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: jdbcconnect.jar (FPM:0x0)
    ActualizeLocalFile: jdbcconnect.jar
    ActualizeLocalFileOrDir: SAPCAR (FPM:0x0)
    ActualizeLocalFile: SAPCAR
    *** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/SAPCAR -> /usr/sap/MMD/D10/exe/SAPCAR (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: rslgsend (FPM:0x1)
    ActualizeLocalFile: rslgsend
    *** ERROR: CopyFile: write <dst> failed: -1 <> 249984, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/rslgsend -> /usr/sap/MMD/D10/exe/rslgsend (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: rslgcoll (FPM:0x1)
    ActualizeLocalFile: rslgcoll
    *** ERROR: CopyFile: write <dst> failed: -1 <> 324120, 28, No space left on device, [sapxxcpe.c:2714]
    *** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/rslgcoll -> /usr/sap/MMD/D10/exe/rslgcoll (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
    ActualizeLocalFileOrDir: gwrd (FPM:0x1)
    Kindly suggest.
    Thanks,
    Bharath.

  • SAP ECC ABAP STACK UPGRADE

    Hi Everyone,
    I am new to this fascinating world of BASIS and to this forum. This is my second post:
    The situation is I need to upgrade the ABAP stack of my ECC 6.0 (dual stack) system from patch level 14 to 17.
    Thus now, what are the things that I should need to consider, that is:
    Do I need any Kernel Upgrade, or individually the component upgrades will do?
    Any SPAM upgrade required?
    Please do reply and if you know any thread having the same question and solutions please give me the URL of it.

    Hi,
    1. For patching the system, ensure you have a complete backup of the system.
    2. Its safer and best to patch the kernel always before starting patching so that your tp and R3Trans are updated.
    3. Patch the tool SPAM to the latest level before starting the patching of the other components.
    4. Now you can patch the rest of the components either individually or put all of them in 1 stack and patch them at 1 go.
    For further info, refer to http://service.sap.com/instguides->SAP Netweaver-> < Release of your system>-> Maintainence-> SP guides.
    Rgds,
    Soujanya

  • BI Reports not working in Portal after SPS 15 upgrade

    Hi,
    We have applied Support Pakage Stack 15 on our BI systems (NW7) and now none of the BI reports in the Portal seems to work anymore.
    We receive the following Portal Runtime error when trying to open any BI report from Portal:
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    No further info is displayed in the log.
    I am thinking it might be possibly due to authorisations.... Has anybody else experienced this issue and have a possible solution?
    Regards,
    CJ

    Hi Radhika,
    The problem was that the BI system was on a higher Support Package Stack level than the Portal. We had to install the same Support Package Stack on the Portal.
    Is this not possibly your issue as well?
    Regards,
    CJ

  • IPhone sync issue with iTunes after Snow Leopard upgrade

    I upgraded to Snow Leopard and since then iTunes does not see my iPhone 3GS and I am unable to sync. I've read the troubleshooting guide to no avail. What am I missing?

    If you are running v10.6.3 as your profile suggests, update to v10.6.8.
    Click your Apple menu / Software Update.
    Restart your Mac after the updates are installed.
    See if iTunes will recognize your iPhone.
    If your software is up to date then try here >  iPhone, iPad, iPod touch: Device not recognized in iTunes for Mac OS X

  • Gmail issues on macbook after mountain lion upgrade

    i recently upgraded my macbook pro to mountain lion, since then i have been having issues with gmail. 
    i have 5 email addresses in mail, some of them functioned whilst others did not.
    i have converted all of the email addresses to imap rather than pop, and this worked yesterday, and messed about with the port numbers using lots of different ones from the original 993, etc. eventually using the 993 for it to work. 
    today, it isn't working.  the ipad i have works fine as does the phone.
    i have been reading that there is some kind of issue, but does anyone know the definitive solution?
    many thanks
    cg

    the macbook works in the apple shop, my sisters, but not at home.  i have sky broadband - any suggestions?

  • Skype issues on ipad2 after ios 7 upgrade

    skype microphone not working after i upgraded to ios7 on ipad 2.Facetime works.Any suggestions?

    Try reset iPad
    Hold down the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears
    Note: Data will not be affected.

  • Font Issue in Safari after Migration Assistant Upgrade

    I just used Migration Assistant to move from an old Mac Pro tower to a new Mac Pro trash can (chose not to transfer Applications) and most everything is fine except for a strange font issue in Safari. Safari doesn't seem to render Helvetica. Instead I get this:
    Chrome seems to render it fine. I was using FontExplorer X to manage fonts on the previous machine so perhaps that is part of the problem (I didn't transfer applications and have not bothered to install it on the new machine yet).
    I tried clearing the font cache and repairing permissions as noted in this article, but no luck. Any ideas? Thanks for any help!

    Applications/Font Book and validate your fonts.

  • Touch ID not responding sometimes,after 7.1 upgrade

    Touch ID not working sometimes.Sometimes its not even try to scan finger, i need to type the passcode to unlock ,but when i try later it will work,And it will stop working again.I tried reseting the phone ,added new finger prints still same issue.Problem started after the software upgrade to 7.1.It was working fine with old version 7.0.x.Somebody help please..
    Regars,
    Tony.

    Hello t0ny,
    It sounds like your Touch ID is not working consistently. I recommend the troubleshooting steps for Touch ID from the article named:
    iPhone 5s: Using Touch ID
    http://support.apple.com/kb/HT5883
    Resolving issues with Touch ID
    Verify that you are using the latest version of iOS.
    Ensure that your fingers and the Home button are clean and dry.*
    Note: Cover the Home button completely. Don't tap too quickly, don't press down hard, and don't move your finger while Touch ID is scanning. Make sure that your finger touches the metal ring around the Home button.
    If you are using a protective case or screen protector, it must leave the Home button and the surrounding ring completely unobscured. If it doesn't, remove the case or screen protector and try again.
    Tap Settings > General > Touch ID & Passcode > Touch ID and verify that:
    iPhone Unlock or iTunes & App Store is enabled.
    One or more fingerprints have been enrolled.
    If one finger isn't working, tap Edit in Settings > General > Touch ID & Passcode > Touch ID > Edit to delete and then reenroll the finger.
    If that finger still isn't working, try enrolling a different finger.
    If you are unable to enroll any of your fingers, take your iPhone 5s to an Apple Retail Store, Apple Authorized Service Provider, or contact AppleCare for further assistance.
    * Moisture, lotions, sweat, oils, cuts, or dry skin may affect fingerprint recognition. Certain activities can also temporarily affect fingerprint recognition, including exercising, showering, swimming, cooking, or other conditions or changes that affect your fingerprint.
    Thank you for using Apple Support Communities.
    Regards,
    Sterling

  • Unable to log into the portal-After Upgrade from NetWeaver 7.0 to 7.3EHP1

    Dear Experts,
    We have poltal landscape(NW 7.0 Dualstack SPS27) with our customozed themes and par files(Company name,logos and colours)
    Recently we upgraded the one of portal from NW 7.0 to NW 7.3EHP1 . Upgrade has been successfilly completed with small issue.
    After upgrade all urls are working(/nwa, /sld) except /irj/portal.We know that NW 7.3 EHp1 accepts only ear file i.e we converted the our customized log on par file to ear file through par migration tool and the same was deployed successfully through NWDS 7.3 version.After deploying we are able to access the
    /irj/portal url with our customized par(means ear file) without issues,
    We are unable to log into the portal after giving the correct user id and password,getting the portal runtime error as foloows.
    Portal runtime error
    An exception occured while processing your request.Send the exception ID your administrator
    Exception id:
    see log files for details about this exception
    Default.trc log file(/server0/log)
    #EP-PIN-PRT#tc~epbc~prtc~api#C00061FD2733006C00000005000056CB#9034950000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.
    runtime#J2EE_ADMIN#4##43E00B85A79911E380F800000089DCC6#3a483a0fa79911e3903000000089dcc6#3a483a0fa79911e3903000000089dcc6#0#Thread[HTTP Worker
    [@900472845],5,Dedicated_Application_Thread]#Plain##
    08:14_09/03/14_0005_9034950
    [EXCEPTION]
    java.lang.RuntimeException: Could not create Resource Repository root folder in PCD
    at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:140)
    at com.sap.portal.resource.repository.ResourceRepositorySrv.init(ResourceRepositorySrv.java:93)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
    at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
    at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
    at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
    at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
    at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
    at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
    at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
    at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
    at com.sap.portal.resource.repository.WebResourceRepositorySrv.init(WebResourceRepositorySrv.java:71)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
            at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
            at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
            at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
            at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
            at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
            at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
            at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
            at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
            at com.sap.portal.resource.repository.WebResourceImportService$ResourceImporter.<init>(WebResourceImportService.java:248)
            at com.sap.portal.resource.repository.WebResourceImportService.importApplicationResources(WebResourceImportService.java:172)
            at com.sapportals.portal.navigation.NavigationMimeRepositoryService.loadAllPicsToWRR(NavigationMimeRepositoryService.java:186)
            at com.sapportals.portal.navigation.NavigationMimeRepositoryService.init(NavigationMimeRepositoryService.java:160)
            at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
            at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
            at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
            at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
            at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
            at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
            at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
            at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
            at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
            at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
            at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
    at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
            at com.sap.portal.pcm.iview.admin.PcmIviewCommon.getAdditionalAttributes(PcmIviewCommon.java:358)
            at com.sap.portal.pcm.iview.admin.PcmIviewCommon.initLayers(PcmIviewCommon.java:173)
            at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:177)
            at com.sap.portal.pcm.page.admin.AdminBasePage.getCustomImplementation(AdminBasePage.java:76)
            at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:642)
            at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:143)
            at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:171)
            at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.prepareAttributes(PhaseConfiguration.java:71)
            at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.storeRelatedAttributesInSharedStorage(PhaseConfiguration.java:35)
            at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doFrameworkPhase(NavigationFpmListener.java:535)
            at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doPhase(NavigationFpmListener.java:122)
            at com.sapportals.portal.pb.fpm.FPMContainer.distributeEvent(FPMContainer.java:63)
            at com.sapportals.portal.pb.fpm.FPM.doDocumentHook(FPM.java:179)
            at com.sapportals.portal.prt.service.document.DocumentHookMulticaster.doDocumentHook(DocumentHookMulticaster.java:100)
            at com.sapportals.portal.prt.service.document.DocumentHookService.doDocumentHook(DocumentHookService.java:119)
            at com.sapportals.portal.prt.service.document.DocumentHookServiceNew.doDocumentHook(DocumentHookServiceNew.java:186)
            at com.sapportals.portal.prt.connection.PortalHook.doDocumentHook(PortalHook.java:665)
            at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:183)
            at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
            at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
            at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:206)
            at com.sapportals.portal.navigation.PortalLauncher.doContent(PortalLauncher.java:116)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
            at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
            at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
            at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: javax.naming.InvalidNameException: Character not allowed: ':' in 'pcd:resource_repository'
    at com.sapportals.portal.pcd.pl.PcdName.checkComponent(PcdName.java:64)
            at com.sapportals.portal.pcd.pl.PcdName.checkNameComponent(PcdName.java:39)
            at com.sapportals.portal.pcd.pl.PcdName.padd(PcdName.java:636)
            at com.sapportals.portal.pcd.pl.PcdName.add(PcdName.java:626)
            at com.sapportals.portal.pcd.gl.util.StringUtils.tokenizeIntoPcdName(StringUtils.java:112)
            at com.sapportals.portal.pcd.pl.PcdName.appendUrlInternal(PcdName.java:408)
            at com.sapportals.portal.pcd.pl.PcdName.<init>(PcdName.java:245)
            at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:121)
            ... 132 more
    1)We are suspecting this issue is related to the theme issue.How to update the theme in the upgraded portal(have a backup of themes)
    2)Want to know if we update a theme where it stored at the operating system level(in NW 7.3 EHP1 as well as NW 7.0)
    3)Is there any post steps after portal upgrade.
    Request you suggest.
    Regards
    Maruthi

    Hi
    Refer the SAP Notes
    1942399 - Fix usage of unregistered class loader while processing HTTP request in an application being updated or stopped at the same time
    1744820 - Migration 7.3 fails while executing migration of pcd_upgrade
    1703578 - WPC migration stops during connection creation
    1918086 - ERROR: Unable to get iView
    Regards
    Ram

  • Warning message in portal after upgrade

    There are warning messages coming in web reports after upgrade to 7.31. In trace we could find the message " The unique is bbeleno is not valid" . Anyone has any input? pls help

    Does this warning happen to all web reports?
    This doesn't look like a reporting error message. Are you sure "bbeleno" is not a user that has been defined for some background connection between the ABAP and JAVA stacks? Check in SU01D to see if that bbeleno might be incorrectly set as a system user, or if it is used in the RFC connections between ABAP and JAVA.
    You say you get the warning in RSRT but was it executed on the ABAP stack ? You can try using RSRT2 and click on ABAP for that.

  • What are the pros and cons of installing java+abap stack for portal?

    Hi all,
      1.What are the pros and cons of installing java+abap stack for portal?
      2.what effect it does on the ume options to be choosen??
      3.for the purpose of integration of r3,bw and crm on portal and crm 4.0 60.2.3 business package which option of stack(java or abap or both)will be good option and which ume option while installation should be choosen?
    regards
    Rajendra

    Hi Rajendra,
    The NetWeaver Installation Master Guide offers some good scenarios on the pros and cons:
    https://websmp201.sapag.de/~sapidb/011000358700005412792005E.pdf
    In a nutshell:
    ABAP+JAVA
    Pros
    - Decrease # of servers required to administer the portal
    - Less costly
    Cons
    - Upgrades could be dependent on ABAP and Java release level
    - Additional load on the server due to ABAP stack
    - Limited scalability
    JAVA and ABAP on separate server
    Pros
    - Improved performance
    - Allows each system to be single-use purpose therefore downtime does not affect other components
    - More scalable
    Cons
    - Adds complexity to landscape
    - Additional costs
    Regards,
    Thomas Pham

  • Issue in registering ABAP stack into SLD

    Hi all
    The issue is as shown below. I appreciate your help.
    Environment: SLD host-Windows Server 2003, Oracle 10g, WAS JAVA 640 SP19
    CRM ABAP+JAVA 640 host - unix, Oracle
    I was able to register CRM JAVA stack in SLD from Visual Administrator>SLD Data Supplier. The CIM Client Test was successfull.
    When i try to register the CRM ABAP stack from tcode RZ70, i get an error as below:
    SLD DS start program
        0: sapsrm_CRM_05                             : Execute program: SLDAPPL_SERV
        0: sapsrm_CRM_05                             : Execute program: SLDBCSYS
        0: sapsrm_CRM_05                             : Execute program: SLDCLIENT
        0: sapsrm_CRM_05                             : Execute program: SLDCOMPSYS
        0: sapsrm_CRM_05                             : Execute program: SLDDBSYS
        0: sapsrm_CRM_05                             : Execute program: SLDGWSRV
        0: sapsrm_CRM_05                             : Execute program: SLDINSTSC
        0: sapsrm_CRM_05                             : Execute program: SLDINSTSP
        0: sapsrm_CRM_05                             : Execute program: SLDIPSERV
        0: sapsrm_CRM_05                             : Execute program: SLDMSGSRV
        0: sapsrm_CRM_05                             : Execute program: SLDASSOC
        0: sapsrm_CRM_05                             : Collection of SLD data finished
        0: sapsrm_CRM_05                             : Data collected successfully
        0: sapsrm_CRM_05                             : RFC data prepared
        0: sapsrm_CRM_05                             : Used RFC destination: SLD_UC
        0: sapsrm_CRM_05                             : RFC call failed: / CPIC-CALL: 'ThSAPECMINIT' : cmRc=17 thRc=236#SAP gateway connection failed. Is SAP gateway started?
        0: sapsrm_CRM_05                             : Existing periodic jobs removed. Number: 1
        0: sapsrm_CRM_05                             : Program scheduled: 20080506 222324
        1: sapsrm_CRM_05                             : Event-controlled job already exists; scheduling not necessary
    I came to know from other forums in sdn that we need to install/configure separate gateway if the SLD is on a standalone JAVA engine.
    Also, in SM59 SLD_UC, SLD_NUC, SAPSLDAPI are failing with the same error of "RFC call failed: / CPIC-CALL: 'ThSAPECMINIT' : cmRc=17 thRc=236#SAP gateway connection failed. Is SAP gateway started?"
    Please suggest how to resolve this. Please let me know if you need more details.
    Thanks already
    Edited by: Rahul Paul Patchigondla on May 6, 2008 9:57 AM

    Rahul,
    as RK already stated: the SLD has to connect to an SAP gateway, such is running on an ABAP system.
    You may initially try to use the SAP gateway from the CRM ABAP stack. Therefore you will have to adjust the SLD to use that SAP gateway. On 6.40 SLD: Administration / Data supplier bridge / RFC gateway: Server (host name) and Service (combination of sapgw and instance number of CRM ABAP system).
    After that, in CRM SM59 SLD_UC, SLD_NUC, SAPSLDAPI will have to be adjusted accordingly.
    Regards, Boris

  • Portal language refresh / reload (user data source ABAP stack)

    Hello,
    I'm on SAP NetWeaver Portal 7.0 with user data source on ABAP stack.
    I'm trying to create simple JavaScript links for changing the Portal language.
    I was able to change the ABAP stack user's logon language by BAPI call.
    But the newly set language shows up only after the user logs out and logs in again.
    I know that in the WebDynpro for Java, which implements the UME user interface, there is a functionality, that allows that relogging of the user is not necessary. After setting the language you only refresh the browser page (F5) and the new language shows up.
    Does anyone know what function I should call, for the language refresh (could be the same as in UME standard WDJ)?

    Hi Andres,
    language doesn't change on the Portal. The content remains in the previous language.
    I know that the switching of Logon language parameter in the user profile in ABAP stack and logoff and login on the portal leads to change of the language on the Portal. But I don't know, how to do it without the relogging of the user.
    I change the Logon language in ABAP by AJAX call of BAPI.
    Thank you for any idea.
    Jiri

Maybe you are looking for