Smart Mailer ASP Support Product Page
This topic was archived by George Petrov on 1/23/2012 10:58:19 AM
reason: old topic
reason: old topic
Not a problem
Again with error msxml3.dll error '80072ee2'
Reported 22 Mar 2005 13:11:26
1
has this problem
22 Mar 2005 13:11:26 Ivan Halen posted:
Ok, since lot of people have problem with this kind of error and none of you supporters gave the shadow of an answer, I decided to write once per day a topic about this: sorry if this would seem bad, but if it's the only way to get your attention maybe it's worth it...Well, I wrote (www.dmxzone.com/forum/link.asp?TOPIC_ID=30333) some months a go a support requst: Camillah answer was unuseful, and I had no answer anymore...
Now, I tried with CDONTS, CDO, AspEmail and all give the same error:
-----------------------------------
msxml3.dll error '80072ee2'
The operation timed out
/shr/ScriptLibrary/incSmartMailer.asp, line 1161
------------------------------------
The timeout script is set to 30000, so this is not the problem
As in this topic: www.dmxzone.com/forum/link.asp?TOPIC_ID=29684, only a few mails are sent, then there's an Operation timeout
Of course, the Flash shows a "Can't load progress information" after a while, but even if this doesn't work as it should, this is not the main problem..
The main problem is that can't send the newsletter 'cause of the Timeout
That's all
See you tomorrow for another topic about this, since you don't solve our problem
Official Solution
Replied 10 Dec 2006 23:55:36
Hi Guys,
Unfortunately all possible causes are already listed in this topic. If it isn't one of this that your server just can not handle the load of sending such newsletter - and just waits too long.
There is really nothing we can do here.
The only thing you can do is (lead from the above):
* increase all timeouts
* cut down the asp code in a html template that you use
* don't use session code in global.asa
* switch sessions off in your template page
That is really all you can do - sorry but I don't see a way how we can *fix* this in the extension as it is very much server dependend.
We are still however researching this issue and if we find some way to bypass the problem will let you know. I will also approach some of you for live testing as this issue is really difficult to test.
Greetings,
George
--------------------------------------------------
George Petrov - Founder of the Dynamic Zones
DMXzone.com, FWzone.net, FLzone.net, CFzone.net,
DNzone.com, FlashFiles.nl
--------------------------------------------------
Unfortunately all possible causes are already listed in this topic. If it isn't one of this that your server just can not handle the load of sending such newsletter - and just waits too long.
There is really nothing we can do here.
The only thing you can do is (lead from the above):
* increase all timeouts
* cut down the asp code in a html template that you use
* don't use session code in global.asa
* switch sessions off in your template page
That is really all you can do - sorry but I don't see a way how we can *fix* this in the extension as it is very much server dependend.
We are still however researching this issue and if we find some way to bypass the problem will let you know. I will also approach some of you for live testing as this issue is really difficult to test.
Greetings,
George
--------------------------------------------------
George Petrov - Founder of the Dynamic Zones
DMXzone.com, FWzone.net, FLzone.net, CFzone.net,
DNzone.com, FlashFiles.nl
--------------------------------------------------
Replies
Replied 03 Sep 2010 19:24:06
03 Sep 2010 19:24:06 Matt Brumpton replied:
I have been struggling with a simialr issue on an ASP site that I have recently inherited for maintenance.
I had moved the site to a testing server and had successfully got it working. I then noticed that I could no longer send messages based on msxml3.dll.
Having trawled the Internet for solutions I finally came across the problem which is in addition to the steps mentioned above. Firstly MS do not recommend requesting information from the same website. There is a finite limit to threads and resources available
support.microsoft.com/kb/290761/EN-US/
However my problem was that I had turned on server side debugging which meant that only one thread was available and hence the timout due to resource conflict.
As soon as I turned server side debugging off the application worked again.
Not sure if this is the issue people are facing but it worked for me.
I had moved the site to a testing server and had successfully got it working. I then noticed that I could no longer send messages based on msxml3.dll.
Having trawled the Internet for solutions I finally came across the problem which is in addition to the steps mentioned above. Firstly MS do not recommend requesting information from the same website. There is a finite limit to threads and resources available
support.microsoft.com/kb/290761/EN-US/
However my problem was that I had turned on server side debugging which meant that only one thread was available and hence the timout due to resource conflict.
As soon as I turned server side debugging off the application worked again.
Not sure if this is the issue people are facing but it worked for me.
Replied 03 Dec 2011 16:52:49
03 Dec 2011 16:52:49 rahat mitul replied:
I had this same dll missing problem..just install direct x from Microsoft... here is the link about how to download and install DirectX... support.microsoft.com/kb/179113