Runtime Error Purchasing BI Content initial setup

Hi all,
I'm trying to setup Purchasing BI Content and i have the dump error during the initial setup in T-Code "OLI3BW" Statistical setup of info structures from purchasing documents.
"Runtime Errors COMPUTE_BCD_OVERFLOW
Except. CX_SY_ARITHMETIC_OVERFLOW
Short text
Overflow during the arithmetical operation (type P) in program "SAPLMCEX02"."
Thanks.

Hi,
Check
SAP notes: 1165576 and 1176819
Thanks
Reddy

Similar Messages

Runtime error while creating applicent initial data in PB10

Dear friends,
       in initial data entry in reruitment in PB10 once i complete the entry of data in organization assignment.it is going into ABAP runtime error.
Trigger Location of Runtime Error
    Program                               SAPLHRAC
    Include                                 LHRACU05
    Row                                     390
    Module type                         (FORM)
    Module Name                        READ_IT_FROM_DB
Short text
    Exception condition "INFTY_NOT_FOUND" raised.
can any help me how to resolve this issue.
Thanks in advance,
Regards,
sai prasad

Hi Revathi,
    With reference to your responce i have checked pb04. all that i found is it is not taking the number range that i have assigned in NUMAP feature it is taking other number range.
How should i go further with this.
Regards,
sai prasad

Display Infocube Content produces Runtime Errors = TIME_OUT

Hi,
Upon trying to display content of an InfoCube (200 records only), I received the following error:
Runtime Errors         TIME_OUT
Date and Time          13.12.2007 11:16:24
Short text
Time limit exceeded.
What happened?
     The program "CL_SQL_RESULT_SET=============CP" has exceeded the maximum
      permitted runtime without
     interruption and has therefore been terminated.
Error analysis
     After a specific time, the program is terminated to make the work area
     available to other users who may be waiting.
     This is to prevent a work area being blocked unnecessarily long by, for
     example:
     - Endless loops (DO, WHILE, ...),
     - Database accesses with a large result set
     - Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
     parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
      time limit is
     exceeded, the system attempts to cancel any running SQL statement or
     signals the ABAP processor to stop the running program. Then the system
     waits another 60 seconds maximum. If the program is then still active,
     the work process is restarted.
Trigger Location of Runtime Error
    Program                                 CL_SQL_RESULT_SET=============CP
    Include                                 CL_SQL_RESULT_SET=============CM006
    Row                                     32
    Module type                             (METHOD)
    Module Name                             NEXT_PACKAGE
Source Code Extract
Line SourceCde
2 *
    3 * Fetches the next bulk of rows into an internal table.
    4 *
    5
    6   DATA:
    7     sql_code       TYPE i,
    8     sql_msg        TYPE dbsqlmsg.
    9
   10   FIELD-SYMBOLS:
   11     <line> TYPE ANY,
   12     <outtab> TYPE STANDARD TABLE.
   13
   14
   15   IF me->cursor = c_invalid_cursor.
   16 *   result set has already been closed
   17     RAISE EXCEPTION TYPE cx_sql_exception
   18       EXPORTING invalid_cursor = 'X'.
   19   ENDIF.
   20
   21 * check that a reference to the output table has been set by
      22 * a preceeding call of SET_PARAM_TABLE; in this case the attribute
   23 * LINE_REF contains a reference to a data structure of the
   24 * table's line type
   25   IF me->itab_ref IS INITIAL.
   26     RAISE EXCEPTION TYPE cx_parameter_invalid
   27           EXPORTING parameter = 'ITAB_REF'.
   28   ENDIF.
   29   ASSIGN me->itab_line_ref->* TO <line>.
   30   ASSIGN me->itab_ref->* TO <outtab>.
   31
>>>>>   CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL'
   33                        ID 'FCODE'    FIELD c_fcode_next_package
   34                        ID 'CONNAME' FIELD me->con_ref->con_name
   35                        ID 'CONDA'    FIELD me->con_ref->con_da
   36                        ID 'CURSOR'   FIELD me->cursor
   37                        ID 'BOUND'    FIELD me->outvals_bound
   38                        ID 'OUTVALS' FIELD me->parameters->param_tab
   39                        ID 'OUTTAB'   FIELD <outtab>
   40                        ID 'LINE'     FIELD <line>
   41                        ID 'UPTO'     FIELD upto
   42                        ID 'ROWCNT'   FIELD rows_ret
   43                        ID 'SQLCODE' FIELD sql_code
   44                        ID 'SQLMSG'   FIELD sql_msg.
   45
   46   IF sy-subrc = 0.
   47 *   some rows fetched
   48     ADD rows_ret TO rows_fetched.
   49
   50 *   set the OUTVALS_BOUND flag; this avoids "reassignement" of the
   51 *   output variables the next time this method is called, i.e. the
Can someone help me to solve this problem. Thanks!

Hi,
Chk the below line from the dump in line 3 - 'Fetches the next bulk of rows into an internal table'
what that error means is the volume which u r trying to view is beyond the size of the internal table buffer and because of that it is leading to a dump.
As the previous reply suggests try to increase the size of table buffer which will help you display much larger volumes.
Selection of fewer columns would be much quicker and easier to analyse data quickly.
Regards

Runtime error during automatic purchase order

Dear Experts,
While i am trying to post automatic purchase order through tcode MB01..system is showing an run time error.
Runtime error RAISE_EXCEPTION
Date and Time 06/09/2009 14:26:03
hort dump has not been completely stored (too big)
Short text
Exception condition "WRONG_PARAMETERS" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
Error analysis
A RAISE statement in the program "SAPLGLT2" raised the exception
condition "WRONG_PARAMETERS".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
Program SAPLGLT2
Include LGLT2F07
Row 19
Module type (FUNCTION)
Module Name G_BEB_MOVE_ACCIT_TO_STRING
rce Code Extract
e SourceCde
*1 ----*
*2 * Created by : SAP* **
*3 * Date : 25.02.2007 **
*4 * Time : 10:01.44 **
*5 ----*
*6 * This Report is generated by Report RGUGGLT0 **
*7 ----*
8
9 IF I_LEDGER = SPACE.
10 RAISE WRONG_PARAMETERS.
11 ELSEIF SY-MANDT = '800' AND I_LEDGER = 'SP'.
12 IF NOT i_accit-GSBER IS INITIAL.
13 E_SPLIT+000000(000004) = I_ACCIT-GSBER .
14 ENDIF.
15 E_PARTNER+000000(000004) = I_ACCIT-PARGB .
16 E_BALANCE+000000(000004) = I_ACCIT-GSBER .
17 E_SPL_PAR+000000(000004) = I_ACCIT-GSBER .
18 ELSE.
>> RAISE WRONG_PARAMETERS.
20 ENDIF.
Kindly help me please. Because of this, i cant able to post.
Regards,
Prasath

Hi,
go to transaction snote in your system and press ctrl + F8 to download the sapnote 985672.
then go through the instructions in the note and implement it in the system.
As per the note corrections you need to do below depicted changes in the function module.
$$----
$$
$ Correction Inst.         0120031469 0000514577                     $
$ Req. Corr. Instructions 0120031469 0000486230 Note 0000942542     $
$----$
$ Valid for       :                                                  $
$ Software Component   SAP_APPL   R/3 Standard                       $
$ Release 500          To SAPKH50014                                $
$$----
$$
*& Object          FUNC G_BEB_BALANCE_DOC
*& Object Header   FUGR GLT0
*& FUNCTION G_BEB_BALANCE_DOC
      IF ld_baldoc_part <> xon.
     find items with partner assignment is set.
        CALL FUNCTION 'G_BEB_MOVE_ACCIT_TO_STRING'
          EXPORTING
*>>>> START OF DELETION <<<<<
            i_ledger = id_ledger
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
            i_ledger = ld_ledger
*>>>> END OF INSERTION <<<<<<
Don't do it manually when you will implement the note it will take care of corrections by itself.
KR Jaideep,

Purchase order runtime error

Hi ,
while creating purchase order iam getting an error of the following.can any body resolve this issue.
Runtime Errors         SYNTAX_ERROR
Date and Time          08.07.2008 10:26:23
Short dump has not been completely stored (too big)
Short text
Syntax error in program "SAPLV61A ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLMEVA" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLV61A " in include "RV63A992
" in
line 17:
"The Dictionary structure or table "ZRC_MKT_PRICE" is either not active"
" or does not exist."
The include has been created and last changed by:
Created by: "DAVIS "
Last changed by: "DAVIS "
Error in the ABAP Application Program
The current ABAP program "SAPLMEVA" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
The following syntax error was found in the program SAPLV61A :
"The Dictionary structure or table "ZRC_MKT_PRICE" is either not active"
" or does not exist."
Trigger Location of Runtime Error
Program                                 SAPLMEVA
Include                                 LMEVAU08
Row                                     55
Module type                             (FUNCTION)
Module Name                             ME_LOAD_VARIANTS_PRICING
Source Code Extract
Line
SourceCde
25
ENDIF.
26
*--> Initialisieren
27
*--> not necessary anymore (Raimond Buchholz)
28
CALL FUNCTION 'CUD0_CONFIGURATION_INITIALIZER'.
29
*--> Preisteile der Varianten besorgen
30
CALL FUNCTION 'CEI0_GET_CONDITIONS'
31
EXPORTING
32
INSTANCE    = I_CUOBJ
33
APPLICATION = 'MM'
34
TABLES
35
             CONDITIONS = T_VCKEY.                 "del 194053
36
CONDITIONS = T_VCKEY                   "ins 194053
37
exceptions                                   "ins 194053
38
error_message = 01                     "ins 194053
39
others         = 02.                    "ins 194053
40
*--> Preisteile der Varianten mit Belegnummer versorgen
41
LOOP AT T_VCKEY.
42
T_VCKEY-KAPPL = 'M '.
43
T_VCKEY-VBELN = I_EBELN.
44
T_VCKEY-POSNR = I_EBELP.
45
MODIFY T_VCKEY.
46
ENDLOOP.
47
ENDIF.
48
49
*--> Preisteile der Varianten an Preisfindung übergeben
50
*- pricing_load_variant_key muß auch bei Positionen ohne Konfiguration
51
*- laufen, da die Logik im PRICING zu 4.0 umgestellt wurde
52
IF I_NO_LOAD IS INITIAL.
53
DATA: I_POSNR LIKE VBAP-POSNR.
54
I_POSNR = I_EBELP.
>>>>>
CALL FUNCTION 'PRICING_LOAD_VARIANT_KEYS'
56
EXPORTING
57
APPLICATION = 'M '
58
VBELN       = I_EBELN
59
POSNR       = I_POSNR
60
TABLES
61
TVCKEY      = T_VCKEY
62
EXCEPTIONS
63
OTHERS      = 1.
64
ENDIF.
65
66
ENDFUNCTION.

Hi Friend,
I thnik the table is created in another server and it is not still transported to the current server, where u are executing PO.
Please check in SE16N, the table is exist or not.
Regards
Krishnendu

Content Copier - MS Visual C++ Runtime Error

Hi I have searched through the posts for Nokia PC Suite and have failed to see any issues that remotely resemble mine. These are my setup details: Phone: Nokia 6255 Cable: CA-53 PC Suite: 6.81.13.0 PC: Windows XP SP2 - all latest patches Upon finally getting a genuine Nokia cable (believe me cheaper cables just don't work) i've have been able to get PC Suite to connect to my Nokia 6255. I am able to browse the contacts, and keep a connection to the phone. However I am unable to even run the Backup option from the PC Suite. When Content Copier tries to load I get the splash screen then Content Copier runs saying connected to phone. A few seconds after that I then get a Microsoft Visual C++ Runtime Library error. Runtime error! Program: C:\Program Files\Nokia\Nokia PC Suite 6\ContentCopier.exe This application has requested the runtime to terminate in an unusual way. Please contact the application's support team for more information. Pressing OK button terminates the program leaving me back at the Nokia PC Suite. Any ideas people? By the looks of it my PC is looking for some types of runtime files but which ones? Shouldn't they all be contained and installed as part of the installation of PC Suite? Regards Ken

Do you have any other issues?
When I click on Settings in Synchronise, nothing happens
When I click Synchronise, nothing happens.
When I connect my phone through InfraRed, i get an error "PC Suite does not recognise the connected phone. The Serial Number of the phone is invalid. Switch off your phone, switch it on, andry again"
I can view my Contacts etc through the Nokia Phone Browser.

Runtime error Raise Exception Initial Product Catalog Replication

Dear All,
We are on CRM ISA MSA 5.0 SP8 & Trex 7 SP 30. Ours is a 3 system landscape. CRM Dev, Q, & P. Recently we added a new system in the landscape for Intergration Testing purpose. and its called as CRI which is a copy of the production Crm box.
I did all the post installation activitiese and did all Connections (sm59, srmo) between Trex and CRM. After the connection was made, the RFC, SSR are all working fine.
I did the settings in spro for the product catalog replication, created the ssr and then did a initial replication without document and it worked fine. I then did a replication with documents, I am getting a runtime error, RAISE_EXCEPTION. All the connections between the crm and trex box are working fine. everything is pinging, the FTP user has all the access on the IMS_DOCS_A5C folder.
Can someone please let me know what the issue could be?
Awaiting a postive response.
Thanks in advance.
Warm Regards,
Rajeet Mathur

Hi Rajeet,
The intitial replication transports product catalog data (for example, product items or text) to the index server. You can replicate all or individual product catalog variants. The replicated product catalog contents are transferred from the index server to the Web server. The product catalog contents are then available in the E-Commerce application. Multimedia objects are transferred from the product catalog to the Knowledge Provider Content Server and are subsequently published on the Web server.
As you said that after you put in the documents the repliaction gives a runitme error, I beleive the replication to the contect server is giving problems.
1. Have you created templates for folder and assigned them to the catalog types for the attachement of documents.
2. While replication are you specifying the Publishing computer ID with the checkbox transfer Document content ticked.
Check in these details.
Regards,
Shalini Chauhan

Portal Runtime Error while creating new system in portal content

Hi
Can anyone solve my problem, i am geting error while creating new system in p ortal content
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file

Hi,
Check this link for creating system object
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
Regards
Arun

Portal Runtime Error --- Portal content is not opening

Hello Experts,
While logging to the system we are getting this message
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/every_user/general/defaultDesktop/frameworkPages/frameworkpage/com.sap.portal.toolAreaiView
Component Name : com.sap.portal.navigation.toolarea.default
The exception was logged. Inform your system administrator..
Exception id: 10:13_02/04/09_0039_12182150
See the details for the exception ID in the log file
How to resolve the issue ??
Moreover we are unable to drill down the portal content in portal content page. It is in "loading " status for long time. Is there any problem.
Regards,
Partha

Hi Sandeep
" You have to log in as an Administrator when using the NOTE referred in the previous post "
--> Yes, I am logged as Administrator user
"I hope you are using your FQDN instead of IP address"
--> Yes i am using FQDN
1. When was the last time you portal was working fine?
--> Till yesterday , today morning while checking the day to day activity I found the issue
2. What changes have you done?
--> We didn't change anything in production portal, it is a satnd alone JAVA stack but we have made some some changes in backend R3 system which is a diffrent system on different server
FYI ---> We are facing the problem with portal content not expanding for quite a long time.
3. Which portal version and which sp level are you on?
--> EP 7.0 and SP11
4. Which browser are you using for your portal?
--> IE 6.X
Thanks for your help.
Thanks and regards,
Partha

Runtime Error when accessing KM Content

Hi Everyone,
I am getting Runtime Error when accessing KM Content through Content Administration/KM Content.
See the below error information.
Runtime Error
An exception occured while processing the request.
Additional information: String index out of range: -28
Exception ID = 00a67a58-06f5-2b10-b997-9edccc061ca6
What could be the problem.
Any help will be appreciated.
thank you
regards
sunil

hi Romano
Here is the log trace file text.
#1.5#001321C84B3300A304DC7AFD00001D50000465605028DB15#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651182th#
#1.5#001321C84B3300A304DC7AFF00001D50000465605028DBEB#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B0100001D50000465605028DCB3#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B0200001D50000465605028DE21#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B0400001D50000465605028DF04#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651183th#
#1.5#001321C84B3300A304DC7B0600001D50000465605028DFDA#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B0800001D50000465605028E0A1#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B0900001D50000465605028E1FE#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B0B00001D50000465605028E2DF#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651184th#
#1.5#001321C84B3300A304DC7B0D00001D50000465605028E3B5#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B0F00001D50000465605028E473#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B1000001D50000465605028E5D8#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B1200001D50000465605028E6B9#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651185th#
#1.5#001321C84B3300A304DC7B1400001D50000465605028E798#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B1600001D50000465605028E856#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B1700001D50000465605028E9AD#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B1900001D50000465605028EAA5#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651186th#
#1.5#001321C84B3300A304DC7B1B00001D50000465605028EB87#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
regards
sunil

Portal runtime error in Purchasing in ESS

Hello,
After logging in to the portal, when I go to Employee Self-Services -> Purchasing, which ever option (Shop, Confirm Goods / Services, Check Status) I click, I get a portal runtime error as shown below:
#1.5 #005056803084006B00000039000000FC0004638903CCAF24#1235340032299#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#smagan#23907##KSCEPD.esr.cri.nz_EPD_3051250#smagan#f667c1b0012b11deb880005056803084#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/System/Server#Java###Exception ID:11:00_23/02/09_0004_3051250
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_purchasing/com.sap.pct.erp.ess.purchasing_services/com.sap.pct.erp.ess.purchasing_service
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : smagan
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/<IAC[SAP_ITS_NAMESPACE]>?sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&DisconnectOnClose=0&DesignBaseUrl=<LAF.BaseUrl[url_ENCODE]>&~design=<LAF.Theme[url_ENCODE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 121. 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:123)
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
Working Time, Timesheet, Personal Information, Pay Statement works perfectly. The error happens only in the case of Purchasing. I am new to ESS, so any help in this regard would be highly appreciated.
Thanks,
Ajay

Hi Bala,
It is happening for all users. I checked the authorizations in the backend. The roles assigned to the user has the following authorizations: S_RFC, S_SERVICE, S_TCODE, S_DATASET, S_TABU_DIS, S_WF_WI, P_TRAVL, PLOG, P_ABAP, P_ORGIN, P_ORGINCON, P_ORGXXCON, P_PCLX, P_PERNR, P_TCODE, M_BANF_BSA, M_BANF_EKG, M_BANF_EKO, M_BANF_WRK, M_BEST_BSA, M_BEST_EKG, M_BEST_EKO, M_BEST_WRK.
In portal the user is assigned the ESS and Standard portal user role.
The transaction ST22 shows the following:
    The user "TESTUSER9" has no RFC authorization for the function group
    "SDIFRUNTIME". Please contact your system administrator to give you
    the RFC authorization for the required function groups (such as "SDIFRUNTIME").
    The RFC authorization object is S_RFC.
Thanks,
Ajay

Portal Runtime Error when operating "Portal Content"

Hi there,
these days, I installed a NW710 in our team server, and try to configure its UWL to one backend system. Therefore I need to create a new system entry from "System Administration->System Configuration->Portal Content->New->System(from template)".
After a few test, I found I can't do these operations: "add folder", "open properties", "open permissions", "new system", I got following runtime error when I clicked them:
If anybody encounter the similar issue? great appreciate your clues!
<b>Portal Runtime Error</b>
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
The object found is not an IView: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.portal.wd_portal_content/com.sap.portal.admin.studio.configuration/actions/new/com.sap.portal.action.newFolder/com.sap.portal.WDfolderWizard.
Exception id: 02:22_30/05/07_0030_708183150
See the details for the exception ID in the log file
<b>Detail Trace:</b>
Exception ID:01:32_30/05/07_0014_708183150
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: The object found is not an IView: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_admin_ws/com.sap.portal.system_configuration/com.sap.portal.admin_studio_system_landscape/com.sap.portal.admin.studio.configuration/actions/new/com.sap.portal.action.newFolder/com.sap.portal.WDfolderWizard
at com.sap.portal.prt.core.PortalJNDIHelper.getPropertyContentProvider(PortalJNDIHelper.java:101)
at com.sap.portal.prt.component.PortalComponentContextFactory.createPortalComponentContext(PortalComponentContextFactory.java:159)
at com.sap.portal.prt.component.PortalComponentContextFactory.getPortalComponentContext(PortalComponentContextFactory.java:82)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:513)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:194)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:145)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:417)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:280)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:393)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:382)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:66)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:304)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:215)
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:137)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)

Hi,
Were u able to do the operations before the UWL configuration? There is possibility that it would have been caused because of improper configurations also.
Regards,
Vijai

Unexpected error during initial setup

An exepected error occurs during the initial set of my time capsule. I've unplugged and replugged the modem and time capsule, what do I try next?

Do the setup in complete isolation.. Plug the TC into the computer by ethernet.. do a factory reset and start again.
Is the Lion OS correct?
If so you can use the older v5 utility which is often better.
What version TC is it?

KM iviews, KM Content, Index Administration showed Portal Runtime error

Hi Experts,
We recently tried migrating our BI production portal to new hardware. The Portal version was not changed just it was migrated from one server to another. After migration the portal restarted properly but the KM iviews, KM Content and Index Administration showed "Portal Runtime Error".
We restarted the portal several times but still the same. Also the KM services were running.
We had migrated the BI development portal in similar manner couple of months back but it did not showed any such error. It was successful in first attempt.
Can anyone please suggest what must have gone wrong and how can this be corrected? Is there any monitoring or tracing tool we can use to check this. Please suggest.
Thanks & Regards,
Seema Rane.

Hi Ricardo , Lorcan,
Thank you for the prompt reply. Following is the default trace I found on the server:
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: sap.com/com.sap.netweaver.coll.appl.room', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: sap.com/com.sap.netweaver.coll.appl.room
     at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:527)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4367)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:589)
     ... 46 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: SAPJ2EE::sap.com/xappscprxrpmui~collroomint', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: SAPJ2EE::sap.com/xappscprxrpmui~collroomint
     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:888)
     at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:511)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [ExternalApplicationItem.prepare]: SAPJ2EE::sap.com/xappscprxrpmui~collroomint
     at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:188)
     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:232)
     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.start(SAPJ2EEApplicationItem.java:192)
     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getAndStartExternalApplication(Mediator.java:132)
     at com.sap.portal.prt.sapj2ee.StartPortalApplication.coreRun(StartPortalApplication.java:59)
     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:884)
     ... 49 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.coll.appl.room
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:180)
     ... 54 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.coll.appl.base
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 55 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.kmc.people
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 56 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.application
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 57 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.main
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 58 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.repository.filter
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 59 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.service.base
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 60 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.protocols.ice
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 61 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.protocols.webdav
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 62 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.bc.rf.service
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 63 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:signature_lib
     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
     ... 64 more
Caused by: com.sapportals.portal.prt.core.broker.SAPJ2EELibraryNotFoundException: Could not find Library SAPJ2EE::library:signature_lib
     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)
I guess the KM applications are not being found. How do I correct this? Our KM repository is connected to BI and has got lot of BI content in it.
Will redeploying the com.sap.km.applications.par file help?
Please provide some solution so that this error will be resolved without effecting the KM Content.
Thanks & Regards,
Seema Rane

Why does content.setLayout() generate runtime error?

Hi all.
Can some guru please explain to me why this code is generating following runtime error:
java.lang.Error: Do not use SampleView.setLayout() use SampleView.getContentPane().setLayout() instead
     at javax.swing.JApplet.createRootPaneException(Unknown Source)
     at javax.swing.JApplet.setLayout(Unknown Source)
This is the top level TopLevelMenu.java which calls SampleView.java
public void init()
    // java code
    public void actionPerformed(ActionEvent aevt)
        SampleView sampleview = new SampleView(); // <-- OKAY so far
}And here is the snippet for SampleView.java
public class SampleView extends JApplet
    public SampleView()
      Container content = getContentPane();
      content.setLayout(newBorderLayout()); // <-- RUNTIME ERROR HERE
}Instead of just correcting my code, could you please explain to me what is wrong with it?
TIA :-)

Thanks, but that was a typo, I'm still getting this runtime error!
I tried several different ways e.g.
public void init()
    Container content = getContentPane();
    JPanel headerPane = new JPanel(new BorderLayout());
    SampleView sampleview = new SampleView();
    headerPane.add(sampleview, BorderLayout.NORTH);
    content.add(headerPane);
public SampleView()
// etc
return;
}throws the same runtime error! Very puzzled!

Runtime Error Purchasing BI Content initial setup

Similar Messages

Maybe you are looking for