Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Exchange 2010 EdgeTransport.exe.config fail

Answered Exchange 2010 EdgeTransport.exe.config fail

  • Wednesday, January 09, 2013 5:01 AM
     
     
    Sign In to Vote
    0

    I'm trying to address the Store Driver issue listed in this Exchange Team blog. I changed the config file by adding 

    <add key=”RecipientThreadLimit” value=”2”/>
    <add key=”MaxMailboxDeliveryPerMdbConnections” value=”3”/>

    As the first two lines under <appSettings>. When I restarted the Transport service, it hung at "Starting" and I saw the following warning in the event log:

    Log Name:
    Application
    Source: MSExchangeTransport
    Date: 1/8/2013 9:19:07 PM
    Event ID: 12028
    Task Category: TransportService
    Level: Warning
    Keywords: Classic
    User: N/A
    Computer: cashub1.domain.com
    Description:
    The process with process ID 6248 is holding the performance counter failure dsns total Value=4160 SpinLock=0 Lifetime=Type: 1 ProcessId: 6248 StartupTime: 130019408674218750 from instance _total(CFBEE918) RefCount=0 SpinLock=0 Offset=32 and category MSExchangeTransport DSN while running processes are: Processes running are:
    ...list of processes

    I restored the backup of the config file, killed the hung service and started it again. This time it went fine, but I'm concerned about our queue growth. 

    So, what gives? Why did the service hang?

    Thanks.



    • Edited by WinadminSM Wednesday, January 09, 2013 5:02 AM
    • Edited by WinadminSM Wednesday, January 09, 2013 5:02 AM
    •  
     

All Replies

  • Thursday, January 10, 2013 3:35 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hello,

    What is the version of your Exchange Server?

    Since the event warning not show the reason why it cannot start, I suggest you follow this way to troubleshoot it:

    Go to increase event log level for Transport service.

    change the configure file and restart the service to have a try.

    Thanks,

    Evan Liu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tnmff@microsoft.com

    Evan Liu
    TechNet Community Support

     
  • Thursday, January 10, 2013 2:48 PM
     
     Answered
    Sign In to Vote
    0

    We ended up calling Microsoft support. They noted that there is a space between the new value and the backslash (e.g. ="2"/>). Removing the space apparently resolved the service-starting issue, but not the queue-filling issue we were seeing.

    We removed patches that were installed right before the problem started. A couple of reboots later, it looks like mail is flowing smoother and the boxes (RDP) performance is certainly faster.


    • Marked As Answer by WinadminSM Thursday, January 10, 2013 2:48 PM
    • Edited by WinadminSM Thursday, January 10, 2013 2:49 PM
    •