locked
Faulting application edgetransport.exe, version 8.1.375.2 RRS feed

  • Question

  • Hi ,

    i have Exchage 2007 Version 8.1 (Build 240.6) in windows 2008 server (sp2)

    i got below error...




    Log: Application
    Type: Error
    Event: 1000
    Agent Time: 19:17:49  6-Jul-09
    Event Time: 07:17:49  6-Jul-09 UTC
    Source: Application Error
    Category: (100)
    Username: N/A
    Computer: KALI.avonside.local
    Description: Faulting application edgetransport.exe, version 8.1.375.2, time stamp 0x49f8e8a8, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000374, fault offset 0x00000000000aef37, process id 0x2628, application start time 0x01c9fe09d5384b50.





    Any help would be appreciated,

    Thanks in advance

    GJ

    Monday, July 6, 2009 2:41 PM

Answers

  • Check info:

    1.      Please describe the exchange topology

    2.      Does the error 1000 occur repeatedly?

    3.      Do you notice mail flow issue or any other issue in the organization?

    4.      Which exchange server shows error 1000, Hub or Edge? What’s the status of the “Microsoft Exchange Transport” service on the problematic server?

    5.      If the “Microsoft Exchange Transport” service is started normally, please schedule a time to restart the “Microsoft Exchange Transport” service, and monitor the event log, see if there’s any error event in the application log

    6.      Is there any error during the problematic exchange server’s installation? Please check the installation log on that server?

    7.      Is there any 3rd party software installed on the problematic exchange server?

    8.      Please run ExBPA on the exchange servers for a health check

    • Marked as answer by Alan.Gim Monday, August 10, 2009 2:21 AM
    Tuesday, July 7, 2009 6:36 AM
  • Hi,

    we also have an Exchange 2007 RU8 on Windows Server 2008 Standard Ed with SP2.

    Today we experienced the same problem on 3 server (all the server hosting only the HUB role).

    We took a edgetransport.exe process dump and submitted it to MS, anyway at the moment we solved the problem by disabling both the Routing and the SMTP agent of Exclaimer Mail Utilities (installed on the HUB servers).

    Hope this could help you, I'll update about MS dump analysis.

    Bye
    Simone
    • Marked as answer by Alan.Gim Monday, August 10, 2009 2:21 AM
    Tuesday, July 7, 2009 5:40 PM

All replies

  • Check info:

    1.      Please describe the exchange topology

    2.      Does the error 1000 occur repeatedly?

    3.      Do you notice mail flow issue or any other issue in the organization?

    4.      Which exchange server shows error 1000, Hub or Edge? What’s the status of the “Microsoft Exchange Transport” service on the problematic server?

    5.      If the “Microsoft Exchange Transport” service is started normally, please schedule a time to restart the “Microsoft Exchange Transport” service, and monitor the event log, see if there’s any error event in the application log

    6.      Is there any error during the problematic exchange server’s installation? Please check the installation log on that server?

    7.      Is there any 3rd party software installed on the problematic exchange server?

    8.      Please run ExBPA on the exchange servers for a health check

    • Marked as answer by Alan.Gim Monday, August 10, 2009 2:21 AM
    Tuesday, July 7, 2009 6:36 AM
  • Hi,

    we also have an Exchange 2007 RU8 on Windows Server 2008 Standard Ed with SP2.

    Today we experienced the same problem on 3 server (all the server hosting only the HUB role).

    We took a edgetransport.exe process dump and submitted it to MS, anyway at the moment we solved the problem by disabling both the Routing and the SMTP agent of Exclaimer Mail Utilities (installed on the HUB servers).

    Hope this could help you, I'll update about MS dump analysis.

    Bye
    Simone
    • Marked as answer by Alan.Gim Monday, August 10, 2009 2:21 AM
    Tuesday, July 7, 2009 5:40 PM
  • How's the issue currenlty? any update?
    Monday, July 13, 2009 12:58 AM
  • Hi,

    I think we've definitively solved the issue.

    It was caused by Exclaimer Mail Utilities that was unable to manage some "malformed" HTML body generated on some messages processed by a custom transport rule. This rule has been implemented to split the messages sent both to internal and external recipient to avoid the disclaimer for internal ones.

    Exclaimer has implemented a new release of Mail Utilities (4.67.1473.902 x64, actually in beta) that it seems to work fine.

    Bye
    Simone
    Friday, September 18, 2009 9:41 AM