Event Log Error

Feb 12, 2010 at 2:54 PM
Edited Feb 12, 2010 at 6:33 PM

Everything is working fine with emails and verification emails, however once and while we get the follwoing error.  It seems to happen after a validation gets sent out and they respond, creating the case, and the case email gets sent out.  The email gets sent, but the error occurs.

Failure sending mail.

Unable to connect to the remote server

Stack trace:
   at System.Net.Mail.SmtpClient.Send(MailMessage message)
   at QueueManager.Helper.CRMHelper.SendNetMail(String Subject, String Body, String SendTo, String SendToBcc, String SendFrom, Boolean Html) in C:\Projects\CRMQueueManager\QueueManagerHelper\CRMHelper.vb:line 509
   at QueueManager.Helper.CRMHelper.ResolveParentAccount(contact Contact, String Address, String ResolveMailTo, String ResolveMailFrom) in C:\Projects\CRMQueueManager\QueueManagerHelper\CRMHelper.vb:line 253


Feb 14, 2010 at 9:24 PM

Hi, I believe you have some incorrect values in resolveparent, resolveparent-notify or resolveparent-from.

Feb 15, 2010 at 3:33 PM

Could be, but they have been working fine up until now with 1.61 and CRM 4.0 RollUp 8, settings are below:

resolveparent-from="Automatic Case Mailer <validation@XXX.com>"


Feb 15, 2010 at 10:04 PM

The weird thing is that you mention that the e-mail gets sent but this error is being logged. It happens in ResolveParentAccount which also sends e-mail to the address enterned in resolveparent-notify when there's a problem with the parent resolving thingy or when it successfully matched a parent account. For some reason that fails with "Unable to connect to the remote server" which is a lame error. Could be intermittent connection error with the smtp server OR problem delivering to the revciever depending on a number of things. After that the case e-mail is sent which indicates it's not the smtp server. Hence my last reply. Can you go back in your log files/event log and see if there are any other errors logged and/or if it's only in ResolveParentAccount? Can you post a complete error (there should be more in the stack trace).