Proposed Exchange 2007 Transport service won't stay started.

  • Mittwoch, 13. Juni 2007 17:01
     
     
    I just updated my system this morning with the latest updates from MS and now the Microsoft Exchange Transport service (new in 2007) won't stay started. When I attempt to start the service, I receive the following error:

    The Microsoft Exchange Transpoft service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.

    I've restarted the server and all exchange services several times with no results. Because this service is not running, users cannot send or receive mail.

    HELP!

Alle Antworten

  • Samstag, 16. Juni 2007 15:00
     
     
    Anything in your event logs?   Do you have at least 4GB of free disk space on the disk that holds the hub transport database?
  • Montag, 18. Juni 2007 12:11
     
     

    try stopping the exchange spam service first, then starting it. (It will start under a domain admin account but not work). Then start the spam service. (Close all monitoring/AV first if that doesn't work)

     

     

  • Montag, 18. Juni 2007 14:56
     
     

    Yep,,, we have had this similar error ...until the DNS was corrected.

    If you have couple of DNS servers ...try pointing to a different one.

     

    On all DNS server except 1 ...turn off Forwarding...and recusion.

    On that DNS server have your Forwarder point the to the ISP's DNS .

    All internal DC 's DNS point to the 1 DC name server.

     

    Run the DCDiag /checkdns

    and DCDiag /sBig Smileomain_servername /dnsAll tests.

     

    Then your Exchange service should keep working. Basically had to get the DNS right..then everything just flows.

     

    Cheers

     

    JB

  • Montag, 23. Juli 2007 16:22
     
     

    Another solution that worked in my particular instance (new Exchange 2007 install on Windows 2003 DC)...

     

    In regedit, right-click on key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" and go to the Security tab. Give NT AUTHORITY\NetworkService permission to Read that key.

     

    The particular problem was that, as NetworkService, the Transport Service could not get the computer name, as evidenced by looking in the Application Events and finding "Event ID 4999" from "MSExchange Common" indicating the error "M.E.N.ComputerInformation.GetComputerName, System.UnauthorizedAccessException."

  • Mittwoch, 15. August 2007 16:07
     
     

    In my case (Exchange 2007 install on Windows 2003 DC) transition from Exchange 2000

     

    I add READ to EVERYONE group in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

     

  • Mittwoch, 20. Februar 2008 19:55
     
     

     

    Hello, Same Problem occur that today in here. I Also try before everything says at this forum, unfortunately I have still unsolved problem.

     

    Now is i downloading Exchange 2007 SP1  then I'll apply that on server, may be that run.

  • Dienstag, 4. März 2008 22:48
     
     
    i have some problem,
    any one got it to work?
  • Donnerstag, 27. März 2008 18:53
     
     
    i thought i post the answer just in case some else comes across this

    Change the Exchange Transport service to run as the local system account, under the logon tab,
    i used my admin account but then again i am running on a test server
  • Freitag, 5. März 2010 13:35
     
     Vorgeschlagene Antwort
    Though this post is very old, but it should reach its Answered stage.
    I have one very pity solution which actually worked for me. I was also having the same problem (Exchange Transport Service) won't stay started, it would STOP after very few minutes.

    I did nothing but only renamed the 'Queue' folder and then started the service again. This not only created a new folder with same name (Queue) but also started the service, after which it did not STOP.

    Location of Queue Folder:
     
    C:\Program Files\Microsoft\Exchange Server\TransportRoles\data
    • Als Antwort vorgeschlagen Jeff Kendrick Montag, 11. Juli 2011 12:15
    •  
  • Dienstag, 9. März 2010 19:37
     
     
    I think It is a back pressure issue and It happend to me because our users send attachment with a large size

    http://technet.microsoft.com/en-us/library/bb201658(EXCHG.80).aspx

    Hope this help
    Regards A.Karam MCSE Messaging
  • Mittwoch, 19. Mai 2010 09:40
     
     Vorgeschlagene Antwort

    First we need to disable IP chimeny with below command.

    netsh int tcp set global chimney=disabled

    check the disk space for transport dumpster on HUB server it sud more then 4 Gb.

    Then restart the HUB server.

    • Als Antwort vorgeschlagen Dinesh111 Mittwoch, 19. Mai 2010 09:40
    •  
  • Donnerstag, 20. Mai 2010 11:35
     
     Vorgeschlagene Antwort

    Hello,

     

    Please try to Rename the complete DATA folder on HUB server.

     

    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.


    MicroSoft Exchange Admin. & Connector EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT
    • Als Antwort vorgeschlagen PKT_ Donnerstag, 20. Mai 2010 11:35
    •  
  • Dienstag, 13. Juli 2010 14:34
     
     

    I know this is a dead post it seems, but in case some body does check this, I am currently having the same problem.  I have tried everything in this forum and nothing is working.  My users can "connect" to exchange now, and send mail - but not receive mail.  The person they send mail too also does not receive the mail.  No error messages come back or anything...

     

    I have renamed the QUEUE folder as well as the complete DATA folder.  Transport service will start only for less than a min. and then auto stop.  PLEASE HELP! I contacted Microsoft and worked with an engineer for over 6 hours on it, and they still couldn't fix it.  They told me to restore the server.  I want to avoid this if at all possible.

     

    THANKS!

  • Mittwoch, 4. August 2010 20:43
     
     

    I have the same problem. I have tried everinthing in this fórum and nothing working. Any Idea?

     

    Thanks!

  • Freitag, 6. August 2010 13:57
     
     

    Hello BandeRJ,

    If you followed the Step provided by me (PKT_), it should start the Transport SERVICE & and even after following the Steps issue is not resolved then please Paste the EVent ID which you are getting so i can provide you the solution. for example 16023, 485, 7001, 7002 or 7009 etc.


    EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT
  • Mittwoch, 18. August 2010 13:43
     
     Vorgeschlagene Antwort
    To resolve this issue, follow these steps:

    1. Open the ADSIEdit tool, and connect to the configuration context.
    Locate the Exchange Administrative Group object.
    2. Open Properties for the Exchange Routing Group object, and copy the distinguishedName value.
    3. Locate the Servers object in Exchange Administrative Group.
    4. Select Properties for the Exchange 2007 Hub server, and find the msExchHomeRoutingGroup attribute
    5. Open the msExchHomeRoutingGroup attribute, and enter the distinguishedName value that you copied in step 3 for the Exchange 2007 Routing Group.
    6. Verify that the Exchange 2007 server is visible in the Exchange Routing Group in Exchange System Manager.
    7. Restart the Microsoft Exchange Transport service on the Exchange 2007 Hub server.
    Dinesh
    • Als Antwort vorgeschlagen Dinesh111 Mittwoch, 18. August 2010 13:43
    •  
  • Dienstag, 7. Dezember 2010 22:57
     
     

    The solution: Enable IPv6 on your computer if it is disabled.

    Transport service depends on "msexchangeadtopologyservice.exe" which does not work properly without IPv6 enabled.

  • Samstag, 11. Dezember 2010 18:05
     
     

    try stopping the exchange spam service first, then starting it. (It will start under a domain admin account but not work). Then start the spam service. (Close all monitoring/AV first if that doesn't work)

     

     

     

    ________________________

     

    For further information please visit our website |tu van du hoc |hoc bong du hoc |du hoc singapore |cửa chống cháy |du hoc
  • Sonntag, 12. Dezember 2010 05:49
     
     

    any update ?

     


    Dinesh S.
  • Mittwoch, 22. Dezember 2010 08:24
     
     Vorgeschlagene Antwort

    Hi,

     

    we had a same problem...

    Thank you so much for your setps...it work for me.

     

    great job...friend...

     

    Vijay

    • Als Antwort vorgeschlagen Dinesh111 Mittwoch, 22. Dezember 2010 19:01
    •  
  • Montag, 3. Januar 2011 11:07
     
     

    I just wanted to add that we had this problem as well, and it was DNS-related.  

     

    A server had been removed from the production environment, and the Exchange server was using this as it's primary DNS.   Once we fixed the DNS, Exchange started normally.  

  • Montag, 3. Januar 2011 17:13
     
     

    ________

     

     

    Hello,

     

    Please try to Rename the complete DATA folder on HUB server.

     

    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.


    MicroSoft Exchange Admin. & Connector EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT

    Hi ,thanks for sharing a lot!

     

     

     

     

     

    ________________________

    du hoc |tu van du hoc | hoc bong du hoc | du hoc singapore

  • Montag, 11. Juli 2011 20:11
     
     
    That has worked. Thank you for that solution! This was quite frustrating trying to figure out why the service kept stopping after I would start it.
  • Freitag, 9. September 2011 04:05
     
     

    This works

     

    Nick Shmakov

    RESQ PTY LTD


    Regards,
  • Donnerstag, 22. September 2011 03:59
     
     

    And this isn't spam? 

    What the hell is a Spam anyways.  A blast message from an employee to all other employees informing them of details and employee should know, if they read all of the fine print..............

    if there were any............

    just an informative email,  like   (i don't know a Black Ice file)))))))))))))))))))))))0

    SHUT UP  that is my favorite scent on the Christmas Tree..............shut up.................

    What, Bouquet used to be my favorit...................oh my GAWD!!!!!!!!!!

    What a pine-ing is all we can do.....................

    DonEAda phish!!!!!!

  • Donnerstag, 22. September 2011 04:00
     
     

    And this isn't spam? 

    What the hell is a Spam anyways.  A blast message from an employee to all other employees informing them of details and employee should know, if they read all of the fine print..............

    if there were any............

    just an informative email,  like   (i don't know a Black Ice file)))))))))))))))))))))))0

    SHUT UP  that is my favorite scent on the Christmas Tree..............shut up.................

    What, Bouquet used to be my favorit...................oh my GAWD!!!!!!!!!!

    What a pine-ing is all we can do.....................

    DonEAda phish!!!!!!


    see above dumbass computer
  • Freitag, 30. Dezember 2011 13:21
     
     
  • Samstag, 2. Juni 2012 17:36
     
     

    Many Thanks Sanaullah ..  :)  

  • Montag, 25. Februar 2013 09:07
     
     
    Marvellous. Thanks Sanaullah