Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Backup Exec 2010 Email Notifications Stopped Working

Created: 23 May 2013 | 3 comments

I have Backup Exec 2010 on the Windows Server 2003 R2 server that up through last June was setup to send out email notifications through an Exchange Account.  That exchange server died at that time and the organization went to Google Apps.  I've never been able to get a Google Apps Account to work in Backup Exec but was able to do so utilizing a Yahoo email account.  The Yahoo account has worked and sent out the notification for the last 9-10 months until about 2-3 weeks ago when it stopped working.  When attempting to send out a test email I get the message that the email has been queued bit it appears that it nevers go out or at least I never receive the email.  I've been able to setup the Yahoo account in Outlook Express on the same server and send out and receive an email from there without any problem.  I cannot get it to work anymore in Backup Exec.  I have the smtp mail server setting at smpt.mail.yaoo.com and the port is 25, utlizing my log in credentials with authentication enabled, none of which have been changed when the notifications were working or after they have stopped.  Anyone have any ideas for a solution to this issue?

Operating Systems:

Comments 3 CommentsJump to latest comment

NOM115's picture

I had actually saw that article and went through it but could figure out things from there with the Notify Return Code it got.  The code was 800e0004,  Here is the entire text of the log after trying to send a test message after start SGmon:

*******************************************************************************
*****                    SGMon log for \\\\XXXXXXX                    *****
*****                    Local Offset =04:00                              *****
*******************************************************************************
BESERVER: [05/20/13 08:45:42] [6624]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:42] [8032]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:42] [6612]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:42] [6624]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:42] [8032]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:42] [6612]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:44] [6624]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:44] [8032]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:44] [6612]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:44] [6624]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:45] [8032]     17 Durham request from server vrts.notificationconfig.NotificationConfig
BESERVER: [05/20/13 08:45:45] [6612]     17 Durham request from server vrts.notificationconfig.NotificationConfig
BESERVER: [05/20/13 08:45:45] [6624]     17 Durham request from server vrts.notifyrecipient.BrokerProxy
BESERVER: [05/20/13 08:45:45] [6624]     17 Doing Notify
BESERVER: [05/20/13 08:45:45] [1788]     17 Notify Return Code:800e0004, batch:72, index:0

I apologize about that, I forgot to include this in my original post.

fbollier's picture

does your Backupexec server performs automatically windows update ? If so check if the date match between update and problem.

an other idea seems to delete mail recipient and recreate it

https://www-secure.symantec.com/connect/forums/email-notifications-quit-working