The best part is that it has ALWAYS been. Its unstable and flaky, as you are discovering. I check with our network team who are in charge of the VPN connection and firewall, and they say that as long as yuo can telnet the SMTP server through port 25, it's Ok from their end. Honestly, your best option is to simply not use Backup Exec anymore. It was working perfectly well a month ago, and I don't know what could have heppened for it to stop working all of a sudden. In some cases, however, it will crash and you will see a generic error message simply stating that Backup Exec has stopped working.
Backup exec has stopped working code#
Most of the time when Backup Exec experiences a problem, it will display an error code that you can use to help determine the nature of the problem. Check if anything else is using port 1000. Backup Exec error: Backup Exec has stopped working. Chances are that the relationship between BE and the agent has gotten corrupted.
Backup exec has stopped working install#
When i click on the test button, backupexec gives me a pop up saying "a test message has been queued for delivery to the selected recipients" (that's me), but i don't recieve any email. If install is successful, test the backup job. I have my own email address as one of the "Recipients" in backup exec, and there is an option to click on a "TEST" button to test if you can recieve emails to this address. Also, on the same server i have a WSUS installation for Windows updates to local clients, which is also configured to send me email notifications through the SAME SMTP server and this works just fine.
I can telnet the SMTP server through port 25 with no problems. Backup exec is a pain at times But it keeps me on my toes - to be fair it has worked for me when Ive needed to restore. They are located in a remote site in Paris, which we have a VPN connection to. We don't have a local exchange server or SMTP server. I've recently installed Backup Exec 12d on a file server of ours.Īll of a sudden, it stopped sending email notifications.
0 kommentar(er)
