Home » Support » Telligent Evolution Platform » Telligent Community » Discussions » Mass email not working. Email not working period.

Mass email not working. Email not working period.

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 3 Replies
  • 0 Subscribers
  • Posted11 months ago
Options

Mass email not working. Email not working period.

This question is answered
jvictor
Posted by
on Wed, Jun 20 2012 5:59 PM

We are running Telligent 6.0 and mass email is not working. We have checked both the mg_emailqueue and mg_bulkemailqueue. Both tables are empty. There is nothing in the event log or exception report. How do we debug this issue. Also, when we try to send an email via code using Queue method on the IEmailQueuingService we get a return value of true but no email is sent. Any help would really be appreciated as we've been stuck on this for over a day now.

Thanks,

Jean
Verified Answer
  • Adam Seabridge
    Posted by
    on Wed, Jun 20 2012 10:47 PM
    Verified Answer
    Verified by

    Hi, those tables are no longer used in 6.0.

    Emails are generated & queued up as dynamic jobs in the Job Scheduler.

    To look at the dynamic job queue, you can check the following tables to look for emails:

    QRTZ_DYNAMIC_TRIGGERS

    QRTZ_DYNAMIC_JOB_DETAILS

    QRTZ_DYNAMIC_FIRED_TRIGGERS

    Hope this helps.

    Adam
All Replies
  • Adam Seabridge
    Posted by
    on Wed, Jun 20 2012 10:47 PM
    Verified Answer
    Verified by

    Hi, those tables are no longer used in 6.0.

    Emails are generated & queued up as dynamic jobs in the Job Scheduler.

    To look at the dynamic job queue, you can check the following tables to look for emails:

    QRTZ_DYNAMIC_TRIGGERS

    QRTZ_DYNAMIC_JOB_DETAILS

    QRTZ_DYNAMIC_FIRED_TRIGGERS

    Hope this helps.

    Adam
  • jvictor
    Posted by
    on Thu, Jun 21 2012 3:53 PM

    Hey,

       Yep that steered me in the right direction. Thank you much. It turns out the Job scheduler was running but the connection string config had the wrong connection string. I wonder why it did not throw any errors in the reports.

    Thanks,

    Jean
  • Alex Crome
    Posted by
    on Thu, Jun 21 2012 8:23 PM

    If the connection string was wrong, the Job Scheduler wouldn't have been able to connect to the database to record the errors.