I realized that this happened when I try to start IIS when Apache web services has started (from XAMPP). When I stop Apache, I can start IIS.
And, vice versa, if I have my IIS started, I can’t able to start Apache. Perhaps this is due to they have the same port.
So, if you encountered this error message, check if you have Apache running at that time
Managed to fix it by going to IIS > Default SMTP Virtual Server > Property > Access > Relay
Even though I still not able to receive the mail I sent out yet, but there is no more error message when I use VB.NET code (System.Net.Mail.MailMessage) to send it.
When I went to C:InetpubmailrootQueue, I saw that the mail was there. My next goal is to make sure I receive this email. I think the next I need to look into SMTP thingy at my code.
During my development, I bound into this error. The short error message is “Failure sending mail”. The long one is
Failure sending mail. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
I googled a bit and found out that this is could be due to my SMTP services was not started. So, I went to start it but I got another message “Could not start the Simple Mail Transfer Protocol (SMTP) service on Local Computer. Error 1068: The dependency Service or group failed to start”.
So, I googled again and found out that this could be due to my IIS services was not started and so I went to start it. And guess what, there was still another error. I didn’t manage to save the error message this time.
Without giving up, I googled again and got tips to check on Event Log to see if there is any thing I can get from there. When I opened it, I saw nothing. Then, I went back to Window Services and found out that Event Log was disabled! I enabled it back, that is it. After that, I can start IIS services and SMTP services liao.
Wait a minute … as I continued with my development, I got another message, “Unable to send to all recipients”. This is will be shared in the next post.
I think I first learn about this and gain some conviction about this topic after I read what Douglas Jacoby wrote about this. This is the link –http://www.douglasjacoby.com/view_article.php?ID=2505
In short, what I learn from Douglas Jacoby is, I shouldn’t use those words / phrase. Reading about this topic again help me to understand why those words / phrase should be avoided.
Another author, Tony Warren, put it this way
But the fact is, saying “Oh My God” (OMG) this way, references God in vain. i.e., it is evoking God without a serious reason, reducing His value and dishonoring the title. In fact this devaluing is inherently part of the very definition of the word vain. Using the name without real purpose.
The word vain essentially means empty, or void of any real value. To take God’s name in vain is to evoke it in a hollow or meaningless way, without real significance or purpose to Him. It is essentially to treat the word God in a valueless way. So it really doesn’t take a rocket scientist to know that “Oh My God,” used in this frivolous way, isn’t really a call for God the father, it is simply used by habit or as an purposeless exclamation. Certainly it isn’t an act of Christians agreeing with, evoking, praising or petitioning God. The truth is, this phrase is almost always little more than a bad cultural or social habit.
(Source)