Developer forum

Forum » Development » sending newsletters crashes

sending newsletters crashes

E-mail notifications

Reply
Posted on 22/03/2011 12:02:16
Our customer tried to send a newsletter to approx. 27.000 recipients;
The process stopped at about 20.000 recipients, with a message in DW that a fatal error occured.

I examined the machine's eventlog and discovered 2 events at the time of the crash.

I replaced some machine/ip-information with asterisks (*)

I hope somebody can make something out of these events.

Thanks,
Ton



Log Name:      Application
Source:        ASP.NET 2.0.50727.0
Date:          2/27/2011 11:53:27 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      *****1
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 2/27/2011 11:53:27 AM
Event time (UTC): 2/27/2011 10:53:27 AM
Event ID: 2568df46e3214c9c88e52c829dd0eb82
Event sequence: 31415
Event occurrence: 2
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1/ROOT-1-129432319359394315
    Trust level: Full
    Application Virtual Path: /
    Application Path: D:\virtual_hosts\*******.nl\application\
    Machine name: *****1
 
Process information:
    Process ID: 4012
    Process name: w3wp.exe
    Account name: *****1\*******
 
Exception information:
    Exception type: HttpException
    Exception message: An error occurred while communicating with the remote host. The error code is 0x80070057.
 
Request information:
    Request URL: http://www.*******.nl/admin/public/NewsLetterV3/Logger.aspx?action=1&userID=4008&newsletterID=41&key=bad131269b35f9bdf82e84154fef8f18
    Request path: /admin/public/NewsLetterV3/Logger.aspx
    User host address: **.***.112.201
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: *****1\*******
 
Thread information:
    Thread ID: 23
    Thread account name: *****1\*******
    Is impersonating: False
    Stack trace:    at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async)
   at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal)
   at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
   at System.Web.HttpResponse.Flush(Boolean finalFlush)
   at System.Web.HttpResponse.Flush()
   at Dynamicweb.Admin.NewsLetterV3.Logger.OpenLetter(Int32 newsLetterId, Int32 userId, Boolean sendResponse)
   at Dynamicweb.Admin.NewsLetterV3.Logger.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

==========================================================================================================================

Log Name:      Application
Source:        ASP.NET 2.0.50727.0
Date:          2/27/2011 11:54:55 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      *******1
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 2/27/2011 11:54:55 AM
Event time (UTC): 2/27/2011 10:54:55 AM
Event ID: 137e3c00347b421c82113ed3beb6c909
Event sequence: 31606
Event occurrence: 3
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1/ROOT-1-129432319359394315
    Trust level: Full
    Application Virtual Path: /
    Application Path: D:\virtual_hosts\*******.nl\application\
    Machine name: *******1
 
Process information:
    Process ID: 4012
    Process name: w3wp.exe
    Account name: *******1\*******
 
Exception information:
    Exception type: Exception
    Exception message: SELECT * FROM [NewsLetterV3NewsLetterRecipient] WHERE [NewsLetterRecipientRecipientID]=417 AND [NewsLetterRecipientNewsLetterID]=41
 
Request information:
    Request URL: http://www.*******.nl/admin/public/NewsLetterV3/Logger.aspx?action=1&userID=417&newsletterID=41&key=65a546b6252becbcc4c1de27ec47a94b
    Request path: /admin/public/NewsLetterV3/Logger.aspx
    User host address: **.***.116.127
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: *******1\*******
 
Thread information:
    Thread ID: 15
    Thread account name: *******1\*******
    Is impersonating: False
    Stack trace:    at Dynamicweb.Modules.Common.DbHandler.GetDataReader(String sql, String db)
   at Dynamicweb.Modules.Common.DbObject.Load(String sql)
   at Dynamicweb.NewsLetterV3.RecipientNewsLetter..ctor(Int32 newsletterId, Int32 recipientId)
   at Dynamicweb.Admin.NewsLetterV3.Logger.OpenLetter(Int32 newsLetterId, Int32 userId, Boolean sendResponse)
   at Dynamicweb.Admin.NewsLetterV3.Logger.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
 
 


Replies

 
Nicolai Høeg Pedersen
Posted on 22/03/2011 13:40:38
Reply
These exceptions have nothing to do with the breakdown of the newsletter sendout...

There must be another exception that was caused by the sending routine.

Is it a returning problem or just occurred once?

It could be a memory problem on large newsletter lists. make sure the apppool has enough memory and is not set to recycle at a specific limit.
 
Posted on 22/03/2011 16:01:43
Reply
Thanks,

Yes, they have encountered this problem more than once.

No memorylimit has been set for recycling the app pool;
there is a time interval set for 29 hours

Please advise.

Many thanks,
Ton
 
Nicolai Høeg Pedersen
Posted on 22/03/2011 16:23:54
Reply
I need the exception from the error it self... Otherwise it will just be long shots...
 
Posted on 25/03/2011 15:23:05
Reply
Please check the attachment screendump of the customer.

Besides that, and the 2 exceptions I mentioned in the original post, I cannot find any other excpetions.

Please advise.

Thanks,
Ton
fatal-error-nieuwsbrief-2.jpg
 
Posted on 06/04/2011 16:30:25
Reply
Please?
 
Nicolai Høeg Pedersen
Posted on 06/04/2011 16:41:55
Reply
Problem is, that an unhandled exception occurs and DW provide no information about what the exception is.

I've created a bug and send the issue for fixing, TFS6345, so we can see which exception is happening. Errors sending each mail is handled and logged, so it is a more general thing - it could be a Notifications.NewsLetterV3.Newsletter.Sent notification subscriber.

Do you by any chance have one of those?
 
Ton Martens
Posted on 25/05/2011 17:44:32
Reply
 I'm sorry, but it seems I missed your reply.

However, you lost me here. What do you mean with 'Do you by any chance have one of those?'.
I gave you all info I could find..

Thanks,
Ton
 
Lars Hejgaard Sørensen
Posted on 25/10/2011 10:39:01
Reply

Hi,

We discovered the same error in the event log on a server where mails are being sent successfully. The solution is running 19.2.4.3. I reported this to your support, and they advice to upgrade the solution with reference to this thread and this entry: http://engage.dynamicweb-cms.com/News-552.aspx?NewsID=2051. But as far as I can see you're discussing two problems here: The error in the event log and mails not being sent. So before advicing the customer to upgrade, I'd be happy if you could confirm that the error in Logger.aspx discovered in the event log has been fixed or not. Thanks.

BR.
Lars


 

You must be logged in to post in the forum