We have purchased the package a number of times so far. For our latest umbraco installation, we are constantly facing the following problems:
We are using the default subscription provider that comes with the package.
When trying to send to a single list that has roughly 40000 subscribers, we get an error during the queue creation operation (before the actual sendout). The log mentions one of the following:
2014-10-24 12:39:22,272 [7] INFO umbraco.BusinessLogic.Log - [Thread 25] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Invalid operation. The connection is closed. :
2014-10-24 13:37:21,746 [7] INFO umbraco.BusinessLogic.Log - [Thread 40] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Object reference not set to an instance of an object. :
And most commonly this:
2014-10-24 13:46:52,068 [7] INFO umbraco.BusinessLogic.Log - [Thread 43] 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. :
The newsletter is then set to status 3 (error), while the queue has a portion of the subscribers to send to (say 15000 of 40000, but we've had as little as 800 of 40000). The UI tells us to "try again".
When we "try again", NewsletterStudio starts sending out the emails to whoever has been pushed to the queue, leaving out all the others (so the newsletter is sent "successfully" to the 15000 of 40000 subscribers that made it to the queue before the error, and all the others are ignored).
There are two issues here. First, is the issue that the queueing process fails. Secondly, there is no recovery for a failed queueing process - i.e. the "errored" newsletter should either clear the queue and start over or resume the queueing process.
I would like to know more about your set up - what database are you using? What version of the package and of Umbraco are you using? How much memory does your web server have?
Multiple issues while pushing subscribers to queue
Hello.
We have purchased the package a number of times so far. For our latest umbraco installation, we are constantly facing the following problems:
We are using the default subscription provider that comes with the package.
When trying to send to a single list that has roughly 40000 subscribers, we get an error during the queue creation operation (before the actual sendout). The log mentions one of the following:
2014-10-24 12:39:22,272 [7] INFO umbraco.BusinessLogic.Log - [Thread 25] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Invalid operation. The connection is closed. :
2014-10-24 13:37:21,746 [7] INFO umbraco.BusinessLogic.Log - [Thread 40] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Object reference not set to an instance of an object. :
And most commonly this:
2014-10-24 13:46:52,068 [7] INFO umbraco.BusinessLogic.Log - [Thread 43] 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. :
The newsletter is then set to status 3 (error), while the queue has a portion of the subscribers to send to (say 15000 of 40000, but we've had as little as 800 of 40000). The UI tells us to "try again".
When we "try again", NewsletterStudio starts sending out the emails to whoever has been pushed to the queue, leaving out all the others (so the newsletter is sent "successfully" to the 15000 of 40000 subscribers that made it to the queue before the error, and all the others are ignored).
There are two issues here. First, is the issue that the queueing process fails. Secondly, there is no recovery for a failed queueing process - i.e. the "errored" newsletter should either clear the queue and start over or resume the queueing process.
Regards,
Yiannis
Hi!
Frist of all! Sorry for taking so long to anwser.
I would like to know more about your set up - what database are you using? What version of the package and of Umbraco are you using? How much memory does your web server have?
/ m
is working on a reply...