error with dump MESSAGE_TYPE_X

Old - This MESSAGE_TYPE_X short dump is mostly caused by unstable processing in Frontend / SAPGUI or in its installation. The common solution for this problem is first restart the computer, then if problem still persists to use another stable SAPGUI version with uninstalling the existing and installing another version.

However this error is generic error not only caused by SAPGUI unstability / GUI issue. If it happened to only few tcode such as known issue in Finance 1365712 - Generating FI programs during posting after importing SP.

In BW the error mostly caused by inconsistency of data definition from design/configuration level transferred to ABAP object/code/dictionary level.

The stable version doesn't mean the latest version but certain patches level. Most of the time the certain patches level is also the latest one. So try first to use the latest GUI version such as SAPGUI 7.10 patches level 2.

Sometimes applying the only patches doesn't work, we need to uninstall the SAP GUI completely then install another. In very rare situation, the server kernel need to be patched to higher patch level.

We also need to consider the maintenance period of our SAPGUI, we can start seeing this from http://service.sap.com/pam (Product Availability Matrix)

So bye bye MESSAGE_TYPE_X ....

notes: ftp to the software is also available as following

• 710 version
• 640 version
• SAPGUI 720

Other case can be happened with similar symptom when

- using new SAPGUI version without additional patches,

- after SAP upgrade, SAP kernel upgrade,

- wrong combination of software component (e.g. SAPGUI, MS Office, .Net, etc),

- wrong connection data for Service/System/Communication users (language, unicode, etc),

- after system copy but landscape data still not match or conflicting,

- failure of data conversion in ABAP code level,

- inconsistency in infocube (corrected using tcode RSRV button "Correct Error"),

- when accessing infopackage after changing transfer rules or communication structures (fixed with deleting flag for specific datasource note 852443 table RSSDLINIT field initstate),

- opening or creating package in BW (solved with note 852443 and 405943), 

- data transfer without init/initialization.

How to check more: run ST22 tcode, SM21, check SAPGUI version from SAPGUI logon pad, checking kernel level from SM51 Release Info (or menu Status)

old material is here.

ABAP DUMP, system error log : Maximum number of permitted terminal connections reached (200)

ABAP DUMP, system error log : Maximum number of permitted terminal connections reached (200)

SAP Note #22099 : parameter to fix the issue

The space available in the C table tm_adm is not sufficient for another
terminal to log on to this applicatin server. The number of table
elements is determined by the profile parameter 'rdisp/tm_max_no'
when the application server is started.
Important: For internal purposes one entry for each work process and
one entry for each CPIC connection is made in tm_adm in addition to
an entry for each work process.

Analysis:
- recheck the profile parameter, file of instance parameter, also try run RSPARAM report, check in all instance one by one
- check SNAP table or SM21
- memory utilization , check in SM50 especially when status PRIV found or NRIV (?)

- session number, computer terminal / workstation number

- a transaction also can open a new other session

- check netstat -a for connection number

500 Internal Server Error in Portal/Java stack

SAP Error: 500   Internal Server Error

Web Dynpro Container/SAP J2EE Engine/7.00

Web Dynpro Container/SAP J2EE Engine/6.40

Failed to process request. Please contact your system administrator.

System: Portal, Netweaver, Java, ESS/MSS, CRM

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

500, internal server error, javax.ejb.EJBException in the object EJBIuclidDispatcherBean.

Error 500- Internal Server Error

java.rmi.RemoteException: Error in ejbCreate:;nested exception is: javax.ejb.EJBException: nested exception is: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.jts.wipPool' Resolved jdbc.jts;remianing name 'wipPool'

   java.lang.NullPointerException

    at com.testsystem.abcd.ess.basicsalary.fc.FcBasicSalary.onInit(FcBasicSalary.java:222)

    at com.testsystem.abcd.ess.basicsalary.fc.wdp.InternalFcBasicSalary.onInit(InternalFcBasicSalary.java:339)

    at com.testsystem.abcd.ess.basicsalary.fc.FcBasicSalaryInterface.onInit(FcBasicSalaryInterface.java:125)

    at com.testsystem.abcd.ess.basicsalary.fc.wdp.InternalFcBasicSalaryInterface.onInit(InternalFcBasicSalaryInterface.java:242)

    at com.testsystem.abcd.ess.basicsalary.fc.wdp.InternalFcBasicSalaryInterface$External.onInit(InternalFcBasicSalaryInterface.java:298)

Web Dynpro Code Generation Infos

testsystem.com/abcd~basicsalary

Analysis:

- program error, if already identified by SAP the correction and solution will be contained in newer version of SCA archive

- error in business package

- not correct DB server URL can cause this error

- caused by problem when connecting to database, caused by database driver

- accessing incorrect URL inside the iview

Solution:

- Download the latest version of the following SCA archive from SAP Service Marketplace and install it on the Java server

- some cases can use SAP Note tool SNOTE, sometimes not possible to use SNOTE, manual correction needed to implement adjustment

- checking database connection, update database driver

old material is here.