7,925 questions
Probably cant start the service if it cant write to the security event log.
Exchange 2016 Transport Service failed to start
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 87%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Sridhar
1
Reputation point
Exchange 2016 server transport service failed to start. Exhausted with all the troubleshooting steps
We have noticed that security event log was not accessible, so after we fixed the event log access issue by following the article below, transport server was started surprisingly
Would like to understand relation between exchange transport service and security event log access, appreciate if anyone can share some input.
Exchange | Exchange Server | Management
{count} votes
-
KyleXu-MSFT 26,396 Reputation points2022-10-05T07:22:02.227+00:00 @Sridhar
I am writing here to confirm with you any update about this thread now.
If the suggestion below helps, please feel free to accept it as an answer to help more people.
Sign in to comment
2 answers
Sort by: Most helpful
-
Andy David - MVP 157.9K Reputation points MVP Volunteer Moderator2022-09-30T11:46:19.837+00:00 -
KyleXu-MSFT 26,396 Reputation points
2022-10-03T02:21:42.653+00:00 The security log records the Exchange and health mailbox activity. I guess the write limitation on system/health mailbox caused the Exchange Transport Service cannot be started.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.