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 recipients being duplicated in alerts (1444 times!!!!)

web-app

Hi,

Just upgraded from the betas to 2.1.1. and after a hiccup with the installer wiping our database (oops!!) and having to recover data from log files (a very painful experience), I now have 2.1.1 running successfully.

However when ever the system sends out an email alert the recipients email address appears multiple times in the To: box. For some people their address oonly appears a couple of times, but for others their email address is appearing up to 1444 times!

Any suggestions?

jvoelcker
· 1
jvoelcker
Replies (8)
helpful
0
not helpful

Can you please check the users and issuewatchers tables for duplicates?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Hi Mark,

No duplicates in the Users table, but there is no issuewatchers table??!?

I have actually been through all existing tables looking for duplicates, but didn't find any.

Cheers,

Julian


jvoelcker
· 1
jvoelcker
helpful
0
not helpful

Sorry, reverse the name: watchissue table.

To get the email addresses we use the gemini_getusersforissuealert stored procedure, it might worth running it passing in a project and issue ids.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

OK, run some tests......

No duplicates in watchissue table, however I am getting multiples coming out of the stored procedure.

If I run it against the database for one issuse and I get 1444 results for myself (watchcode 959).  On another issue I get 64 results for one person and then one result for another (both watch code 1024).

We only have 308 items in the WatchIssue table and 10 users.

Stepping through the stored procedure geminigetusersforissuealert, it is all apparently working fine until we get to the final part of the querying:

    select a.userid,a.watchcode,a.emailaddress,isnull(b.svalue,N'H') as emailformat,isnull(c.svalue,N'Y') as emailmyself
        from #temp3 a
        left outer join (select userid,svalue from usersettings where sname=N'email
format') b on b.userid=a.userid
        left outer join (select userid,svalue from usersettings where sname=N'email_myself') c on c.userid=a.userid

Changing it to select DISTINCT seems to resolve the problem.

Does that make any sense?

Cheers,

Julian


jvoelcker
· 1
jvoelcker
helpful
0
not helpful

Have you got duplicates in the usersettings table?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Possibly, I can't tell what is in the tstamp column.  Looking at the other columns there are a number of entries that match.


jvoelcker
· 1
jvoelcker
helpful
0
not helpful

You can ignore the timestamp column. Due have duplicates?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Yes, a few.

In the end I have deleted them all out and got the users to reset their preferences, this seems to have resolved the problem.

Thanks.


jvoelcker
· 1
jvoelcker