Problems: Runtime Error, Uncaught Exception.  Please Help!

Hi I am using an online blog called BLOG CMS (www.blogcms.com) which runs on my website server. I use it to update my website with news, etc. The program uses a javascript WYSIWYG text editor based on http://www.fckeditor.net/
However, when the BLOG CMS program tried to load the WYSIWYG text editor, I get the following errors:
LINE: 36
Char: 2046
Error: Access is denied.
URL: http://mysite.com/nucleus/plugins/wysiwyg/editor/fckeditor.html?InstanceName=more&Toolbar=Default
Runtime error has occurred.
Line: 35
Do you wish to debug?
Error: Access Denied (sometimes it says, permission denied)
Error: uncaught exception: Permission denied to set property Window.FCK_STATUS_NOTLOADED
Error: uncaught exception: Permission denied to get property HTMLDocument.getElementById
I already have the latest version of Javascript, I am running IE 6.0 on Windows XP so I have no idea what is causing the error and I would greatly appreciate your help if possible. My webserver is reputable and configured correctly since it is running on iPowerWeb and the correct versions of PHP, MySQL, etc.
Thanks in advance for your help and I am looking forward to your replies!
Ryan :)

Ryan,
This looks like a permission problem (even though its free, some kind of authentication might be there). You can contact the site administrator.
Regards,
Chandra

Similar Messages

  • Runtime error--can someone please help me?!

    ok so when i try to open my itunes (i have itunes 7) it opens but almost immediately a window pops up that says "software application has encountered a problem and needs to close. we are sorry for the inconvenience." it also says that they prepared an error report to send to microsoft about the problem. i've tried sending it but nothing has happened so now i click the "don't send" option. then a window pops up titled "Microsoft Visual C++ Runtime Library" and it says "Runtime Error! Program: C:\Program Files\iTunes\iTunes.exe This application has requested the Runtime terminate it in an unusual way. Please contact the application's support team for more information." i've tried uninstalling quicktime and then repairing iTunes but that doesn't fix it. i don't know what else to do. can someone please help me?!

    NoClassDefFoundError happens because the JVM cannot find some class from your program, not because the OS cannot find your JVM (PATH regulates the latter, but not the former). JVM looks up classes in directories (or JAR files) specified through the -classpath option, like "java -classpath c:\myclasses MyMainClass". Read the online doc for the "java" launcher for more info.

  • HT1443 I can't open iTunes. My PC gives a runtime error R6034. Please help !

    I was updating my Quicktime i guess. There was a internet problem and i couldn't finish the update. After i got everytime a Runtime Error with the code R6034. I delete iTunes and Quicktime from my laptop and install them again but still i can't open iTunes on my laptop. Anyone has a idea to sowl this problem?
    THX

    Quicktime is no longer a required component of iTunes. I would uninstall that and then fix the start-up issue with the following...
    Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (later)
    Remove all of these items in the following order:
    iTunes
    Apple Software Update
    Apple Mobile Device Support (if this won't uninstall move on to the next item)
    Bonjour
    Apple Application Support
    Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
    The uninstall and reinstall process will preserve your iTunes library and settings, but ideally you would back up the library and your other important personal documents and data on a regular basis. See this user tip for a suggested technique.
    Please note:
    Some users may need to follow all the steps in whichever of the following support documents applies to their system. These include some additional manual file and folder deletions not mentioned above.
    HT1925: Removing and Reinstalling iTunes for Windows XP
    HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
    tt2

  • ýesterday  my iphone 5c screen  suddendly  shows connect to itune and i try to restore it using itune but halfway i got a message error occured (14). please help me in solving this problem.

    ýesterday  my iphone 5c screen  suddendly  shows connect to itune and i try to restore it using itune but halfway i got a message error occured (14). please help me in solving this problem.

    what did you learn when you search the internet for iPhone error 14?

  • TS1368 I have a problem downloading music i have bought off of iTunes. It says unknown error 502. Please help.

    I have a problem downloading music i have bought off of iTunes. It says unknown error 502. Please help.

    Hello Matthew,
    Thank you for the details of the issue you are experiencing with the iTunes Store.  I recommend continuing with the steps in the following article:
    iTunes: Advanced iTunes Store troubleshooting
    http://support.apple.com/kb/TS3297
    Thank you for using Apple Support Communities.
    Best,
    Sheila M.

  • TS3376 I was able to use the findmyiphone app last week, but now I have been getting an error message "Can't load findmyiphone.  There was a problem loading the application."  please help as we are trying to locate an ipod with pics of a no deceased loved

    I was able to use the findmyiphone app last week, but now I have been getting an error message "Can't load findmyiphone.  There was a problem loading the application."  please help as we are trying to locate an ipod with pics of a no deceased loved one.

    Had the same problem and the same message --  was suddenly unable to access icloud apps on my pc, also using Windows 7 and Internet Explorer. After several days of pulling my hair out, decided to try a different browser and was able to get in by using Firefox instead of Internet Explorer.  Hope this helps. 

  • In SCM 5.0 Runtime Errors: DBIF_DSQL2_SQL_ERROR Exception: CX_SY_NATIVE_SQ

    Hi,
    I am getting following shortdump in my SCM 5.0 system with LiveCache 7.6.03 on AIX 5.3.
    Please help me.
    Runtime Errors         DBIF_DSQL2_SQL_ERROR
    Exception              CX_SY_NATIVE_SQL_ERROR
    Date and Time          01.07.2008 09:20:09
    Short text
    An SQL error occurred when executing Native SQL.
    What happened?
    The error "-4016" occurred in the current database connection "LCA".
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    How to correct the error
    Database error text........: "POS(1) Unknown procedure
    name:SIM_SIMSESSION_GET_ACTIVE"
    Database error code........: "-4016"
    Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE""
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU23"
    "/SAPAPO/OM_SIMSESSION_GET_ALL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", or its possible occurrence must
    be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    System environment
    SAP-Release 700
    Application server... "dewall43"
    Network address...... "10.40.16.43"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "00C912FC4C00"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 14
    Shortdump setting.... "full"
    Database server... "dewall43"
    Database type..... "ORACLE"
    Database name..... "APO"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Jan 23 2008 21:25:00"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 144
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 1117168
    EM...... 0
    Heap.... 0
    Page.... 24576
    MM Used. 720672
    MM Free. 376056
    User and Transaction
    Client.............. 100
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "48692ABF23D6012AE10080000A28102B"
    Program............. "/SAPAPO/SAPLOM_CORE"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "/SAPAPO/SAPLOM_CORE" - in
    "/SAPAPO/OM_SIMSESSION_GET_ALL".
    The main program was "/SAPAPO/OM_DELETE_OLD_SIMS ".
    In the source code you have the termination point in line 39
    of the (Include) program "/SAPAPO/LOM_COREU23".
    The program "/SAPAPO/SAPLOM_CORE" was started as a background job.
    Job Name....... "/SAPAPO/OM_DELETE_OLD_SIMSESS"
    Job Initiator.. "DDIC"
    Job Number..... 08200801
    The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
    in
    procedure "/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", but it was neither
    handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "/SAPAPO/SAPLOM_CORE "; its source code begins in
    line
    1 of the (Include program "/SAPAPO/LOM_COREU23 ".
    Source Code Extract
    Line
    SourceCde
    9
    *"     REFERENCE(ET_ACTIVE_SIMSESSION) TYPE  /SAPAPO/OM_SIMSESSION_TAB
    10
    *"     REFERENCE(ET_RC) TYPE  /SAPAPO/OM_LC_RC_TAB
    11
    *"  EXCEPTIONS
    12
    *"      LC_CONNECT_FAILED
    13
    *"      LC_COM_ERROR
    14
    *"      LC_APPL_ERROR
    15
    16
    17
    data_def.
    18
    create_gen_com_params_default.
    19
    CLEAR ls_gen_com_params-client.
    20
    21
    Verbindung zum liveCache aufbauen
    22
    start_function 'OM_SIMSESSION_GET_ALL'.                   "#EC *
    23
    check_server.
    24
    connect_to_livecache.
    25
    IF et_simsession IS REQUESTED.
    26
    COM-Routine zum Auslesen aller trans. Sim.
    27
    EXEC SQL.
    28
    EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ALL" (
    29
    IN  :LS_GEN_COM_PARAMS,
    30
    OUT :LV_RC,
    31
    OUT :ET_SIMSESSION)
    32
    ENDEXEC.
    33
    Returncodes pruefen und evtl. Exception raisen
    34
    lv_subrc_sav = sy-subrc.
    35
    ENDIF.
    36
    IF et_active_simsession IS REQUESTED.
    37
    COM-Routine zum Auslesen aller aktiven trans. Sim.
    38
    EXEC SQL.
    >>>>>
    EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE" (
    40
    IN  :LS_GEN_COM_PARAMS,
    41
    OUT :LV_RC,
    42
    OUT :ET_ACTIVE_SIMSESSION)
    43
    ENDEXEC.
    44
    Returncodes pruefen und evtl. Exception raisen
    45
    lv_subrc_sav = sy-subrc.
    46
    ENDIF.
    47
    48
    end_performance_measure.
    49
    end_function_no_main om_simsession_get_all.
    50
    check_returncodes.
    51
    if iv_get_testguids = gc_false.
    52
    delete ET_ACTIVE_SIMSESSION where table_line cs '~'.
    53
    delete ET_SIMSESSION        where table_line cs '~'.
    54
    endif.
    55
    ENDFUNCTION.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Periodic Deletion of Hanging Simulation Versions
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080701
    SY-UZEIT
    092008
    SY-XPROG
    RSDBRUNT
    SY-XFORM
    %_INIT_PBO_FIRST
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    3 FUNCTION     /SAPAPO/SAPLOM_CORE                 /SAPAPO/LOM_COREU23                    39
    /SAPAPO/OM_SIMSESSION_GET_ALL
    2 FUNCTION     /SAPAPO/SAPLOM_CORE                 /SAPAPO/LOM_COREU12                    52
    /SAPAPO/OM_SIMSESSION_SELECT
    1 EVENT        /SAPAPO/OM_DELETE_OLD_SIMS          /SAPAPO/OM_DELETE_OLD_SIMS             67
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       3 Ty.          FUNCTION
    Name  /SAPAPO/OM_SIMSESSION_GET_ALL
    IV_GET_TESTGUIDS
    X
    0
    0
    5
    8
    ET_ACTIVE_SIMSESSION
    Table IT_9[0x44]
    \FUNCTION=/SAPAPO/OM_SIMSESSION_SELECT\DATA=LT_SIMSESSION
    Table reference: 2
    TABH+  0(20) = 0000000000000000000000000000000000000000
    TABH+ 20(20) = 0000000200000009000000000000002CFFFFFFFF
    TABH+ 40(16) = 04000021000026C00010249401800000
    store        = 0x0000000000000000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 2     (0x00000002)
    label        = 9     (0x00000009)
    fill         = 0     (0x00000000)
    leng         = 44    (0x0000002C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000192
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    ET_RC
    Table[initial]
    ET_SIMSESSION
    Table[initial]
    OM_LC_NAME
    LCA
    000000000000000000000000000000
    000000000000000000000000000000
    444222222222222222222222222222
    C31000000000000000000000000000
    GC_OM_SYSUBRC
    -16842752
    F
    E
    SY-SUBRC
    0
    0000
    0000
    %_SPACE
    0
    0
    2
    0
    %_VIASELSCR
    0
    4
    OM_LC_APPL_NAME
    000000000000000000000000000000
    000000000000000000000000000000
    222222222222222222222222222222
    000000000000000000000000000000
    SPACE
    0
    0
    2
    0
    LS_GEN_COM_PARAMS
    DDIC                                 # /SAPAPO/OM_DELETE_OLD_SIMS
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222444422222222222222222222222222222222202254545424454444545444554452222222
    0000000000000000000000449300000000000000000000000000000000000F31010FFFDF45C545FFC4F39D30000000
    LV_RC
    00
    00
    00
    00
    GC_OM_SPP_FORECAST_EXT
    K
    4
    B
    GC_IMMEDIATE_TRANSFER
    65537
    0
    0
    GC_RESOURCE_MULTI
    16909060
    0
    1
    GV_SIMSESSION_TYPE
    0
    0
    2
    0
    OM_MEASURE_PERFORMANCE
    0
    0
    2
    0
    GC_OM_OBJECT_OUTPUT_NODE
    454827294
    1
    B
    OM_AS_KEY
    000000000000000000000000000000
    000000000000000000000000000000
    222222222222222222222222222222
    000000000000000000000000000000
    %_DUMMY$$
    0000
    0000
    2222
    0000
    No.       2 Ty.          FUNCTION
    Name  /SAPAPO/OM_SIMSESSION_SELECT
    IV_MIN_AGE_IN_HOURS
    1
    0000
    0001
    IV_SAVED_INCLUSIVE
    0
    0
    2
    0
    ET_OMS_VERSION
    Table[initial]
    ET_SIMSESSION_DELTA
    Table[initial]
    SCREEN
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GC_OM_RPM_PORD_DEL
    2004
    000D
    0074
    GC_OM_OBJECT_UNKNOWN
    66051
    0
    0
    GC_OM_OBJECT_ORDER
    16909060
    0
    1
    GS_OMS_VERSION
    00000000                      ########
    000000000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000000C
    222222222222222222222233333333222222222222222222222200000000
    000000000000000000000000000000000000000000000000000000000000
    GC_MINTIME
    09011000
    1700002C
    GT_OMS_VERSION
    Table[initial]
    GC_APPLICATION_BLRG
    235868177
    0
    E
    GC_OM_OBJECT_MODE
    50595078
    0
    3
    GC_TRUE
    X
    0
    0
    5
    8
    RSJOBINFO
    00000000000000                                  ##
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GC_OM_OBJECT_RESOURCE
    67438087
    0
    4
    LT_SIMSESSION
    Table IT_9[0x44]
    GC_APPLICATION_CTPE
    168496141
    0
    A
    SY-REPID
    /SAPAPO/SAPLOM_CORE
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454254544454454222222222222222222222
    F31010FF310CFDF3F25000000000000000000000
    GC_APPLICATION_MATP
    185339150
    0
    B
    SYST-REPID
    /SAPAPO/SAPLOM_CORE
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454254544454454222222222222222222222
    F31010FF310CFDF3F25000000000000000000000
    GC_ATP_UPD_RPM
    R
    0
    0
    5
    2
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    VARI
    ###00000000000000      ############
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222200033333333333333222222000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    /SAPAPO/OM_DELETE_OLD_SIMS
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454244544445454445544522222222222222
    F31010FFFDF45C545FFC4F39D300000000000000
    GC_OM_OBJECT_RPM_GENERIC
    791687475
    2
    F
    SY-SUBRC
    0
    0000
    0000
    %_VIASELSCR
    0
    4
    SY-REPID
    /SAPAPO/OM_DELETE_OLD_SIMS
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    2545454244544445454445544522222222222222
    F31010FFFDF45C545FFC4F39D300000000000000
    SY-MSGID
    00000000000000000000
    00000000000000000000
    22222222222222222222
    00000000000000000000
    GC_TRANSPORT
    y
    0
    0
    7
    9
    SPACE
    0
    0
    2
    0
    SY-MSGNO
    000
    000
    000
    333
    000
    SY-MSGV1
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    GC_ITRUE
    16777623
    0
    1
    GC_FALSE
    0
    0
    2
    0
    SYST
    ###############################################################################T########X ####
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000100000000000000000000000000000000000000000000000E000200
    0000000000000000000000000000000000000006000000000000000000000000000000000000010500000001520000
    000001010000010000000000010001000000000A00000000000000000000000000000000000006040000000080000C
    GC_IFALSE
    104192
    0
    0
    GT_OMS_VERSION
    Table[initial]
    GC_MINTIME
    09011000
    1700002C
    GT_SIMS_DELTA
    Table[initial]
    SY-XFORM
    %_INIT_PBO_FIRST
    000000000000000000000000000000
    000000000000000000000000000000
    254445554454455522222222222222
    5F9E94F02FF6923400000000000000
    %_DUMMY$$
    0000
    0000
    2222
    0000
    SCREEN
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Internal notes
    The termination was triggered in function "DsqlErrorHandler"
    of the SAP kernel, in line 2062 of the module
    "//bas/700_REL/src/krn/runt/abexsql.c#2".
    The internal operation just processed is "DSQL".
    Internal mode was started at 20080701092008.
    Internal call code.........: "[DBDS/NEW DSQL]"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = unlimited
    => Core limit      = 4294965248
    => File size limit = unlimited
    => Heap address  = 0x0x1152ede20
    => Stack address = 0xfffffffffff84a0
    => Stack low     =  0xfffffffffff84a0
    => Stack high    =  0xffffffffffff7a0
    => Stack Trace:
         AixStack() at 0x1000c7d94
         CTrcStack2() at 0x1000c7e8c
         rabax_CStackSave__Fv() at 0x1000b2d70
         ab_rabax() at 0x1000af728
         ab_dbdserr__FiPCUsT1T2P9DS_HEADERT2T1Pv() at 0x10057efbc
         DsqlErrorHandler__Fi() at 0x10135b8e8
         ExecuteCall__Fv() at 0x10135b454
         ab_jdsql__Fv() at 0x101356b40
         ab_extri__Fv() at 0x10040d93c
         ab_xevent__FPCUs() at 0x100a9d170
         ab_trigg__Fv() at 0x100a9ce5c
         ab_run() at 0x1014bee48
         N_ab_run() at 0x100d5bca8
         dynpmcal() at 0x100d5aa74
         dynppai0() at 0x100d58a08
         dynprctl() at 0x100d6047c
         dynpen00() at 0x100d52364
         Thdynpen00() at 0x1000e2410
         TskhLoop() at 0x1000e4254
         ThStart() at 0x1000fe324
         DpMain() at 0x10156c770
         nlsui_main() at 0x101a99998
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    /SAPAPO/OM_DELETE_OLD_SIMS
    0
    28.09.2006
    17:13:54
    115712
    E
    1
    Prg
    SAPMSSY0
    1
    07.01.2008
    17:16:23
    92160
    E
    2
    Prg
    SAPMSSYD
    1
    27.09.2006
    18:38:20
    21504
    E
    3
    Prg
    SAPFSYSCALLS
    1
    03.12.2004
    17:45:45
    8192
    E
    4
    Prg
    RSDBRUNT
    0
    07.01.2008
    17:27:13
    254976
    E
    5
    Typ
    RSSCR
    0
    12.10.1999
    15:50:05
    5120
    6
    Prg
    RSDBSPBL
    0
    22.02.2005
    08:58:45
    72704
    E
    7
    Prg
    SAPDB__S
    0
    03.12.2004
    17:45:45
    19456
    E
    8
    Prg
    RSDBSPMC
    0
    27.09.2006
    18:23:16
    79872
    E
    9
    Typ
    DDSHDESCR
    0
    28.11.1997
    16:26:30
    4096
    10
    Typ
    SPPARAMS
    0
    07.03.1997
    14:48:48
    2048
    11
    Prg
    SAPLSABE
    11
    03.12.2004
    17:45:46
    13312
    E
    12
    Prg
    SAPLSECU
    12
    07.01.2008
    17:09:46
    87040
    E
    13
    Typ
    RSSUBINFO
    0
    25.02.2000
    15:47:23
    3072
    14
    Prg
    SAPLSTUP
    14
    07.01.2008
    17:08:20
    74752
    E
    15
    Prg
    SAPLCNDP
    15
    13.12.2007
    16:41:21
    195584
    E
    16
    Prg
    SAPLSCNT
    16
    22.02.2005
    08:58:56
    30720
    E
    17
    Prg
    SAPSHDTV
    16
    31.01.2005
    15:41:11
    33792
    E
    18
    Prg
    SAPFGUICNTL
    1
    22.02.2005
    08:58:14
    24576
    E
    19
    Prg
    SAPLOLEA
    19
    12.12.2007
    14:16:36
    96256
    E
    20
    Prg
    SAPLSGUI
    20
    07.01.2008
    17:16:23
    84992
    E
    21
    Prg
    SAPLSTTM
    21
    28.07.2005
    11:12:25
    69632
    E
    22
    Prg
    SAPLSBDC
    22
    07.01.2008
    17:09:02
    44032
    E
    23
    Prg
    SAPLSFES
    23
    07.01.2008
    17:27:14
    260096
    E
    24
    Prg
    SAPLTHFB
    24
    07.01.2008
    17:16:23
    394240
    E
    25
    Typ
    WPINFO
    0
    08.02.1999
    14:18:32
    6144
    26
    Prg
    SAPLURFC
    26
    07.01.2008
    17:13:39
    22528
    E
    27
    Prg
    SAPLSPLUGIN
    27
    03.12.2004
    17:45:46
    8192
    E
    28
    Typ
    SWCBCONT
    0
    07.10.1997
    12:13:50
    3072
    29
    Typ
    OLE_VERBS
    0
    09.02.1995
    13:23:37
    2048
    30
    Typ
    OLE_PA
    0
    13.01.1995
    11:06:59
    2048
    31
    Prg
    /1BCDWBEN/SAPL/SAPAPO/EN0001
    31
    08.06.2001
    20:33:24
    233472
    E
    32
    Prg
    SAPLSENA
    32
    12.12.2007
    14:18:37
    33792
    E
    33
    Prg
    /SAPAPO/SAPLOM_CORE
    33
    28.07.2005
    16:02:32
    502784
    E
    34
    Prg
    SAPLSAL2
    34
    07.01.2008
    17:15:35
    81920
    E
    35
    Typ
    /SAPAPO/OM_OMS_VERSIONS_STR
    0
    16.02.2006
    18:01:55
    3072
    36
    Prg
    CL_ABAP_CHAR_UTILITIES========CP
    36
    28.07.2005
    11:12:24
    13312
    E
    37
    Prg
    CX_SY_NATIVE_SQL_ERROR========CP
    37
    12.12.2007
    12:39:14
    13312
    E
    38
    Typ
    SCX_SRCPOS
    0
    08.07.2004
    09:59:00
    2048
    39
    Prg
    CX_SY_SQL_ERROR===============CP
    39
    28.07.2005
    11:12:24
    10240
    E
    40
    Prg
    CX_DYNAMIC_CHECK==============CP
    40
    28.07.2005
    11:12:24
    10240
    E
    41
    Prg
    CX_ROOT=======================CP
    41
    12.12.2007
    17:18:15
    11264
    E
    42
    Prg
    CX_NO_CHECK===================CP
    42
    28.07.2005
    11:12:24
    10240
    E
    43
    Prg
    CX_SY_NO_HANDLER==============CP
    43
    28.07.2005
    11:12:24
    10240
    E
    44
    Prg
    %_CSYDES
    0
    22.02.2005
    08:58:46
    8192
    E
    45
    Prg
    %_CSYDB0
    0
    22.02.2005
    08:58:45
    36864
    E
    46
    Typ
    RSVAMEMKEY
    0
    16.12.1996
    19:31:50
    2048
    47
    Prg
    %_CRSDS
    0
    22.02.2005
    08:58:21
    10240
    E
    48
    Prg
    %_CSLIS
    12
    17.02.2006
    08:58:39
    89088
    E
    49
    Typ
    DTC_S_LAYO
    0
    08.06.2001
    15:59:56
    6144
    50
    Typ
    CAT_SVARS
    0
    19.05.2004
    16:00:08
    3072
    51
    Typ
    SYST
    0
    03.12.2004
    17:45:35
    31744
    52
    Typ
    RSJOBINFO
    0
    09.02.1995
    13:25:17
    3072
    53
    Typ
    VARI
    0
    16.12.1996
    19:38:11
    6144
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  /SAPAPO/OM_DELETE_OLD_SIMS
    SYST                                     03.12.2004 17:45:35   00004612
    \0\0\0\0\0\x0001\0\x0001\0\0\0\0\0\x0001\0\0\0\0\0\0\0\0\0
    VARI                                       .  .       :  :     00003052
    Program  /SAPAPO/SAPLOM_CORE
    RSJOBINFO                                  .  .       :  :     00000164

    As per note 1619720, drop following two tables and then validate by running t-code lca03.
    drop table APPSYSNAME
    drop table APPSYSPARAM
    dbmcli -d LCSID -n hostname -u superdba,sdbapassword -uSQL SAPSID,password
    dbmcli on hostname : SID>sql_execute drop table APPSYSPARAM
    OK

  • Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

    Hi All,
    I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
    At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
    ===========================================
    Runtime Errors RAISE_EXCEPTION
    Date and Time 25.07.2008 08:31:11
    Short text 
    Exception condition "METADATA_MISSING" raised. 
    What happened? 
    The current ABAP/4 program encountered an unexpected 
    situation. 
    What can you do? 
    Note down which actions and inputs caused the error. 
    To process the problem further, contact you SAP system 
    administrator. 
    Using Transaction ST22 for ABAP Dump Analysis, you can look 
    at and manage termination messages, and you can also 
    keep them for a long time. 
    Error analysis 
    A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception 
    condition "METADATA_MISSING". 
    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. 
    How to correct the error 
    If the error occures in a non-modified SAP program, you may be able to 
    find an interim solution in an SAP Note. 
    If you have access to SAP Notes, carry out a search with the following 
    keywords: 
    "RAISE_EXCEPTION" " " 
    "SAPLDSVAS_SERV" or "LDSVAS_SERVC7I" 
    "MAP_DSVAS_TT_DATA_TO_TT_25" 
    or 
    "SAPLDSVAS_SERV" "METADATA_MISSING" 
    or 
    "RDSMOP_MAIN " "METADATA_MISSING" 
    If you cannot solve the problem yourself and want to send an error 
    notification to SAP, include the following information: 
    1. The description of the current problem (short dump) 
    To save the description, choose "System->List->Save->Local File 
    (Unconverted)". 
    2. Corresponding system log 
    Display the system log by calling transaction SM21. 
    Restrict the time interval to 10 minutes before and five minutes 
    after the short dump. Then choose "System->List->Save->Local File 
    (Unconverted)". 
    3. If the problem occurs in a problem of your own or a modified SAP 
    program: The source code of the program 
    In the editor, choose "Utilities->More 
    Utilities->Upload/Download->Download". 
    4. Details about the conditions under which the error occurred or which 
    actions and input led to the error. 
    System environment 
    SAP-Release 700 
    Application server... "terra" 
    Network address...... "172.16.1.198" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x Intel 801586" 
    Character length.... 16 Bits 
    Pointer length....... 32 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "TERRA" 
    Database type..... "ORACLE" 
    Database name..... "DSM" 
    Database user ID.. "SAPSR3" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Oct 23 2007 01:07:18" 
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" 
    Database version. "OCI_10201_SHARE (10.2.0.1.0) " 
    Patch level. 133 
    Patch text.. " " 
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." 
    SAP database version. 700 
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows 
    NT 6.0" 
    Memory consumption 
    Roll.... 8176 
    EM...... 37628064 
    Heap.... 0 
    Page.... 65536 
    MM Used. 31785376 
    | MM Free. 1656912
    =============================================
    Configuration:
    OS :Windows 2003 server.
    Solution Manager 7.0 SP15
    Oracle 10.2
    RAM - 2 GB
    Its bit urgent, Please help out us.
    Thanks in advance.
    Best Regards,
    Pratyusha

    Hi
    Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
    This error is related to ABAP program.
    Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

  • Receive 'runtime error: Unknown exception' w/99% processed when creating DVD from movie

    Hi,
    I have tried several times to create a DVD of a movie with several Scene (w/Stop) Markers only to receive 'runtime error: Unknown exception' with 99% completion.
    I'm using Adobe Premiere Element 11 ver 11.0 (20120901.B261.425551).
    I'm running Windows 7 Ultimate w/SP1 on a Dell XPS M1530 w/4GB Memory
    I have created DVDs in the past with little or no problems.
    Would appreciate any help with my problem.
    Thanks...

    Harry
    Thanks for the additional information.
    Typically, if you are doing a multi movie Timeline and you want the viewer to be able to navigate to a specific movie followed by return to main menu, then:
    Main Menu Marker at beginning of movie 1 and Stop Marker at end of movie 1....then gap of at least 12 frames...Main Menu Marker at beginning of movie 2 and Stop Marker at end of movie 2....and so on. But for the last, remember no Stop Marker at the end of that last Movie on the Timeline.
    With those 25 .mts video clips, are you sure that you want or need all those return to main menu possibilities.... a scene marker at the beginning of each and a stop marker at the end of each for a return to menu after each of the 25 video clips? Especially if these are small video clips.
    Large project...
    Keep in mind that the DVD disc 4.7 GB/120 minutes is in reality 4.3 GB capacity. So as you can tell my the program's lowering of the Bitrate (8.00 to 7.97 Mbps), the program is trying to make the fit by lowering the bitrate. Depending on how your troubleshooting goes, you may want to start thinking about DVD Double Layer Disc (8.5 GB/240 min) if your project gets much larger. In the case of the DVD double layer, 8.5 GB is in reality 7.3 GB. Typically, lower the Bitrate, the lesser is the Quality of the end product. So you do not want to force the program to lower the Bitrate to low to make the fit.
    As for the Timeline - + slider to which I referred...
    In the above screenshot, please note in the right side of the Premiere Elements 11 Timeline (Expert view)...from left to right at that location,
    the Render Button
    the icon named "Fit to Visible Timeline
    the icon named Zoom Out ( - ) which is related to the slider to its right
    the icon named Zoom In ( +) which is related to the slider to its left
    That slider is moved by either of those icons or by moving the circular button of the slider with the mouse curser.
    We will be watching for further developments.
    Thanks.
    ATR

  • Unable to View SMS, Error- Uncaught exception: Index 87 = 87

    Hi
    Pls help - I am unable to view my SMS (Both Sent and Received). Not getting any notification also.  If i compose SMS after sending it disappears.  And I am getting error -Uncaught exception: Index 87 >= 87 everytime i switch on the device. Not able to find the SMS in Messages>View Folder>SMS Inbox also.  I have tried by wiping all applications, device has enough memory- 127MB.  Even Checked Firewall... Pls help...
    Regards
    Sandeep
    Solved!
    Go to Solution.

    Hi sandeep23101985
    Welcome to BlackBerry Support Forums
    There are no specific  Knowledge Base regarding the error Uncaught exception : index 87 >= 87 or similar, As you had already wiped or deleted all applications from your device but still error appearing so to rule out any software issue you can reload your Device OS ,but first do your device backup using BlackBerry Desktop Software,For further instruction please refer to this Knowledge Base :
     KB11320 : How to perform a clean reload of the BlackBerry Device software using BlackBerry desktop software for windows.
    After Reload restore your backup.I hope it will solve your issue.
    Prince
    Click " Like " if you want to Thank someone.
    If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.
    Click " Like " if you want to Thank someone.
    If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.

  • Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB

    Hi,
    i need some guides to solve this problem.
    The program works fine in client DEV. However, when it's in QAS, we encounter  short dump: Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB
    info from short dump:
    An SQL error occurred when accessing a table.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "FILL_T_DATA_TABLE" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "FILL_T_DATA_TABLE"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-24371: data would not fit in current prefe
    buffer"
    Internal call code.........: "[RSQL/FTCH/VBUK ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "ZSDR_SHIPPING_REPORT" or "ZSDR_SHIPPING_REPORT"
    "FILL_T_DATA_TABLE"
    If you cannot solve the problem yourself, please send the...
    Information on where terminated
    The termination occurred in the ABAP program "ZSDR_SHIPPING_REPORT" in
    "FILL_T_DATA_TABLE".
    The main program was "ZSDR_SHIPPING_REPORT ".
    The termination occurred in line 3561 of the source code of the (Include)
    program "ZSDR_SHIPPING_REPORT"
    of the source code of program "ZSDR_SHIPPING_REPORT" (when calling the editor
    35610).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "FILL_T_DATA_TABLE" "(FORM)" but was not handled locally, not
    declared in the
    RAISING clause of the procedure.
    The procedure is in the program "ZSDR_SHIPPING_REPORT ". Its source code starts
    in line 3468
    of the (Include) program "ZSDR_SHIPPING_REPORT ".
    source code:
    035490
    035500   *get all open sales orders (those that are deemed open at the Sales
    035510   *Order "Header" level)
    035520     clear open_orders.
    035530     refresh open_orders.
    035540     select * into corresponding fields of table open_orders
    035550       from vbuk
    035560       where ( vbtyp = 'C' or vbtyp = 'I' )
    035570         and ( gbstk = 'A' or gbstk = 'B' ).
    035580
    035590   *get all open deliveries(some sales orders may be closed yet the
    035600   *associated Delivery is not yet PGI'd)
         >     clear open_deliveries.
    035620     refresh open_deliveries.
    035630     select * into corresponding fields of table open_deliveries
    035640       from vbuk
    035650       where vbtyp = 'J'
    035660         and ( wbstk = 'A' or wbstk = 'B' ).
    035670
    035680   *get sales orders associated with the Open deliveries
    Please advice.
    Thanks.

    Thanks for the response.
    Hi Renga,
    The error happens in second selection.
    this is the souce code:
    data: begin of open_orders occurs 0,
            vbeln like vbuk-vbeln,
            gbstk like vbuk-gbstk,
            vbtyp like vbuk-vbtyp,
          end of open_orders.
    data: begin of open_deliveries occurs 0,
            vbeln like vbuk-vbeln,
            wbstk like vbuk-wbstk,
            vbtyp like vbuk-vbtyp,
          end of open_deliveries.
    *get all open sales orders (those that are deemed open at the Sales
    *Order "Header" level)
      clear open_orders.
      refresh open_orders.
      select * into corresponding fields of table open_orders
        from vbuk
        where ( vbtyp = 'C' or vbtyp = 'I' )
          and ( gbstk = 'A' or gbstk = 'B' ).
    *get all open deliveries(some sales orders may be closed yet the
    *associated Delivery is not yet PGI'd)
      clear open_deliveries.
      refresh open_deliveries.
      select * into corresponding fields of table open_deliveries
        from vbuk
        where vbtyp = 'J'
          and ( wbstk = 'A' or wbstk = 'B' ).
    Hi Prabhu,
    how to identify the problem in DB02?
    Please advice.
    Thanks.
    regards.

  • Runtime error - DBIF_RSQL_INVALID_RSQL, Exception - CX_SY_OPEN_SQL_DB

    Hi,
    Following code is working fine in Development system and in Production system I am getting a runtime error. Only difference I am finding is in r_lifnr value. In development system I have few lifnr and in Production system it's not so... am I getting error because of it? Is there any restriction to no. of items populated in a range? Or Basis person need to change any parameter? Enclosed the detail dump below the code...
    Advance thanks.
    Regards,
    Balaji Viswanath.
    Code:
      SELECT bukrs
             lifnr
             augdt
             augbl
             zuonr
             gjahr
             belnr
             buzei
             waers
             dmbtr
             wrbtr
             zlsch
             shkzg
             blart
             gsber
             sgtxt
      INTO TABLE t_bsak_tmp
      FROM bsak CLIENT SPECIFIED
      WHERE mandt = sy-mandt AND
            lifnr IN r_lifnr AND
            bukrs IN s_bukrs AND
            augdt IN s_augdt AND
            blart IN s_blart.
      IF sy-subrc <> 0.
      No data found for selection criteria
        MESSAGE i018.
        LEAVE LIST-PROCESSING.
      ENDIF.
    Dump:
    Runtime Errors         DBIF_RSQL_INVALID_RSQL
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     14.11.2005 at 14:35:22
    Error in the module RSQL accessing the database interface.
    What happened?
    Error in ABAP application program.
    The current ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P" had to be terminated
    because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "GET_CLRD_VEN_DATA" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    The SQL statement generated from the SAP Open SQL Statement violates a
    restriction imposed by the database system used in R/3.
    Possible errors:
    o The maximum size of an SQL statement has been exceeded.
    o The statement contains too many input variables.
    o The space needed for the input data exceeds the available memory.
    o ...
    You can usually find details in the system log (SM21) and in the
    developer trace of the work process (ST11).
    If an error occurs the developer trace often informs you about the
    current restrictions.
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "GET_CLRD_VEN_DATA"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    The SAP Open SQL statement must be divided into several smaller units.
    If the problem occurred due to the use of an excessively large table
    in an IN itab construct, you can use the addition FOR ALL ENTRIES
    instead.
    When you use this addition, the statement is split into smaller units
    according to the restrictions of the database system used.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
    "/DS1/FI_CR_REPT_PGSR802_VEND_P" or "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    "GET_CLRD_VEN_DATA"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    System environment
    SAP Release.............. "620"
    Application server....... "ztm1003"
    Network address.......... "145.26.160.103"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C004DC4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 6
    Short dump setting....... "full"
    Database server.......... "ztm1003"
    Database type............ "ORACLE"
    Database name............ "A94"
    Database owner........... "SAPR3K"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 7 2005 20:44:35"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "85"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
    10.1.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    User, transaction...
    Client.............. 110
    User................ "INBVI0"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    in "GET_CLRD_VEN_DATA".
    The main program was "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
    The termination occurred in line 503 of the source code of the (Include)
    program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    of the source code of program "/DS1/FI_CR_REPT_PGSR802_VEND_P" (when calling
    the editor 5030).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "GET_CLRD_VEN_DATA" "(FORM)" but was not handled locally, not
    declared in the
    RAISING clause of the procedure.
    The procedure is in the program "/DS1/FI_CR_REPT_PGSR802_VEND_P ". Its source
    code starts in line 501
    of the (Include) program "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
    Source code extract
    004730   &----
    004740   *       get country names from t005t
    004750   ----
    004760   FORM get_country_names.
    004770
    004780     t_lfa1_land[] = t_lfa1[].
    004790     SORT t_lfa1_land BY land1.
    004800     DELETE ADJACENT DUPLICATES FROM t_lfa1_land COMPARING land1.
    004810
    004820     IF NOT t_lfa1_land[] IS INITIAL.
    004830       SELECT land1
    004840              landx
    004850       INTO TABLE t_t005t
    004860       FROM t005t
    004870       FOR ALL ENTRIES IN t_lfa1_land
    004880       WHERE spras = sy-langu AND
    004890             land1 = t_lfa1_land-land1.
    004900       REFRESH t_lfa1_land.
    004910       SORT t_t005t BY land1.
    004920     ELSE.
    004930       MESSAGE i014 WITH 'No vendor data fetched'(001).
    004940     ENDIF.
    004950   ENDFORM.                    " get_country_names
    004960   &----
    004970   *&      Form  get_clrd_ven_data
    004980   &----
    004990   *       Cleared vendor data
    005000   ----
    005010   FORM get_clrd_ven_data .
    005020
    >     SELECT bukrs
    005040            lifnr
    005050            augdt
    005060            augbl
    005070            zuonr
    005080            gjahr
    005090            belnr
    005100            buzei
    005110            waers
    005120            dmbtr
    005130            wrbtr
    005140            zlsch
    005150            shkzg
    005160            blart
    005170            gsber
    005180            sgtxt
    005190     INTO TABLE t_bsak_tmp
    005200     FROM bsak CLIENT SPECIFIED
    005210   * the order of the fields are as in the secondary Index.
    005220     WHERE mandt = sy-mandt AND
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 0
    SY-TABIX 1                             SY-DBCNT 59
    SY-FDPOS 0                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY
    SY-UCOMM
    SY-TITLE Vendor Payment  Details for IRD
    SY-MSGTY I                             SY-MSGID SF
    SY-MSGNO 616                           SY-MSGV1 /DS1/FI_CR_REPT_PGSR802_VEND_P
    SY-MSGV2 RE                            SY-MSGV3 EN
    SY-MSGV4
    Active calls / events
    No.... Type........ Name..........................
           Program
           Include                                  Line
           Class
         2 FORM         GET_CLRD_VEN_DATA
           /DS1/FI_CR_REPT_PGSR802_VEND_P
           /DS1/FI_CR_REPT_PGSR802_VEND_P             503
         1 EVENT        START-OF-SELECTION
           /DS1/FI_CR_REPT_PGSR802_VEND_P
           /DS1/FI_CR_REPT_PGSR802_VEND_P             135

    Hi Balaji,
    Here is what the dump said and my answers are right below them.
    <i>Possible errors:</i>
    o The maximum size of an SQL statement has been exceeded.</i>
    This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
    <i>o The statement contains too many input variables.</i>
    Most likely this is your issue. I think your r_lifnr is filled with all the vendors in your system and filled as single values. In that case you may be exceeding a limit set on the system. Instead of trying to remove this setting, what I would suggest is to do the following.
    Define a select-option for LIFNR on your selection screen. This way users can have the flexibility of specifying certain vendors. If they don't enter anything, it is still ok. Don't fill it with single values.
    Use this select-option in your select statement. After the select statement, do a delete from itab where the vendors are not in your r_lifnr as below.
    DELETE t_bsak_tmp WHERE NOT lifnr IN r_lifnr.
    Also, avoid using client. You don't need that unless you really want to select from a different client other than your logon client. Your select statement is using logon client anyway, so you don't need to specify that.
    <i>o The space needed for the input data exceeds the available memory.</i>
    If the above changes are made and the problem is still there, then this is the next thing to look at.
    Srinivas

  • Portal Runtime Error : An exception occurred while processing a request

    Hello friends,
    After upgradation of my portal to the following patch level, SAP J2EE 6.20:
    <b>Portal Version :</b> EP 6 SP 2 patch 29 hotfix 0
    <b>Content Mgmt and Collaboration  version</b> : 6 SP2 patch 5
    i faced many performance related issues. Portal seems to be <b>very slow</b>. After logging in, most of the time I get 2 errors:
    <b>Either</b>
    <b>1></b> Iview remains blank.
    <b>Or
    2></b> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
    But when I refresh that particular iview, it works fine.
    I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found <b>the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."</b>Aug 18, 2005 6:07:42 PM # PRT-Async 2          Fatal           Exception ID:06:07_18/08/05_0669
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
    Component class : com.sapportals.portal.prt.pom.RootComponentNode
    User : tempuser
            at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
            at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
            at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    <b>Help needed.(</b>as i am helpless now.)
    Regards,
    Nilz

    Anthony,
      I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
    I created like this
             project-> rightclick->   export-> par ->selecting project-> givint protal password-> and finish.
    The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
    but the par file is  created in the NW studio Navigation bar.
      Let me know any help regarding this
    thanks
    venkat

  • Runtime error when executing F4 help on 0FISPER or 0FISCYEAR

    Hi experts,
    I got a problem on F4 help.
    When executing F4 help on 0FISPER or 0FISCYEAR using tcode LISTCUBE,
    abap dump occurs. The problem also exists when run query in BEx analyzer.
    My BW version is NW2004s. And SAPKW70012 has been implemented.
    Thanks very much for any advices.
    <b>The error message when run in BEx analyzer:</b>
    System error in program SAPLRRS2 and form EXTRA_FIELDS_SET-01- (see long
    text)
        Message no. BRAIN299
    Diagnosis
        This internal error is an intended termination resulting from a program
        state that is not permitted.
    Procedure
        Analyze the situation and inform SAP.
        If the termination occurred when you executed a query or Web template,
        or during interaction in the planning modeler, and if you can reproduce
        this termination, record a trace (transaction RSTT).
        For more information about recording a trace, see the documentation for
        the trace tool environment as well as SAP Note 899572.
    <b>And the ABAP dump log:</b>
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_PROPAGATE_X
    Date and Time          2007.04.28 15:08:47
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_RSR_PROPAGATE_X' was raised, but it was not caught anywhere
    along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_RS_BASE====================CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_PROPAGATE_X', was not caught
    and
    therefore caused a runtime error.
    The reason for the exception is:
    No text available for this exception
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SY_NO_HANDLER", which was raised in the program
    "CL_RSMD_RS_BUILD_QUERY========CP",
    specifically in line 1 of the (include) program
    "CL_RSMD_RS_BUILD_QUERY========CM00Y".
    The cause of the exception was:
    An exception with the type CX_RS_SQL_ERROR_SILENT occurred, but was neither
    handled locally, nor declared in a RAISING clause
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_RS_SQL_ERROR_SILENT", which was raised in the program
    "CL_RSDRS_SQL_QUERY============CP",
    specifically in line 288 of the (include) program
    "CL_RSDRS_SQL_QUERY============CM00J".
    The cause of the exception was:
    No text available for this exception
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 32 of the (include) program
    "CL_SQL_STATEMENT==============CM004".
    The cause of the exception was:
    Invalid object name 'T009C'.
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RSR_PROPAGATE_X"
    "CL_RS_BASE====================CP" or "CL_RS_BASE====================CM005"
    "X_PROPAGATE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "sapdev2"
    Network address...... "192.168.1.74"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "SAPDEV2"
    Database type..... "MSSQL"
    Database name..... "BW1"
    Database user ID.. "bw1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Sep 1 2006 00:19:17"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 75
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 16192
    EM...... 14617568
    Heap.... 0
    Page.... 163840
    MM Used. 4553264
    MM Free. 663776
    User and Transaction
    Client.............. 100
    User................ "HANDLCR"
    Language key........ 1
    Transaction......... "LISTCUBE "
    Program............. "CL_RS_BASE====================CP"
    Screen.............. "SAPMSHLP 0600"
    Screen line......... 7
    Information on where terminated
    Termination occurred in the ABAP program "CL_RS_BASE====================CP" -
    in "X_PROPAGATE".
    The main program was "GP9QWV49ZUMYUSW6JLZIZ85P81N ".
    In the source code you have the termination point in line 12
    of the (Include) program "CL_RS_BASE====================CM005".
    Source Code Extract
    Line
    SourceCde
    1
    METHOD X_PROPAGATE .
    2
    3
    DATA: l_r_x TYPE REF TO cx_rs_no_check.
    4
    5
    TRY.
    6
    l_r_x ?= i_r_root.
    7
    CATCH cx_root.
    8
    CLEAR l_r_x.
    9
    ENDTRY.
    10
    11
    IF l_r_x IS INITIAL.
    >>>>>
    RAISE EXCEPTION TYPE cx_rsr_propagate_x
    13
    EXPORTING
    14
    previous = i_r_root.
    15
    ELSE.
    16
    RAISE EXCEPTION l_r_x.
    17
    ENDIF.
    18
    19
    ENDMETHOD.

    I got reply from SAP. The problem can be solved by running program RSDG_XPRA_IOBJ_TO_NW05. Note 939484 describes this.
    Note 939484 - Input help for tech characteristic and time characteristics
    Summary
    Symptom
    You upgraded to SAP NetWeaver 2004s. An open SQL error occurs when you execute input help for a technical characteristic, a time characteristic or a unit.
    The 'SAPSQL_INVALID_FIELDNAME' short dump in the 'CL_RSDM_READ_MASTER_DATA' class indicates that these characteristics have not been maintained. This error may also occur when you activate InfoProviders, for example.
    The error MAY occur for the following InfoObjects:
    0CALMONTH
    0CALMONTH2
    0CALQUART1
    0CALQUARTER
    0CALWEEK
    0CALYEAR
    0CURRENCY
    0FISCPER
    0FISCPER3
    0FISCVARNT
    0FISCYEAR
    0LOGSYS
    0SOURSYSTEM
    0UNIT
    0WEEKDAY1
    0RATE_TYPE
    0DATE
    0LANGU
    Other terms
    Input help, F4, 0CALMONTH, 0CALMONTH2, 0CALQUART1, 0CALQUARTER, 0CALWEEK, 0CALYEAR, 0CURRENCY, 0FISCPER, 0FISCPER3, 0FISCVARNT, 0FISCYEAR, 0LOGSYS, 0SOURSYSTEM, 0UNIT, 0WEEKDAY1, 0RATE_TYPE, 0DATE, 0LANGU, RSDG_XPRA_IOBJ_TO_NW05
    Reason and Prerequisites
    The problem can have the following causes:
    The characteristic does not have any master data, although you did define a master data read class.
    There is no generated master data table for the characteristic (for example, 0CURRENCY) and you have not defined a corresponding master data read class in the meta data.
    Solution
    Technical characteristics and time characteristics were delivered again for SAP NetWeaver 2004s with new properties. The first time you call the data warehousing workbench, the system activates the technical content. If the (time) characteristic already exists in the active version, the system does not copy it from the technical content again.  For SAP NetWeaver 2004s, however, the following conditions must be fulfilled:
    The characteristic has the property "With master data", which ensures that the master data read class functions correctly.
    If the active version of the characteristic does not have any master data, copy the characteristic from the content again. Make any necessary adjustments. Ensure that the "With master data" property is set.
    The characteristic does not have a generated table, rather it has its own table, delivered by SAP (for example, unit 0CURRENCY -> table TCURC). The definition of the characteristic must include a relevant master data read class (for example, unit 0CURRENCY -> class CL_RSMD_RS_0CURRENCY).
    The RSDG_XPRA_IOBJ_TO_NW05 XPRA defines a master data read class automatically. This XPRA is executed when you upgrade. It may, however, occur, that the XPRA is not executed successfully. If this happens, you can execute the XPRA again manually.
    Start Transaction SE38.
    Enter the name RSDG_XPRA_IOBJ_TO_NW05 in the 'Program' field.
    Choose 'Execute' to execute the program.

  • Runtime Errors    BCD_FIELD_OVERFLOW Exception CX_SY_CONVERSION_OVERFLOW

    Dear All,
    I am getting below error in PRD system. We are using ecc6, oracle 10g and windows 2003. The error coming  after we have restarted  the server. Please suggest how to solve the issues.
    SM21 log
    09:30:21 DIA  000 000 DDIC                               AB  0 Run-time error "BCD_FIELD_OVERFLOW" occurred
    09:30:21 DIA  000 000 DDIC                               AB  1 > Short dump "100913 093034 nodeA " generated
    ST22
    Runtime Errors         BCD_FIELD_OVERFLOW
    Exception              CX_SY_CONVERSION_OVERFLOW
    Date and Time          13.09.2010 00:30:19
    Short text
         A calculation field is defined too small.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_SWNC_RECORD================CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
         caught in
        procedure "DO_TRANSFORMATIONS" "(METHOD)", nor was it propagated by a RAISING
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        A value generated during processing is too large for the
        field "ME->MAIN_RECORD_STR+1020(7)" of the program
         "CL_SWNC_RECORD================CP".
    Regards,
    Kumar

    Dear Friends,
    We even got same dump "BCD_FIELD_OVERFLOW" just after system restart. But error was slightly different. Please find below error details and solution:
    Error Details:
    The current ABAP program "CL_SWNC_RECORD================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
    Error Analysis:
    An exception occurred that is explained in detail below. This exception cannot be caught in the context of the current statement.
    The reason for the exception is: A value generated during processing is too large for the field " " of the program "CL_SWNC_RECORD================CP".
    "BCD_FIELD_OVERFLOW" " "
    "CL_SWNC_RECORD================CP" or "CL_SWNC_RECORD================CM002"
    "CALCULATE_PROCESSING_TIME"
    SOLUTION:
    An OSS Note:
    Note 1103295 - BCD_FIELD_OVERFLOW in CALCULATE_PROCESSING_TIME (It solves the problem)

Maybe you are looking for