SendNewsletterService: Length cannot be less than zero.
Hi,
We've just upgraded from v.1.3.2 to 1.3.4 and it seems there are some underlying changes which has broken our implementation. I don't have much to go by. It seems to happen prior to the custom subscription provider being called.
It looks like it is trying to instantiate the right job (Epic1 is the name of the email), but something goes wrong.The log indicates the following:
2013-05-29 10:13:44,573 [33] INFO umbraco.BusinessLogic.Log - [Thread 15] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: ScheduledTask | User: 0 | NodeId: 0 | Comment: NewsletterStudio: ScheduledTask. Started thread to send newsletter "Epic1" (id 1923)
2013-05-29 10:13:47,852 [33] INFO umbraco.BusinessLogic.Log - [Thread 26] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Length cannot be less than zero.
Parameter name: length :
2013-05-29 10:13:48,612 [33] INFO Umbraco.Core.PluginManager - [Thread 13] Completed resolution of types of umbraco.MacroEngines.IRazorDataTypeModel, found 15 (took 9ms)
2013-05-29 10:14:05,008 [33] INFO umbraco.presentation.publishingService - [Thread 36] newsletterstudioBounces has been called with response: True
I'm currently out of office until monday but will try to help you as much as I can. It looks like it might me some corrupt data. Can you try to send to a new mailing list with just valid e-mails?
Are you using a custom subscription provider? Are you sure that this provider works and only returns valid emails?
Looks like this was us who had not configured everything correctly for the newsletters subscription provider in the config, the assembly name was set to newsletterstudio, so it presumably couldn't instantiate the provider.
A more meaningful error message in the log would have been nice though :-)
SendNewsletterService: Length cannot be less than zero.
Hi,
We've just upgraded from v.1.3.2 to 1.3.4 and it seems there are some underlying changes which has broken our implementation. I don't have much to go by. It seems to happen prior to the custom subscription provider being called.
It looks like it is trying to instantiate the right job (Epic1 is the name of the email), but something goes wrong.The log indicates the following:
2013-05-29 10:13:44,573 [33] INFO umbraco.BusinessLogic.Log - [Thread 15] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: ScheduledTask | User: 0 | NodeId: 0 | Comment: NewsletterStudio: ScheduledTask. Started thread to send newsletter "Epic1" (id 1923)
2013-05-29 10:13:47,852 [33] INFO umbraco.BusinessLogic.Log - [Thread 26] Redirected log call (please use Umbraco.Core.Logging.LogHelper instead of umbraco.BusinessLogic.Log) | Type: Error | User: 0 | NodeId: 0 | Comment: NewsletterStudio, SendNewsletterService: Length cannot be less than zero.
Parameter name: length :
2013-05-29 10:13:48,612 [33] INFO Umbraco.Core.PluginManager - [Thread 13] Completed resolution of types of umbraco.MacroEngines.IRazorDataTypeModel, found 15 (took 9ms)
2013-05-29 10:14:05,008 [33] INFO umbraco.presentation.publishingService - [Thread 36] newsletterstudioBounces has been called with response: True
Hi!
I'm currently out of office until monday but will try to help you as much as I can. It looks like it might me some corrupt data. Can you try to send to a new mailing list with just valid e-mails?
Are you using a custom subscription provider? Are you sure that this provider works and only returns valid emails?
// m
Hi Markus,
Looks like this was us who had not configured everything correctly for the newsletters subscription provider in the config, the assembly name was set to newsletterstudio, so it presumably couldn't instantiate the provider.
A more meaningful error message in the log would have been nice though :-)
Thanks,
Sune
Hi!
Great to hear that you found the issue!
Yes I agree the message could have been better we'll see how that can be improved.
Thank you for using the packge!
/ m
is working on a reply...