Runtime error: Protection Violation

Hello,
I am having an issue running reports in Labware LIMS. Labware is using crystal runtime XI to generate its reports. Basically what is happening is I can run a few reports (anywhere from 2-7) then I will get an error that states:
runtime error: Protection Violation
It also writes to error.log which i will post an excerpt from that file as well.
The only way to continue running reports is to close out of Labware and start over.
My operating system is Windows Vista SP2 and we are using Labware 5
Please help!!!
Thanks,
Cody
Error log timestamp Wed. 06/08/2011 10:42:24 AM
Runtime error: Protection Violation
Error(Exception)>>defaultAction
Error(Exception)>>activateHandler: <anUndefinedObject>
Error(Exception)>>handle
Error(Exception)>>signal
Error class(Exception class)>>signal: <'Protection Violation'>
Process class(Object)>>error: <'Protection Violation'>
Process class>>protectionViolationInterrupt
Process class(Object)>>perform: <#protectionViolationInterrupt>
UserDLL(Object)>>vmInterrupt: <#protectionViolationInterrupt>
UserDLL(DynamicLinkLibrary)>>invalidArgument
UserDLL>>dispatchMessage: <aByteArray>
NotificationManager>>readWinQueue
Process class>>osEventInterruptGui
Process class>>osEventInterrupt
SmallInteger(Object)>>vmInterrupt: <#osEventInterrupt>
String(IndexedCollection)>>includes: <aCharacter>
[] in MenuWindow>>menuTitledPrim:
[] in Collection>>reject:
String(FixedSizeCollection)>>select: <aBlockClosure>
String(Collection)>>reject: <aBlockClosure>
[] in MenuWindow>>menuTitledPrim:
[] in Collection>>detect:ifNone:
OrderedCollection>>do: <aBlockClosure>
OrderedCollection(Collection)>>detect: <aBlockClosure> ifNone: <aBlockClosure>
MenuWindow>>menuTitledPrim: <'A&udit'>
MenuWindow>>menuTitled: <'A&udit'>
CrystalFolderManager(ViewManager)>>menuTitled: <'A&udit'>
CrystalFolderManager>>updateMenus
CrystalFolderManager(FolderManager)>>updateItem
CrystalFolderManager(FolderManager)>>refreshObjects
[] in FolderManager>>unReleaseSamples
ProtectedFrameMarker(BlockClosure)>>setUnwind: <aBlockClosure>
BlockClosure>>ensure: <aBlockClosure>
CursorManager>>changeFor: <aBlockClosure>
CrystalFolderManager(FolderManager)>>unReleaseSamples
CrystalFolderManager(Object)>>perform: <#unReleaseSamples>
[] in MenuWindow>>performMenuItem:
Time class>>millisecondsToRun: <aBlockClosure>
MenuWindow>>performMenuItem: <1029>
TopPane(ApplicationWindow)>>performMenuItem: <1029>
Message>>perform
NotificationManager>>empty
NotificationManager>>runPendingEvents
NotificationManager>>runEventLoop
Message>>perform
Message>>evaluate
Process>>safelyEvaluate: <aMessage>
Process>>evaluate: <aMessage>

You will have to contact Labware and ask them. As it is, we don't even know what CR SDK they are using...
- Ludek

Similar Messages

Problem since upgrade to 2.0 "Error: Session state protection violation"

I've upgraded to 2.0. Everything fine except one particular page when I submit it I get "Error: Session state protection violation". I have read up about session state protection, and it is turned off in my application. There are no items, pages or URLs that have any session state protection. There is nothing particularly different about this screen when compared to other screens that work. What can be causing this?
Steve

Steve - Thanks for putting that test case out there. This is an odd bug. It happens when you apply the read-only attribute to a "Display as Text (does not save state)" item. Normally, these items are not HTML input items on the page (you see only the value rendered). However, because of a bug, applying the read-only attribute causes an INPUT item to be created. This leads to the problem that you saw -- when an item that should never be POSTed because it is: a) an application item, b) a page item that has the Session State Protection attribute "Restricted - May not be set from browser", or c) a page item of display type "Display as Text (does not save state)", is POSTed, the Session State Protection violation is detected and reported. These checks are performed whether the Session State Protection feature is enabled for the application or not. The reason for that is that checking for cases(a) and (c) is always legitimate and checking for case (b) is always necessary because the Restricted attribute for page items of qualifying display types is always in effect.
So the workaround in your case is not to use the read-only attribute for the display-only items. They are read-only anyway.
Thanks again for pointing this out.
Scott

Session State Protection Violation error

I am developing my first Apex application. I have this page which has been running fine until I made some changes. The error I get is the following:
-----Error message:
Session state protection violation. This may be caused by manual alteration of a URL containing a checksum or by using a link with an incorrect or missing checksum. If you are unsure what caused this error, please contact the application administrator for assistance.
--End of error message.
This happens Whenever the page is submitted for process, e.g. when I select from a "LOV with Submit" item or when I click the "Save Changes" button. It is fine if the button redirects to another page. Using Debug, I saw that the error occurs right after "Fetch page attributes" and before "Fetch session state from database".
About the changes I made before this error first surfaced: nothing to do with session state protection and nothing I can think of that is related to session state protection. In fact, I did not specify any session state protection at any level at this stage. That is, all pages and items are unrestricted. I did add a javascript to the page which is invoked onChange of an item to update another item. I made the same changes (except for the Javascript) to another similar page which is still running fine.
I tried logging out of Apex (I am using OracleXE) and getting back on, the error still persists. I even shut down and restart the Apex database to no avail.
Can anyone point me to where it might be the cause of this problem? Thank your help and/or suggestions in advance.
Message was edited by:
muighi

Scott - I should have posted this question sooner! I wasted a whole day trying to figure this out. Thanks a lot, Scott. By the way, where can I find any documented known bugs in Apex?
--Candy

Page protection violation Error

Hi guys,
I have two tabs in a tabset and when I try to click second tab from first tab it gives below exception.
"Page protection violation: This may be caused by manual alteration of protected page items. "
As the exception said I change an item value on page1 from page2 by using link-> f?p=10:1:690313625705501::::P1_SELECTED_OBJ:OBJ_VALUE (P1_SELECTED_OBJ is the item on page 1)
How can I fix this problem , do you have any idea? I found some topics related with same error but they are related with upgrade of Apex.
Apex Version : 4.1.1.00.23
Thanks.
Edited by: nscglr on Jun 28, 2012 6:24 AM

This might be because you are changing the protected items value using JavaScript.
You can edit the apex item > set the protected to No

Very Urgent : Error Page protection violation: This may be caused by submitting a page that had not yet finished loading or by manual alteration of protected page items. For further assistance, please contact the application administrator.

Hi,
I getting this error press on upload button , its working in google chrome and firefox
Error Page protection violation:
This may be caused by submitting a page that had not yet finished loading or by manual alteration of protected page items.For further assistance, please contact theapplication administrator.Contact your application administrator.
Please help me any one

First, please don't post questions/issues and start with "Very Urgent". If you have an "urgent" issue I recommend you contact Oracle Support. Second, if your issue is so urgent, I further recommend that you read this (url below) before going any further. Posting questions without including product names, versions, and related information like platform, configuration and so on, will make it almost impossible for anyone to help you.
http://blogs.oracle.com/shay/entry/10_commandments_for_the_otn_fo
Finally, I am going to guess and say that you are having problems with Oracle Apex version 4.2. If I am correct, I will tell you that this forum space is for Oracle Forms. APEX questions should be posted here (below). However, if you plan to post the same issue there, please consider reading the blog I mentioned above and follow its recommendations before posting anywhere else.
https://community.oracle.com/community/developer/english/oracle_database/application_express

Dump : Runtime Errors DBIF_RSQL_INVALID_RSQL

Hi Experts,
I got a dump at the select statement in the production during the excution.The Details of the program are :
DATA : BEGIN OF it_ekko OCCURS 0.
 INCLUDE STRUCTURE ekko.
DATA : END OF it_ekko.
START-OF-SELECTION.
SELECT * FROM ekko
 INTO TABLE it_ekko
 WHERE ebeln IN p_ebeln
 AND aedat IN p_aedat
 AND bsart IN p_bsart
 AND lifnr IN p_lifnr.
In ST22, the description of dump details is as follows.
What happened?
Error in ABAP application program.
The current ABAP program "ZMMRP126_1" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not
caught, which
led to a runtime error. The reason for this 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.
Source Code Extract
001830
> SELECT * FROM ekko "read through purchase orders
001850 INTO TABLE it_ekko
001860 WHERE ebeln IN p_ebeln "for order number
001870 AND aedat IN p_aedat "created date
001880 AND bsart IN p_bsart "document type
001890 AND lifnr IN p_lifnr.
001900
001910 LOOP AT it_ekko INTO ekko.
001920 PERFORM process_items. "read, check and save line items
001930 ENDLOOP.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 69682
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE Purchase Order Receipt Status
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1 5000098347
SY-MSGV2 SY-MSGV3
SY-MSGV4
Kindly help me to solve out this issue.
Thanks & Regards,
Krishna Kishore .K

hi,
I think you declared p_ebeln as parameter and used in where condition with IN operator.
Could you change with EQ operator.
Or If p_ebeln is select-oprions means check you are giving high range in the selection screen for the input values.
try to check by giving 1 purchase order i.e p_ebeln = 'XXXX' only.
dont give range.
If output is big range means program goes to dump.
are you trying to modify EKKO table in the program?
Please reward if its useful.
Thanks
Sivaparvathi
Or

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.
Possible errors:
o The maximum size of an SQL statement has been exceeded.
This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
o The statement contains too many input variables.
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.
o The space needed for the input data exceeds the available memory.
If the above changes are made and the problem is still there, then this is the next thing to look at.
Srinivas

Runtime error assertion_failed

hello,
i am getting a runtime error 'assertion_failed' while activating the transformations.
it says the assert condition was violated. i am attaching the error message here.
In the running application program, the ASSERT statement recognized a
situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
i need help regarding this.
thanks in advance.
muralik

Hello MuraliK,
Plz apply note :998730.
U need to check RSTRANRULE table with certain combination and delete inconsistent records.
-- Plz assign points if helpful --
Regards,
Mainak

Portal runtime error, custom logon page HElpp

Hi,
I'm new to EP, please kindly help me to solve my problem
I've read so many topic about this, but I still can't understand what I'm supposed to do.
I want to change umHelpPage, so I download by using system administration -> support -> support desk -> portal runtime -> browse deployment -> root -> web-inf -> portal ->portalapps -> com.sap.runtime.logon
Then, download and I make certain changes in UmHelpPage, directly in winzip,without extract it. Save, and then change .zip to .par, by using system administration -> support -> support desk -> portal runtime -> administratioin console -> upload -> com.sap.runtime.logon.par
At first, after I upload the com.sap.runtime.logon, all of my jsp files are missing. And then I'm facing the following error :
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
The exception was logged. Inform your system administrator..
See the details for the exception ID in the log file
Previously, I have backed up my com.sap.runtime.login.par in my local. After several times trying to upload , my jsp files still missing. Then, I tried to copied them manually one by one, from my original backup to folder /irj/root/web-inf/portal/portalapps using unix. But, the error still exists.
I also download .bak one in the pcd directory and renamed in .par and upload it again, but it doesn't make any changes.
I've also checked the .jar files. In my lib folder I have 2 files :
- com.sap.runtime.logon.logon_api.jar
- umelogonbase.jar
but i don't have the com.sap.runtime.logon.logon_core.jar one. Is the file also important ? if so, in which directory I can have it?
Please tell me, what I have to do ?
I have original back up in my local, and seems like I accidentaly erase the original one in the portal.

Hi Desiana,
I think you are missing something in your portalapp.xml
See the sample..
<components>
 <component name="DeploymentChecker">
 <component-config>
 <property name="ClassName" value="com.shell.ep.sapportals.epone.adminviews.page.DeploymentChecker"/>
 </component-config>
 <component-profile>
 <property name="tagLib.inheritance" value="final"/>
 <property name="tagLib.value" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 </component-profile>
 </component>
</components>
Regards,
[email protected]

Runtime Error in SQL command ..

Hi everybody
I have a report wich terminates with a dump message.
The error is in an SQL command, here the program aborts:
SELECT KUNNR KKBER KLIMK SAUFT SKFOR SSOBL
    INTO TABLE I_KNKK
    FROM KNKK
   WHERE KUNNR IN R_KUNNR
     AND KKBER IN R_KKBER
     AND SBGRP IN S_SBGRP.
DATA: BEGIN OF I_KNKK OCCURS 0,
      KUNNR LIKE KNKK-KUNNR,
      KKBER LIKE KNKK-KKBER,
      KLIMK LIKE KNKK-KLIMK,
      SAUFT LIKE KNKK-SAUFT,
      SKFOR LIKE KNKK-SKFOR,
      SSOBL LIKE KNKK-SSOBL,
      SBGRP LIKE KNKK-SBGRP,
      END OF I_KNKK.
In first moment, i saw the table and SQL filter have the SBGRP field but the SQL fields selection has not this field. But, these same program works good with others selection parameters, in fact this SQL only terminates the program for the bigest company, wich causes the program make many BD access because all previous SQL.
The dump log says:
Runtime errors         DBIF_RSQL_INVALID_RSQL
Exception              CX_SY_OPEN_SQL_DB
Occurred on            23.05.2006 at   17:27:15
Error in the module RSQL accessing the database interface.
An exception occurred. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', neither caught nor passed along using a RAISING clause, in the procedure "(FORM)" . Since the caller of the procedure could not have expected this except to occur, the running program was terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL Statement violates 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 ...
How can i be sure the dump is for a lot of BD access for all the SQL commands ?
If these is the error, does somebody knows how can i eliminate this error ?
Please help ..
Regards
Frank

I think the field discrepancy is a red herring here. Not guilty! I agree that using the 'CORRESPONDING FIELDS OF' is safer though.
The error could be happening because your range variables have lots of entries in them which makes the generated sql huge.
To break it up you could use the 'package size' option of the select. This will work it's way through the input in chunks (or packages) of the size you specify.
You could change it to:
SELECT KUNNR KKBER KLIMK SAUFT SKFOR SSOBL
INTO TABLE I_KNKK package size 2000 "or a variable value
FROM KNKK
WHERE KUNNR IN R_KUNNR
AND KKBER IN R_KKBER
AND SBGRP IN S_SBGRP.
process current contents of i_knkk here
endselect.
or ,
SELECT KUNNR KKBER KLIMK SAUFT SKFOR SSOBL
appending TABLE I_KNKK package size 2000
FROM KNKK
WHERE KUNNR IN R_KUNNR
AND KKBER IN R_KKBER
AND SBGRP IN S_SBGRP.
endselect.

Runtime error with windows 7

Hi,
I have a new laptop with Windows 7 and Adobe reader 10 'X' installed. I am unable to open a PDF dopcument. A box shows up titled Microsoft visual C++ Runtime library and within the box is written 'Runtime Error Program :C... This application has requested the Runtime to terminate in an unusual way.Please contact the applications support team for more information'. I have tried to follow instruction on support for adobe but cannot find the information they are suggesting i change such as preferences etc. Can anybody help me as I do not have a good knowledge of computers and nobody to ask....

Try the following and check if you could launch reader or not?
1. Right click on Reader icon and choose Properties...
2. Goto Compatibility tab and check 'Run this program in compatibility mode for'
3. Click OK
4. Double click on Reader icon and choose 'Open with protected mode disabled' and click OK.

Runtime Error when doing a Network migration

I get a Visual C++ Runtime error on DesktopDNA.exe (abnormal program
termination)
- It happens when I am doing a network migration (with and without crossover
connection)
- The moment I choose Current User or when I choose next after choosing the
user in Multiple Users
- It works on other machines, could it be something to do with the user
account I am trying to migrate?
Kevin VanSchepen

Actually it also happens when I don't do a network migration. I choose -
create - and it errored when I choose Current User.
>>> Kevin VanSchepen<[email protected]> 3/23/2006 9:37 AM >>>
I get a Visual C++ Runtime error on DesktopDNA.exe (abnormal program
termination)
- It happens when I am doing a network migration (with and without
crossover
connection)
- The moment I choose Current User or when I choose next after choosing the
user in Multiple Users
- It works on other machines, could it be something to do with the user
account I am trying to migrate?
Kevin VanSchepen

Runtime error in sorted itab

Q2]] A runtime error occurs if you violate the sort order of a sorted table by appending to it -
WHY?

Hi,
First of all you should try and understand the meaning of Append and Insert.
Append always adds a new line to the end of the internal table.If the table is empty,then it would add it as the first line.
Insert always inserts the row according to the sorting or if you have given any condition then accordingly.
Modify can play the role of either the Append or Insert depending on the type of the table.
Hence,if you try to use Append in a sorted table, it adds a new row at the end of the table and disturbs the sorting.Insert on the other hand includes the row at a place according to the sorting.
In case you have any further clarifications,do let me know.
Regards,
Puneet Jhari.

Runtime Error # DBIF_RSQL_INVALID_RSQL for large size BOMs

Hi All,
I am facing problem running a custom report for Routing summary. When Executing the report gives the above runtime error.
ShrtText: Error in RSQL module of database interface.
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
     "CP_SC_MTK_LOAD_COMPLEX_BY_TSK" "(FUNCTION)"
Since the caller of the procedure could not have expected this to occur, the running program was terminated.
    The reason for the exception is: The SQL statement generated from the SAP Open SQL Statement violates 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.
How to correct the error
The SAP Open SQL statement must be divided into several smaller units.
    If the problem occurred due to the use of an excessively large 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 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
    "SAPLCPSC" or "LCPSCU03"
    "CP_SC_MTK_LOAD_COMPLEX_BY_TSK"
This report uses SAP standard Function module "CP_SC_MTK_LOAD_COMPLEX_BY_TSK" in the select statement.
When Analysed, We found that since the BOM size for routing is large(More than 2000 components), this dump is coming. for rest of the routings, the report works fine.
I could not found any SAP note relevant for this.
This is definitely related to large BOM size, if anybody of you came across such problem and how to correct it now.

Hi,
We did solve this problem. This problem usually comes when there is very large records in internal table (More than 2000 Approx).
We need to split that select statement and make multiple statements so that the memory overflow doesn't happen. refer SAP note: 13607.
We modified the coding as follows by splitting the SELECT statementu2026
SELECT DISTINCT MANDT PLNTY PLNNR PLNAL MATNR WERKS VBELN POSNR
        INTO CORRESPONDING FIELDS OF TABLE E_MTK_IDENT
        FROM MAPL FOR ALL ENTRIES IN I_TSK_IDENT
        WHERE PLNTY = I_TSK_IDENT-PLNTY    AND
              PLNNR = I_TSK_IDENT-PLNNR    AND
              PLNAL = I_TSK_IDENT-PLNAL    AND
              MATNR IN I_CPSC_MTK_SEL-MATNR AND
              WERKS IN I_CPSC_MTK_SEL-WERKS AND
              VBELN IN I_CPSC_MTK_SEL-VBELN AND
              POSNR IN I_CPSC_MTK_SEL-POSNR AND
             (FREE_WHERE-WHERE_TAB).
SELECT MANDT PLNTY PLNNR PLNAL MATNR WERKS VBELN POSNR
         INTO CORRESPONDING FIELDS OF TABLE E_MTK_IDENT
         FROM MAPL FOR ALL ENTRIES IN I_TSK_IDENT
         WHERE PLNTY = I_TSK_IDENT-PLNTY    AND
               PLNNR = I_TSK_IDENT-PLNNR    AND
               PLNAL = I_TSK_IDENT-PLNAL    AND
              (FREE_WHERE-WHERE_TAB).
Delete E_MTK_IDENT where matnr NOT in I_CPSC_MTK_SEL-MATNR.
Delete E_MTK_IDENT where werks NOT in I_CPSC_MTK_SEL-WERKS.
Delete E_MTK_IDENT where VBELN NOT in I_CPSC_MTK_SEL-VBELN.
Delete E_MTK_IDENT where POSNR NOT in I_CPSC_MTK_SEL-POSNR.
Hope this helps you.
Regards, Madhu

Runtime Error DBIF_RSQL_INVALID_RSQL

Hello Gurus,
One of the ABAP programs failed in the process chains with a short dump.
The details are as follows:
Could you help me resolve this?
Thanks and best wishes,
raj
Runtime Error          DBIF_RSQL_INVALID_RSQL
Exception              CX_SY_OPEN_SQL_DB
       Occurred on     02.07.2008 at   20:55:20
What happened?
Error in ABAP application program.
The current ABAP program "Z_GENERATE_PLAN" 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.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not
caught, which
led to a runtime error. The reason for this 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 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
"ZGENERATE_PLAN" or "Z_GENERATE_PLAN"
"START-OF-SELECTION"
Thanks and best wishes,
raj

Tried this solution:
The current size of one of the input datasets was breaking the maximum length of the SQL statement (which is generated dynamically). Adjust edthe program to handle situations when the input is too large.
Will update you.
Thanks,
Raj

Runtime error: Protection Violation

Similar Messages

Maybe you are looking for