Tim
Posts:2
new to the springs
 |
| 03/17/2008 6:30 PM |
|
Every time we send a newsletter, a large number of duplicate emails are sent.
The number of duplicate emails seems some what random but about 80% of intended recipients get 2 copies. As far as we know, no-one is sent more than 2 copies.
This is un-expected we would expect only 1 email message sent to each intended recipient. There are about 500 recipients on our list.
The scheduler is enabled with a "time lapse" of 10 mins and a "Retry Frequency" of 20 mins.
We have OptInEmail31 EnterpriseEdition running in 2 portals.
Any suggestions much appreciated? |
|
|
|
|
Chad
Posts:2256
river guide
|
| 03/17/2008 7:46 PM |
|
Hi. Check the scheduler settings, I would change that from 10 minutes to maybe 1 hour. 10 could possibly overlap distributions depending on the server, the logging settings, the SMTP server, etc... The only way to make sure this doesn't happen is to increase the time span between scheduled distributions. I would set this to maybe 500 ever 30 minutes or even 1000 an hour or something. The system does check who was already distributed a message, but if its not finished with the scheduler instance of the last time it will not know.
-Chad |
|
|
|
|
Tim
Posts:2
new to the springs
|
| 03/17/2008 7:48 PM |
|
Have found the problem. Opt-In Email 3 does not properly support multi portal installations.
An Opt-in email scheduler configured in one DNN portal, can send emails from a newsletter scheduled in a totally separate DNN portal.
AND if the schedules of more than 1 portal execute at the same time, duplicate messages are sent, which makes a mess.
Hope this helps. |
|
|
|
|
Will
Posts:6
skipping stones
|
| 09/11/2008 8:37 AM |
|
I'm getting this too and it's really causing a problem with my client.
I've removed the only other schedule from another portal and have run a query to see if duplicates are being sent. They are. I've actually looked in the mailroot/Queue and can see the duplicates lined up and going out.
I have no idea what to do - please help!
Will
ps. the query was from another poster in these forums and was
SELECT PreviousDistributionID, PreviousNewsletterID, OptInEmailID, EmailAddress, Status, SentDateTime, PortalID, Inactive
FROM DataSprings_OptInEmailPreviousDistribution
WHERE (PortalID = 6) ORDER BY PreviousNewsletterID, EmailAddress, SentDateTime
a sample of the report is:
42ef3df6-adf8-4e47-b0de-82b97b831e1e a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 58bd29a3-a740-4b02-aa6c-c4673f07ead8 akelly@xxx.co.uk Sent 11/09/2008 15:40:35 6 0
630d9731-240b-41bf-b1d2-a17e5cb0c3e3 a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 58bd29a3-a740-4b02-aa6c-c4673f07ead8 akelly@xxx.co.uk Sent 11/09/2008 15:40:35 6 0
ee0cf58f-ba13-4bb2-bbd5-e339a17be6a1 a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 3ed2cd04-1eca-45ac-8380-25e5ed5fa656 alan.brown@xxx.com Sent 11/09/2008 15:10:01 6 0
ce897ca1-2e2a-4f3e-b681-fe815ebc3ea1 a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 3ed2cd04-1eca-45ac-8380-25e5ed5fa656 alan.brown@xxx.com Sent 11/09/2008 15:10:01 6 0
835a02ab-13a2-4bb8-bee6-d5d764a2013b a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 3ed2cd04-1eca-45ac-8380-25e5ed5fa656 alan.brown@xxx.com Sent 11/09/2008 15:10:11 6 0
48bdfd69-bd09-44cd-8844-729d0de0236e a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 3ed2cd04-1eca-45ac-8380-25e5ed5fa656 alan.brown@xxx.com Sent 11/09/2008 15:10:12 6 0
44d7a314-3b19-4a9d-849b-744372e2d339 a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 3929b0f2-45f8-4e6c-8719-ffd86df9645b alastair.henderson@xxx.org Sent 11/09/2008 15:50:23 6 0
45f6b82d-da7c-44eb-b58f-38b9e16a0e86 a7ef29c1-4b65-46fd-9cf3-4f9bdf16132b 3929b0f2-45f8-4e6c-8719-ffd86df9645b alastair.henderson@xxx.org Sent 11/09/2008 15:50:24 6 0 |
|
|
|
|
Will
Posts:6
skipping stones
|
| 09/12/2008 9:03 AM |
|
I should add the schedule is set to send 100 emails every hour...
Will |
|
|
|
|
Will
Posts:6
skipping stones
|
| 09/14/2008 11:09 PM |
|
Hi Chad,
Do you have any suggestions that may help? I've tried this using a small test email list with no duplication.
I'm hesitant to use my one of my full lists in test mode as I've seen other forum posts saying these have actually gone out to the list and not a test mail.
I'd really like to stay with your product but unless this can be fixed, I'm afraid that we'll have to find another solution...
Thanks,
Will |
|
|
|
|
Will
Posts:6
skipping stones
|
| 09/14/2008 11:21 PM |
|
Hi, to add to my confusion I've just sent an email in test mode to my test list of 5 addresses and received 10 emails to my test address.
It looks like I have more duplicates... |
|
|
|
|
Will
Posts:6
skipping stones
|
| 09/15/2008 8:23 AM |
|
I really have to make a call on this - please let me know what you can suggest...
Thanks,
Will |
|
|
|
|
Chad
Posts:2256
river guide
|
| 09/15/2008 5:12 PM |
|
Will,
Hi. The best suggestion I have (we are changing this in the 4.0 release to ALWAYS check even though it will add a little overhead) is to make sure that your Opt In Scheduler is not overlapping. We recently had to adjust this for a client for the scheduler (under host settings) to be set to 'Timer' mode and not 'User Request' mode.
A quick run down...
1. The Opt In Email Scheduler pulls from a SQL query for each scheduler run, this query reviews all emails that have been sent and doesn't include those in the mailing.
2. If a scheduler runs, but lets say one starts 5 minutes after the first one is already running... You run the risk of the query pulling in 'X' number to send and sending duplicates.
So... I would check the scheduler history (I think how this happened was a change in DNN version) because you should never see another instance of the scheduler running while the current instance has not yet finished. This is the only time when a duplicate can occur.
-Chad
|
|
|
|
|
Will
Posts:6
skipping stones
|
| 09/22/2008 6:07 AM |
|
I've just sent out an email to a group of 550 recipients. My settings are as you've suggested here and in other posts:
TimerMode is set from under host settings
Timelapse: 1hour
Emails to send out: 200
Retry: Blank
Run on event: None
Again, I'm going to have to explain to my client why their clients have received not just duplicates but in some cases triplicates.
I've tried everything I can think of in getting your product to work as advertised and frankly it's taking me too much time and proving to higher risk. Despite being a developer who's used DNN for a few years now, it seems that I don't have the necessary level of skill to troubleshoot your product's integration with the framework.
|
|
|
|
|
Chad
Posts:2256
river guide
|
| 09/23/2008 5:08 PM |
|
Will,
Sorry for your frustrations... What we have been finding is that our module schedule (and from our research the schedule in general) has changed between DNN versions. I am not sure which change but my guess is somewhere before DNN 4.5 and 4.7 etc... Anyway, because of this I think its kicking off the schedule sometimes on the users thread and all of a sudden you have three instances of the scheduler running. For example, if you have the schedule to run hourly upon the hour its supposed to kick off it will (all of a sudden) kick off several instances of it.
Each time the opt in email application scheduler runs it runs a stored procedure to NOT pull in any opt in subscribers that have already sent the newsletter. Well this works great, except when multiple instances of the scheduler all of a sudden start up. Then the query it returns for all instances of the schedule has the same subscribers in it and therefore is sending duplicates.
So... From our research what we can tell is that changing the scheduler mode to 'Timer' instead of 'User Requests' under Host Settings is setting up the scheduler to execute properly etc....
A few other things... Version 4.0 has many new improvements (and is the next major release we are working very hard on). One minor change was also added that checks to see if the subscriber was already sent a message immediately before it sends the newsletter. While this can add a small overhead to the number of newsletters distributed, it saves the worry or headache of duplicates. So, for example if 3 instances of the schedule are all of a sudden kicked off it will pull in maybe the same 200 within the stored procedure but then within those three instances it will determine if the user was already sent it and skip that user. This is added to the new feature called email campaigns as well.
So just to confirm, if your schedule is firing off more than once and its not supposed to (for example if you set it for an hour) and the schedule is kicking off multiple instances or more than it should and overlapping, I would change the scheduler to be on Timer mode.
I will attach a few screenshots of the upcoming 4.0 release as well. The 4.0 release includes MANY new features including bounceback protection, email campaigns (send a series of emails), link tracking, better newsletter tracking with more options, and many other features.
-Chad
|
|
|
|
|
Chad
Posts:2256
river guide
|
| 09/23/2008 5:19 PM |
|
I just wanted to throw in some upcoming 4.0 screenshots as its getting closer to release... Should have a full release out by Nov
 
|
|
|
|
|
Jukka
Posts:26
going with the flow
|
| 09/30/2008 1:06 AM |
|
Hi,
can you Chad confirm me that the Opt In Email module (03.10.00) works with a two parent portals on the same DNN instance (4.8.4).
How many Scheduler instance should these two module instances on separate parent sites create?Now it is creating two and sending duplicates! Are these schedule instances in the scheduler module instance specific? One for each module instance of Opt In Email?
Regards
Jukka
|
|
|
|
|
Chad
Posts:2256
river guide
|
| 09/30/2008 8:01 AM |
|
Jukka,
Hi. Did this just start happening and was it never doing this before? If this is happening DO NOT send out any newsletters until we get a patch out. We should have one for the 3.1 release by the end of the week. The patch will double check for every single email that it has not already went out for that newsletter, so that in the case of scheduler instances overlapping it will not be a problem. The real problem though is that multiple schedule instances of the same schedule should not kick in. If it is scheduled for 1 hour it should only execute every 1 hour, but instead what is happening on some clients servers is that its kicking in 2 or 3 times during that hour or 2 or 3 times during the first minute of that hour etc... We are working to verify what version of DNN this started in and also any other information. Can you tell me if this was running successfully before or if this is a new implementation, and also what version of DNN you are on, and if this version was an upgrade or a fresh installation.
-Chad
|
|
|
|
|
Jukka
Posts:26
going with the flow
|
| 09/30/2008 10:41 PM |
|
I didn't have two parent portals on the same DNN instance before, so I can't tell you whether this could have happened before. I just installed last week a new parent portal and added a new Opt In Email module there, configured it, and my first client reported that all their newsletter emails were duplicated. I looked at the scheduler and saw that there were two scheduler items (Dataspring.DNN.Modules.OptInAdvanceEmail.SendNewsletters, Dataspring.DNN.Modules.OptInAdvanceEmail) enabled. I assumed that this had caused the duplication. Then I deleted the other one, but realized that an item was always recreated every time I saved the Opt In Email settings for the second (new) parent portal.
Again ... Is there supposed to be as many Scheduler items enabled as there are Opt In Email modules installed on the DNN instance?
-Jukka
|
|
|
|
|
Chad
Posts:2256
river guide
|
| 10/06/2008 11:37 AM |
|
No, there should only be one scheduler instance per DNN installation. From our research on this issue though (and its been heavy since Will's thread) it was the same scheduler item but firing off multiple times. If you go to Host, Scheduler do you actually see two specific scheduled items with the same name? Or is it when you click on History you see that it fired 2x from the same scheduler item?
-Chad
|
|
|
|
|
Jukka
Posts:26
going with the flow
|
| 10/08/2008 8:20 AM |
|
Yes, I see to scheduler instances with the same name in Host -> Scheduler. Any ideas why it creates an additional scheduler instance with the same name when I save the settings in the Opt In Email module?
Do have the new version finished that should tackle the problems we are experiencing?
-jukka |
|
|
|
|
Jukka
Posts:26
going with the flow
|
| 10/21/2008 4:14 AM |
|
Anything new that you could tell us? Couple of weeks has passed and we haven't heard anything on the patch we thought you were supposed to be working on.
-Jukka
|
|
|
|
|
Chad
Posts:2256
river guide
|
| 10/21/2008 2:10 PM |
|
Jukka,
Hi. We have this fixed and are planning to release the patch for the 3.1 version when we release the 4.0 build of Opt In Email (scheduled for only about a week from now, Nov 1st). The module just checks each and every single time to verify it has not already sent an email, however we are still researching to find out why its creating multiple instances of DNN (the scheduler will not send to them, but it shouldn't be running at all on multiple instances to begin with). This was never an issue until some recent versions of DNN, I think the scheduler stored procedure to get the latest scheduler items has changed recently maybe in the 4.6 to 4.8 from what I can tell. Either way, its not affecting many of our customers which is what makes it difficult to debug. You are also welcome to test and demo the latest 4.0 release under www.betasprings.com (login as host with a password of dnnhost).
-Chad
|
|
|
|
|