BrightStor ARCserve Backup Alerts not working

Sometime in 2006, the Alerts stopped functioning in ARCserve, and we can't get them to work again.  When we send a test alert, we receive it, but we do not receive a message at night when the backup is complete.  The Alert  Activity Log shows "Sending SMTP Successfully" each night.
Windows Server 2003
BrightStor ARCserve Backup v11.5 SP2 Build 4232
SMTP Settings are administrator@domain.local, Subject "BAB Alert Notification", SMTP Server  (domain is our client's domain).
Preflight Check runs fine.  We upgraded them from an older version to 11.5, thinking that would fix it, but there must be another problem?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Well if Alert reports sending the messages, how do you know it is not really sending them?
Perhaps the messages are being sent but something at the other end or in between has changed to prevent their arrival at the destination.

Off the top of my head, check to see that the destination is receiving other SMTP messages.
Perhaps there is some filtering preventing them from reaching the destination.
Try sending an SMTP message from some other application at the same system to see if it reaches the destination.
johndgriffinAuthor Commented:
We are the recipient of the messages.  We receive email from their users to our support inbox daily.  We sent a message from Outlook on that server and received it.
Also, we did delete the job and started from scratch.
Any other ideas?
If the SMTP engine on the BAB server is sending the message to their local domain, then something else is supposed to pick it up from there and send to its destination.  Assuming it's Exchange, I can think of 2 things: 1) The Exchange server is rejecting the message, possibly due to Microsoft security patches or 2) there's a spam or antivirus gateway that's rejecting the message because it hasn't been whitelisted or otherwise exempted from the spam/antivirus gateway's detection criteria.

Internal non-Exchange SMTP traffic is usually considered suspect unless those tools that watch for malware/spambot activity are told otherwise.

Having it suddenly stop functioning souns suspiciously like a Windows Update or Exchange service pack action...
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

As davidmichael said, you should send an SMTP message from  another app on the same system.  Outlook doesn't send SMTP unless it's pointing at an SMTP server, and then, as an SMTP client.  If you've got Exchange, it's more likely to be sending the message via MAPI.
johndgriffinAuthor Commented:
I don't think there's another application on the server to send an SMTP message, how would I do this?
Also, because I can send the Test Alert and it comes through, that should have gone through SMTP anyway?  If the test goes through, doesn't that foil that theory?
johndgriffinAuthor Commented:
We tested and SMTP is working.
Other thoughts?
johndgriffinAuthor Commented:
Okay, here is another piece of the puzzle, and I'm upping the points...
We do get the messages on after the backups on Friday nights, but not Monday-Thursday.

Is it the same job for both? Perhaps there is a mistake with the way the Mon-Thurs. job is setup.
johndgriffinAuthor Commented:
Same job, there is only one backup job (there is the pruning job, too).  
The only difference is Monday-Thursday is incremental, Friday is full.
Yes, weird :)
Sorry but this one has me stumped I'm out of idea, but will keep thinking about it.
johndgriffinAuthor Commented:
I thought I'd increase the points to see if there are any further ideas....we are having the same issue now at another client of ours.  We were getting the messages, then all of sudden they stop.  Test alerts work.  The other client is a little different in that we're running BrightStor ARCserve (v11.5 SP1 Build 4146) from a host computer (using VMware).  The original client that does not send messages, though, is running Windows.
Did some research and came up with these things that got it working for others.

resolutions: configured Virtual SMTP-server's relay (from server's properties, access, relay) to allow relay from it's own IP-address because that's where Alert Managers SMTP-connections come from
I installed the patch Wiedie sugested but still couldn't get the notifications. I then did a tcpdump on the SMTP server and saw that CA doesn't follow the RFC om SMTP.

They use "RCPT" and not "RCPT TO:<>" as the RFC says. So i then changed the "Address" field in the "SMTP Recipients" to <> instead of and now it works. So if you have a picky SMTP server you could try this.
To get the alerts working you need to logon locally to the server using the agent account that you have setup with a mailbox in your domain. Then you need to run through the Exchange agent configuration whilst logged on as this user. Specify the mailbox and account details for this user during the setup and the configuration will complete succesfully then you should be able to send the test message.

The account will need the right to log on locally, act as part of the OS, log on as a service and I would also add them to the backup operators group.
Yes you are correct SMTP server has to be existing with the machine having alert Manager otherwise it won't work
In case you have more than one Arcserve Server you need to
configure SMTP server for each,CA promised to relase a new version on Alert manager which you can specify the SMTP server,but till this momemmt no new about it.
What we can do is just to wait and accept what CA gives us.
Working solution:
Install SMTP service of IIS, set Smart host to be your Exchange server (IP or domain name).
Setup SMTP in Alert Manager, do a test mail and viola..
and this one is from rindi
Also make sure your firewall has port 25 open so that you can send from that port. Some mailing systems require you to authenticate yourself with the mail server to be able to use it to send messages (in outlook you sometimes have to check this option when you setup an account). If this is the case you might have to get the arcserve alerting agent to log on to your mail server first, before you can send alerts.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Forced accept.

EE Admin
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.