Error sending newsletter to large subscribers list
Hello,
We have
installed a licensed edition of Newsletter Studio v.1.4.3on our customer's
Umbraco v.6.2.4 installation. We have a major problem with
the following: we cannot send newsletters to large subscribers lists (about
20000 subscribers), which is very important for our customer. We have tried to use
throttling, setting 100 to 1000 emails per 10-30 seconds (in other words, we
used trial and error method, either by increasing or lowering the limits of
throttling, or by unchecking throttling as well, with no luck). When we try to
send to smaller lists (up to 2000 subscribers), the newsletter was sent, which
means that our installation works fine. While trying to send, an
"A service error has occurred. The sending was aborted. Please try again"
error pops up. After that, the following appears on the newsletter
This e-mail has status error
This status
is used when something goes wrong during the send out to prevent the send out
engine from keep sending e-mails when there is a problem.
This status is only used when an error is thrown in during send out and is most
of the time related to custom render tasks, custom subscription providers,
invalid data in the database and so on.
To find out more about the error details, please check the Umbraco log and/or
the trace log.
The only
thing that is recorded in the log files is a
"Type: Error | User: 0 | NodeId: 0
| Comment: NewsletterStudio, SendNewsletterService: Invalid operation. The
connection is closedType: Error | User: 0 | NodeId: 0 | Comment:
NewsletterStudio, SendNewsletterService: Invalid operation. The connection
is closed."
error.
We checked
the ns_EmailTrackingItems table and each time we tried to send, a different
number of subscribers was recorded in the table, having SendDate and Error
columns null values, before the error popped up on the screen and the procedure
was cancelled.
We need your help on that, since no error is recorder in order to help
us fix this.
Sorry to hear about your issues - I'll help you to get this going correctly.
First of all I'm wondering about your hosting enviroment and set up? Are you on your own server or some shared host etc?
How long does it take for the error to appear? Does the accual send out start at all or is it during the start up of the send out that the error appear? What happens if you restart the send out?
I could also recommend that you upgrade to the lastest version of Newsletter Studio.
I'm experiencing the same problem, while sending a mailing to 21000 addresses:
I see around 5600 rows created in the ns_EmailTrackingItems table for this newsletter, and this amount differs in a new attempt.
Are you also using DiscountAsp.Net as the hosting provider (shared hosting)? At March 25, they moved the SQL-server from a physical to a virtual server. Shouldn't make any difference, they said ;)
Please let me know which hosting provider you are using.
I'm using Umbraco 7.1.8 and Newsletter Studio 2.1.0
The website is on our own server (no shared hosting), windows server 2008 r2 and sql server 2008r2.
The error message appears a few seconds after "initializing" message. It seems as if it starts sending, but a few seconds later the error occurs. When i tried to restart the sendout, the email was sent only to the subscribers who where recorded in ns_EmailTrackingItems table, but not every time. This is another thing i cannot explain: why it acts in a different way each time i try to send.
Upgrading to the latest version could be a could attempt to fix this, but we consider this a bit risky, since it is a production environment.
Yes,indeed, this happens without any changes. In fact i tried sending a simple newsletter with only one small sentence "this is a test" (no templates or nodes where used), to see if anything goes wrong with our template.
Subscribers list is imported by a csv file (just email). No other providers have been used.
I just checked once again the resources on the server and nothing seems to go wrong (i had checked the resources before i sent you my question). Nothing is logged in sql server logs and no error is recorded in the Event Viewer.
If we upgrade to a later version, do we need a new license or is it going to work with the old one?
No, it is the first time we try to send a newsletter to so many subscribers, since it is a new website and our customer wants to send his first real newsletter. So far, we only tested the functionality using much smaller lists (up to 20 subscribers).
I run a test earlier today and i got another error logged (still has to do with connection issues). The overall reaction of the system was as described above, no changes.
“INFO umbraco.BusinessLogic.Log - [Thread 10] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) |
Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: There is already an open DataReader associated with this Command which
I did a succesful mailing to 21000 adresses a few weeks ago. Nothing significant changed since that time, except that the Sql Server 2012 moved from a physical to a virtual server at our hosting provider Discountasp.net.
When reopening the newsletter in the Drafts folder, I'm getting a null reference exception (Object reference not set to an instance of an object):
@Tina, I don't want to hijack your topic, but our database problems seems to be related and I just want to provide more relevant information for Markus.
@Tina You will have to upgrade to the latest version of Newsletter Studio and also send me an e-mail so that I can provide you with some pre-release patcher.
@Marco Please send me an email so that we can work on this togheter and try patches.
Please send to markus [ag sign goes here] enkelmedia.se and I'll get back to you.
I'll post here when we find a solution to this problem.
The latest version is 2.1, but it is not compatible with Umbraco v.6.2.4 that we have installed. Would the previous version of Newsletter Studio (1.4.5) fix the problem?
I just upgraded our NS version to 1.4.5.1 (instead of 1.4.5) and everything seems to work fine! Does this version fix the problem indeed? Because version 1.4.5 did not work for us a month ago.
@Keilo It should work just fine! There was a bug that during some special situations closed the db-connection but this bug is fixed in the latest release.
I am running on v2.1 and dont see any means to access v.2.1.1 either from here or NS website. I too would be interested to know if/when it'll be available for download.
Do you happen to know what particular bug or issue addressed in that communicated version (2.1.1.0) ?
This fix is included in the current version on both our and newsletterstudio.org. Don't know why the version number was not changed but there will be a new release coming in a week or two.
Error sending newsletter to large subscribers list
Hello,
We have installed a licensed edition of Newsletter Studio v.1.4.3 on our customer's Umbraco v.6.2.4 installation. We have a major problem with the following: we cannot send newsletters to large subscribers lists (about 20000 subscribers), which is very important for our customer. We have tried to use throttling, setting 100 to 1000 emails per 10-30 seconds (in other words, we used trial and error method, either by increasing or lowering the limits of throttling, or by unchecking throttling as well, with no luck). When we try to send to smaller lists (up to 2000 subscribers), the newsletter was sent, which means that our installation works fine. While trying to send, an
"A service error has occurred. The sending was aborted. Please try again"
error pops up. After that, the following appears on the newsletter
This e-mail has status error
This status is used when something goes wrong during the send out to prevent the send out engine from keep sending e-mails when there is a problem.
This status is only used when an error is thrown in during send out and is most of the time related to custom render tasks, custom subscription providers, invalid data in the database and so on.
To find out more about the error details, please check the Umbraco log and/or the trace log.
The only thing that is recorded in the log files is a
"Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Invalid operation. The connection is closedType: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Invalid operation. The connection is closed."
error.
We checked the ns_EmailTrackingItems table and each time we tried to send, a different number of subscribers was recorded in the table, having SendDate and Error columns null values, before the error popped up on the screen and the procedure was cancelled.
We need your help on that, since no error is recorder in order to help us fix this.
Thank you in advance,
Tina
Hi Tina!
Sorry to hear about your issues - I'll help you to get this going correctly.
First of all I'm wondering about your hosting enviroment and set up? Are you on your own server or some shared host etc?
How long does it take for the error to appear? Does the accual send out start at all or is it during the start up of the send out that the error appear? What happens if you restart the send out?
I could also recommend that you upgrade to the lastest version of Newsletter Studio.
// m
Hi Tina,
I'm experiencing the same problem, while sending a mailing to 21000 addresses:
I see around 5600 rows created in the ns_EmailTrackingItems table for this newsletter, and this amount differs in a new attempt.
Are you also using DiscountAsp.Net as the hosting provider (shared hosting)? At March 25, they moved the SQL-server from a physical to a virtual server. Shouldn't make any difference, they said ;)
Please let me know which hosting provider you are using.
I'm using Umbraco 7.1.8 and Newsletter Studio 2.1.0
Hello Markus and Marco,
Thank you for your reply.
The website is on our own server (no shared hosting), windows server 2008 r2 and sql server 2008r2.
The error message appears a few seconds after "initializing" message. It seems as if it starts sending, but a few seconds later the error occurs. When i tried to restart the sendout, the email was sent only to the subscribers who where recorded in ns_EmailTrackingItems table, but not every time. This is another thing i cannot explain: why it acts in a different way each time i try to send.
Upgrading to the latest version could be a could attempt to fix this, but we consider this a bit risky, since it is a production environment.
Tina
Hi Tina!
So have this "just suddenly happened" without any changes from your side?
Are you using the built in subscription providers?
During the init-part of the send out service all the email tracking items are created, this is before the accual send out starts.
What if you watch your resources on the server? Any peeks during this part of the app? Does SQL Server get out of memory?
Hi Markus,
Yes,indeed, this happens without any changes. In fact i tried sending a simple newsletter with only one small sentence "this is a test" (no templates or nodes where used), to see if anything goes wrong with our template.
Subscribers list is imported by a csv file (just email). No other providers have been used.
I just checked once again the resources on the server and nothing seems to go wrong (i had checked the resources before i sent you my question). Nothing is logged in sql server logs and no error is recorded in the Event Viewer.
If we upgrade to a later version, do we need a new license or is it going to work with the old one?
Thank you
Hi!
Now you don't need a new license if you upgrade.
I'm having problems to reproduce this as the error states that the connection to the database is closed which I can't really figure out why.
Since Marco is running the new version and have the same issues it feels like it's something other than the upgrade that is the problem.
So have you ever been able to send to lager lists or have this issue always been there?
No, it is the first time we try to send a newsletter to so many subscribers, since it is a new website and our customer wants to send his first real newsletter. So far, we only tested the functionality using much smaller lists (up to 20 subscribers).
I run a test earlier today and i got another error logged (still has to do with connection issues). The overall reaction of the system was as described above, no changes.
“INFO umbraco.BusinessLogic.Log - [Thread 10] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) |
Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: There is already an open DataReader associated with this Command which
must be closed first. “
Tina
Hi!
This is a bug that we have not seen before but I will look closer at this asap and try to reproduce your issue.
As far as I understand you its just random how many email tracking items that gets created.
// m
That's right. Marco mentioned the same thing about the number of tracking items.
Thank you for your instant response.
I will wait for your answer.
Tina
I accidentally marked your answer as "Solved". Can you please correct it?
Thank you!
I did a succesful mailing to 21000 adresses a few weeks ago. Nothing significant changed since that time, except that the Sql Server 2012 moved from a physical to a virtual server at our hosting provider Discountasp.net.
When reopening the newsletter in the Drafts folder, I'm getting a null reference exception (Object reference not set to an instance of an object):
@Tina, I don't want to hijack your topic, but our database problems seems to be related and I just want to provide more relevant information for Markus.
@Tina
You will have to upgrade to the latest version of Newsletter Studio and also send me an e-mail so that I can provide you with some pre-release patcher.
@Marco Please send me an email so that we can work on this togheter and try patches.
Please send to markus [ag sign goes here] enkelmedia.se and I'll get back to you.
I'll post here when we find a solution to this problem.
Hi Markus,
The latest version is 2.1, but it is not compatible with Umbraco v.6.2.4 that we have installed. Would the previous version of Newsletter Studio (1.4.5) fix the problem?
Hi!
No, you will have to use 1.4.5 but I can't promies that this will solve the issues but to apply our fixes you will have to be on the latest version.
Hello Markus,
I just upgraded our NS version to 1.4.5.1 (instead of 1.4.5) and everything seems to work fine! Does this version fix the problem indeed? Because version 1.4.5 did not work for us a month ago.
Thank you,
Tina
Hi Tina!
Yes that version is targetet to this issue and should make things a lot better.
If you still have issues - let us know.
/ m
@Marco
Did you manage to sort out the issue with sending to large (21000) recipients in Umbraco 7.1.8 with Newsletter Studio 2.1.0 ?
Curious if there are still any outstanding issues to watch out for..
@Keilo It should work just fine! There was a bug that during some special situations closed the db-connection but this bug is fixed in the latest release.
Sorry for the late reply, because of a holiday.
It succesfully worked with a new version (v 2.1.1.0), which I received from Markus.
@Markus, the current published version on http://www.newsletterstudio.org/download/ is still v2.1.0. When will the new version be published?
Thanks for following up Marco.
I am running on v2.1 and dont see any means to access v.2.1.1 either from here or NS website. I too would be interested to know if/when it'll be available for download.
Do you happen to know what particular bug or issue addressed in that communicated version (2.1.1.0) ?
cheers
Hi!
This fix is included in the current version on both our and newsletterstudio.org. Don't know why the version number was not changed but there will be a new release coming in a week or two.
Cheers
Hi Markus,
Do you have any updates when a new version will be released officially, containing this fix and maybe others?
Hi!
It's beeing tested right now - in about a week or two - but you can use the currently released version - the upgrade will be very seamless.
is working on a reply...