topic Re: Error MESSAGE_TYPE_X in Application Development and Automation Discussions

Error MESSAGE_TYPE_X

Former Member — Wed, 06 Feb 2008 09:30:52 GMT

Hello Experts,

I have a program scheduling back ground it's taking 60000 sec to finish and giving dump in st22

Runtime Errors MESSAGE_TYPE_X

Technical information about the message:

Diagnosis

The system tried to initialize the environment for processing

parallel RFCs using the function module SPBT_INITIALIZE. Here the

system established that there are no resources in the system. This

is a configuration problem. Only those application servers with at

least three dialog work processes can be used to process parallel

RFCs.

System response

Procedure

1. If no specific server group name is specified for processing

parallel RFCs:

All application servers in your system have less than three

dialog work processes. If you want to process parallel RFCs, a

least one application server must have at least three dialog

work processes.

2. If a server group name was specified using Transaction RZ12 fo

processing parallel RFCs:

All application servers in the server group have less than

three dialog work processes. If you want to process parallel

RFCs, then at least one application server in the server group

must have at least three dialog work processes.

88 * Parallel Execution

89 CALL FUNCTION '/SAPAPO/MSDP_PAR_PROCESS_START'

90 EXPORTING

91 iv_application = gs_application_parallel-dp_batch

92 iv_par_profile = gs_tsplb-PAR_PROFILE

93 iv_pareaid = gs_tsplb-parea

94 * IMPORTING

95 * ET_MESSAGE =

96 EXCEPTIONS

97 INVALID_INPUT = 1

98 INTERNAL_ERROR = 2

99 NO_BATCH_MODE = 3

00 NO_AUTHORITY = 4

01 OTHERS = 5.

02 IF sy-subrc <> 0.

>> MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

04 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

05 ENDIF.

When I clicked the abap editor then it's taking to '/SAPAPO/TS_BATCH_RUN' report.

Can you please suggest me what would be the error and how to find the solution...

Thanks in advance.

Sandhya

Re: Error MESSAGE_TYPE_X

Former Member — Wed, 06 Feb 2008 09:34:05 GMT

error with dump MESSAGE_TYPE_X

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 to use another stable SAPGUI version with uninstalling the existing and installing another version.

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.

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)

Reward Points if useful.

Re: Error MESSAGE_TYPE_X

Former Member — Wed, 06 Feb 2008 09:44:16 GMT

Hi Sravan,

Thanks a lot for quick reply.

This error I am getting in the Quality.

I got this error actually when I have changed the program logic .

Before that the Program working fine in the quality and taking only 6500 sec (BG job).

In my coding I have added 2 read statements and 2 more conditions.with this the program working fine in the development.In quality it's taking long time and giving dump.

Is this becuase of my new changes in the program.

Please help me out.

Best Regards,

Sandhya

Re: Error MESSAGE_TYPE_X

Former Member — Wed, 06 Feb 2008 09:50:41 GMT

In your report, you must have used Message of type X, which gives dump. Message of type X is used to achieve Forceful termination (give ABAP dump).

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1

Note 689991 - Runtime error MESSAGE_TYPE_X

Reward points if useful.

Re: Error MESSAGE_TYPE_X

Former Member — Wed, 06 Feb 2008 10:21:39 GMT

I have not used the Message X.

If I want to trace out why this is happening how can I do that.

Thanks and Regards,

Sandhya

Re: Error MESSAGE_TYPE_X

Former Member — Wed, 06 Feb 2008 15:20:47 GMT

You haven't posted the code, but I will take a guess.

You said that you added two READ statements. Make sure you use the BINARY SEARCH addition of the READ.

Rob

Re: Error MESSAGE_TYPE_X

Former Member — Thu, 07 Feb 2008 09:04:31 GMT

Hi Rob,

I used the Read statements with Binary search and sorted it before with the keys.

The job finished successfully in quality but its showing dump with Message_X.In diagnosis it gave

The system tried to initialize the environment for processing

parallel RFCs using the function module SPBT_INITIALIZE. Here the

system established that there are no resources in the system.

Is this error becuase of the long time of execution of the job or

something else.

can we trace why it's taking this much of time.

Thanks and Regards,

Sandhya

Re: Error MESSAGE_TYPE_X

Former Member — Thu, 07 Feb 2008 15:26:54 GMT

From the error message, it seems to be saying that there are not enough dialogue processes available.

Rob

Re: Error MESSAGE_TYPE_X

Former Member — Mon, 18 Feb 2008 04:17:59 GMT

Hello Experts ,

I have checked about the Dialogu work processes that are available there are 16 dialogue work processes in the Quality.

And I have executed this program with SE30 it gave dump.

In the dump it is showing that aNative SQL statement in the BAPI is taking more time and it gave Native SQL Error.

Can you please tell me why this is happening.

Thanks and Regards,

Sandhya

Re: Error MESSAGE_TYPE_X

Former Member — Mon, 18 Feb 2008 04:40:21 GMT

You still haven't posted the code.

Rob