ThermoSight
March 12th, 2009, 08:54 PM
Hello.
I've encountered an eMail problem well beyond my meager debugging capability. Perhaps you know the answer or have a suggested starting point ....
I have a little C++ .NET (Visual Studio 2003) application which has been working exceptionally well since some time in 2006. This routine sends out email messages (using System::Web::Mail) as per the statement "SmtpMail::Send(pMessage)" whenever an event occurs. Indeed, it normally sends two such messages: one to the individual, and one to the system administrator (Me).
Now, as mentioned a moment ago, this HAD been working flawlessly EVERY DAY since going operational sometime in 2006. EVERY DAY.
However, a week or two ago, just for giggles, I wrote (and continue writing) a new version of the program in C# (Visual Studio 2008) on a second machine on the network. The new version sends email (using System.Net.Mail) via the SmtpClient class - that is, via the statement "client.Send(note)".
I can't say for certain WHEN the problem arose, but suspiciously, sometime around the time the C# program began sending its first such emails, the older version on the Sony Vaio STOPPED sending the email to the individual ... but it CONTINUES, however, to send the email to the administrator.
The network is configured such that both PCs are connected to a router and each finds a connection to the internet thru the router, so it's not like one machine relies on the other for an internet connection.
So, the question is, is it possible that the C# program has somehow affected the email capability of the C++ program on a different machine on the same network, or is that timing just coincidence ?
Is it possible that there is some incompatibility or conflict between the System::Web::Mail and System.Net.Mail, causing one to quit working ? on DIFFERENT machines ?
May I have the benefit of your thoughts ?
Oh! before I leave you with this brain twister, let me impart this thought .... I went into the C++ program with the debugger. The older program *** DOES *** reach the failing SmtpMail::Send(pMessage)" statement. And when that apparently failing statement returns, the program continues on its way thru the next coupla statements to send the Administrator (me) his copy of the message. Two SmtpMail::Send statements are executed within half a dozen lines of each other. The first fails, the second succeeds. EVERY TIME.
NOW may I have the benefit of your suggestions ?
thanks.
Best wishes.
bill
I've encountered an eMail problem well beyond my meager debugging capability. Perhaps you know the answer or have a suggested starting point ....
I have a little C++ .NET (Visual Studio 2003) application which has been working exceptionally well since some time in 2006. This routine sends out email messages (using System::Web::Mail) as per the statement "SmtpMail::Send(pMessage)" whenever an event occurs. Indeed, it normally sends two such messages: one to the individual, and one to the system administrator (Me).
Now, as mentioned a moment ago, this HAD been working flawlessly EVERY DAY since going operational sometime in 2006. EVERY DAY.
However, a week or two ago, just for giggles, I wrote (and continue writing) a new version of the program in C# (Visual Studio 2008) on a second machine on the network. The new version sends email (using System.Net.Mail) via the SmtpClient class - that is, via the statement "client.Send(note)".
I can't say for certain WHEN the problem arose, but suspiciously, sometime around the time the C# program began sending its first such emails, the older version on the Sony Vaio STOPPED sending the email to the individual ... but it CONTINUES, however, to send the email to the administrator.
The network is configured such that both PCs are connected to a router and each finds a connection to the internet thru the router, so it's not like one machine relies on the other for an internet connection.
So, the question is, is it possible that the C# program has somehow affected the email capability of the C++ program on a different machine on the same network, or is that timing just coincidence ?
Is it possible that there is some incompatibility or conflict between the System::Web::Mail and System.Net.Mail, causing one to quit working ? on DIFFERENT machines ?
May I have the benefit of your thoughts ?
Oh! before I leave you with this brain twister, let me impart this thought .... I went into the C++ program with the debugger. The older program *** DOES *** reach the failing SmtpMail::Send(pMessage)" statement. And when that apparently failing statement returns, the program continues on its way thru the next coupla statements to send the Administrator (me) his copy of the message. Two SmtpMail::Send statements are executed within half a dozen lines of each other. The first fails, the second succeeds. EVERY TIME.
NOW may I have the benefit of your suggestions ?
thanks.
Best wishes.
bill