Comments
Sort by recent activity
Ah, hidden in plain sight. Thanks. / comments
Ah, hidden in plain sight. Thanks.
Ok, having access to the logs is nice, but even that info isn't helping me get email sent. Here is the error in the log:
10:43:42.971|Error |AlertRepository |8 |Error sending test email|System.Net.Mail.SmtpException: Transaction failed. The server response was: 5.7.1 <kevin.broughton@elmlocating.com>: Sender address rejected: Access denied
at System.Net.Mail.RecipientCommand.CheckResponse(SmtpStatusCode statusCode, String response)
at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at e.a(a , RepositoryConfiguration , Boolean )
at e.a(String , RepositoryConfiguration , String& )
I've checked and rechecked my settings for SMTP Host, Port, Account User Name, Password, Send From Name, and Test Email address and they are all correct. I have other server software using the same email values fine, in addition the same values work in MS Outlook without problem. Based on the error message above, where do you suppose the problem lies?
P.S. I also have SQL Backup and I'm using the exact same email values in SQL Response as I am in SQL Backup. I copied and pasted all of them except the password which I retyped into both programs. SQL Backup can sent a test email, SQL Response still can't. / comments
Ok, having access to the logs is nice, but even that info isn't helping me get email sent. Here is the error in the log:
10:43:42.971|Error |AlertRepository |8 |Error sending test email|Syst...
I'm getting this same error and it also appears to be happening on frequently run jobs. I just download and installed SQL Response yesterday and I'm running version 1.0.0.1596. / comments
I'm getting this same error and it also appears to be happening on frequently run jobs. I just download and installed SQL Response yesterday and I'm running version 1.0.0.1596.
I also have seen a negative job duration in SQL Response, but that isn't what reality reflects in the SQL Agent logs. Haven't seen in this thread the reason for the negative duration. / comments
I also have seen a negative job duration in SQL Response, but that isn't what reality reflects in the SQL Agent logs. Haven't seen in this thread the reason for the negative duration.
I would concur that if users are required to close out incidents, you would want to record at a minimum the user name of the person who closed out the issue, the close time, and make available a note field.
Also, to follow the thought logically, it would make sense to allow a user to close a group of events by highlighting them and providing the opportunity to enter a note that would attach to every incident in the group as well as mark the username and time of the closing. / comments
I would concur that if users are required to close out incidents, you would want to record at a minimum the user name of the person who closed out the issue, the close time, and make available a no...