EEM - E2E trace error "Backend request for populating Messages failed"

[Former Member]

Gurus,

We are on Solman 7.1 SP13 with LM-SERVICE 7.10 SP13 Patch 4.

I am running a EEM script (HTTP, ICWEB) hitting my CRM7.0EHP3 system, which then calls back-end ECC6.0EHP7 system.

My script is part of a technical scenario that the 2 managed systems are also a member.

These systems look good in SLD/LMDB/Managed sys conf.

The script runs OK!  But I would like to "jump" into the E2E trace from the EEM UI:

Then jump into EEM E2E

Also, EEM UI settings

E2E shots:

See the error there?

Extractors look good.  So does SLG1.

Unless I'm missing something:

I have checked all these NOTES and applied what I could:

2072828  Corrections for EEM 7.1 SP12 + SP13

1357045 - End-User Experience Monitoring Central Note

2235189 - LM-SERVICE 7.10 SP13 Patch 4

2120689 - End User Experience UI - SolMan sp10 to sp13 - Latest release

I also just put a message in, but who knows?  Any direction someone could give me would be greatly appreciated.

EEM is great, but the real gold is in being able to jump into E2E trace to REALLY look at what is going on when you have integrated systems like we do!

NICK

[christianmarco_niedermaye · Accepted solution]

Hi Nick,

Please start the browser's developers tools (F12) and check the JavaScript console for errors. There should be an exception stack trace when this error message has appeared. Maybe this is caused by a bug and we have to provide a fix for it.

Best regards,

Christian

[Former Member · Accepted solution]

Hey Christian,

Thanks for replying.  I still can't explain that particular error, but I did find a way to get what I want.

From my "E2E shot" above, once I click on the "pie" I do get another window show up below it.

And that window gives me all the trace stuff I was looking for.

But as far as that error I mentioned originally, I'm still not sure.

I did open a message and support said something about in MSC (managed sys config) for these systems to run the step marked

Activate E2E Trace Upload Service

Which I have not done.

But the documentation for the step says:

Use

SAPUI5 allows recording of E2E Trace without SAP ClientPlugin. The
BusinessTransaction.xml is send to the SAP Netweaver Gateway system where it is
persisted and forwarded to the SAP Solution Manager.

Requirements

This functionality requires at least ST-PI 2008_1 SP09 in the SAP Netweaver
Gateway system.

Activities

In this step you tell the SAP Netweaver Gateway system the URL of the SAP
Solution Manager where the data should be send to.

SO since we didn't have a gateway, I did not think there was a point to it.

What you think?

NICK

[Former Member · Accepted solution]

Turns out this is a real bug with Solman 710 SP13.  So the fix is to go to SP14.

Otherwise, you can't perform the scenario I detail above since you will get the error I documented.  The only other work-around is to click like below.  (Related links - E2E Trace Analysis (full scope)

NICK