I think my SQL database is hosed.  I have been unable to create child portals for the past few weeks and I have tried to run the SqlDataProvider fixes that have been mentioned on this forum. 

Now I notice that my SMTP does not work properly.  When someone creates an account or a DNN notification tries to be sent, it doesn't go out and I get a General Exception in the logs.  I have posted an example message that is in the log.

Any Ideas?

AssemblyVersion: 04.04.01
PortalID: 0
PortalName: iBikeClubs
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
RawURL: /Home/tabid/36/ctl/Register/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.ibikeclubs.com/Home/tabid/36/ctl/Register/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.04506.30)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: ed98323e-4f34-4375-8ef7-749884e39a4b
InnerException: Mailbox unavailable. The server response was: <kevin@fabrizio.us> No such user here
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Net.Mail.SmtpTransport.SendMail
StackTrace:
Message: System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: <kevin@fabrizio.us> No such user here at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception) at System.Net.Mail.SmtpClient.Send(MailMessage message) at DotNetNuke.Services.Mail.Mail.SendMail(String MailFrom, String MailTo, String Cc, String Bcc, MailPriority Priority, String Subject, MailFormat BodyFormat, Encoding BodyEncoding, String Body, String Attachment, String SMTPServer, String SMTPAuthentication, String SMTPUsername, String SMTPPassword, Boolean SMTPEnableSSL)
Source:
Server Name: ANAXAVPS78

I know the error seems descriptive, except for the fact that EVERY email returns this response, no matter what email address.  Since this is my email address and I know it is valid, the problem is something within DNN.  Also, none of my other DNN installs have this problem (even to the same addresses). 

The problem with child portals is in reference to other posts I have made.  Basically whenever I try to create a new portal within this DNN install, it returns "Error Creating Portal".  Nothing appears in the Log to indicate a problem, but others have indicated it probably has somthing to do with the SQLDataProvider.  Since the error message from my email problem has a reference to the SQLDataProvider, I am assuming there is a problem with my database.

Does this provide any info that might spark an idea to try?

Thanks,

Kevin

After a LOT of digging around I resolved the problems. Here is what I discovered along the way:

1. The "Failed Recipient" error message is misleading. The recipient's address may not be the problem. I got this error for a lot of VALID addresses. 
2. You will see this message if DNN can't log into the SMTP account it is trying to send mail from. This could be because the SMTP user name OR the SMTP password are wrong.
3. DNN appears to cache the SMTP user name and password, so even if you change them to be correct in the Host/Admin UI they DON'T actually change until you restart the application.
4. If you are using Site settings for the SMTP configuration, the Test SMTP button does not use this configuration. This test button always uses the HOST configuration to test the email sending. So you could think you have it set up properly but it is not.
5. If you have an Administrator set for a site, mail will appear to come from that address. This can cause a "From domain must match authenticated domain" error if the administrator's email address is from a different domain than the SMTP user.

    

   6.DNN would CHANGE the passwords for my SMTP account set up for some reason. I did not figure out why or when.

So the key(s) to solving this are: Make sure your SMTP settings are correct, then UPDATE (testing at this point may reset the password), then restart the application. You cannot test a site setting with the "test" button, but you can test a host SMTP set up this way. Make sure at least the host setting works. I used a different email account for each site setting.

In order to track this down I had to modify the source code of the DNN platform to provide useful diagnostics. I have submitted those changes on GitHub and I hope they are incorporated in an upcoming release so others don't have to go through this ordeal.