"Event not covered" for transactional message | Community
Skip to main content
H
hkurz
New Participant
July 26, 2016
Solved

"Event not covered" for transactional message

  • July 26, 2016
  • 14 replies
  • 13823 views

I am trying to test transactional messaging (sending an email by SOAP request) to no avail.

What i did:

- created a template, type (called "t3") according to the steps in the documentation file "message-center-v6.1-en.pdf".

- Created the event "t3"

- published the template

- sending a proof worked perfectly

Then i created send SOAP message to the server with "Boomerang SOAP & REST client". This worked after using the content of a cookie "__sessiontoken" as "sessionToken".

Request looks like this.

l got back a response with HTTP code 200 (success) with this content:

In the event history of the message center i see the event (see screenshot), but it is marked as "Event not covered" and no email is sent.

I do not see any entry in any logfile i searched on the server for this event.

Apparently the server cannot associate the request (type="t3") with the template for some reason. Event type of the template is "t3", as you see in this screenshot:

Server works OK for workflows, but just not for transactional messages via SOAP (proof sending works also). We are using a linux machine for the server.

Additional info

in the Audit log of the Workflow "Processing real time events" i see "[Routing] 1 message(s) with errors" (see screenshot).

But i cannot find out what the actual error was. How is this done?

Does anybody know what's (not) going on here? Is there any place on the server where i can see what is going on?

any help appreciated

Hermann

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by hkurz

Hi Linda,

Both "Transactional Message Control" and "Transactional Message Execution" Packages are installed on one instance. Template was successfully published. So i assume that both Control and Execution instances are set up correctly, see also the screenshots above.

I will do a fresh server install of Campaign 6.1 soon (on Redhat 7 w PostgreSQL). Which Packages are the absolute minimum to get transactional messages working? Do they have to be installed on the same instance or is it necessary to set up separate instances with each contains one of these packages?

Hermann

14 replies

V
Vishnu_Prakash
Employee
June 28, 2024

If you are using a user other than the mc user provisioned for the RT instance, this issue could happen due to lack of folder access as well. The new user should match mc user Folder access levels.

A
AnanthanJa
Employee
March 2, 2018

I too faced similar issue but later figured out that when we don't login as the message center agent and issue the soap request, then i got this "Event Not covered error". Once i changed the login to the message center agent and changed the appropriate session and security token and then issued the soap call, the transactional message did went through.

    Jonathon_wodnicki
    Jonathon_wodnicki
    New Participant
    November 7, 2017

    Happened in a fresh 8853 install. A better fix might be to change the mc operator's home folder (under access rights), as that's where that path comes from.

    Linda_Stinson
    Linda_Stinson
    Employee
    November 7, 2017

    Hi Jonathon,

    That is interesting. Do you think it is a bug in that build or misconfiguration in the training environment?

    Linda

    Jonathon_wodnicki
    Jonathon_wodnicki
    New Participant
    November 7, 2017

    For future searchers, I fixed same error by moving the published templates folder so it's under /Administration/Production/Message Center/Default

    The messageCenter.js code is looking at these fields:

    [triggerMessage/@eventType]

    [@messageType]

    [folder/@fullName]

    [triggerMessage/@publicationStatus]

    [@isModel]

    [mapping/@name]

    Where [folder/@fullName] was testing "LIKE ('/Administration/Production/Message Center/Default/'+ '%')" instead of the ootb path.

    jirilmongeorge
    jirilmongeorge
    Employee
    July 25, 2017

    Hi Malarrajan,

    Thanks for the reply. Yes i already made sure the eventType internal name is used correctly in the soap call.  But still the error is coming from my v6.

    malarrajans8868
    malarrajans8868
    New Participant
    July 21, 2017

    Hi,

    Kindly check the event type when you passed in the SOAP Call. The event type should match the event type internal name(administration->Platform->Enumerations->eventType->t3). This would help for Event not covered problem.

    Thanks,

    Malarrajan Sundarraj.

    jirilmongeorge
    jirilmongeorge
    Employee
    July 20, 2017

    Hi Hermann,

    Please share the root cause/solution for this problem. I am also facing the same issue in my local instance.

    Thanks

    George

    aga_otta
    aga_otta
    New Participant
    March 23, 2017

    Hi,

    did you find root problem, why this is happening? It seems that I have the same problem.
    So, could you help me with solving this issue?

    BR,
    Aga

    jrstheandonly
    jrstheandonly
    New Participant
    February 13, 2017

    Hi,

    I do have same issue. Can you please elaborate how this issue got fixed?

    Thanks,

    Jrs

    Show more replies
    Terms & ConditionsAccessibility statement

    Loading footer...