About Us Products Services Partners Certification Testimonials Contact Us Support
Call Us :(718) 361-1010
Lansend Microsoft Certified Partner Microsoft Small Business Specialist

Backup Exec email alerts with Exchange 2007 Exchange 2010 SBS 2008

clock February 25, 2011 15:04 by author Ashwin Pai

The issue has been resolved.

  1. In the Exchange MMC , under server configuration select Hub transport
  2. in the action menu on the right hand side select " New Receive Connector"
  3. Give it a name.  any name will do , we call it "Application relay"
  4. In the next screen  Local Network settings
    4.a provide the fully qualified ( internal) dns name of the mail server
    4b. Edit the the receive connector binding & change the port to 26
  5. In the next screen Remote network settings
    5a. remove the default bindings of 0.0.0.0-255.255.255.255
    5b. Add the IP address of the server running Backup exec, in our case 10.0.0.4
    This address is often the same as that of the Exchange server especially if you are running SBS
  6. On the next screen New Connector you will be displayed a summary of your configuration which will look somewhat like this , click NEW to build it.
    Name: Application relay
    Type: Custom
    IP Address(es):
    (All available IPv4 addresses): Port 26
    FQDN: mailserver.domainname.com
    Remote IP range(s):
    10.0.0.4
  7. IF all is well  On the next screen Completion you will be informed  so . click Finish
  8. In the Exchange MMC double click the connector you just created &
    8a. select the Permission groups tab & check Exchange Server
    ( Note: if backupexec is not on the same server as the exchange server you may have to play around with this)
    8b. select the Authentication tab & additionally check off  Externally Secured
  9. Go to Symantec Backup Exec & select E-mail alerts and Pager notifications from the drop down menu
  10. Enable SMTP Configuration & fill up the information for your mail server , remember to specify port 26, Sender name & Sender email address. There is no need to Enable SMTP Authentication

 

That's it you are done.

 If you still cannot send email alerts , you will want to set the logging for the recive connector you just created to Verbose

You will find the log in the following folder.

Receive Connector logs are located in:
Exchange 2010: C:\Program Files\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive
Exchange 2007: C:\Program Files\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive
 

Send Connector logs are located in:
Exchange 2010: C:\Program Files\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend
Exchange 2007: C:\Program Files\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend

 images coming shortly



SQL error number: "0011".

clock September 15, 2010 08:30 by author Ashwin Pai
Event Type:        Error Event Source:    Backup Exec Event Category:     None Event ID:              57860 Date:                     9/15/2010 Time:                     7:00:19 AM User:                     N/A Computer:          SPRDC Description: An error occurred while attempting to log in to the following server: "Server name".  SQL error number: "0011".  SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.   Refer to Symantec Knowledgebase article Document ID: 264616 http://support.veritas.com/docs/264616  


The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid.

clock September 15, 2010 06:42 by author Ashwin Pai
Event Type: WarningEvent Source: SQLBrowserEvent Category: NoneEvent ID: 3Date:  9/15/2010Time:  10:17:51 AMUser:  N/AComputer: SERVER NAME Description:The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid. Cause: one of two reasons. 1. TCP/IP and Named Pipes is disabled Enable TCP/IP and Named Pipes using SQL Server Configuration Manager 2. Listening on the wrong IP address. This was our problem. Backup exec 11d was installed on Small business Server 2003  & the SBS Server also served as the VPN server. We disabled the VPN interface to stop  the SQL server from listening on the VPN interface. See 3rd IP below.  This worked for us  


TextBox

Blogroll

    Calendar

    <<  September 2019  >>
    MoTuWeThFrSaSu
    2627282930311
    2345678
    9101112131415
    16171819202122
    23242526272829
    30123456

    View posts in large calendar

    Sign in

    About Us Products Services Partners Certification Testimonials Contact Us Support Site Map Copyright © 2019. All Rights Reserved.