Announcement

Collapse
No announcement yet.

SBS 2011 Exchange Stopped Processing Email Microsoft Exchange Transport Errors

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SBS 2011 Exchange Stopped Processing Email Microsoft Exchange Transport Errors

    Hi all
    I have an SBS2011 With Exchange 2010 and recently installed AVG and Symantec Backup Exec, all worked fine for a week then exchange stopped processing emails. In event viewer I started to get lots of Microsoft Exchange Transport Errors and could not Telnet to Exchange. Below is an Warning event log that appears frequently.

    The process with process ID 6260 is holding the performance counter server alive Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6260 StartupTime: 130189790682619983 from instance _total(CFBEE91 RefCount=0 SpinLock=0 Offset=32 and category MSExchangeTransport ServerAlive while running processes are: Processes running are:
    4136 SPWRITER
    4332 sqlwriter
    2360 mad
    6100 Microsoft.Exchange.RpcClientAccess.Service
    6676 SMSvcHost
    776 winlogon
    1760 avgwdsvc
    7076 fdlauncher
    1164 svchost
    4116 wsstracing
    1160 inetinfo
    3916 svchost
    4940 avgcsrva
    3980 WSSADMIN
    1684 svchost
    1932 dns
    5280 sppsvc
    7408 mssdmn
    352 avgrsa
    6260 MSExchangeTransport
    8168 fdlauncher
    348 svchost
    2436 conhost
    740 csrss
    3008 mssearch
    7824 w3wp
    4868 Microsoft.Exchange.AddressBook.Service
    1912 svchost
    1852 dfsrs
    2500 sqlservr
    1508 MSExchangeADTopologyService
    1704 avgidsagent
    4796 dfssvc
    1308 svchost
    716 wininit
    1968 PresentationFontCache
    3468 SMSvcHost
    1068 svchost
    900 LogonUI
    5824 Microsoft.Exchange.ProtectedServiceHost
    5232 powershell
    2472 mqsvc
    5260 MsExchangeFDS
    4636 DataCollectorSvc
    8180 svchost
    5616 MSExchangeMailSubmission
    8308 svchost
    292 smss
    8368 conhost
    4820 Microsoft.Exchange.AntispamUpdateSvc
    1380 ismserv
    8364 conhost
    2056 vdsldr
    5008 WmiPrvSE
    4472 wsusservice
    672 csrss
    7172 vds
    4216 sqlbrowser
    4412 svchost
    2440 msftesql
    3224 sqlservr
    2236 store
    1644 Microsoft.ActiveDirectory.WebServices
    828 services
    8340 fdhost
    5384 MSExchangeMailboxAssistants
    4988 Microsoft.Exchange.Search.ExSearch
    4396 w3wp
    3804 ntfrs
    8332 fdhost
    844 lsm
    1124 svchost
    6160 MSExchangeThrottling
    836 lsass
    8124 taskeng
    4380 svchost
    1616 spoolsv
    5380 Microsoft.Exchange.ServiceHost
    624 svchost
    1016 svchost
    4360 svchost
    2980 sqlservr
    1204 svchost
    5536 MSExchangeMailboxReplication
    3956 silsvc
    1788 certsrv
    5136 Microsoft.Exchange.EdgeSyncSvc
    1348 OWSTIMER
    6512 MSExchangeTransportLogSearch
    404 avgcsrva
    5936 msexchangerepl
    4 System
    2564 sqlservr
    2168 exfba
    0 Idle


    Also an critical event log below
    Watson report about to be sent for process id: 6584, with parameters: E12, c-RTL-AMD64, 14.01.0438.000, edgetransport, M.E.Extensibility.Internal, M.E.D.M.I.MimeCacheMap.Load, M.E.D.Mime.MimeException, 8c10, 14.01.0438.000.
    ErrorReportingEnabled: False

    Also this event log
    The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.

    The problem appears to be at the Microsoft Exchange Transport and have so far after reading numerous other posts with similar problems restarted the Exchange Services, but the Microsoft Exchange Transport was unable to stop until I uninstalled Backup Exec and AVG. I then reinstalled AVG as suggested by AVG and all Exchange Services appeared to be running fine and I was able to telnet but still no email, this lasted all of 15 minutes then everything went back to being unable to telnet and problems with the MET.

    I've tried to put the transport services back to defaults using X:\Program Files\Microsoft\Exchange
    Server\Scripts\ReinstallDefaultTransportAgents.ps1 " script from the Management Shell, and this had no affect

    Any help would be appreciated.

  • #2
    Re: SBS 2011 Exchange Stopped Processing Email Microsoft Exchange Transport Errors

    How much resources are free on the server (CPU, RAM, Disk, network)?
    Regards,
    Jeremy

    Network Consultant/Engineer
    Baltimore - Washington area and beyond
    www.gma-cpa.com

    Comment


    • #3
      Re: SBS 2011 Exchange Stopped Processing Email Microsoft Exchange Transport Errors

      Hi Jeremy

      Thank you for your reply, I don't think its a performance issue as there are plenty of resources and HDD disk space, the network cards are 1gig but as required by SBS one is disabled.

      Comment


      • #4
        Re: SBS 2011 Exchange Stopped Processing Email Microsoft Exchange Transport Errors

        OK, have you run the BPA for SBS 2011?
        Are you up-to-date with patches and service packs for SBS, Windows, and Exchange?
        Regards,
        Jeremy

        Network Consultant/Engineer
        Baltimore - Washington area and beyond
        www.gma-cpa.com

        Comment


        • #5
          Re: SBS 2011 Exchange Stopped Processing Email Microsoft Exchange Transport Errors

          Hi

          I found the problem, well I knew what the problem was as it was the Microsoft Exchange Transport. But I have managed to fix it, here's what I did in case anyone else has the same problem.

          I firstly uninstalled AVG again and rebooted, I needed to reboot after uninstall because AVG would not allow the MET to be restarted or stopped. Once AVG was off I stopped all the Exchange Services and followed the advice below.

          It may be possible that the Queue & IPFilter folder under Data folder was corrupt.

          After renaming the Data folder on the HUB server. Then restart the Transport service.

          It will fix the problem.

          It worked perfectly and I now have mail flowing again.

          Basically renaming the data folder forced the exchange to create a new one and repair the ipfilter & Queue.

          One side effect is that the built in spam filtration in exchange has stopped working, which is not much of a problem to me as I found it to be useless and we now use a proxy. I can work on that later.


          Thank you for your help Jeremy and I hope this helps anyone else with similar problem
          Last edited by meresolveit; 23rd July 2013, 21:16.

          Comment


          • #6
            Re: SBS 2011 Exchange Stopped Processing Email Microsoft Exchange Transport Errors

            Thanks for posting back your solution!
            I'm sure others will find it helpful.
            Regards,
            Jeremy

            Network Consultant/Engineer
            Baltimore - Washington area and beyond
            www.gma-cpa.com

            Comment

            Working...
            X