none
SBS2008, Exchange Transport Service Failed and won't STOP to RESTART

    Question

  • Hi

    Internal emails are fine.

    Fix my network said all OK, BPA reports all OK but getting Exchnage Transport Stopped error in event viewer

    Tried to stop and restart te service but service keeps reporting STOPPING...

    Next move anybody without a reboot?

    Thanks

    Daren

    Tuesday, October 04, 2011 2:00 PM

Answers

  • It generally happens when the queue has gone bad.

    Try renaming the queue folder under C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue folder [ex2007]

    Restart transport service

    If this work then you can manually run a repair on queue database.

    Tuesday, October 04, 2011 4:01 PM
  • Hi Daren,

     

    Since you have noticed the error message in the application logging file, could you please paste the error event you found to get further analysis?

     

    I suggest that you could look into the message tracking logging file to see whether there are many large emails in the queue. And how about the CPU status, nearly 100% usage?

     

    Of course, the issue could be transport database corruption. Just like the Jkazama mentioned.

     

    Regards,

    James
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, October 06, 2011 12:45 AM

All replies

  • It generally happens when the queue has gone bad.

    Try renaming the queue folder under C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue folder [ex2007]

    Restart transport service

    If this work then you can manually run a repair on queue database.

    Tuesday, October 04, 2011 4:01 PM
  • Hi Daren,

     

    Since you have noticed the error message in the application logging file, could you please paste the error event you found to get further analysis?

     

    I suggest that you could look into the message tracking logging file to see whether there are many large emails in the queue. And how about the CPU status, nearly 100% usage?

     

    Of course, the issue could be transport database corruption. Just like the Jkazama mentioned.

     

    Regards,

    James
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, October 06, 2011 12:45 AM