Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Email alerts - scheduler service

web-app

We have installed and configure Gemini 2.2.6 and are now trying to get email alerts to work for us.  The webservice is running and reading the 'issuealerts' table (this tested by updating table and so producing an error from the ws).  We are not able to see any records being written to the table though.

SMTP configuration is complete and the test button produces a test email.

Global settings Notifications screen is set all to 'Yes' and alert engine set to SchedulerService

The Project email alerts are all ticked.

My profile shows Yes to receive alerts and Yes to Email me my changes

My watched issues show that I am watching the issues.

Not sure where to look next, anyone help?

 

 

SeanJ
· 1
SeanJ
Replies (6)
helpful
0
not helpful

Did you install the scheduler service? Are there any errors in the Gemini log or event viewer on the machine were the scheduler is installed?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Yes, the scheduler is running, as mentioned we were able to generate an error message by populating the 'issuealerts' table.  There are not any records being written to this table tough.


SeanJ
· 1
SeanJ
helpful
0
not helpful

Did you try to reboot the web app?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Yes we have restarted the application, still no error messages in syslog or in gemini log.  And still not rows written to issuealerts table.


SeanJ
· 1
SeanJ
helpful
0
not helpful

Hello,

Can you please check SQL permissions on the issuealerts table?  If you have to, recreate it.


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Thanks, that gave us a cue.  The issue was to do with the permissions that the ap on the webserver needed to write to the SQL server, at a higher level.  Issue fixed


SeanJ
· 1
SeanJ