we have the following error message in our newsletter section:
Error message:
NewsletterStudio, SendNewsletterService: Not allowed to change the 'ConnectionString' property. The connection's current state is connecting. : at System.Data.SqlClient.SqlConnection.ConnectionString_Set(DbConnectionPoolKey key)
at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
at NewsletterStudio.Infrastucture.Data.PetaPoco.Database.OpenSharedConnection()
at NewsletterStudio.Infrastucture.Data.PetaPoco.Database.Execute(String sql, Object[] args)
at NewsletterStudio.Infrastucture.Data.PPDatabaseAdaptor.Execute(String sql, Object[] parameters)
at NewsletterStudio.Infrastucture.Data.SubscriberRepository.SetAsActive(Int32[] ids)
at NewsletterStudio.Services.SendNewsLetterService.SendEmails()
You can try to continue to send the newsletter by going to the "Send options" and follow the instructions.
we are using Newsletter Studio 2.0.0 in an umbraco 7.1.6 environment, sending out mails through mandrill!
the error occured during the send out. we are composing the newsletter in the content section and trigger the send out from the content section. the newsletter then appears in the newsletter section under drafts with this error. i think the error occured after 4000 mails where sent.
we already sent out 2 newsletter the last days without any errors.
It's a really random error as I have never seen this before and the datalayer has been around for over one year now. Did you do anything else during the send out? Ie. worked with the db in some way?
Did you try to continue the send out? Did that work?
we have enabled throttling with 500 mails per batch and 120 seconds delay between. i've to ask you editor what they were doing during the sendout? Maybe the App Pool reclycled, i dont know.
do you think its save to continue the send out? so that only the 1000 missing get the newsletter?
the sendout of the missing newsletters finished without anymore troubles. just disabled throttling for the future.
in terms of mandrill i think the best way would be to use their rest api an have a single post for sending out a complete newsletter. i think that we should talk a bit more about your package and how we can integrate it deeper in our upcomming multisite project.
Both yes and no - We have been working on some proof on concepts but the downside is that each email is totally unique when it comes to links, some text, tracking pixels etc. So if you send to something like 10 000 subscribers thats 10 000 x 300 kb thats 3GB of email data that needs to be sent to them API. Of course there could be ways to do this if we where to disable some of the features but at the moment we're not looking to close at going down that path - we believe stronger in the possibilities that comes with having the newsletter system tightly integrated with the web site/web shop and its data.
Get in contact with me? Just send me an email, markus [at sign goes here] enkelmedia.se
Error on newsletter send out
Hi,
we have the following error message in our newsletter section:
Error message: NewsletterStudio, SendNewsletterService: Not allowed to change the 'ConnectionString' property. The connection's current state is connecting. : at System.Data.SqlClient.SqlConnection.ConnectionString_Set(DbConnectionPoolKey key) at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value) at NewsletterStudio.Infrastucture.Data.PetaPoco.Database.OpenSharedConnection() at NewsletterStudio.Infrastucture.Data.PetaPoco.Database.Execute(String sql, Object[] args) at NewsletterStudio.Infrastucture.Data.PPDatabaseAdaptor.Execute(String sql, Object[] parameters) at NewsletterStudio.Infrastucture.Data.SubscriberRepository.SetAsActive(Int32[] ids) at NewsletterStudio.Services.SendNewsLetterService.SendEmails() You can try to continue to send the newsletter by going to the "Send options" and follow the instructions.
we are using Newsletter Studio 2.0.0 in an umbraco 7.1.6 environment, sending out mails through mandrill!
Please need help regarding this issue.
thx,
Andreas
Hi!
First of all - thank you for using the package!
Do you know when you are getting this error? Just when the packge loads or during the accual send out?
Is this a new clean Umbraco installation or has the error just "showed" up?
Are you getting this error all the time or just once?
// m
Hi,
the error occured during the send out. we are composing the newsletter in the content section and trigger the send out from the content section. the newsletter then appears in the newsletter section under drafts with this error. i think the error occured after 4000 mails where sent.
we already sent out 2 newsletter the last days without any errors.
so it just happend today.
thx,
andreas
Hi again!
It's a really random error as I have never seen this before and the datalayer has been around for over one year now. Did you do anything else during the send out? Ie. worked with the db in some way?
Did you try to continue the send out? Did that work?
// m
Hi,
we have enabled throttling with 500 mails per batch and 120 seconds delay between. i've to ask you editor what they were doing during the sendout? Maybe the App Pool reclycled, i dont know.
do you think its save to continue the send out? so that only the 1000 missing get the newsletter?
thx
Hi!
I see the throttling should not have any impact but why are you using that with Mandrill? There is no need to use that - just adds complexity.
If the app pool recycle the send out batch will restart in a couple of minutes if the send out is not completed.
It is safe to continue it will just pick up where the error accoured.
/ m
Hi,
the sendout of the missing newsletters finished without anymore troubles. just disabled throttling for the future.
in terms of mandrill i think the best way would be to use their rest api an have a single post for sending out a complete newsletter. i think that we should talk a bit more about your package and how we can integrate it deeper in our upcomming multisite project.
whats the best way to get in contact?
thx
andreas
Hi!
Great to hear that its working now!
Both yes and no - We have been working on some proof on concepts but the downside is that each email is totally unique when it comes to links, some text, tracking pixels etc. So if you send to something like 10 000 subscribers thats 10 000 x 300 kb thats 3GB of email data that needs to be sent to them API. Of course there could be ways to do this if we where to disable some of the features but at the moment we're not looking to close at going down that path - we believe stronger in the possibilities that comes with having the newsletter system tightly integrated with the web site/web shop and its data.
Get in contact with me? Just send me an email, markus [at sign goes here] enkelmedia.se
Cheers!
// m
is working on a reply...