Error Message Tyoe

[Former Member]

Dear Experts,

I am facing dump and error during System Preparation steps in steps 6.6 connect Diagnostic agent

when clicking this step

and in st22

Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_UNKNOWN
ABAP Program           CL_WDR_MESSAGE_MANAGER========CP
Application Component  BC-WD-ABA-RUN
Date and Time          16.04.2014 19:37:36
	Short text
	Message type "e" is unknown.
	What happened?
	Error in the ABAP Application Program
	The current ABAP program "CL_WDR_MESSAGE_MANAGER========CP" had to be
	terminated because it has
	come across a statement that unfortunately cannot be executed.
	What can you do?
	Note down which actions and inputs caused the error.
	To process the problem further, contact you SAP system
	administrator.
	Using Transaction ST22 for ABAP Dump Analysis, you can look
	at and manage termination messages, and you can also
	keep them for a long time.
	Error analysis
	Only message types A, E, I, W, S, and X are allowed.
	There is probably an error in the program
	"CL_WDR_MESSAGE_MANAGER========CP".
	How to correct the error
	Probably the only way to eliminate the error is to correct the program.
	-
	If the error occures in a non-modified SAP program, you may be able to
	find an interim solution in an SAP Note.
	If you have access to SAP Notes, carry out a search with the following
	keywords:
	"MESSAGE_TYPE_UNKNOWN" " "
	"CL_WDR_MESSAGE_MANAGER========CP" or "CL_WDR_MESSAGE_MANAGER========CM00R"
	"IF_WD_MESSAGE_MANAGER~REPORT_T100_MESSAGE"
	If you cannot solve the problem yourself and want to send an error
	notification to SAP, include the following information:
	1. The description of the current problem (short dump)
	To save the description, choose "System->List->Save->Local File
	(Unconverted)".
	2. Corresponding system log
	Display the system log by calling transaction SM21.
	Restrict the time interval to 10 minutes before and five minutes
	after the short dump. Then choose "System->List->Save->Local File
	(Unconverted)".
	3. If the problem occurs in a problem of your own or a modified SAP
	program: The source code of the program
	In the editor, choose "Utilities->More
	Utilities->Upload/Download->Download".
	4. Details about the conditions under which the error occurred or which
	actions and input led to the error.

[Former Member]

Hello guys,

We have a similar issue.

Here is why we got to this error. When i setup the SLD in step 6.1 i used another system, and the Solution Manager was non existent in that SLD/LMDB.

I now configured a local SLD in 6.1 and created a local LMDB.

I am now running the synchronization again ( which as you know takes a while ).

Probably the easiest way would have been just to define the system in the first LMDB, but in our case it's a development system and i wanted to try this also.

I will let you know after the sync is finished.

Catalin

[Former Member]

Hi guys,

I can confirm that it is working now. There are two options.

1. Set up a local SLD and LMDB.

2. Configure Solution Manager system in the used LMDB ( did not test this one but i'm pretty sure it works).

Regards,

Catalin