Event not covered error for transactionnal message

thibaultb473199

10-04-2018

Hello everyone,

I got an issue that involve my transactionnal message when trying to link a template I create with an event using SoapUI.

I already see another post on the forum but with no real answers on my issue.

So I first make a simple template and create an event name to specify the event type of the template and I publish the template with success.

I also send a proof with no problem.

I then make a SoapRequest such as this :

SoapUI-5.4.0_2018-04-10_09-48-22.png

I got a success answer :

SoapUI-5.4.0_2018-04-10_09-49-20.png

But still, when I check in the Adobe Campaign's event history, my events are not covered and the documentation doesn't help get through the problem.

nlclient_2018-04-10_09-52-38.png

I already check in the properties of the template to make sure the event name is correct and it's the case.

I also see that lots of people are facing this issue, do you have some answers for my problem ?

If you need more information, feel free to ask me !

Using Adobe Campaign v7 on Windows 10.

Regards,

Thibault

Replies

Highlighted

Jean-Serge_Biro

MVP

16-04-2018

Ajoute xmlEnvoyer, le paramètre que tu as ajouté en argument, au logInfo. Peut-être est-il vide.

Please check the value of xmlEnvoyer as parameter to logInfo, perhaps it is empty value.

Highlighted

thibaultb473199

16-04-2018

Quand je rentre le xmlEnvoyer, il me renvoie un \n, qu'est ce que ca signifie ?

When i put the xmlEnvoyer, he gives me back a \n, what does that mean ?

nlclient_2018-04-16_13-23-39.png

Highlighted

parveshp7822672

03-08-2018

Hello,

Make sure you are sending the soap request with the same operator, using which you have connected your execution server with the control server. i.e mc.

So Firstly take a session token from mc user -

1541255_pastedImage_0.png

Then use this token within your request.

1541256_pastedImage_1.png

I was using the different operator then I got the same issue. But after that I tried with mc then issue is resolved.

Thanks.

Parvesh.