Administration

AL11 Display SAP Directories
OSS1 Logon to Online Service System
SARA Archive Management
SCC3 Copy Analysis Log
SCC4 Client Administration
SCC5 Client Delete
SCC7 Client Import Post-Processing
SCC8 Client Export
SCC9 Remote client copy
SCCL Local Client Copy
SICK Installation Check
SM01 Lock Transactions
SM02 System Messages
SM04 User Overview
SM12 Display and Delete Locks
SM13 Display Update Records
SM14 Update Program Administration
SM21 System Log
SM35 Batch Input Monitoring
SM50 Work Process Overview
SM51 List of SAP Servers
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM66 System Wide Work Process Overview
SAINT SAP Add-on Installation Tool
SPAM SAP Patch Manager (SPAM)
SPAU Display modified DE objects
SPDD Display modified DDIC objects
ST11 Display Developer Traces
ST22 ABAP/4 Runtime Error Analysis
SU56 Analyze User Buffer

Alert Monitoring

AL01 SAP Alert Monitor
AL02 Database alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL16 Local Alert Monitor for Operat.Syst.
AL18 Local File System Monitor
RZ20 CCMS Monitoring

Configuration

FILE Cross-Client File Names/Paths
RZ04 Maintain Operation Modes and Instances
RZ10 Maintenance of Profile Parameters
RZ11 Profile parameter maintenance
SE93 Maintain Transaction Codes
SM63 Display/Maintain Operating Mode Sets
SPRO Customizing: Initial Screen

Database Administration

DB01 Analyze exclusive lockwaits
DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar
DB15 Data Archiving: Database Tables

Jobs

SM36 Define Background Job
SM37 Background Job Overview
SM39 Job Analysis
SM49 Execute External OS commands
SM62 Maintain Events
SM64 Release of an Event
SM65 Background Processing Analysis Tool
SM69 Maintain External OS Commands

Monitoring

AL08 Current Active Users
OS01 LAN check with ping
RZ01 Job Scheduling Monitor
RZ03 Presentation, Control SAP Instances
ST01 System Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace
ST06 Operating System Monitor
ST10 Table call statistics
ST03 Performance, SAP Statistics, Workload
ST07 Application monitor
STAT Local transaction statistics
STUN Performance Monitoring (not available in R/3 4.6x)

Spool

SP01 Output Controller
SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration

Transports

SCC1 Client Copy – Special Selections
SE01 Transport Organizer
SE06 Set Up Workbench Organizer
SE07 CTS Status Display
SE09 Workbench Organizer
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE16 Data Browser
SE80 Repository Browser
SM30 Call View Maintenance
SM31 Table Maintenance
STMS Transport Management System

User Administration

PFCG Profile Generator (Activity Group Maintenance)
PFUD User Master Data Reconciliation
SU01 User Maintenance
SU01D User Display
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 User Mass Maintenance
SMLG Maintain Logon Group
SUPC Profiles for activity groups
SUIM Infosystem Authorizations

ABAP DUMPS:

An error in an ABAP program that is running in a background generally causes an immediate termination of the background job. If an ABAP program terminates, an ABAP dump is usually generated. This dump contains a description of the precise cause of the error.

You can use transaction code: ST22 to look at the dumps generated.

Some more info, I was forwarded these in an email and thought it might be useful for the readers here:

1.)We are running SAP release 4.0B using the 620 GUI. By default, my list, save, local file, directory is C:SapWorkDir. How do I change this to something else? If I click on Options there is a directory for the local data area, which looks like the place to change the directory, but that does nothing. There must be a way to change this.

Use transaction SO21 to maintain the PC local directory. Or, run the ABAP program (via SA38 or SE38) RSSOPCDR.

2.)I would like to know which users have access to particular transactions. Is this possible?

Yes. There are several ways.

I think the easiest one is for you to run transaction /nSUIM. In this transaction (User Information System), drill down to:

Infosystem authorization -User -Users by complex selection criteria -By transaction authorizations

Finally, enter the transaction in question and execute.

If you are running R/3 4.7, you can also run transaction /nPFCG.

3.)I want to install SAPGUI into 50 machines. Can I do it from the server by installing the SAP installation server? If so, how?

Go to the “Knowledge Corner” section and look for it under “SAPGUI 6.20 for Windows”. The steps are basically the same for SAPGUI 6.40 –if you are installing that version.

Once you have set up the server you can use SAPadmin to create custom packages and install the client software remotely.

4.)I’d like to know if we make client copy today, will the data will be copied to another client today as well? Suppose after one week I want to copy the rest of the data to the same client. Will I have to copy all the client data and overwrite it, or do I have an option to copy only one week’s worth of data and update it?

A client copy overwrites the target client. The only exception is the user master records (SAP_USER copy profile). But, you cannot just copy a week’s worth data using SAP standard tools. You need to use ALE to transfer the data you want or use third-party tools for that.

5.)I have a problem with my server. When I start the server the dispatcher (disp+work.exe) is getting started, but then it’s stopping. I am using R/3 4.6B. Its sysid = DEV and the OS = 2003server.

This could be due to a number of reasons. My best recommendation at this time is to examine the developer tracer.

Within the SAP MMC, right-mouse click on the instance name and choose developer traces from the drop-down menu. There, choose to examine the file dev_disp, dev_ms and see if there are any dev_wpX files exist.

Also, make sure that the system profiles exists under usrsapsysprofile. Check that the services file contains the appropriate entries (example: sapMS xx).

6.)Can we make the WPs changes in operation mode effective immediately by force? One of our consultants said that it is possible through a transaction.

Yes. It’s possible via transaction RZ03.

Choose the instance and use Control -> Switch Operation Mode.

7.)Users are complaining that the SAP system shows a hour glass for a long time at the time of logon and they aren’t able to log on to the system. How can I troubleshoot this problem?

This is a symptom of busy dialog processes. Use one of these tools to find out the status of the work processes: dpmon.exe at the OS level (part of the R/3 kernel), MMC and SM50 (Work Process Overview).

Also, check the CPU and other system resources via ST06 and using Performance Monitor at the OS level.

8.)I have a stand-alone computer for which I forgot the user and password for log in.

Is there anyway I can log in to it?

Yes. This requires you to go to the database level, though. I don’t know what RDBMS you have (MSSQL, Oracle, MaxDB, etc.). But, really all you have to do is to delete the SAP record in table USR02 for client 100. After that, SAP will let you log in as SAP with password PASS.

9.)Our SAP file system is filling up because initially it was defied too small. What are the non-required files that can be deleted from the SAP system? We are using HP-UX NetWeaver2004s on an Oracle database.

The files that can be deleted are mentioned below.

1. Offline Redo log files

Backup them and then delete

2. Old spool and log files

They are not necessary for R/3 functions and should be deleted regularly by scheduling a periodic batch job.

3. File name “CORE” (Unix only)

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often contains a file called ‘core’ from previous program terminations. This file may be deleted at any time.

4. Old ABAP/4 trace files.

Use Transaction SE30 to delete the files

5. Old output requests

They are stored on the data directory as files SP*.

Remember that deleting these files is not a permanent solution. You should increase the file system sizes.

10.)It is a very common misconception that “sequential reads in SM50 means that a full table scan is executed and an index is not used”. The correct definition/concept is:

Direct read

The term “Direct read” refers to accesses in which a maximum of one line is returned by the database. This includes summarization queries such as SELECT COUNT and fully-qualified primary key accesses.

Sequential Read

A “Sequential Read” refers to all other read database accesses, in which there may be more than one line returned. It is true that the term “Sequential read” is a little deceptive since it implies that blocks are always read sequentially (as in a full table scan). In reality, however, when you perform a trace on these queries you will see that index is used in most cases.

So, “Direct read” and “Sequential read” in SM50 are worthless for a performance analysis. It only shows that the processes are running and processing one of the queries directed at the database interface.

For expensive SQL statements analysis, “Reads/User Calls” value (TCODE BACOCKPIT or ST04OLD) is an indication. If this value is above 15, the SQL statements should be checked in detail.

11.)My admin user ID has been locked out. Is there a table I can update in Oracle to reset the flag and enable myself to log in?

Select all entries of table USR02 where ‘UFLAG’=128. These users are locked by reason of incorrect logons. ‘UFLAG’=64 will give you the users that are blocked by Administrator. Set ‘UFLAG’ to 0, to unlock your account.

12.)Why are transport requests classified into workbench and customizing? What does this classification indicate?

All customizing changes (changes to SAP functionality) are collected in customizing requests. Changes to the SAP repository and data dictionary (customers development or changes to SAP standard objects) are collected in workbench requests.

All you  need to know about SAP Notes:

SAP Notes give you instructions on how to remove known errors from SAP Systems. They include a description of the symptoms, the cause of the error, and the SAP Release and Support Package level in which the error occurs.

Depending on the type of error, an SAP Note may also include:

· Workarounds

· Descriptions of how to correct repository objects in the ABAP workbench, known as correction instructions

· Links to Support Packages that solve the problem

You can access SAP Notes both from the SAP Service Marketplace and SAPNet – R/3 Frontend.

Caution: The Note Assistant can automatically implement only SAP Notes that have correction instructions.
Read the SAP Note carefully before you use the Note Assistant to implement it. The SAP Note can contain prerequisites, interactions, and references to postprocessing activities (making changes to a table, for example) that you must take into consideration when you implement it.
Technical Details on Correction Instructions Locate the document in its SAP Library structure

You can find information about the following topics here:

The format of correction instructions

The validity of correction instructions

Prerequisites for correction instructions

Objects that can be changed using correction instructions.
Format

Correction instructions describe the changes that must be made to repository objects in the ABAP Workbench and particularly the source code of ABAP programs to correct errors.

Changes to the Source Code

Each change specifies the object (include, function module, and so on) and the modularization unit (FORM routine, for example). To identify the code that needs to be changed, a unique number of preceding unchanged lines is specified (context block). These are followed by the lines that need to be deleted (delete block) and then the new lines (insert block).

Correction instructions can consist of multiple context, delete and insert blocks.

When the system implements correction instructions automatically, it searches for the context blocks in the function module or include, checks whether the delete blocks follow and then replaces them with the insert block.

If the function module or include has been modified by the customer, the system sometimes cannot find the context blocks or delete blocks specified in the correction instructions, and it cannot implement all the corrections. If this is the case, you can use the split-screen editor to adjust the corrections from the SAP Note to your modifications.

Changes to Other Repository Objects

Repository objects or parts of them that are not of the source code type are stored in database tables. A correction instruction contains information about which table entries have to be deleted, inserted or changed to correct an error. The system displays this information in the form of contents of a correction instruction. However, this display is primarily designed with experts in mind, for the purpose of problem analysis. We recommend that you do not implement correction instructions manually using this information. Use the automatic implementation only.

Validity

All correction instructions specify the releases and Support Package levels in which you can implement them. These release and Support Package levels are known as the validity range of the correction instructions.

For example, if Support Package 5 corrects and error in Release 4.6C, the validity range of the correction instructions is 4.6C Support Packages 1 -4.

An SAP Note can also determine that correction instructions are not allowed to be implemented if a certain software component (an add-on, for example) exists in the system. This is the case, for example, when a correction changes a program part that is required by another software component in an unaltered form.

If an exception such as this was defined, it is displayed in the header area of the correction instructions, under Invalid for .

The Note Assistant automatically checks the validity and only implements a correction instruction if the system status is within the validity range specified.

Prerequisites

In some cases, you can only implement correction instructions if certain other correction instructions have already been implemented. This is due to related changes made to the same part of the source code, or semantic dependencies.

These dependencies are described in the header area of the correction instructions. These dependencies (prerequisites) mean that you need to implement a sequence of SAP Notes, and not just one SAP Note.

Objects that can be changed using correction instructions.

Troubleshooting SAP startup problems:

SAP System startup Problems:

On Windows, Two places you need to check are: EventViewer (Application and System logs) and the SAP Management Console (MMC).
Event Viewer can provide useful information and it may help you pinpoint where the problem resides. The SAP MMC gives you the ability to visually see the system status (green, yellow or red lights), view the work processes status and view the developer traces, which are stored in the “work” directory. Example: /usr/sap/TST/DVEBMGS00/work.

For a central SAP instance to start successfully, both the message server and the dispatcher need to start. If one of them or both fail to start, users cannot log in to the system. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message:
“DISPATCHER EMERGENCY SHUTDOWN “.

Developer Traces:
dev_disp Dispatcher developer trace
dev_ms Message Server developer trace
dev_wp0 Work process 0 developer trace

The “services” file, which contains TCP and UDP services and their respective port numbers. This plain-text configuration file is located under winnt/system32/drivers/etc.

Windows Task Manager (TASKMGR.exe), Event Viewer (EVENTVWR.exe).

Dispatcher Monitor (DPMON.exe), which is located under /usr/sap//sys/exe/run. Database logs.

1. Dispatcher does not start due to a port conflict

No work processes (disp+work.exe) exist in Task Manager.

Dispatcher shows status “stopped” in the SAP MMC.

Errors found in “dev_disp”:

LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti.c 1488]
*** ERROR => NiIBind: service sapdp00 in use [nixxi.c 3936]
*** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi.c 3505]
*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]
*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit
*** DISPATCHER EMERGENCY SHUTDOWN ***

Problem Analysis
I highlighted the keywords in the error messages above: Address already in use Service sapdp00 in use The TCP port number assigned in the “services” file is being occupied by another application. Due to the conflict, the dispatcher shuts down.

Solution
If your server has a firewall client, disable it and attempt to start the SAP instance again.
If the instance starts successfully you can enable the client firewall back again.
If there is no firewall client at all, or if disabling it did not resolve the problem, edit the “services” file and check what port the appropriate “sapdp” is using.
If the instance number is 00, look for sapdp00. If the instance number is 01 look for sapdp01 and so on. You can use the following OS command to help you resolve port conflicts:
netstat -p TCP There are also utilities on the Internet that can help you list all the TCP and UDP ports a system is using.

2: Dispatcher dies due to a database connection problem

No database connections.

No work processes

SAP MMC -> WP Table shows all processes as “ended”.

Errors found in “dev_disp”:
C setuser ‘tst’ failed — connect terminated
C failed to establish conn. 0
M ***LOG R19=> tskh_init, db_connect (DB-Connect 000256) [thxxhead.c 1102]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8437]
*** ERROR => W0 (pid 2460) died [dpxxdisp.c 11651]
*** ERROR => W1 (pid 2468) died [dpxxdisp.c 11651]
*** ERROR => W2 (pid 2476) died [dpxxdisp.c 11651]. . .
*** ERROR => W11 (pid 2552) died [dpxxdisp.c 11651]
*** ERROR => W12 (pid 2592) died [dpxxdisp.c 11651]
my types changed after wp death/restart 0xbf –> 0×80
*** DP_FATAL_ERROR => DpEnvCheck: no more work processes
*** DISPATCHER EMERGENCY SHUTDOWN ***
DpModState: change server state from STARTING to SHUTDOWN

Problem Analysis
A connection to the database could not be established because either the SQL login specified in parameter “dbs/mss/schema” is set incorrectly or the SQL login was deleted from the database server. This parameter needs to be set in the DEFAULT.pfl system profile (under /usr/sap//sys/profile). In the messages above, we see that the SQL login ‘tst’ is expected but it does not exist at the database level.

Solution
Set the entry to the appropriate database owner. If the system is based on Basis <= 4.6 or if the system was upgraded from 4.x to 4.7 the database owner should be “dbo”. But, if the system was installed from scratch and it’s based on the Web AS 6.x the database owner should match the SID name in lower case. Example: if the SID is TST then the database owner should be “tst”. If the parameter is set correctly in the DEFAULT.pfl profile check at the database level if the SQL login exists. If it doesn’t, create it and give it database ownership to the .

3: SAP does not start at all: no message server and no dispatcher

The message server and the dispatcher do not start at all in the SAP MMC. The following error when trying to view the developer traces within the SAP MMC: The network path was not found. No new developer traces written to disk (under the “work” directory.)

Problem Analysis
The network shares “saploc” and “sapmnt” do not exist. That explains the “network path not found” message when attempting to view the developer traces within the SAP MMC.

Solution
Re-create the “saploc” and “sapmnt” network shares. Both need to be created on the /usr/sap directory

4: Users get “No logon possible” messages

Work processes start but no logins are possible.

Users get the login screen but the system does not log them in. Instead, they get this error: No logon possible (no hw ID received by mssg server).

In the SAP MMC, the message server (msg_server.exe) shows status “stopped”.

The dev_ms file reports these errors:
[Thr 2548] *** ERROR => MsCommInit: NiBufListen(sapmsTST) (rc=NIESERV_UNKNOWN) [msxxserv.c 8163]
[Thr 2548] *** ERROR => MsSInit: MsSCommInit [msxxserv.c 1561]
[Thr 2548] *** ERROR => main: MsSInit [msxxserv.c 5023]
[Thr 2548] ***LOG Q02=> MsSHalt, MSStop (Msg Server 2900) [msxxserv.c 5078]

Problem Analysis
Work processes were able to start but the message server was not. The reason is because the “services” file is missing the SAP System Message Port entry. Example: SAPmsTST 3600/tcp

Solution
Edit the “services” file and add the entry. Then, re-start the instance. Make sure you specify the appropriate TCP port (e.g. 3600) for the message server.

5: The message server starts but the dispatcher doesn’t

The dispatcher shows status “stopped” in the SAP MMC.

The “dev_disp” file shows these errors:
***LOG Q0A=> NiIServToNo, service_unknown (sapdp00) [nixxi.c 2580]
*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]
*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit
*** DISPATCHER EMERGENCY SHUTDOWN ***

Problem Analysis
The keyword in the messages above is “service unknown” followed by the entry name “sapdp00″. The dispatcher entry “sapdp00″ is missing in the “services” file. Example: sapdp00 3200/tcp

Solution
Add the necessary entry in the “services” file. Example: sapdp00 3200/tcp Then, re-start the instance.

6: Work processes die soon after they start

All work processes die right after the instance is started.

The SAP MMC shows work processes with status “ended”.

Only one work process shows status “wait”.

An ABAP dump saying “PXA_NO_SHARED_MEMORY” is generated as soon as a user logs in.

The SAP MMC Syslog shows the following error multiple times: “SAP-Basis System: Shared Memory for PXA buffer not available”.

Problem Analysis
The instance profile contains misconfigured memory-related parameters. Most likely the “abap/buffersize” instance profile parameter is set to high.

Solution
Edit the instance system profile at the OS level under /usr/sap//sys/profile and lower the value assigned to “abap/buffersize”. Then, restart the instance. Also, it’s important to find out if any other memory parameter were changed. If not, the system should start once the adequate memory allocation has been set to the the “abap/buffersize” parameter.

‘logical system’ is used to identify an individual client in a system, for ALE
communication between SAP systems. That’s why you see a field for ‘logical
system’ in the client master data in SCC4 (table T000). You use logical systems
in ALE config – this should be documented further in the IMG guide, or SALE and
BALE transactions.

The naming convention for the logical system names which includes distinct IDs depending on:
System ID (SID), and client number, and maybe also system number if you have more than one instance per host machine. Hostname would be useful too, but I think there’s only 10 characters in v3.1x (maybe more with long name functionality in 4.x ??).

eg., in DEV box , sys no 00, client 100, choose something like ‘DEV00_100′.

The logical system must be defined or you get error messages all over the place during order processing stating the logical system has not been defined. The logical system is defined in the IMG. In 4.* it is found in the IMG > Cross Application Components > Distribution ALE > Basic settings > Logical systems > Define logical systems. Here the entry is just an identifier and a text entry.
“Logical Systems. The distribution of systems ( ALE ) makes it necessary to be able to
identify every system individually within a network. The “logical system” is
used to do this. A logical system is an application system within which the applications are
coordinated to work in one database. In the SAP sense of the word, a logical
system corresponds to a client. In the following steps, you must define every client as a logical system by first of all defining logical systems and then assigning the clients in
question to the corresponding logical systems

Note: Assignments must be unique (that is, a client may only be assigned to one
logical system.
Several clients must never be assigned to the same logical system.” Reading this it does seem that it is nothing more than another identifier for a “Client”.

So, What are user groups and how can we use them?

Transaction SUGR is used for User Groups.

User group can be used for different reasons and in different way.

In the latest versions of SAP, there are two types of usergroups

The authorization user group &
The general user groups

Naturally the main reason of user groups is to categorize user into a common denominator.

The authorization user group is used in conjunction with S_USER_GROUP authorization object. It allows to create security management authorization by user group. e.g. you can have a local security administrator only able to manage users in his groups, Help-Desk to reset password for all users except users in some group.

The general user group can be used in conjunction with SUIM and SU10, to select all the users in a specific group. User can only be member of one authorization user group but several general user group.

One of the Primary uses of user groups is to sort users into logical groups.

This allows users to be categorised in a method that is not dependent on roles and Responsibilities and Profiles.

User Groups also allow segregation of user maintenance, this is especially useful in a large organization as you can control who your user admin team can maintain – an example would be giving a team leader the authority to change passwords for users in their team.

Why, just because we can!

If you want the user to be locked after unsuccessful logon attempts, you can put a parameter in the Instance Profile to prevent them from doing so.

Transaction RZ10–> Instance Profile–> Extended Maintenance

Use the ‘login/fails_to_user_lock’ Parameter.
Defines the number of unsuccessful logon attempts before the system locks the user. By default, the lock applies until midnight.

Default value: 12; permissible values: 1 -99

To remove the lock after midnight :
login/failed_user_auto_unlock: Defines whether user locks due to unsuccessful logon attempts should be automatically removed at midnight.

Default value: 1 (Lock applies only on same day); permissible values: 0, 1

rdisp/vbname: Specifies the name of the update server that is to process the updates if load balancing is deactivated ( rdisp/vb_dispatching = 0 ).

In the standard system, this parameter specifies the name of an update server (set when the update server is created). If rdisp/vb_dispatching is set to 0, the updates are only processed by the server in rdisp/vbname.

rdisp/vb_delete_after_execution:Determines whether update records are deleted automatically after they have been processed successfully.

In the standard system, this is set to 1 (automatic deletion activated).

If set to 2, automatic deletion is deactivated. This value can be used to set the update and database performance. In this case, the report rsm13002 with the parameter DELETE = X should run in the background at least once a day to prevent the update tables from becoming excessively large. See also the section entitled Structure link Background Processing in the CCMS documentation.

rdisp/max_vb_server: Maximum number of update servers permitted in the SAP System. Default = 50 servers.

rdisp/vb_included_server:List of the SAP update servers, which are to be used to process updates in accordance with the load balancing principle. No updates are assigned to update servers that do not appear in the list.

This parameter is empty in the standard system. This means that all active update servers are taken into consideration for the load balancing mechanism. This is generally speaking the optimum value.

rdisp/vbdelete:Specifies the number of days after which the update records are deleted. The parameter is set to 50 days in the standard system.

Once this interval has expired, an update record is deleted irrespective of its status (processed, not processed, error etc.).

If set to 0, automatic deletion is deactivated. This value should only be set temporarily, and only if an incorrect update record is to be kept for further analysis.

You may get the above error when trying to login to ITS or setting up the URL for HTTP Connect – URLAccess

http://<server_name>:8000/sap/bc/gui/sap/its/webgui?sap-client=nnn

Primary problem is that the memory parameter em/global_area_MB has not been set correctly or is not high enough for ITS. Use the following note to calculate it or just set it to 360 to start with.

Note 742048 – Integrated ITS, memory requirement in application server

Complete error message was:
Error when processing your request

What has happened?

The URL http://server:8000/sap/bc/gui/sap/its/webgui was not called due to an error.

Note

* The following error text was processed in the system SID : New session was refused due to memory bottleneck

* The error occurred on the application server server_SID_00 and in the work process 0 .

* The termination type was: ABORT_MESSAGE_STATE

* The ABAP call stack was:
Function: ICF_ATTACH_ITS_PLUGIN of program SAPLHTTP_RUNTIME
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP

What can I do?

* If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SID in transaction ST22.

* If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server server_SID_00 in transaction SM21.

* If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server server_SID_00 . In some situations, you may also need to analyze the trace files of other work processes.

* If you do not yet have a user ID, contact your system administrator.

Error code: ICF-IE-http -c: 300 -u: USER -l: E -s: SID -i: server_SID_00 -w: 0 -d: 20100112 -t: 121110 -v: ABORT_MESSAGE_STATE -e: New session was refused due to memory bottleneck

HTTP 500 – Internal Server Error

Your SAP Internet Communication Framework Team