01-08-2014 09:20 AM
Backup exec isn't sending email notifications anymore. I have checked all of backup execs email/notification settings, and have compared them to another server that we have backup exec on, and that is working.
Seemed to have happened over night. It was working one day then the next it stopped.
I captured a log from the debug monitor while sending a test email. It says it failed to send the mail, mentions our mail servers ip and port which is correct. Besides that I don't understand anything else on the log file.
Please see the attached log file.
Solved! Go to Solution.
01-08-2014 11:04 PM
This usually happens if a needed port is blocked or in use by another app. For further isolation, consider testing notifications using this KB - http://www.symantec.com/business/support/index?page=content&id=TECH22965
01-08-2014 09:29 AM
Hello phoneepert,
Have you tried sending a test notification?
Here is a great troubleshooting article Troubleshooting Email Notifications in Backup Exec
01-08-2014 09:55 AM
hello imsla,
I'm not sure if you read my post. Seems you are just going through the motions of replying. But i did fail to mention that i was sending the test notifications while running the backup exec debug monitor. Before I posted here i came accrose that article. Followed the instructions up to where it asks you to find,
"notify return code"
I was unable to find that code in the log report so I was unable to do a search for it like the artical suggests.
More or less i was hoping someone could look over the log file and give me some insight.
01-08-2014 12:06 PM
It looks like you are running Symantec Endpoint Protection. Have you excluded the Backup Exec processes on the Media server and remote server? As a test try disabling it.
01-08-2014 01:17 PM
01-08-2014 04:52 PM
in ur log said ....
BESERVER: [01/08/14 09:47:19] [0000] In Function MN: SendNotification SmtpException System.Net.Mail.SmtpException: Failure sending mail. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 10.1.0.214:25
01-08-2014 11:04 PM
This usually happens if a needed port is blocked or in use by another app. For further isolation, consider testing notifications using this KB - http://www.symantec.com/business/support/index?page=content&id=TECH22965