cancel
Showing results for 
Search instead for 
Did you mean: 

SolMan configuration - Message type "e" is unknown

former_member117942
Participant
0 Kudos

Hi all,

every time i select the step 6.6 (Connect Diagnostics Agents to Solution Manager) of the System Preparation in SolMan 7.1 SP11 i receive the following message (and related dump in ST22).

Message type "e" is unknown.

Same thing happens in two different Solution Manager (same version and SPS).

Looking for SAP Notes without help.

Any suggestions?

Regards.

Accepted Solutions (0)

Answers (8)

Answers (8)

Former Member
0 Kudos

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
0 Kudos

Hello;

Unfortunately same problem. Did you find any solution about that?

Former Member
0 Kudos

Hi Enis,

Have you tried to find an error message as Rainer suggested?


Regards,

Alex

Former Member
0 Kudos

Hi;

I can not found message number. can you help me about it?

Former Member
0 Kudos

Enis,

Try to use CTRL+F...



Regards,

Alex

RainerKunert
Active Participant
0 Kudos

Hello,

reason for the dump is the lowercase character "e". It must be an uppercase "E".

But you can find the message in the dump.

Search for entries SY-MSGID and SY-MSGN0,

f.e.

  SY-MSGIDCL_DIAGSTP_MESSAGE

  SY-MSGN0021

You found the message class and the number (in my example CL_DIAGSTP_MESSAGE and 021).

Call transaction SE91 with this information. Enter message class and message number. Then the system will provide the error message.

This may guide you into the right direction ...

v_veeramalla
Active Participant
0 Kudos
Former Member
0 Kudos

Dear Venkat!

Thank you for your willingness to help! But these notes are very old. I've already checked them out. They are not applicable for SP11 unfortunately.
Some other help suggested here

former_member311325
Discoverer
0 Kudos

Hi  Alex ,

is there a solution for this issue ?. We have the same problem ?

Kind regards

Former Member
0 Kudos

Hi Marion,

As I've already mentioned above, the error is gone for me after carefully re-executioning of previous substeps inside the step 6 (initial content sync, automatic activities and so on).

Regards,

Alex

Former Member
0 Kudos

Somehow the runtime error is gone after re-execution of previous steps in system preparation.
¯\_(ツ)_/¯

Former Member
0 Kudos

Same problem for me. Any updates?

Find attached the dump from my system.


Another thread about this issue:

Former Member
0 Kudos

Can you upload full dump (preferably as attachment)?

former_member190691
Participant
0 Kudos

Hi Maurizio,

Please check if there is not a problema with the shared memory by by increasing th parameter "abap/buffersize"

Also run the command /$sync

Regards.

Fernando de la Cruz.

former_member117942
Participant
0 Kudos

Hi Luis,

tried to increase the abap/buffersize parameter and reset the buffer with /$sync

No help, same problem with step 6.6

Thanks anyway.

Regards.