Hello!
I have a client running BE 10 revision 5484 and SP1 on a Windows Server 2003 Enterprise Edition server, not running SP1 yet. Notifications are sent via an external SMTP server that does not require authentication.
I have job notifications set up for four users: Gregg, Chris, Mike, and Howard, in that order. If I click the Test button in each user's setup window, each user gets an email. If I run a test backup of a few hundred MBs, each user gets an email. If I let the full backup run at night, SOME users get notified.
I tested it yesterday with SGMon.exe running, and I ran two full backups of 22GB. Fortunately, their LTO2 drive is FAST and did the full backup in 45 minutes. After both of those full backups, I reviewed the SGMon log. It showed the following information (frivolous stuff trimmed to clarify):
beserver: 07/12/05 11:06:42 18 Doing Notify
Notify Return Code:0, batch:6, index:0
Notify Return Code:0, batch:6, index:1
Notify Return Code:0, batch:6, index:2
Notify Return Code:0, batch:6, index:3
All four users got an email notification.
I let it run on its own last night with SGMon watching, and it had these results, again trimmed for clarity.
beserver: 07/12/05 20:44:52 18 Doing Notify
Notify Return Code:800e0005, batch:8, index:0
Notify Return Code:0, batch:8, index:1
Notify Return Code:0, batch:8, index:2
Notify Return Code:800e0005, batch:8, index:3
In the job setup for the daily backup, the users are listed in this order: Gregg, Chris, Mike, and Howard. Last night, only Chris and Mike got an email notification, which matches up with the return codes above, assuming they follow the order that the job has set up for those users.
Would this article http://seer.support.veritas.com/docs/266050.htm apply here, and would the extracted version be different since I have BE 10 SP1 installed?
Any ideas what the "Notify Return Code:800e0005" error means?
Thanks for the help!
Gregg Hill