on 12-12-2008 2:06 AM
when i use the tcode:pfcg->change role "role_de"->menu->"from sap menu"->choose one node->save,
then error is display below:
http://picasaweb.google.com/lh/photo/Q-4BpuuXxBVpMpI40S5BBw
http://picasaweb.google.com/lh/photo/uyNkGRn3h6SXvTsMHPlH6g
How can i do it?
Thanks very much!
Because i'm a beginner, so i hope you can help me step by step.
Thanks very much!
http://picasaweb.google.com/lh/photo/5B7fgKxqPlTOZzmeo7cS0w
http://picasaweb.google.com/lh/photo/5B7fgKxqPlTOZzmeo7cS0w
http://picasaweb.google.com/lh/photo/1kFtk8YZGbSc_wGZ-To1Mg
http://picasaweb.google.com/lh/photo/NHZQfdj3aHTUUcci09UlXA
http://picasaweb.google.com/lh/photo/zcS6iSn6qpne5hIgv_PpIw
http://picasaweb.google.com/lh/photo/Bj3eWe2DIUJ7Tba-u37--Q
http://picasaweb.google.com/lh/photo/GTzTQzgU500bM3FioOcwXw
Edited by: Jean Hawk on Dec 12, 2008 4:42 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When i create the menu for the user, then "Runtime Errors STORAGE_PARAMETERS_WRONG_SET".
Please help me!
This is the error message:
Runtime Errors STORAGE_PARAMETERS_WRONG_SET
Date and Time 12.12.2008 10:26:56
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 741665808 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?
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 741665808. 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 DDDDDD_GREATWAYCOM_03 on host DDDDDD (wp 0)"
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 700
Application server... "DDDDDD"
Network address...... "192.168.99.23"
Operating system..... "Windows NT"
Release.............. "5.1"
Hardware type........ "Intel 801586 (M"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "DDDDDD"
Database type..... "MSSQL"
Database name..... "GREATWAYCOM"
Database user ID.. "ecc"
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.... 1609456
EM...... 447355872
Heap.... 313508640
Page.... 16384
MM Used. 734465040
MM Free. 27458464
User and Transaction
Client.............. 001
User................ "ADMIN"
Language Key........ "E"
Transaction......... " "
Program............. "SAPLSMNU_NEW"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "GREATWAYCOM"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........."C0A8001609E04941C90A0045"
Outbound Queue Name.." "
Client.............. 001
User................ "ADMIN"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_SHIP"
Call Destination.... "NONE"
Source Server....... "DDDDDD_GREATWAYCOM_03"
Source IP Address... "192.168.99.23"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPLSMNU_NEW" - in
"READ_MENU_HIERARCHY_FAST".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 1131
of the (Include) program "LSMNU_NEWF01".
Source Code Extract
Line SourceCde
1101 L_LIST_OF_TEXTS.
1102 PERFORM READ_HIERARCHY_INCLUDING_REFS
1103 TABLES L_LIST_OF_NODES
1104 L_LIST_OF_REFS
1105 L_LIST_OF_TEXTS
1106 L_VISITED_TREES
1107 USING P_TREE_ID
1108 SPACE
1109 L_MENU_LEVEL
1110 SPACE.
1111
1112 * get total number of nodes
1113 DESCRIBE TABLE L_LIST_OF_NODES LINES L_NUM_OF_NODES.
1114
1115 L_RATIO = L_NUM_OF_ALL_NODES / L_NUM_OF_NODES.
Thanks for your help!
> Please help me!
Do mind the forum rules about strongly asking for help. If you have a problem on your company landscape SAP support is the one to contact. We're just a bunch of volunteers with our own fulltime jobs.
Now, from your dump:
> What happened?
> The current program had to be terminated because of an
> error when installing the R/3 System.
> The program had already requested 741665808 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.
This is definately not a security issue...... As stated before in this thread, it is something about memory.
> What can you do?
<SNIP>
> In the system profile, set the parameters
> -abap/heap_area_dia and
> -abap/heap_area_nondia
> to a maximum of 741665808. To be on the safe side, reduce the value by 10,000,000.
>
> Then restart the SAP system.
Did this help? Did you do it?
Call Transaction RZ10. Specify the name of the profile whose parameters you want to change in the Profile field.
If you want to change the name of the file in which the profile should be activated, check Administration data and choose Change.
You can create, change or delete all parameters in a profile by choosing Extended maintenance. Once you have made the changes, choose Copy
Click create/change parameter and enter the parameter and value.
Once you have made the changes, choose Copy.
Save and activate the profile and restart the sap instance.
Regards,
Jazz
.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.