Event ID's 7010, 7002 and 3017

Posted on 2007-10-01
Last Modified: 2012-08-13
On my Exchange 2003 server I m having 3 Event ID errors I can t solve. The ID s are 7010, 7002 and 3017. The ID of 3017 concerns me the most. We have 2 front end servers and two back end servers. The error is happening on EXBE01
For the 3017 event ID error I have checked that no DNS internal or External are setup.  Under routing groups connectors there are 3 connectors and they have EXBE01 as the Default SMTP server.  And it s setup to use DNS to route to each address space on this connector.
Below are the SMTP Virtual server the Fully-qualified Domain name
Front end servers
EXFE01   exfe01.domain.local
EXFE02   exfe02.domain.local
Back End servers
Question by:soupy66
    LVL 104

    Expert Comment

    Error IDs are useless on their own.
    You need to post the full error message.

    However if you have routing groups the entry on the SMTP virtual server under FQDN becomes important.
    That can be resolved by changing the SMTP IP address setting from All Unassigned to the specific IP address of the server. Then recreate the routing group connectors.


    Author Comment

    First  event ID error 3017
    A non-delivery report with a status code of 5.3.5 was generated for recipient rfc822; (Message-ID  <>).  
    Causes: A looping condition was detected. (The server is configured to route mail back to itself). If you have multiple SMTP Virtual Servers configured on your Exchange server, make sure they are defined by a unique incoming port and that the outgoing SMTP port configuration is valid to avoid looping between local virtual servers.    
    Solution: Check the configuration of the virtual serverÆs connectors for loops and ensure each virtual server is defined by a unique incoming port.

    I've checked the setting for the solution I found and still receive this error.
    LVL 104

    Accepted Solution

    Did you make the change that I have outlined in my first response?
    Having both servers with the same FQDN on the SMTP virtual server is not a good idea and it will cause problems.
    Unless you have a good reason not to, I would suggest that you configure SMTP Connectors to route email out through the frontend servers. Then ensure that the frontend servers have their own DNS names, with matching reverse DNS entries etc.


    Author Comment

    This can be close as we can't make any changes until December as thats a slow month and this is are busy month.
    LVL 1

    Expert Comment

    Oh thats no good, I was having the same issue - and was monitoring the posts

    Featured Post

    Free book by J.Peter Bruzzese, Microsoft MVP

    Are you using Office 365? Trying to set up email signatures but you’re struggling with transport rules and connectors? Let renowned Microsoft MVP J.Peter Bruzzese show you how in this exclusive e-book on Office 365 email signatures. Better yet, it’s free!

    Join & Write a Comment

    Suggested Solutions

    Granting full access permission allows users to access mailboxes present in their database. By giving full access permission one can open and read the content of any mailbox but cannot send emails from that mailbox.
    Easy CSR creation in Exchange 2007,2010 and 2013
    In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

    746 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    19 Experts available now in Live!

    Get 1:1 Help Now