Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

vbSendMail Errors 1

Status
Not open for further replies.

AEtherson

Programmer
Oct 10, 2003
119
GB

We are utilizing the above code to automate the sending of processing emails to our exchange server. However, it is very intermittent sending say 3, then stalling on the fourth with a SMTP timeout error.

Anyone had this problem and if so managed to get around it??

Thanks in advance.

AL
 
Where is "the above code"? :)
Try DoEvents... Could help. That's the first idea that's crosses my mind.
 

Search the net for the code - it has been mentioned regularly here.

DoEvents would do nothing.
 
Ha?!?
You want me to search the net for the code you are using?
And then provide a solution?
You are joking, are you? Ha ha!
What would be a Google search like:
"AEtherson's error code for vbSendMail" ?
 
NOW you're talking!...
Let's see...
Uh, that's a third party dll you are using. First of all, you should get in touch with the one that posted that dll.
And you still haven't tell us how you use that code. Do you call that sample sub from a loop? If soo, I still sugest you to use in that loop a doevents...
Is this any good?
 

It's a DLL but the underlying code is within the zip and it is THIS code that is causing the error (and yes have tried the code AND the compiled exe/dll)

DoEvents will do NOTHING.

If you read the above problem you would have noticed the error is a timeout on the SMTP. NOT VB.
 
OK. OK.
Dont get upset of me. I was just makying a point that without an exact error on an exact code, noone could ever help you. Think about it: you actualy sugested me to search the net for the code that doesn't work for you!... :) Do you realy think this is a good approuch?!?

Now, let's get serious and solve your problem. Are you aware about inprocess/outprocess debug in VB?
What you need to do is make a project group in VB and include in it your application together with the dll source code(as a second project in your group) and debug to identify the line of code that generates the error inside that dll.
That's all. After you find the error, post that piece of code together with the error and maybe someone will come up with an idea...
 

BogdanMBM - please don't patronise me. You obviously do not know what we are talking about so please leave it to others that do.
 
AEtherson,
Let me assure you that patronising WAS NOT my intention. Maybe my english is not soo goog (I'm not a native).
I was just trying to offer a solution. I'm sorry if you felt offended by my replyes.
I know VB and I've worked in projects regarding mailing solutions in VB so I think I can come up with an idea but I need the code that generates the error and a better explanation of the context in with the error appears.

Btw: have you seen my profile in this site? Does it recommend me as a diletant? I think not and I hope not. I have nothing but good intentions.
 
BogdanMBM - the whole code in question is enclosed within the zip file mentioned earlier.

The problem I raised is that I asked if anyone else had had the same problem utilizing this code. It became apparant that you have not used the code in question and therefore maybe unable to provide a solution.

The code as it comes works fine - I have the feeling it is the exchange server that is at fault - Not the underlying VB code.

I apologise if I may have upset you but I am looking for the solution to this ASAP.
 
Hmm...
If the code works fine for you, I'm afraid I can not help you.
I can not test the functionality of the code wright now (I'm at the office and can not recreate the hole environment <SMTP service & stuff> cause I'm not admin on my machines(darn company politics :) )) but I'll trie to test it at home (that's in about 6 hours...).
Meenwhile, maybe someone else on this forum can provide some ideas. I'm curious too to find out what is going wrong. If you find out on yourself, it would be a good (nice) ideea to post the findings back here so we could all learn from it.
Good look!
 
>If you read the above problem you would have noticed the error is a timeout on the SMTP

Frankly, I'd be more inclined to blame MSWINSCK.OCX
 
Thanks strongm

Do you know of any other methord of sending data to the exchange server
 
I tend to use CDO for Windows 2000 (or the slightly more comprehensive CDO for Microsoft Exchange)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top