CounterSoft User Forums

Welcome to CounterSoft User Forums Sign in | Join | Help
Home Forums

Emails not being sent

Last post 03-01-2010, 4:16 PM by Matt. 5 replies.
Sort Posts:
  •  02-24-2010, 1:11 PM

    Emails not being sent

    Hi,

    We're having trouble setting up Email Alerts.

    We've completed the SMTP Configuration screen and the test message has been sent successfully. Global Notifications are all enabled. Project email alerts are also all switched on.

    The scheduler service is up and running and logging events saying '0 issue alerts found'.

    We've also noticied that no records are being added to the gemini_issuealerts table.

    We're on Gemini v 3.6.1 build 2671

    Thanks
    Matt
  •  02-24-2010, 1:45 PM

    Re: Emails not being sent

    Can you please make sure that in the Administration -> Notifications page you have set it to the scheduler service?
    Also, try and add yourself as an issue watcher and update the issue (make sure that you allow to email your changes), does it work?

  •  02-24-2010, 1:57 PM

    Re: Emails not being sent

    Yes, we have the Email Alert Engine set to SchedulerService.

    I added myself to the Issue Watchers list for an issue - I got an email telling me I had been added to the issue watch list. But when I change the issue or add a comment to the issue I don't get anything.
  •  02-24-2010, 2:02 PM

    Re: Emails not being sent

    Is this a new installation or an upgrade?
    Did you change between the mail plug in and the scheduler service? If so, please try and restart the web app (save the web.config file).

    If you still don't get emails and no records are added to the gemini_issuealerts table, please send an email to support at countersoft dot com and we will remote in.

  •  03-01-2010, 4:09 PM

    Re: Emails not being sent

    Hello there.

    As we seem to have similar problems:

    Matt: Has this issue been solved? (How?)

     

     

    tnx

    Heiko

  •  03-01-2010, 4:16 PM

    Re: Emails not being sent

    Hi,

    Yes this was fixed by the support team. Here's an excert from the resolution email:

    "We believe we have found the issue. It is to do with impersonation.

    Basically, you should run the application pool under the user identity rather than specifying the user in the web.config file.

    I suggest removing the impersonate = true and setting the identity for the application pool."

    Thanks
    Matt
View as RSS news feed in XML