STORAGE_PARAMETERS_WRONG_SET Error.

[Former Member]

Hello Gurus,

I am frequently getting this error while PFCG. Please lemme know the solution.

Enclosed are the details of our server.

IDES ECC 6.0 SR2,

Window 2003 (32 BIT) SR2,

SQL Server 2005 SR3

I changed the parameters but still, I am getting same error. Please help me.

Runtime Errors STORAGE_PARAMETERS_WRONG_SET

Date and Time 03.08.2009 09:35:25

Short text

The system is configured incorrectly.

What happened?

The current program had to be terminated because of an error when installing the R/3 System. The program had already requested 743014688 bytes from the operatingsystem with 'malloc' when the operating system reported after a further memory request that there was no more memory space available.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator.

You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference.

In the system profile, set the parameters

-abap/heap_area_dia and

-abap/heap_area_nondia

to a maximum of 743014688. To be on the safe side, reduce the value by 10,000,

000.

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 safely

to provide. To avoid a system crash, you must prevent this situation from occurring. Last error logged in SAP kernel

Component............ "EM"

Place................ "SAP-Server vmsapecc62_EC6_00 on host vmsapecc62 (wp 2)"

Version.............. 37

Error code........... 7

Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "

Description.......... " "

System call.......... " "

Module............... "emxx.c"

Line................. 1881

The error reported by the operating system is:

Error number..... " "

Error text....... " "

How to correct the error

Report the error to the group responsible for installing your

R/3 System.

System environment

SAP-Release " "

Application server... "vmsapecc62"

Network address...... "192.168.10.200"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "2x Intel 80686"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 2

Shortdump setting.... "full"

Database server... "VMSAPECC62ECC6"

Database type..... "MSSQL"

Database name..... "EC6"

Database user ID.. "ec6"

Char.set.... "C"

SAP kernel....... 700

created (date)... "May 22 2007 00:14:27"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "SQL_Server_8.00 "

Patch level. 111

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, Windows

NT 6.0"

Memory consumption

Roll.... 1709536

EM...... 452602104

Heap.... 743014688

Page.... 57344

MM Used. 1170395136

MM Free. 20469344

User and Transaction

Client.............. 800

User................ "ANKIT"

Language key........ "E"

Transaction......... "PFCG "

Program............. "SAPLPRGN_STRUCTURE"

Screen.............. "SAPLPRGN_TREE 0300"

Screen line......... 22

Information on where terminated

Termination occurred in the ABAP program "SAPLPRGN_STRUCTURE" - in

"PRGN_STRU_PROCESS_STRUCTURE".

The main program was "SAPLPRGN_TREE ".

In the source code you have the termination point in line 60 of the (Include) program "LPRGN_STRUCTUREU16".

Source Code Extract

Line SourceCde

30 READ TABLE in_agr_hier

31 WITH KEY PARENT_ID = 1 BINARY SEARCH.

32 SAVE_TABIX = SY-TABIX.

33 IF SY-SUBRC NE 0. EXIT. ENDIF.

34 INDEX1 = INDEX + 1.

35 INSERT in_agr_hier INTO out_agr_hier INDEX INDEX1.

36 DELETE in_agr_hier INDEX SAVE_TABIX.

37 ENDDO.

38 DO.

39 INDEX = INDEX + 1.

40 READ TABLE out_agr_hier INDEX INDEX.

41 IF SY-SUBRC NE 0.

42 EXIT.

43 ENDIF.

44 DO.

45 READ TABLE in_agr_hier WITH KEY

46 PARENT_ID = out_agr_hier-OBJECT_ID BINARY SEARCH.

47 SAVE_TABIX = SY-TABIX.

48 IF SY-SUBRC NE 0. EXIT. ENDIF.

49 INDEX1 = INDEX + 1.

50 INSERT in_agr_hier INTO out_agr_hier INDEX INDEX1.

51 DELETE in_agr_hier INDEX SAVE_TABIX.

52 ENDDO.

53 ENDDO.

54 sort out_agr_hier by object_id.

55 * Texte:

56 loop at in_agr_hiert.

57 read table out_agr_hier with key object_id = in_agr_hiert-object_id

58 binary search.

59 if sy-subrc = 0.

*>>>>> append inagr_hiert to out_agr_hiert.*_

61 endif.

62 endloop.

63 * Links

64 loop at in_agr_buffi.

65 read table out_agr_hier with key object_id = in_agr_buffi-object_id

66 binary search.

67 if sy-subrc = 0.

68 append in_agr_buffi to out_agr_buffi.

69 endif.

70 endloop.

71 * In Schnittstelle umfüllen:

72 cor_agr_buffi[] = out_agr_buffi[].

73 cor_agr_hier[] = out_agr_hier[].

74 cor_agr_hiert[] = out_agr_hiert[].

75 ENDFUNCTION.

Please lemme know if you need any thing.

Thanks

Rhishabh

[Former Member]

Dear

STORAGE_PARAMETERS_WRONG_SET this abap genrally comes out , memeory is not avilable

please active the /3 GB Memeory option

please do the followings

1-/3Gb option Actiove

2-whatis the ram SIZE if low - incraese

3-vireus Scan

becasue you are using only pfcg sap t-code , it will not required a more memeory . why consume a more memeory ,most probly virus problem .

4-Program bug - serch note 0r communcate with sap

thanks

[Former Member]

Hello,

Thanks for the suggestions.

Just want to check one thing that 32 bit OS can create Memory related problem in ECC 6.0. Our ECC 6.0 is on window 2003 32 bit with SQL Server 2005.

Please suggest me.

Thanks

Rhishabh

[Former Member]

Hi,

You will always get memory problems when running ECC6 on a 32 bit system...

You can't even install it with the SR3 installation media.

Regards,

Olivier

[markus_doehr2]

> Just want to check one thing that 32 bit OS can create Memory related problem in ECC 6.0. Our ECC 6.0 is on window 2003 32 bit with SQL Server 2005.

Yes - because of the fact,that on 32bit the per-process memory is limited to 2 GB (3 GB). Your problem is explained in

Note 546361 - FAQ: Storage problems on NT/Windows 2000

There's also

Note 931024 - FAQ: 64-bit platforms for Windows

which says:

As of basis release 6.20 productive use of 32-bit platforms is not recommended.

There are more notes on that topic:

Note 996600 - 32 Bit platforms not recommended for productive NW2004s apps (NW2004s = Netweaver 7.0 = Basis of ERP 6.0)

Note 1280759 - SAP recommends only 64-Bit Windows for SAP Appl. Servers

I HIGHLY suggest considering upgrading to a 64bit OS. Most server produced in the last two years are able to run a 64bit operating system.

Markus

[markus_doehr2]

> Runtime Errors STORAGE_PARAMETERS_WRONG_SET

> Date and Time 03.08.2009 09:35:25

That parameter means, that you reached the OS imposed limits.

There are quite a few threads here on SDN giving suggestions what you can do to have a "workaround" for this (use the search function).

Markus

[former_member182034]

hi

STORAGE_PARAMETERS_WRONG_SET an error code, that points to memory bottleneck Minimum 
data transfer with context change; however, the increase helps to avoid problems 
(address space, swap space, operating system paging).

Please increase the 20 % value of this parameter abap/buffersize and check.

Regards,

[Former Member]

I changed the parameter but suddenly, PF page size become 8+ GB, its about to crash. So, I changed the parameter to the previous value (1,50,000)

I am getting memory related problem is it due to window 32 Bit? Server is running on win 2003 32 bit not on 64 bit.

Please suggest me.

Thanks

Rhishabh

[former_member182034]

please also check parameters for PHYS_MEMSIZE

and

read SAP Note 88416 - Zero administration memory management

secondly

you can revert those parameter or you can use back file of instance profile in profile parameters

Regards