topic SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH in Application Development and Automation Discussions

SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Fri, 15 Apr 2011 08:39:00 GMT

Dear all, When I am executing a TCode SE30, Runtime Errors CREATE_DATA_ILLEGAL_LENGTH Except occurs. I make sure that my account is correct, I can use this Tcode with my account on others computer . Please give me some solution , Thanks. Best Regards, Eric.

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

Former Member — Fri, 15 Apr 2011 08:42:06 GMT

Post the Error where it is showing some arrow mark..

Check it once.

Generally this kinds of errors will come when you have Pass value more than Length defiend.

or else use Data base adjustments to fix first if you make any changes to table after creating data

Regards

sas

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

ThomasZloch — Fri, 15 Apr 2011 08:54:40 GMT

Did you check for SAP notes related to this error?

Thomas

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Fri, 15 Apr 2011 09:08:00 GMT

I have searched the issue on Google ,but no related SAP found for this .

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Fri, 15 Apr 2011 09:13:53 GMT

Runtime Errors CREATE_DATA_ILLEGAL_LENGTH

Exception CX_SY_CREATE_DATA_ERROR

Date and Time 15.04.2011 05:35:53

Short text

CREATE DATA: Illegal value for the length of an object of the type "X"

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_ABAP_TRACE_FILE============CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

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 that is explained in detail below.

The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not

caught in

procedure "READ_INFO" "(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 data object of the type "X" with length 0 was to be created using

CREATE DATA. The value 0 is not within the allowed range.

Allowed range for the length specification:

Typ C, N, X: 1 .. 65535

TYP P: 1 .. 16

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

Sandra_Rossi — Fri, 15 Apr 2011 09:24:24 GMT

Hi Eric,

I'd really like to know how it's possible that the solution is not solved by a SAP note, as suggested by Thomas ? Of course, saslove explained the technical background, but it's not the solution.

Please think to people who look at whom you credited the solution, they would be very surprised.

Could you tell us how you solved?

Thanks

Sandra

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Mon, 18 Apr 2011 05:20:45 GMT

Becasue some wrong operation , i marked the question as answered.So i want recover the status to Not answer , thanks .

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Mon, 18 Apr 2011 05:37:05 GMT

Hi Sandra So long time ... Because my wrong operation , i marks the question as 'Answered'. I have checked the Notes 896886 - SE30: Termination in method CL_ABAP_TRACE_FILE=>READ_INFO. there are three solution suggested,but it is so strang. my colleagues can use SE30 on the same server. So i can make sure that our system have implement the relavant support package .So i think the solution B may be a way . For sulotion B:Do you know how to delete the old version performance data files on the application server ? Best Regards, Eric. *************************************************************************************************************************************************** Solution The problem is solved with a Support Package. For information about the Support Package level that is relevant for your release, see the "Support Packages" section. In lower Support Package levels, to avoid the problem, you can proceed as follows: A.Ensure that the version for the performance data files that is set in SE30 is correct. This is for - 6.40: Version B - 7.0 and 7.10: Version C Call transaction SE24 to check whether the attribute VERSION of the class CL_ABAP_TRACE has the required value. If this is not the case, contact SAP. B.Use transaction AL11 to check whether there are performance data files with the old version on one of your application servers. If this is the case, delete these files. C.If you use Release 6.40, you must also ensure that the system does not create any new performance data files with an incorrect version when you call transaction ST12. Due to an error, transaction ST12 creates files with the Version A (this is incorrect). This error is corrected with the Version 01L* of the Add-On ST-A/PI. This version is available as of November 2008 (see Note 69455). ****************************************************************************************************************************************************

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

Sandra_Rossi — Mon, 18 Apr 2011 07:48:28 GMT

Hi Eric,

I think you may change to unsolved again, and also move and reassign points as you wish (or ask the moderator).

You may delete files using SE30 (first menu -> files -> others), or using OS commands (ask the admin). The performance files are located in the SAP directory DIR_ATRA in AL11.

Sandra

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Tue, 19 Apr 2011 01:59:10 GMT

Hello Sandra I use one of my colleagues's PC log in the platform under my acount, then execute SE30 MENU-->DELETE FILE .But there is no any performance file found , I think if there are some different version performance file in application server, may be i can't use SE30 with other's too. And thank you all the same . I am going to re-install my SAP GUI , and try again. I hope it is a way . file. Best Regards, Eric.

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Tue, 19 Apr 2011 03:17:04 GMT

Hello Sandra , The problem has been fixed , thanks. Solution: Step1:SE24 , find class CL_ABAP_TRACE_FILE , and then break point at Method READ_INFO line 31: read dataset FNAME into L_BUFFER_LN. create data L_BUFFER type X length L_BUFFER_LN. Breat point here. Step2:SE30 ,when the break point reached , then change L_BUFFER_LN to an number which bigger than '0', then you will access to the SE30 initial screen successfully . then exit. Check the Application file via 'AL11', you will find the DIR_ATRA--->AT000001 has been delete and replace by another new version one. Then you can execute SE30 successfully. Reason:Please check the Note 896886 , Seems that replace the old version performance file is a better way. Best Regards, Eric.

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

former_member447033 — Tue, 19 Apr 2011 03:18:51 GMT

Problem has been fixed , Thanks for yours attention . For the solution , if anyone are not very clear , you can concate me .

Re: SE30 Runtime Errors: CREATE_DATA_ILLEGAL_LENGTH

Sandra_Rossi — Tue, 19 Apr 2011 15:04:39 GMT

Hi Eric,

thank you for the feedback.

I use one of my colleagues's PC log in the platform under my acount, then execute SE30 MENU-->DELETE FILE .But there is no any performance file found , I think if there are some different version performance file in application server, may be i can't use SE30 with other's too.

No, you must not select menu -> delete file, you must select menu -> files -> Other files, select user *, and select all dates, that will display all existing files, and then you can delete. As far as I know, there's no authority check (except at the OS level of course). Be careful, the runtime analysis is application-server-dependent, so you may have to switch to another application server (SM51, select another one, double-click, and enter /NSE30 in the command field).

Anyway, it would have dumped the same way, as any listed file is opened/read by method READ_INFO.

I am going to re-install my SAP GUI , and try again. I hope it is a way.

Probably not (as SAPGUI is not related to application server runtime analysis). If the problem happens once again, it will be better to contact SAP support.

If I have well understood, instead of using debug to be able to delete a trace file, we should interpret this sentence (from note 896886) :

If this is the case, delete these files.

as being :

If this is the case, delete these files from an OS command line, as doing it from SE30 would terminate with a short dump.

Sandra