spool error whle converting to xcel sheet

[Former Member]

Hi experts,

I am getting the following two dump errors from twodays,

1) STORAGE_PARAMETERS_WRONG_SET

This is when trying to view more than 1100 pages of report

2) DATA_OFFSET_TOO_LARGE

If i get the output of 1100 pages, while trying to convert in to excel, i am getting this error.

earlier users can able to convert 1400 pages of data in to excel sheet with out any dump errors.This is happening from two days.Why it suddenly giving this dump errors ?Is this related to only storage parameters?

Kindly suggest me to resolve this.

Regards,

Gayathry.

Following is the dump messages for each error.

___________________________________________

1)STORAGE_PARAMETERS_WRONG_SET

&INCLUDE INCL_INSTALLATION_ERROR

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The program had already requested 732101232 bytes from the operating

system with 'malloc' when the operating system reported after a

further memory request that there was no more memory space

available.

What can you do?

Make a note of the actions and input which 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.

Set the system profile parameters

- abap/heap_area_dia

- abap/heap_area_nondia

to a maximum of 732101232. Then reduce the value by 10.000.000 to be on the

safe side.

Then restart the SAP System.

Error analysis

When the program was running, it was established that more

memory was needed than the operating system is able to provide savely.

To avoid a system crash, you must prevent this

situation.

How to correct the error

Report the error to the group responsible for installing your

R/3 System.

________________________________________________

2) DATA_OFFSET_TOO_LARGE

Invalid partial field access: Offset too large

What happened?

Error in ABAP application program.

The current ABAP program "RSSCD100_PFCG" 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_RANGE_OUT_OF_BOUNDS',

was neither

caught nor passed along using a RAISING clause, in the procedure

"PRGN_LOG_PATTERN" "(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 system tried to access field "GV_TABKEY" with type "C" and length

70 in the current program "RSSCD100_PFCG" using offset 70.

Partial field access is not allowed with an offset specification that is

larger than actual field length.

How to correct the error

The exception must either be prevented, caught within the procedure

"PRGN_LOG_PATTERN"

"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Make the offset smaller with which you want to access the field.

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:

"DATA_OFFSET_TOO_LARGE" CX_SY_RANGE_OUT_OF_BOUNDSC

"RSSCD100_PFCG" or "RSSCD100_PFCG"

"PRGN_LOG_PATTERN"

_________________________________________________

[Former Member · Accepted solution]

Hello Gayathry,

If your OS is Windows,

Check the note numbers 110172 and 88416

Regards,

Nagendra.

[Former Member · Accepted solution]

Hi,

Ask your SAP BASIS consultant to change the parameters and as per the error it clearly says it is out of memory. the reason could be some other people running some other reports and holding the memory for a long time, SAP Basis PPL can figure out if there is sufficient memory allocated or not. The other way you can do it put a trace tcode ST22 so you can exactly know where and why the error is occuring (this is done by BASIS consultants).

Kind Regards,

Vamsi